I am supporting a couple of well-known LMSs. Recently 2 of our clients received the very same error, while trying to run Storyline SCORM contents: The file Configuration.js could not be loaded. Upon examining their storyline SCORM files, it apperas that the lms/ folder contained the file, but called "configuration.js" (lower-case c), which, for our linux servers, was not accessible as Configuration.js.
Can you please let me know if there is a workaround or suggestion about this, so we can advise our clients?
I had the same problem 5 minutes ago. Some servers are very particular about the uppercase letters, that is why this problem occurs. I just changed configuration.js into Configuration.js and now it works.
Problem is actually from line 16 of the index_lms.html.
Perhaps you could duplicate the file, and give it a lower-case c. That way, you have a Configuration.js and a configuration.js. I'm not sure, though. I'm just throwing my ideas at the wall to see if they stick.
4 Replies
I had the same problem 5 minutes ago. Some servers are very particular about the uppercase letters, that is why this problem occurs. I just changed configuration.js into Configuration.js and now it works.
Problem is actually from line 16 of the index_lms.html.
Actually, I did some digging and it seems that in Storyline app folder the file actually is capitalized!
C:\Program Files (x86)\Articulate\Articulate Storyline\Content\lms
So it is really strange, why the file is lower case only after the publish ...
Perhaps you could duplicate the file, and give it a lower-case c. That way, you have a Configuration.js and a configuration.js. I'm not sure, though. I'm just throwing my ideas at the wall to see if they stick.
Hans, I guess that could work, but you would need a Linux machine, you can not do that on a Windows machine, the file would overwrite the other one.
This discussion is closed. You can start a new discussion or contact Articulate Support.