I have tried the new AS3 demo files and when importing the imsmanifest.xml, Pathlore only see it as SCORM 1.2. Before the changes were made to the demo Pathlore saw the file as SCORM 2004 when importing.

I did try setting it manually by adding the line SCORM.version = 2004 before the line SCORM.connection.initialize() in the SCORM_API_wrapper.js as per instructions on the website. This did not have any affect.

So at this time I can get the wrapper demo to work in Pathlore 6.5 to work but both AS2 and AS3 demos still fail.

Anyone else using pathlore having these issues?
Phillip just a fyi, in the AS3 demo zip file the source folder is missing that had the FLA and action scrip file is missing. (I want to thank Philip for all his hard work in this... this will help a lot of us who are not code warriors)
Thank you.

haven't forgotten about this, i've just been a bit busy... will get to it soon

Hi Walt

Sorry I took so long to get to this, I've had a ton of work to do.

I just re-read your post; if Pathlore is seeing the SCORM 2004 manifest as a SCORM 1.2 manifest, changing the code in the wrapper won't make a difference -- the manifest is what turns the LMS's SCORM support on or off. If the LMS thinks it's a SCORM 1.2 course, it will (usually) only expose the SCORM 1.2 API.

Specifying SCORM 2004 in the wrapper won't change the fact that the LMS has already decided this is a SCORM 1.2 course (based on the imsmanifest). If the SCORM 1.2 API is the only one made visible by the LMS, no amount of JavaScript will get the LMS to switch to SCORM 2004 mode... the LMS has to make that switch internally. (Hope I'm making sense here)

So the first thing I suggest doing is double-checking the manifest to make sure it's the right manifest. I know I get my files jumbled once in a while, but I'm pretty sure the current ZIP has all the right files. :)

If it IS the right manifest, and Pathlore continues to see the 2004 manifest as a SCORM 1.2 manifest, we'll need to figure out why.

I think the (sort of) good news is that the problem here lies in the manifest, not the SCORM wrapper code. Usually once the LMS is in the right 'mode' everything works as expected.

- philip

Hi Walt

Sorry to hear it still isn't working for you. After your latest post, I decided to test the SCORM 2004 example in the ADL test suite again (both the SCO and the imsmanifest.xml tests), and everything passed just fine.

I'm not sure which version of the demo you have, but maybe you can try downloading the latest version (if you haven't already) and see if it works?

Likewise the "Planets" demo also passed the SCORM 1.2 test.

I've received feedback from others that the files run fine on various LMSs, including Moodle, SumTotal and Saba. Maybe this is a Pathlore issue (I've never used Pathlore, so I don't know how they run things).

- philip

They can't all be blocked... the SCORM API uses JavaScript, and sends communication back and forth between the browser and LMS.

In my experience, an error such as "Object doesn't support this property or method" usually indicates your support files are not all available, or have been called out of sequence.

For instance, if you use pipwerks.scorm.init() before the object has fully initialized, you'll get an object error.

You could also get an error like that from a typo, such as window.onloadd instead of window.onload.

If you could possibly get me a logon to your system (sometime next week), I can have a look at the resulting error and see if I can sort it out.

- philip

Hmm... maybe ExternalInterface is not working in your environment. ExternalInterface facilitates the JS communication between the Flash SWF and the HTML file. If it were blocked somehow, you'd wind up with the same results you're describing in this thread.

But I have no idea why it wouldn't work for you! Maybe your Pathlore installation uses multiple domains, which could cause a cross-domain security error

Here are some things you can try:

In the Flash file, add this line of ActionScript then republish:

System.security.allowDomain("*");

In the embed code in the HTML, add the allowScriptAccess parameter and set it to "always".

In my Planets example, I'm using SWFObject 1.5 to embed the SWF. You can add this line of JavaScript just before the "so.write" line:

so.addParam("allowScriptAccess", "always");

- philip

interesting. definitely let me know how it goes!