Forum Discussion

ChristianOmpad's avatar
ChristianOmpad
Community Member
7 years ago

Storyline Suspend Data Compression

Good day! As some of us know SCORM 1.2 only limits its suspend data for up to 4096 characters. Storyline (360) compresses its data (e.g. SL variables and such) in order to fit the limitations of t...
storyline 360
NiteshKumar-34e's avatar
NiteshKumar-34e
Community Member
6 years ago

Hi David,

If I am using pako.min.js. and follow the same procedure what have you suggested.

My module is removing the resume behavior, it run always from the first slide.

con you suggest me why it is happening.

I am using classic player and exporting in SCORM 1.2 

  • DavidHansen-b20's avatar
    DavidHansen-b20
    Community Member
    6 years ago

    Well, I would think one of two possibilities is going on: either the LMS is truncating or corrupting your suspend_data; or you may have made a very small typo or error in your implementation of the above. 

    The first thing to check would be to open the browser developer console and then check for any errors.  If you accidentally made any mistakes when patching the above files, those errors would be reported in the developer console.

    The other thing you can do to help debug, is to look at the LMS interface debug window.   To see the LMS debug window, you simply have to make a couple of changes in the file lms/Configuration.js.  First, make sure the first line has blnDebug = true;  If it's false, then just change it to true.   Then scroll down to or search for SHOW_DEBUG_ON_LAUNCH = false; and change that to true.  You will then need to re-zip the package and re-upload it to the LMS.   This simple change will then cause an additional window to open up when you launch the course that has all the debug logs for the LMS interface.

    Note: if blnDebug is already set to true, then you can also open the debug window from the browser developer console of an already launched course.  To do that, go to the console section of the developer console, and type: window.SearchParentsForContentRoot().ShowDebugWindow();

    Within the debug window, what you need to do is to find and compare the value of the suspend_data when SetDataChunk() is called versus the value when resuming from GetDataChunk().   If these values are different then your LMS is likely truncating or corrupting the data.

    I hope that helps with your debugging.

Related Content