I publish a number of courses to LMS using articulate storyline. When I click publish, it goes through a process and I get a message that my course was successfully published. I then have the option to save it as a zip file. This is what happens about 98% of the time. However, at random times when I go to publish a course, I do not get the message that the publish was successful and it does not give me the option to save it as a zip file. I attempt to manually zip the output file that articulate creates, but it does not work in the LMS. Why does this happen? Is there something I am not doing?
Hello Ashley, thanks for your reply. We do follow the process described in our reply. The difference is, that my coworker and I do different things. My coworker creates the content on their local machine and the loads it to shared drive for me to download to my machine. I make edits and publish to the LMS. Should we try something different?
And, just to confirm - you download the file to your local drive, and then open from there? Are they zipping it to load to the shared drive, or just loading the .story file? I may try loading a zipped file then when you receive it save it to your local hard drive and fully extract it before opening it in Storyline.
When you're publishing, are you also publishing locally and ensuring the file path and name don't include any special characters and that the file path is well below the 256 character limit as detailed here.
I'd also look at closing down any other programs or applications that could be drawing on the memory while publishing.
I download the .story file to my local drive and then open from there. I will try loading the zip file and see what happens. I have had issues with special characters before and continue to keep an eye out for them.
Thanks Craig - if you'd like us to take a look we're also happy to. You can share the file here with us. Since it's not every file, my guess is it's something file specific - have you tried importing it into a new project and then trying to publish that one?
8 Replies
I would like to also add that the courses I am publishing was created on someone else's computer. - Thanks
Hi Craig,
When you and your coworker were sharing files, were you following along with the guidelines here?
Also, please make sure you're publishing to a local drive.
Hello Ashley, thanks for your reply. We do follow the process described in our reply. The difference is, that my coworker and I do different things. My coworker creates the content on their local machine and the loads it to shared drive for me to download to my machine. I make edits and publish to the LMS. Should we try something different?
Hi Craig,
And, just to confirm - you download the file to your local drive, and then open from there? Are they zipping it to load to the shared drive, or just loading the .story file? I may try loading a zipped file then when you receive it save it to your local hard drive and fully extract it before opening it in Storyline.
When you're publishing, are you also publishing locally and ensuring the file path and name don't include any special characters and that the file path is well below the 256 character limit as detailed here.
I'd also look at closing down any other programs or applications that could be drawing on the memory while publishing.
I download the .story file to my local drive and then open from there. I will try loading the zip file and see what happens. I have had issues with special characters before and continue to keep an eye out for them.
Thanks Craig - if you'd like us to take a look we're also happy to. You can share the file here with us. Since it's not every file, my guess is it's something file specific - have you tried importing it into a new project and then trying to publish that one?
I would love for you to take a look. what is the best way to get it to you?
Hi Craig,
You can attach the .story file here or send it along to us here.
This discussion is closed. You can start a new discussion or contact Articulate Support.