13 Replies
Leslie McKerchie

Hi Sandeep,

Thanks for reaching out! We simplified the published output in Storyline 360 builds 3.35.20995.0 and later. When you publish HTML5-only or Flash-only courses, Storyline no longer generates these files in your published output:

• index_lms_flash.html
• index_lms_html5.html
• story_flash.html
• story_html5.html

You'll only see the files above when you publish courses with both HTML5 and Flash formats.

Sandeep B

Hey Leslie,

thank you for quick revert and confirmation.

I published one course before '3.35.20995.0 ' update and it had these additional files, hence got confused with different outputs.

I noticed one issue though: When course opened in internet Explorer 11, some image files  (inside mobile folder of the published output) do not load.  I tried on Chrome and it loads without any issue. 

Is this known issue?

 

Doug Nelson

This change affects how some users are integrating custom xAPI calls into Storyline using Javascript, using xAPI.ly or similar approaches. In that workflow, a line of script is added to the story_html5.html file to call an external script. This is done after publishing the Tin Can package. 

I just did a quick test and found that adding the required line of script to the story.html file (instead of the now-missing story_html5.html file) seems to accomplish the same objective, but I haven't tested this thoroughly. 

Attaching a screenshot showing the script call added to the story.html file. 

Stacy Parker

Lauren,

It appears that there are several organizations that use Storyline 360 here and the "streamlined files" where the HTML5 file removal is breaking our courses. Am I right in understanding this was an intentional change? And what do we do as a permanent solution when it breaks our courses? So far, the only permanent solution I'm seeing is rolling back your update to a previous version of software that does contain these files. Can you point me in the right direction for knowing what to do? 

Joe Dey

This change is causing a real headache and a disproportional amount of work.  I have literally hundreds of full courses and smaller applets I designed, with a master menu linking to each of them and each linked from within each other.  Now that the html5.html is gone all those links are broken each time I update or make changes to any one of these courses. Absolute nightmare!!!

Not a happy Teddy...

Leslie McKerchie

Hi Stacy and Joe,

I appreciate both of you taking the time to share your concerns and feedback on our approach to simplifying the published output folder.

We’ve always recommended linking to the story.html file in the published output and if your LMS requires you to identify a file, point to index_lms.html. This allows Storyline to determine what to display.

If you need to roll back to a previous update, that would provide time for you to update your custom solution and continue to publish with HTML5 only. Directions on installing a previous version can be found here.

Tara McLoughlin

I'm with you on this.  Wow - what a nightmare this has become.  We now have to publish with Flash backup just to keep the HTML5 file active so all of our links don't break.  We have SO many documents and courses that link to one specific file.  It will take us forever to fix them. 
Now instead, it's taking us hours to publish files (we don't have an LMS so we're publishing to the web) because of the Flash back up. 
Not a happy camper to say the least! TGIF

Lisa Jones
Leslie McKerchie

We’ve always recommended linking to the story.html file in the published output and if your LMS requires you to identify a file, point to index_lms.html. This allows Storyline to determine what to display.

Same issue with now needing to act with much caution in the future (and being congnizant of which files are in a folder we're replacing),

Just in case you're wondering why some folks might have linked to the story_html5 file directly, the reason was that story.html bugged out in IE11 (content wouldn't load as it was missing a meta tag) and was never fixed. The workaround was to link to story_html5.

It's not ideal for others having this linking issue - but we have to just copy/paste the story.html and rename as story_html5.html. Yep, another step in the process. Yep, have to do it every time, Yep, have to remember to do it. Yep, another workaround to resolve another workaround - but at least it will buy some time until you're able to redirect/relink all your agendas :).

Fiona Williams

Does anyone have this issue when using TinCan Output? There is no index_lms file to link to. Our LMS will automatically choose the html5 file because it is a html5 published output file.

We have now found that any time we update content after this new update, and re-upload to one of our sites, the content no longer plays. there is just a blank white space where the slide should be. I have tried renaming the story.html file, but so far it hasn't fixed the issue. It fixes the problem when we're just creating links, but when you're trying to update content on a website it doesn't seem to fix it.

Inspect element says that there is some kind of error in the bootstrap-min.js file. (Uncaught TypeError "Cannot read property '0' of null" on line 82). I'm not much of a coder, does anyone have any clue what this means?