Forum Discussion
You are offline. Trying to reconnect... message when viewing course on LMS
Hi there. We are encountering circumstances where folks are viewing SL courses on our LMS and get this message. If they close out of the course and relaunch it doesn't seem to be tracking their pr...
Hi, everyone!
I have some great news to share. We just released another update for Storyline 360. In Update 76, we’ve included important fixes and new features!
One enhancement we’ve included:
The lost connectivity alert is now optional. Turn it on in the player properties.
To take advantage of this update, launch the Articulate 360 desktop app on your computer, and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
This is a temporary solution to help authors get their learners unstuck by bypassing the lost connectivity feature. This is like rolling back to Update 68, but unlike a complete downgrade, this solution is more surgical and all the other features and fixes we've released from then up to 75 are still intact for authors to enjoy.
You also mentioned that this can be observed on both LMS and Web. That is correct. This is the reason why there is a solution for both environments in the earlier post. Thank you for reiterating that.
We have seen the workaround, and haven't vetted or tested the changes James has brought up, instead we've opted for a much simpler solution of changing one line of code in the main html file than changing multiple .js files.
Just making it clear that we are still investigating and still treating this seriously in spite of a workaround being present.
We have seen the workaround, and haven't vetted or tested the changes James has brought up, instead we've opted for a much simpler solution of changing one line of code in the main html file than changing multiple .js files.
of course, the new workaround is much simpler - but that's not really the point
maybe it will help the developers to identify the real problem, if they can understand why the first workaround has worked
only when you REALLY understand the cause of the problem can you fix it appropriately
Hello Jurgen, I appreciate your vigilance and apologize if I wasn't clear with my previous messaging.
We are still investigating this from all angles.
