Follow

Directory Structure of SCORM Package/Communication with API

Avatar

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?

Andrew.

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

Comments

  • Avatar
    John Mensel

    Andrew.

    I'm not sure I know what you mean by "a standard JS SCORM file".  There's no "standard" here... just lots of different ways to do it. 

    Often people program to exactly what the ADL test suite tests for, but fail to develop things in such a way that they will be widely usable.  One example of this is that the ADL test suite always launches content in its own window, so many API discovery algorithms fail to look in their parent frames.  It's possible this is what's happening here.  There are also about 50 other things that could be going on.

    In Test Track, there's likely a workaround that would save you here, but it's probably worth getting it right so you can deliver to non-SCORM Engine based systems.

    I would suggest checking out this post on discovering the API.  If that doesn't get you there, feel free to send your course along to me to review briefly.  support@scorm.com.

    Thanks for the question.

  • Avatar
    Andrew Wilson

    Hi Tim,

    Thanks for the prompt reply.

    When I say standard I mean that it is a file called "APIWrapper.js" that many of the packages I have looked at seem to be using (de facto, I suppose). I should have made that clear.

    I have tried calling the initializeCommunication from within flash and also in the HTML. In both cases The javascript function is called but it can't find the API.

    It checks for frames (500 deep) and also openers for the API and works in other CPs (which makes me think it is the structure of my test CP).

    Thanks for the link. The APIWrapper is doing pretty much what you are saying in the link.

    I suppose what I am asking is, does it matter if the player files are not in the root of the CP but in a sub directory?

    Andrew.

  • Avatar
    John Mensel

    Provided the subdirectory is properly referenced (relative references only), then yes, it should be fine.  If you want to send the course over, I'll take a quick look at it... It's probably something simple.

  • Avatar
    Andrew Wilson

    Hi there,

    I have sent that over to you now.

    Thanks,

    Andrew.

Powered by Zendesk