I have been asked to make updates to a Storyline online course which was created by someone else. In order to make the requested updates, I need to edit the original .story file and re-upload to ArticulateOnline. Is there a way to determine which .story source file a course is based on using ArticulateOnline?
You won't be able to pull the course from Articulate Online to edit it as once published it's a different file type than .story. Are you able to connect with who originally created the course to find the original .story file? If you have access to the original files, the file names may also be similar which would help you narrow it down.
I know this is an old question, but I have a similar inquiry. I used Storyline 2 to create a course for a client. I first delivered them v01, which they used to publish and we found a bug with the html5 version of the course. I fixed it and sent them v02, which works perfectly for me, but they are seeing the same bug. I am suspicious that they used v01 to publish again. Is there a way to determine the name of the source file (.story) from the published course?
Unfortunately not from the source file, although you can find it if you look at the source code of a published file in the web browser. That'll tell you the product, version and update it was created with.
Within Chrome on a Mac choose View > Developer > Source
On a PC, click the dropdown at the top of Chrome > More Tools > Developer Tools > Elements and you'll use the "head" dropdown to see the version notes.
Thanks for the response. I had seen that. Correct me if I am wrong, but that is the information on the build of Storyline that was used to publish and nothing about the source file itself.
Correct - so if the file wasn't published with the particular version or they were still accessing a version published with an earlier version, that's how you'd know by looking at the source code. If you sent a source file from a particular update and they were still using an older update to view it within Storyline presumably they published it to get it back on their site?
Perhaps I'm misunderstanding what you're looking for...it is Friday after all. :)
6 Replies
Hi Trisha and welcome to Heroes!
You won't be able to pull the course from Articulate Online to edit it as once published it's a different file type than .story. Are you able to connect with who originally created the course to find the original .story file? If you have access to the original files, the file names may also be similar which would help you narrow it down.
I know this is an old question, but I have a similar inquiry. I used Storyline 2 to create a course for a client. I first delivered them v01, which they used to publish and we found a bug with the html5 version of the course. I fixed it and sent them v02, which works perfectly for me, but they are seeing the same bug. I am suspicious that they used v01 to publish again. Is there a way to determine the name of the source file (.story) from the published course?
Hi Ted,
Unfortunately not from the source file, although you can find it if you look at the source code of a published file in the web browser. That'll tell you the product, version and update it was created with.
Within Chrome on a Mac choose View > Developer > Source
On a PC, click the dropdown at the top of Chrome > More Tools > Developer Tools > Elements and you'll use the "head" dropdown to see the version notes.
Thanks for the response. I had seen that. Correct me if I am wrong, but that is the information on the build of Storyline that was used to publish and nothing about the source file itself.
Correct - so if the file wasn't published with the particular version or they were still accessing a version published with an earlier version, that's how you'd know by looking at the source code. If you sent a source file from a particular update and they were still using an older update to view it within Storyline presumably they published it to get it back on their site?
Perhaps I'm misunderstanding what you're looking for...it is Friday after all. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.