Forum Discussion
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...
Thanks for info David. Was this patch created in part to help solve freezing or forever loading screens upon resume? Have you tested this in a version of Moodle? Something I run into occasionally when using SCORM 1.2 in Moodle is situation where the activity won't load (loading dots) when trying to pull the resume data back in so then the attempt in Moodle needs to be reset to unlock the activity. I can't really recreate the issue consistently enough to troubleshoot and it only happens to maybe 1 in 100 users. Still very frustrating.
Oh, and I can say that I have run into issues like you describe with the stuck loading prompt in the past. Usually it has turned out to be some odd event that failed upon resuming. One of the best troubleshooting things in this situation is to have the user who experienced the problem (loading stuck) open their browser developer console (usually Ctrl-Shift-I on most browsers or right click then inspect). All the browser errors are logged to that console, and though there are often lots of warnings and other errors going on, there may be a tell-tale error message that could help you down the path to a solution (or at least with what's going on that's preventing it from completing the resume).
Thanks for the in-depth answer. I'm definitely going to test the compression patch for suspend data in Moodle using SCORM 1.2. As for the odd loading event, I was able to inspect a frozen activity and in console I was shown an error that was not thrown in the same activity that's loading for another student. I'm currently chasing this down and it seems promising. Might fix a bug that has been an annoyance for some time.
To provide more information about my freeze error for SCORM 1.2 in Moodle, I found that if a user (myself for testing) answers one of the essay questions in the activity and the user's response has an apostrophe in it (conjugation or used as a single quotes) the activity freezes on the loading dots when resumed without the resume button loading (modern player/html5). For some reason the single quote/apostrophe is being read as code and not as punctuation because the student_response is closed with single quotes:
cmi.interactions_0.student_response = 'I'm gonna try with apostrophe';
Not even sure where/how to tackle this issue. It could be how it's pushed from Storyline to Moodle via SCORMfunctions.js or it could be how the suspend data is formatted and pushed to back to the activity.
Yes, that is an excellent example of the issue I encountered with one of our customer's LMS systems but was dealing with the suspend_data specifically. The interface between the SCORM layer and that LMS system was doing a Javascript eval. So, when you do something like eval("cmi.interactions_0.student_response = 'I'm gonna try with apostrophe';") that will then lead to a Javascript error because there is extraneous characters following the variable assignment (in this case: just the 'I'). However, I wouldn't think that should effect reloading, but maybe it does. I haven't exactly studied whether Articulate resends interaction data from the LMS as it resumes - but I could see that if it did, it might present a problem upon reload. Anyway, good luck!
