Changing the file name of Published Web Content

You can change either. If you change story.html to index.html and have a course published for both Flash and HTML, the new index page will still do its magic and recognize a non-Flash device and redirect to story_html5.html.

If you change story_htmal5.html to index.html, then only the HTML5 version will be displayed.

Thanks Michael.  Where do I make the change from story.html to index.html?

How about creating an index.html and redirecting it to story.html?

You'll have to change the name manually, after publishing. While I haven't tried this myself, Kawstov's suggestion should work too.

Hi Jacquii and welcome to E-Learning Heroes! 

I'm glad that Michael and Kawstov have been able to assist you here and if you need anything else, please let us know. 

Hi Michael. I know this is an old thread, but do you know if you can just rename the story.html file to index.html in Storyline too? My LMS supplier is asking me to do this. Thanks.

Hi Steven,

Once you publish the course, you can modify the name per the end of this article on publishing for LMS. You'll want to make sure you keep the file/folder structure that is created and upload all the contents of the published output folder to your LMS. 

Thanks Ashley. I thought as much, but if this 'story.html' file is renamed to 'index.html', will the HTML5 file still automatically be called up when the content is viewed in a non-flash broser? In Storyline2 of course. Thanks.

Yup - it should still work normally to show the HTML5 output. 

I've tried changing the story.html and index_lms files to index.html individually, and the course will no longer play on our lms. Adding a blank index.html file seems to work, so I'll just have to do that in the meantime. Bummer.

Hi Steven,

Are you changing both of those file names or just one of them? You could also look at testing it at SCORM Cloud to see if it's something specific to how your LMS may be reading the content, as SCORM Cloud is an industry standard for testing LMS content. It does sound like you've found a workaround that'll work for you though. 

Only one at a time Ashley. I have had issues with my LMS before (it is an internal system) so I'll dig out my SCORM Cloud login and do some more testing. Thanks.

Always gotta ask, as you never know. ;)  

Let us know how it goes at SCORM Cloud! 

For the LMS, you'll either want to leave things the way they are or, if you do change something, go into the imsmanifest.xml file and change the pointer to match. The LMS knows which file to launch by looking at the manifest file when the SCO is loaded. I believe the launch file is index_lms.html.

I think that's the direction I'll be heading in Steve, but I am teaching for the next two weeks so will have to get on to it then. Watch this space! Thanks.

One other thing to keep an eye on:

Launching the LMS API connected file directly from your web server (yourserver/content-folder/index_lms.html) will probably throw a lot of errors. Launching the story.html file won't throw errors.

If your intent is to launch from a direct link for folks that don't want to be tracked, you'll probably want to refer to the story.html file. There are a few ways to use Javascript to alert users that their progress won't be tracked or retained. We've done this for content packages we wanted to expose to a broad audience of folks without LMS accounts.

Thanks Steve. I will be sending all users to the LMS. Courses were opening and running fine, it's just that the LMS administrators complained that the LMS kept throwing up errors relating to a missing index.html file. So I added a blank one, error gone.

The fact that a 'blank' file "solved" this error problem has me concerned that the LMS isn't serving up my content correctly, in particular HTML5 content, which I have no way of testing.

I think you're right, I'll need to alter the imsmanifest file and possibly play with Javascript, but will get back to you all when I've got the time for it. Thanks again.

In out testing, IE11 on Windows 7 and 10 comes up with a blank web page when we rename story.html to index.html. It does NOT resolve over to the story_html5.html file. It does work in Edge, Chrome, and Firefox. I think IE gets stuck somewhere in the JS scripting in the story.html/index.html file and never makes it over to story_html5.html.