Storyline 1 - HTML5 output LMS issue with suspend_data
Jul 30, 2015
Hi,
We are using Storyline 1 update 8, we've set the player to Never Resume and we use our own JavaScript code to store the course progress within the LMS. If running the course via Flash all works fine. If we disable the Flash plugin and run in HTML5 storyline stores it's own course progress within suspend_data in the LMS, the standard encrypted way which we don't want and our JavaScript is ignored. The reason we don't want the encrypted progress stored within the LMS is that it makes future updates impossible, as if additional slides are added it corrupts the users progress and corrupts the course.
Does anyone know how to stop the player in HTML5 storing progress data within the LMS in Suspend_data and make the JavaScript triggers work as they do in Flash?
40 Replies
Hi, Marcus -- You may already be aware of this, but I thought I would mention for good measure... Unfortunately, we don't provide support for JavaScript coding, it may be helpful to take a look at this document on JavaScript Best Practices. Hopefully, some of our JS experts in the community can chime in with suggestions! :)
Thank you for your reply, however the question isn't really about JavaScript code.
Question 1 - In HTML5, Storyline stores progress data in the LMS suspend_data, how do you stop this? Setting the Player to Never Resume works for Flash but in Html5 it is still putting data into suspend_data.
Question 2 - Are JavaScript Triggers supported in HTML5 output? Ours don't work in Html5 but work fine in Flash. So before I spend time trying to fine out why, just wanted to know.
This MUST be a bug, both on SL1 and SL2 if you disable Flash in browser and run as html5 storyline stores data within the LMS in suspend_data even though Never Resume is set.
Has anyone else had the same problem?
Haven't seen that particular problem. Never tested but that shouldn't happen. If it is, def seems like a bug.
I regularly use JS triggers and the GetVar / SetVar as well as a heap of other player API methods in HTML5. Do you have an example you can share where they're not working.
Just confirmed. Seeing exactly the same behavior in a test file. Definitely pushing suspend data for the HTML5 version. It's not restoring (obeying the setting) but it's cramming stuff into suspend data.
Thank you Steve for confirming, how do I report this bug? Or will a staff member pick this up?
Hi, Marcus -- I would be happy to submit the ticket to our QA team for review. Would either you or Steve care to share your test files so that I am able to attach them to the ticket, as well?
Pretty easy to replicate. Build any LMS output, even a single slide. Set the player to never resume. Change the launch target to index_lms_html5.html. I've attached a SCORM published output that will show the issue in SCORM cloud.
By the way, this is SL2. But I imagine it's exactly the same issue in SL1.
Fantastic -- thanks so much, Steve! I'll create the ticket momentarily, and any updates or information I receive from QA will be shared here in the thread. Your help is appreciated. :)
I can confirm it's the same in SL1.
Many thanks to you as well, Marcus! :)
Hi Christie, have you received any information from QA on this issue yet? Just wondering whether it's likely to be days/weeks/months. Or whether there's anything in the outputted code I change to resolve the issue prior to an update being released.
Hi, Marcus -- Unfortunately, I am unable to provide a timeframe for potential resolution, but I will be sure to update here in the thread with any new information I receive. Thank you for your patience.
Any update?
Hi, Marcus -- I just checked and unfortunately, I still have no new information to share and do not have a timeframe for if or when this issue will be addressed. I will be certain to update here immediately if I am provided any new details. Your continued patience is appreciated.
I am facing exactly the same issue. I am using storyline 1 update 10. Is there any update regarding this issue.
Hi Uttam!
I popped in to check on this and do not have an update to provide at this time. It is still in the hands of our QA Team, but is flagged for update when applicable.
Hi Marcus,
Do you have found any solution for this issue although they have no solution still now.
Hi Uttam!
Not sure if Marcus is still subscribed, but if you do not hear from him soon - you are welcome to utilize the 'Contact Me' option on the user profile.
Sure, but I got stuck with this issue and need immediate attention. Desperately waiting for your solution.
Yes, I'm still here and no we didn't find a solution. We had to remove all references to our courses being html5 compatible because of this bug :(
You mean you didn't keep any external JS reference . Have been kept all java script code inside js trigger or totally you had removed js.
I mean that we used JavaScript triggers to store our own data within suspend_data in the LMS with Player set to NEVER resume, but the JS just doesn't get called 99% of the time and storyline instead overwrites the data within suspend_data with it's progress (like it's set to ALWAYS resume). We then tried saving data within lesson_location using JavaScript, but if Storyline saves it's progress within suspend_data it doesn't seem to call our JS triggers.
Another issue we found was if saving progress in LIVE LMS using ALWAYS resume, if you have to update the course (add a page) when you outputted the course and uploaded to LMS. People lost there progress within the course or worse the course displayed all over the place. As some of our courses are 2 hours long, this was a disaster.
Therefore we don't output for html5 now and will probably have to look for another product next year.
This discussion is closed. You can start a new discussion or contact Articulate Support.