When you publish, do you make sure to delete previous output folders?
What is the target file you are using to launch?
Do you make sure that Storyline is up to date before publishing?*
All three can cause issues.
If you overwrite an existing folder when publishing, legacy files can be retained, which can cause a variety of issues. Makin sure it's a clean publish each time can avoid issues.
We have had issues with content where Developers were overwriting content, and hadn't been updating Storyline 3. So we had some persistent issues when Flash passed End of Life, and when Synchronous XHR was deprecated.
And where some courses were set up to use poor target file (not index_lms.html). Older versions of Storyline had more target file options, and some would roll over to the one best for a browser, and others couldn't (and cause other functional issues on the LMS).
It could also be something with your organizations browser settings. I would consult with your LMS admin and back end support, as well as your IT team responsible for browers. The lengths your IT team may have had to go to in order to keep legacy systems working prior to IE11 End of Life were likely Herculean, and I'm sure there are still some holdovers from that. It may be that your browser settings go quickly to Internet Explorer mode because of that.
Recommend checking all the above, and using debugging mode to isolate the cause.
*We use Storyline 3, but I assume Storyline 360 operates with a desktop client which could get out of date.
Hello! I am having this same issue using Storyline 3 files published for LMS. It is a SCORM 1.2 output. I am curious what the fix was here. It seems that Jennifer offered several solutions. Did you find that one worked?
Also, we have a vendor who is building content in Storyline 360 and giving to my company to use in Storyline 3. I am publishing the files from Storyline 3. Is there any reason building in 360 and publishing in 3 would cause the issue above?
for all courses made with storyline 360 version 3.65 (June 2022) or newer, storyline courses don't start anymore if the IE11 mode is active for the url of the LMS
-> deactivate the IE11 mode for the url of the lms with group policy (-> company administrator)
8 Replies
Is your instance of Edge in "Internet Explorer Mode?"
All three can cause issues.
If you overwrite an existing folder when publishing, legacy files can be retained, which can cause a variety of issues. Makin sure it's a clean publish each time can avoid issues.
We have had issues with content where Developers were overwriting content, and hadn't been updating Storyline 3. So we had some persistent issues when Flash passed End of Life, and when Synchronous XHR was deprecated.
And where some courses were set up to use poor target file (not index_lms.html). Older versions of Storyline had more target file options, and some would roll over to the one best for a browser, and others couldn't (and cause other functional issues on the LMS).
It could also be something with your organizations browser settings. I would consult with your LMS admin and back end support, as well as your IT team responsible for browers. The lengths your IT team may have had to go to in order to keep legacy systems working prior to IE11 End of Life were likely Herculean, and I'm sure there are still some holdovers from that. It may be that your browser settings go quickly to Internet Explorer mode because of that.
Recommend checking all the above, and using debugging mode to isolate the cause.
*We use Storyline 3, but I assume Storyline 360 operates with a desktop client which could get out of date.
Please advise on how to determine
Thanks so much. Will investigate.
Hello! I am having this same issue using Storyline 3 files published for LMS. It is a SCORM 1.2 output. I am curious what the fix was here. It seems that Jennifer offered several solutions. Did you find that one worked?
Also, we have a vendor who is building content in Storyline 360 and giving to my company to use in Storyline 3. I am publishing the files from Storyline 3. Is there any reason building in 360 and publishing in 3 would cause the issue above?
this is a setting in MS Edge
for all courses made with storyline 360 version 3.65 (June 2022) or newer, storyline courses don't start anymore if the IE11 mode is active for the url of the LMS
-> deactivate the IE11 mode for the url of the lms with group policy (-> company administrator)
Thank you for the quick response! And is this the only way to address this issue even if the file is published using storyline 3?
I don't have Storyline 3, but Storyline 3 will most likely have exactly the same behavior
you could try an old version* of Storyline 3
or Storyline 360
* with these old version you cannot open SL courses made with current SL 360
** these version don't start with Firefox, if you use audio in the course