End of Flash Support


We have been using Storyline for many years now and while we now publish our content for HTML5, we know we have a whole lot of content published for Flash or Flash with HTML5 fallback.  

We have realised we need to do an audit of our courses to see how each one has been published to see what needs to be republished and are looking for an efficient way of doing this.  

Is there anything in the output files that would help us identify how our courses have been published?



3 Replies
Matthew Bibby

Sure, you can check the files in the published output to determine this.

If it's an older module, and you just have a story.html file (and not a story_html5.html file), then the module was likely published just using Flash.

If you have story.html and story_html5.html or story_flash.html and story_html5.html then you've published to both. If Flash isn't installed, it should play the html5 version. 

If it's a module you published in the last couple of months, and you just have a story.html file, then that is likely HTML5 only (assuming that you aren't publishing just to Flash at this stage!).

This is because recently in SL360, Articulate changed the way things are published so the file is just called story.html if only the HTML5 or Flash output has been viewed. They only append _html5 or _flash to the file name if both options have been selected. 

That being said, it's a good opportunity to test all of your modules in whatever browsers you need to support as there may be other issues that have cropped up as a result of browsers maturing.

Does that help?