The scenario at play:
- There is a scorm.
- Some users finish this scorm and it is marked completed, but some only start it
- The scorm file is updated
- The users who never finished it return to the updated scorm
- User cannot complete scorm because it either:
- Does not load (because the suspend data is for the previous scorm version), OR
- It loads but they cannot complete it (because the suspend data is similar enough to load, but not correct to be able to complete it properly)
When you change the scorm ZIP, there should at least be the option to purge existing in progress attempts since the suspend_data is likely not valid anymore.
There is currently the ability to manually delete all attempts or selected attempts, but it would be nice to have this happen automatically for any in progress attempts.
- will help resolve
-
MDL-67538 Unable to load the scorm files after updating the scorm files with the new changes for all the started user
-
- Closed
-