The team a work with has a question - using Storyline 3.
A learning module needs updating but the source files for the project have been lost in some computer disaster - we've all heard of these situations.
However, we might be able to get the .ZIP from the LMS. If we can, then is it possible to un-zip the folder and import it onto Storyline? So that we don't have to rebuild it all from scratch? Any thoughts?
No sorry Marcus - the published folder doesn't contain a copy of the source.
Any chance someone in the team has a copy in their temp folder?
Check file path “AppData\Roaming\Articulate\Storyline” on your drive where you have installed you Articulate Storyline and there may be a copy with a .tmp file extension...if so copy it and change to .story ...you may be able to recover something
Thank Tom, Where we can we are taking this approach. The most frustrating thing is that once the storyline is published the whole slide becomes an image - insofar as you cannot copy the text. Does anyone know why it publishes like that? I am guessing there is a technical or logical reason for it.
8 Replies
No sorry Marcus - the published folder doesn't contain a copy of the source.
Any chance someone in the team has a copy in their temp folder?
Check file path “AppData\Roaming\Articulate\Storyline” on your drive where you have installed you Articulate Storyline and there may be a copy with a .tmp file extension...if so copy it and change to .story ...you may be able to recover something
Thanks - will try that.
This may help. If you have a published version of the course.
I wrote a post on this a while back. It's not perfect, but it's an easy way to get the course rebuilt (assuming it's not too complex).
Thank Tom, Where we can we are taking this approach. The most frustrating thing is that once the storyline is published the whole slide becomes an image - insofar as you cannot copy the text. Does anyone know why it publishes like that? I am guessing there is a technical or logical reason for it.
Hi Marcus,
The text (and other slide elements) are contained with an SVG upon publishing, and the text isn't selectable in that output.
If you've published with Storyline 3 or Storyline 360 you could use the following method to access the slide text:
Hope that helps!
Hi Ashkley,
Do you have a list of command line calls I can use in Chrome Dev Consle?
Only code I use is ShowDebugInfo();
I was wondering if there are some functions I can use to trouble shoot the user.
Here's another post I did that that shows some tips on how to pull text from screens where the text isn't selectable.
Hi Sungmin,
I don't have any other Dev Console commands documented - that one came from our engineers looking to help with this specific question.
This discussion is closed. You can start a new discussion or contact Articulate Support.