Ghosts in the (Storyline) Shell?
Jun 05, 2019
Hey folks. Long-time listener, first-time caller. Thank you for all your insights and tips along the way.
Has anyone experienced issues with Storyline 360 undoing changes and reverting to older file versions, post-save?
My example: One slide in our module needed changing, so a co-worker took this .story file and - because we have been having problems - deleted all other slides except the one that needed to be modified. She made the changes, gave the new .story file a unique name, and uploaded it to Box, the tool used for storage and sharing by our client.
When a second co-worker downloaded and opened this new file the next day, all of the file's old slides were back in, and none of the fresh edits had been saved. The file name was about the only thing that had been retained.
We're trying to track down ghosts here. Is Box the likely culprit, or has anyone run into instances where Storyline has retained vestiges of old versions?
Thanks. I'll take my question off-air. ;)
Martine
1 Reply
Hi Martine, and happy to have you as a first-time caller!
It's possible that Box is haunting your files if the files are being edited/saved while still on the Box domain. You mentioned downloading them, so that sounds like you're downloading locally and working on it from your local drive? We've seen working off a network/shared/cloud drive cause odd behavior and ultimately leads to file corruption.
I haven't seen other scenarios where Storyline keeps older versions accessible in the file itself. We do keep changes until you "Save and Close" so that an author can use the undo button to revert those.
Let me know if that sheds a light on anything else for you - and happy to keep 👻 hunting with you!
This discussion is closed. You can start a new discussion or contact Articulate Support.