Directory Structure of SCORM Package/Communication with API


Hi there,

We have our own Content Package player that is included with the content packages that we deliver.

We are using a standard JS SCORM file to communicate with the LMS (which works with other SCORM packages).

However, in the SCORM Cloud, we are getting a JS error returned that it is unable to locate the LMS's API.

Our Content Package has a player folder which contains the flash files for playing that package and the manifest file sits in the root of the entire package and points to "player/index,html".

The Flash/JS communication is working, since it is JS that is returning the error.

Could the directory structure (having the player in a sub-dir) be causing a problem with the communication with the API?


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk