I updated to the latest version of 360 yesterday. When I published with the "Web" option. I noticed that there's no more story_html5.html. It this correct?
Currently, when I post my courses to our LMS. I am telling to run the story_html5.html file of the published course.
As we continue to prepare for the sunsetting of flash, published Storyline outputs that are html5 only will now only have the story.html file. If a course is published using the HTML5 with Flash fallback option, a _html5 and _flash file will be included in the published output.
Please let us know if you have any questions! We are happy to help!
Unfortunately, when I try to link custom JavaScript to the story.html file only (in order to allow xAPI statements to report to our LRS), it no longer works. It did work with the story_html5 file. This is a significant concern as our LRS *is* our way of tracking learner activity data. We'd like to publish html5-only, but will continue to publish with the fallback in order to avoid this issue. I look forward to hearing updates!
Thank you for the info you provided, I have a couple add on question for you regarding this:
Will the html5.html file still be included when published for HTML5 only SCORM output?
Is this change happening or has happened with the other Articulate 360 products as well? For example: Articulate Presenter 360 and Articulate Quizmaker 360.
If you’re publishing for Web or LMS, you may not see a story_html5.html file as 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.
In regards to Studio 360, each published output will still include the _hmtl5 file.
Please let us know if you have any additional questions!
Just a quick comment/question: In the past we pointed to the story_html5.html-file to launch the course. If I now make an update, publish to web again and replace the old files with the new output links to the story_html5.html are not working anymore since there is none. That creates a problem. Is the easy workaround just to rename (or make a copy and rename) the new story.html file to story_html5.html and I am good to go? Or am I missing something and run into an error or functionality issues later on? First testing renaming the file seems to work just fine.
I pointed my LMS to launch the story.html to keep the integrity of the file. Also, once you set it, you don't have to worried about renaming the file every time you publish the course again.
8 Replies
Hi Ted,
Happy to help dive in here!
As we continue to prepare for the sunsetting of flash, published Storyline outputs that are html5 only will now only have the story.html file. If a course is published using the HTML5 with Flash fallback option, a _html5 and _flash file will be included in the published output.
Please let us know if you have any questions! We are happy to help!
Thanks for clarifying.
Unfortunately, when I try to link custom JavaScript to the story.html file only (in order to allow xAPI statements to report to our LRS), it no longer works. It did work with the story_html5 file. This is a significant concern as our LRS *is* our way of tracking learner activity data. We'd like to publish html5-only, but will continue to publish with the fallback in order to avoid this issue. I look forward to hearing updates!
Sorry hear. I was surprised by this also. I was wondering when will Articulate going to announce what Vincent stated to the mass.
Hi Vincent,
Thank you for the info you provided, I have a couple add on question for you regarding this:
Thank you
You’ll only see the files above when you publish courses with both HTML5 and Flash formats.
In regards to Studio 360, each published output will still include the _hmtl5 file.
Please let us know if you have any additional questions!
Just a quick comment/question: In the past we pointed to the story_html5.html-file to launch the course. If I now make an update, publish to web again and replace the old files with the new output links to the story_html5.html are not working anymore since there is none. That creates a problem. Is the easy workaround just to rename (or make a copy and rename) the new story.html file to story_html5.html and I am good to go? Or am I missing something and run into an error or functionality issues later on? First testing renaming the file seems to work just fine.
Thanks!
Honestly,
I pointed my LMS to launch the story.html to keep the integrity of the file. Also, once you set it, you don't have to worried about renaming the file every time you publish the course again.
This discussion is closed. You can start a new discussion or contact Articulate Support.