Notification
Newbie
9 posts
Hi,
Whenever I open my project on my other computer the project file does not open. Captivate tries to open the file then says The file is corrupted. Even if I restore the backup file that I automatically make, it still does not work.
However, when I open the file in the exact location that it was built, it opens fine. There seems to be a fixed directory expectation. If I reproduce the exact directory structure on my other computer, then the file will open fine. Thus proving my point of a fixed structure dependency.
Is there a way to use relative paths for the asset references in the project? It appears the program cannot traverse from it’s current location through the folders nested before it. I do not change anything in the root level of the project and inward. It appears if I don’t keep the exact structure leading up to this folder including the drive letter, it claims the project is corrupt.
Please help this is so scary that I may lose all my source work if I don’t have the exact path it expects to see. I can not be victim to this restriction as I change computers often and never mirror my exact directory structure or naming convention for drives.
also one more thing, an aside from this question but oddly related, why is it that this text editor that I’m using to write this message (from within Captivate Community) doesn’t allow you to auto correct your spelling. it highlights the word that has an error but it doesn’t let you right click and choose the correct word. This I imagine would be a fundamental expectations (right click spell correct for red squiggle line on a word to view it’s suggested spelling, or using relative paths for a project and it’s contents) yet both are lacking here.
Thank you for your help!
Best,
Todd
Hi,
Whenever I open my project on my other computer the project file does not open. Captivate tries to open the file then says The file is corrupted. Even if I restore the backup file that I automatically make, it still does not work.
However, when I open the file in the exact location that it was built, it opens fine. There seems to be a fixed directory expectation. If I reproduce the exact directory structure on my other computer, then the file will open fine. Thus proving my point of a fixed structure dependency.
Is there a way to use relative paths for the asset references in the project? It appears the program cannot traverse from it’s current location through the folders nested before it. I do not change anything in the root level of the project and inward. It appears if I don’t keep the exact structure leading up to this folder including the drive letter, it claims the project is corrupt.
Please help this is so scary that I may lose all my source work if I don’t have the exact path it expects to see. I can not be victim to this restriction as I change computers often and never mirror my exact directory structure or naming convention for drives.
also one more thing, an aside from this question but oddly related, why is it that this text editor that I’m using to write this message (from within Captivate Community) doesn’t allow you to auto correct your spelling. it highlights the word that has an error but it doesn’t let you right click and choose the correct word. This I imagine would be a fundamental expectations (right click spell correct for red squiggle line on a word to view it’s suggested spelling, or using relative paths for a project and it’s contents) yet both are lacking here.
Thank you for your help!
Best,
Todd
You must be logged in to post a comment.
- Most Recent
- Most Relevant
What OS?
Its pretty long the question
Thank you! that makes sense. I might not have the same sub version on both computers (2019.XXX). I was referring to cptx files and not the published HTML.
I will try to match up versions or at least update my laptop to see if it will open my desktop project. I hope it works. But it is still strange how i was able to open my project up on my laptop that claimed to be corrupted when I recreated the same path from the desktop.
I will post back if upgrading to the latest build works.
best,
Todd
