-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Course Exit while disconnected from LMS loses progress #320
Comments
When attempting to replicate this in SCORM Cloud (with 'Reset RunTime Data Timing: When Exit Is Not Suspend' in Compatibility Settings) and a Moodle based LMS, all runtime data is reset when relaunched, unless a suspended For SCORM Cloud, even when data is restored correctly on relaunch, the LMS UI does seem to always be missing the last entry and doesn't reflect the data being persisted. This is repeated until the course is relaunched and then closed whilst a connection is still established, at which point the UI is updated accordingly. Interestingly, the LMS UI not updating but the course being restored correctly on relaunch, can be replicated in SCORM Cloud even when a connection is always present, by using launch behaviour settings of:
The LMS UI issues cannot be resolved, but we should probably look to set the |
…ta being reset on relaunch if disconnected whilst course widow is closed (fixes #320).
🎉 This issue has been resolved in version 5.9.10 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Subject of the issue/enhancement/features
Within SCORM 2004, all of my course progress is being erased if I am exiting the course while my internet is disabled. SCORM 1.2 seems to work as you would expect, assuming the data had been committed before the disconnect. SCORM 2004 doesn't and the data is reset unless the cmi.exit state has been set.
The other odd thing is that a status doesn't seem to be reflected back into LMS UI until I've relaunched the SCORM. And within certin test LMSs, a potential fix works in Chrome but not Firefox. So a fix would likely need to be tested across a few LMSs & browsers.
Your environment
Steps to reproduce
Expected behaviour
The LMS UI should be updated with approrpate statuses. Bookmarking should immediately address the issue on relaunch and the appropriate progress should be retained.
The text was updated successfully, but these errors were encountered: