JavaScript runs locally but not in LMS

Hi Sven,

Although it sounds like a good idea to use external Javascript in a course, I would recommend that you try to keep the Javascript internal when you are using it with Storyline. It make it easier to find, and easier to publish. In fact, in general, I always recommend to users; if there is a way to do what you want without resorting to Javascript, then that is generally your best option. There is a lot you can do with Storyline's triggers, states, and layers. 

With that being said, you can still use external Javascript, but you will have to add it back into your course after you publish it. If you publish a course with Javascript, you will notice that Storyline adds a folder for the Javascript files. You will need to copy your external Javascript into that folder after your publish. Since you are publishing for an LMS, this means you need to add it to the .zip file. 

I'm going to leave to you to experiment, and locate that folder. Good Luck,

Dave

If your LMS is running from an "https" website instead of "http", then make sure your external javascript source is also called with "https". See if that fixes the problem.

I do agree with Dave that relying on external javascript may not be the best solution, because if the site hosting the js ever goes down, it will break your course.