Getting spinning wheel on HTML5 output.

[tharkins52]

We've published many HTML5 (no SWF) courses in the past without any issue, but today when I went to preview a new course on SCORMCloud, all I get is a spinning wheel when trying to view the HTML5 course in IE9. I republished and uploaded the last course we created and it ran fine. I also cleared the Captivate cache and republished, but that didn't work. So it seems like it's the course specifically. I don't use widgets or anything like that and there wasn't anything in the HTML5 tracker. No video and all audio is in MP3 format 96kbps.

I then published the course WITH SWF and HTML5 and uploaded it to SCORMCloud, and the SWF worked in IE9, but the HTML5 is still spinning when I checked in on my iPad.

Anyone have an ideas of what I could try next to salvage the course, or will I have to recreate the course again and hope for the best?

[BDuckWorks · Accepted solution]

It's tedious, but you can avoid rebuilding it from scratch.

You can troubleshoot by feature type:

A) Turn off all the quiz questions, and quiz results; republish, and test.

If it works, you've identified the part of the course needing your attention.

If it doesn't work, you need to turn those features back on, and turn the next block of features off.

Turn off all the learning interaction slides; republish and test.

If it works, you've identified the part of the course needing your attention.

If it doesn't work, you need to turn those features back on, and turn the next block of features off.

Repeat again for Video, animations, etc.

Or, you can troubleshoot by brute force, treating all the slides as equal:

B) Break the whole course into blocks of slides, maybe divide by 5 or 10. A 100 slide course could be tackled in 10 blocks of 10 slides, or 5 blocks of 20 slides. You'll possibly need to publish each block, so deciding for more blocks means more round trips.

Turn off the first block, republish, and test.

If it works, you've identified the part of the course needing your attention.

If it doesn't work, you need to turn that block back on, and turn the next block of slides off.

Turn off the second block, republish, and test.

If it works, you've identified the part of the course needing your attention.

If it doesn't work, you need to turn that block back on, and turn the next block of slides off.

Turn off the first block, republish, and test.... lather, rinse, repeat!

Once you've identified the troublesome block, you need to test for which slide might be the problem.

This type of question is why I tend to build features onto a course rather than working from front to back and completing each slide. As I build features I create versions, publish and test.

I cycle through test environments by testing: locally, to a local DEV webserver, to a PILOT LMS; finally to a PRODUCTION LMS. At each stage I add features and test what was added.

[tharkins52]

I tend to build a course that way too. And the kicker is that this thing worked in HTML5 at one point too, which is why it's frustrating. The bad thing is I'm not sure what additions I made from that point to where I am now, that would have had an impact.

I'll try what you suggested on a duplicate of the cousre and see if I can narrow it down. Worst case scenario is I have to re-build, but that's not an overwhelmingly daunting task. This course is only 20 some slides.

Thanks for the reply BDuckWorks!

[TLCMediaDesign]

I think it always best to launch the developer tools in the browser to see if any errors or warnings are being generated. Post those results if you have any.

[tharkins52]

It was a gummed up slide. I narrowed it down using what BDuckWorks suggested and found it pretty quickly. Great advice.

Thanks again.