The following problem seems true of all projects that are based on a template, but I will give just one example:
I have a template that already has a value filled in in the "Project Title" field of the Publish dialog. (The value is Quiz Template).
When I create a new project based on the template and open the Publish dialog, the project title is initially "Quiz Template". I then change the title to one that is suitable for the actual project and publish it, and save and close the project. However, the next time I reopen the project to republish it, the title has reverted to Quiz Template.
Is there a way to make Captivate store the updated project title so I don't have to remember to correct it every time I republish the project?
I have had exactly the same problem when trying to publish in Captivate 5. When I go to publish, I open the Publish dialog, change the current project title to what I want, publish the project (and the output files correctly show the new title). But when I next come to publish, the title has reverted to its original value.
Unfortunately, no amount of trawling through the menu options appears to provide an answer.
Is there a Captivate developer who can help with this?
I'm having the same problem myself. there has to be a fix for this. i even went in and cleared (deleted all content) from the Adobe Captivate Cached Projects folder located at:
\My Documents\Adobe Captivate Cached Projects
no luck. the original title is there.
hopefully there will be a fix for this.
Just after making my post last year I discovered that
if you save the Captivate project (using Save As to rename it) the
new project name is used in the project title. You might like to try using save as to see if you can change the project title that way.
I've not tried it since, so I can't make any promises...
The important part of the trick is that you must Save As to an entirely different name in an entirely different folder, then publish your project again with the new title.
Then you can Save As the original file name into the original folder (overwriting the original file) and your title should remain as you want.
Saving As in the same folder as the original doesn't usually achieve the change.
Guys I think you try opening the Template by
Open Captivate the File > Open > ( Default Location of Captivate Projects ) My Document> My Adobe Captivate projects > Templates> Project template > Quiz > Project_Name (lets Say you select this)
Then you make some Changes to the Default template then go File > SAVE AS> (It would save the file as a New Template with a.cptl extension) choose the same location and a New_Template_Name .
Now this New Template would be available for your use and you wont have remember the changes everytime.
Thanks and Regards,
Based on the previous discussion in this thread, I've now adopted the strategy that when I create a new project based on a template, my very first action (even before saving the new project for the first time) is to publish the project, setting the required project title. I then save the new project. That ensures that the correct project title will be in place in the Publish dialog window for all subsequent publish actions.
To my knowledge this issue only resulted where projects were being upgraded from Captivate 4, or where templates created in Captivate 4 were upgraded to Captivate 5 and then used to spawn projects.
I've not experienced the issue in any project created from scratch in Captivate 5 or above.
>> I've not experienced the issue in any project created from scratch in Captivate 5 or above.
Well, now you know someone who did. My project was authored in 184.108.40.2064. This might now be quite the latest version, but the gotcha of not being able to rename project titles should never have been an issue with any version of Captivate. I suppose the income we tech writers provide Adobe is low compared with those Photoshop-loving graphic designers. Still, it's not right that we endure hours of drudgery and endless workarounds to produce elearning deliverables, just because the billionnaire developer is unwilling to devote the resources necessary to bring Captivate up to the standard of, say, InDesign. This is what happens when one developer buys up the competition. (I know there are some very fine people working at Adobe helping people like me, some of them right here on this forum. My frustrated words are not aimed at them. Quite the contrary, they are all that stand between us users and a black hole of bugs and "undocumented issues.".)
I fully agree. Even at corporate level this is not cheap software.
This particular issue has been bugging me for a long time [since day 1 of using Captivate some 2 years ago] so this discussion has really helped me a lot.
We bought, installed and have been trained using 5.02.630 having had no previous knowledge or experience of Captivate.
We are creating simple in-company e-learning modules, and because of the low level of experience, minor changes have had to be made to modules and republished. This includes language variations where the only change may be such as Project Title_en; Project Title_de etc.
This has proved risky and even embarrassing before we discovered this issue, which itself became an issue as we struggled to find the right folder / files to upload to our portal.
It has also taken sometimes as long to republish as to correct an error or omission.
What also irritates me is that there are actually no help files. In my opinion, basic issues in the use of software should not be down to a benevolent community, and having to trawl through a series of answers to a search.
But at least this one is solved.
Correction - not solved - it's a workround to a very annoying problem within an expensive piece of software.
Adobe obviously make too much out of their customers to want to make things right for customers!
I had the same issue with the Project Title not saving when changed in Captivate 5.5. Using Save As did not make any difference. I was able to work around it though.
I renamed the .cptx file (filenameFIXED.cptx or something. ) When I opened that file the Project Title was blank, and the new Project Title saved just fine. I am not sure what else disappeared with the little work around, but since I had tried the "correct" method several times with no joy, I thought I'd put this up here so the next person doesn't have to face the same frustration.
Dear Adobe, $1000 for a suite upgrade that is this buggy? WTH?
Actually upgrading to 5.5 resulted in good news for us with regard to this particular issue. I can now freely change the Project Title as many times as I choose and the last Title is always remembered. In testing mode this has finally eliminated so much frustration.
[ In case it matters to anyone it is version 220.127.116.117 ]
I was hopeful when I saw that this issue had an answer, but soon became disappointed when it was clearly a workaround. I wonder how much time we all have wated retyping the Project Title and then, subsequenlty, with the workaround. I guess it's not going to be fixed since 5.5 and now 6 are out.
If there was no patch issued for this Cp5 issue during the reign of Cp 5.5 then there's no way you'll get a fix for this after Cp6 has been released. Sorry. Adobe's priorities will have moved on now.
But in any case, I heartily recommend you consider now pushing for an upgrade to Cp6 as this version has so many extra features and is the first Cp version to really support HTML5 in any serious manner.
Yes, you are right on both accounts. I think there will be a need for CP6 here very soon. I am still a little bitter about our upgrade from CP4 to CP5, though. We were told that there would not be another release of CP for a while when we purchased the TechComm suite last year. I believe it was 32 days later that CP 5.5 came out. Adobe would not upgrade us for free. I tried and tried. Nope, it was outside of the 30 day window.