What SL creates is launched by an HTML file, whether in web or LMS configuration. When it is launched by your LMS, it opens in a web browser. Is that what they are calling a web file? Is it causing a problem in your LMS? If so, what problem?
Articulate "updates" completely uninstall, then re-install SL, so they are built for that. You won't lose anything by reinstalling (although, in SL2, you usually had to add an additional click the next time you started it, to find the serial number.)
My LMS is treating it like a HTML file and not as a scorm. Basically every time I uploaded the file, instead of it loading as a course option it's a hyperlink within my uploaded files. The LMS support tech said, the file type determines what the course is (HTML - web or scorm).
I have also reloaded a different course, already in my LMS as a course. This time it's showing up as HTML. Seem to me like a setting in SL but i'm not sure.
This problem started about 2 months ago. Nothing has changed on my end.
I'm somewhat new at this, especially working with Storyline 360
Alyssa, I only have one LMS and that's Target Solutions. I did upload it to SCORM Cloud this morning (thanks for the reminder). In SCORM Cloud it shows up as a SCORM 1.2. Is this a indication that the course is packaged correctly from SL360 and this is a Target Solutions issue? I've only used the SCORM Cloud twice.
Glad to hear it worked correctly in SCORM Cloud. I would bring that information to your LMS support team, as they'll best know how to troubleshoot LMS-specific issues.
Alyssa, I just spoke with Target Solutions and they found a problem in the coding coming from Articulate. This is a little above me. However, the support tech suggest a problem with BOM (Byte order mark) in the code standard within Articulate 360. He states that the code is causing the scorm to convert to HTML once uploaded.
Thanks for following up, David! That's above my head, too, so I'd like our Support Engineers to weigh in. 😊
Would you mind sharing your original (unpublished) Storyline file with us by clicking here? We'll take a closer look into this and let you know what we find.
7 Replies
What SL creates is launched by an HTML file, whether in web or LMS configuration. When it is launched by your LMS, it opens in a web browser. Is that what they are calling a web file? Is it causing a problem in your LMS? If so, what problem?
Articulate "updates" completely uninstall, then re-install SL, so they are built for that. You won't lose anything by reinstalling (although, in SL2, you usually had to add an additional click the next time you started it, to find the serial number.)
My LMS is treating it like a HTML file and not as a scorm. Basically every time I uploaded the file, instead of it loading as a course option it's a hyperlink within my uploaded files. The LMS support tech said, the file type determines what the course is (HTML - web or scorm).
I have also reloaded a different course, already in my LMS as a course. This time it's showing up as HTML. Seem to me like a setting in SL but i'm not sure.
This problem started about 2 months ago. Nothing has changed on my end.
I'm somewhat new at this, especially working with Storyline 360
Hi there Dave,
What LMS are you using? Also, have you tried hosting the content in another LMS environment to see if the same thing happens?
SCORM Cloud is great for this kind of testing. Let me know if you'd like some help with that!
Alyssa, I only have one LMS and that's Target Solutions. I did upload it to SCORM Cloud this morning (thanks for the reminder). In SCORM Cloud it shows up as a SCORM 1.2. Is this a indication that the course is packaged correctly from SL360 and this is a Target Solutions issue? I've only used the SCORM Cloud twice.
Hey Dave,
Glad to hear it worked correctly in SCORM Cloud. I would bring that information to your LMS support team, as they'll best know how to troubleshoot LMS-specific issues.
Alyssa, I just spoke with Target Solutions and they found a problem in the coding coming from Articulate. This is a little above me. However, the support tech suggest a problem with BOM (Byte order mark) in the code standard within Articulate 360. He states that the code is causing the scorm to convert to HTML once uploaded.
Thanks for following up, David! That's above my head, too, so I'd like our Support Engineers to weigh in. 😊
Would you mind sharing your original (unpublished) Storyline file with us by clicking here? We'll take a closer look into this and let you know what we find.
This discussion is closed. You can start a new discussion or contact Articulate Support.