Was working in Storyline 2 when some of my slides suddenly seemed to lose their objects and slide master contents. Since I had a recently saved copy, I tried to save to see if it was just an issue displaying the objects. I got the attached "Could not save" error message saying that Articulate Storyline "Could not find a part of the path". The only way to resolve it was to close, losing my most recent work, and reopen. The reopened file seems fine.
Has anybody seen this or have any idea what might cause it? It's not at all pleasant.
Hi, Debby -- So sorry to hear of your troubles! Please see this information on Unexpected or Erratic Behavior and run through the repair steps listed in #2 and let us know if you're all set or if issues persist.
Christie,
Thank you for the fast reply.
I work on my project from two separate computers and am careful to keep copies of all the files, images, videos, etc. on both local drives. Would working in this manner be a problem with the internal/temporary file structure used by Storyline?
Debby
Hi, Debby -- Typically, we recommend for best results that you work on your local hard drive, as explained below:
Always save and publish to your local hard drive (typically your C: drive). Working on a network drive or an external (USB) drive can cause erratic behavior due to latency, such as file corruption, an inability to save changes, and loss of resources.
If you need to place a copy of your project on a network drive or a USB drive for backup or versioning purposes, it's fine to do that after you've closed Storyline. Avoid reopening the project again until you've copied it back to your local hard drive.
Similarly, hosting published output on a network drive isn't supported. Instead, place your content in the location for which it was published. For example, if you published for web, upload your content to a web server; if you published for LMS, upload your content to an LMS, etc.
Use File paths and Naming Conventions That Are Safe for Windows
Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows. (Publishing adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)
Avoid using special characters, accents, or symbols in your file paths and file names. Learn more about naming conventions in this Microsoft article.
3 Replies
Hi, Debby -- So sorry to hear of your troubles! Please see this information on Unexpected or Erratic Behavior and run through the repair steps listed in #2 and let us know if you're all set or if issues persist.
Christie,
Thank you for the fast reply.
I work on my project from two separate computers and am careful to keep copies of all the files, images, videos, etc. on both local drives. Would working in this manner be a problem with the internal/temporary file structure used by Storyline?
Debby
Hi, Debby -- Typically, we recommend for best results that you work on your local hard drive, as explained below:
Always save and publish to your local hard drive (typically your C: drive). Working on a network drive or an external (USB) drive can cause erratic behavior due to latency, such as file corruption, an inability to save changes, and loss of resources.
If you need to place a copy of your project on a network drive or a USB drive for backup or versioning purposes, it's fine to do that after you've closed Storyline. Avoid reopening the project again until you've copied it back to your local hard drive.
Similarly, hosting published output on a network drive isn't supported. Instead, place your content in the location for which it was published. For example, if you published for web, upload your content to a web server; if you published for LMS, upload your content to an LMS, etc.
Use File paths and Naming Conventions That Are Safe for Windows
Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows. (Publishing adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)
Avoid using special characters, accents, or symbols in your file paths and file names. Learn more about naming conventions in this Microsoft article.
This discussion is closed. You can start a new discussion or contact Articulate Support.