Wheel of death when story.html is unzipped

Nov 10, 2016

Hi everybody, I am running into a big issue and I am wondering if anyone else experienced it before and might have a solution. We created a course for our employees, published for web, everything runs fine. We now want to offer the same course for our external partner. In the past we zipped the published files, made the zip file available for download and the external partner takes it from there. Now just recently it so happens when the external partner unzips the files and double clicks on story.html all that appears is the spinning wheel. The course never loads. On the other hand the story_html5.html file works, but we don't really want them to use it. It doesn't look as crisp, the formatting is slightly off and usually our people take courses of desktops anyways. 

Any idea what we could do to fix the story.html issue?

Thanks!

Alex

9 Replies
Crystal Horn

Hello, Alex!  Your external partner might be bumping into a new Flash Player setting that was implemented with their update 23.  You can read about how it affects local viewing and how to restore that function here.

And to piggy-back on Phil, though not literally, because we are mostly professional, I'd also recommend hosting your content on a web server if it is published for web, and then sending them a link.  Viewing your content locally frequently is hampered by browser security settings.

Thanks for reaching out!

Diane Brochu

Hi there, I'm running into a similar issue. Internally, I publish as a scorm package to our LMS. I've created a couple of eLearning modules for an external client and published them as CD.  When the client goes to open the modules, they get the wheel of death. The same modules published to the LMS work fine. The story module itself isn't huge, it's only 11,600kb. I wouldn't think that was an issue. Any ideas? I can send you the .story file....

 

Leslie McKerchie

Hello Diane,

Thanks for reaching out and letting us know what your client is experiencing. Are you able to replicate this error when you open the file as well?

The recommendation to publish to CD above was because they were viewing the content locally. Do you know how your client is using the module that you are sharing with them? Will they host it in their own LMS or on a web server perhaps?

With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

This discussion is closed. You can start a new discussion or contact Articulate Support.