Whilst working on older Articulate project files, we have occasionally encountered issues around file corruption. This is usually a result of updating our Storyline version and opening project files which we created with an older version. What does Articulate do to protect old files and ensure they do not become non-compatible with the latest versions of Storyline?
I'm sorry to hear this! Storyline files should always be saved locally and then backed up to a shared server or network drive once you've closed the file. Typically the default location is within your C drive, and a folder labeled My Articulate Projects.
Storyline also creates a backup or temporary site of files in the event of an autorecovery situation. Those files are stored in this folder: %Appdata%\Articulate\Storyline
They will also be labeled as *.tmp files, but you can change the file extension to *.story and open it within Storyline.
3 Replies
Hello Adam!
I'm sorry to hear this! Storyline files should always be saved locally and then backed up to a shared server or network drive once you've closed the file. Typically the default location is within your C drive, and a folder labeled My Articulate Projects.
Storyline also creates a backup or temporary site of files in the event of an autorecovery situation. Those files are stored in this folder: %Appdata%\Articulate\Storyline
They will also be labeled as *.tmp files, but you can change the file extension to *.story and open it within Storyline.
If you need any other help, please let us know!
Thanks Lauren for your guidance. We will definitely use your suggested approach when saving our Storyline files.
I think our problem was encountered because we were using OneDrive with auto-synching which was causing some files to become corrupted.
Thanks again!
That could do it, Adam. I'm glad to hear that you're on the right track, and I appreciate you sharing an update with us here.