CP7 Issues

[nakana75]

I'm working as part of a team where there are multiple people touching the same file on different machines. I mention this as we continue to expeirence issues where revisions were made, then saved, and published.  For example, onscreen buttons at one point are there, then not there.  Or, onscreen buttons work with one test and then they don't work in another test.  I'm not sure what could create this sense of instability we continue to experience.  Any ideas or thoughts as to why revisions seem to not save or functions fail to work in the output randomly?

Thanks for any and all help!!!

[TLCMediaDesign]

You need a version control system, or check the files out in Dreamweaver so everyone knows the file is being edited. Doesn't sound like a CP issue.

[nakana75]

We do have version control in place.  No one works on a file until they received it from another person with a new version number.  We made changes yesterday all of us standing at one computer while one person made the changes.  Saved it as a new version and published it, but only after we validated in preview that buttons functioned and changes were indeed there.  However, today, buttons are not functioning for some reason. 

In terms of changes not saving, I'm curious if it could be a cache issue?

Thank you again!

[TLCMediaDesign]

Have a look at this thread:

http://www.linkedin.com/groups/Using-Captivate-7-in-Corporate-2009048.S.5816195416974184450?qid=a046...

[RodWard]

It could indeed be a cache issue.

To test this theory:

Try clearing the Captivate cache on any computer that will be opening a project file last edited on a different computer.  If you clear the cache before opening the CPTX file then Captivate will totally recreate the cache based on the incoming CPTX file.  If your issue is caused by a mistmatch between the cache and the CPTX then not have a cached version to start with might resolve the issue.

Please let us know the results of your test.