I have a module that has worked fine for over a year - built with Storyline 2. Today it dies on startup. Tried to fix it in Storyline 360 - it can't get past the first slide. (Wheel of death!) Removed first slide - can't get past the 2nd slide (new 1st slide). HELP! I really don't want to have to re-build every slide all over again.
I managed to resolve my issue. It seems that EVERY text item on the slide was corrupted during conversion (Storyline 2 > Storyline 360). NOTHING I did to the text objects fixed anything. Creating new text boxes with the same font and same content did fix each in turn. The bad news is that it took most of the day to find and fix this. The good news is that only one of 26 slides was corrupted - so once that slide was fixed, the whole module worked.
Oh no, Dave! I'm sorry to be seeing this post only now. 😕
Identifying corruption is never easy or fun, but I'm happy you were able to find it and fix up these slides. Now, let's look at what happened so we can prevent this in the future!
It sounds like you upgraded Storyline 2 files into Storyline 360, and everything appeared normal until you went to preview?
Do you know what update of Storyline 2 these were created or last opened with?
If it was a single slide, was there anything special about that slide (animation, images, audio, etc.) that stands out?
We have some general best practices outlined here to help prevent corruption, and I also always recommend trying to import a .story file into a new version of the file to fix up any odd issues.
Let me know if any of that sounds like a piece you may have hit, or if you need additional help. We're always happy to look at and test your .story file too. You can share here or send along to our Support Engineers.
2 Replies
I managed to resolve my issue. It seems that EVERY text item on the slide was corrupted during conversion (Storyline 2 > Storyline 360). NOTHING I did to the text objects fixed anything. Creating new text boxes with the same font and same content did fix each in turn. The bad news is that it took most of the day to find and fix this. The good news is that only one of 26 slides was corrupted - so once that slide was fixed, the whole module worked.
Oh no, Dave! I'm sorry to be seeing this post only now. 😕
Identifying corruption is never easy or fun, but I'm happy you were able to find it and fix up these slides. Now, let's look at what happened so we can prevent this in the future!
We have some general best practices outlined here to help prevent corruption, and I also always recommend trying to import a .story file into a new version of the file to fix up any odd issues.
Let me know if any of that sounds like a piece you may have hit, or if you need additional help. We're always happy to look at and test your .story file too. You can share here or send along to our Support Engineers.
This discussion is closed. You can start a new discussion or contact Articulate Support.