User previous learning progress lost after new attempt

Hi there,

thank you for reaching out. What CLUEVO Version are you using? Could you check what option is set under CLUEVO -> Settings -> Module settings -> Module attempts?

Please try to disable all other plugins and revert to a standard theme to rule out any conflicts.

I could not replicate this on our test systems, so this is hard to debug. If you need help in a more direct way, you could consider writing a ticket on our ticket system under https://wp-lms.cluevo.at/

Best,
Elias

The module attempts have been set on both ‘user decide’ and ‘always resume’. In either case the same thing happens to the learner progress history.

I have just tested having the display mode set to Lightbox. This option doesn’t mess up the user previous learning progress. So I set it back on iFrame and used the browser dev tools to check the console log.

The following is what is being recorded:

priming api 29
api primed 29
connection.initialize called.
SCORM.API.find: API found. Version: 2004
API Object
Cluevo API, lms init
errorCode 0
SCORM.data.get(‘cmi.completion_status’) value: unknown
SetValue cmi.completion_status incomplete
SCORM.data.set(‘cmi.completion_status’) value: incomplete
cluevo.js?ver=1.10.0:178 commit
SCORM.API.find: API found. Version: 2004
API Object
init cluevo lms api without suspend data, setting api item id 29

I’ve bolded the bit that seems to be the problem. This happens even before I select resume or new attempt. I check the learner progress in reporting section and it is already been reset to incomplete at this stage.

I have deactivated all plugins and used the latest WordPress default theme to test, I had to keep the Really Simple SSL plugin active because I was getting mixed content issue when tying to load the iFrame. The setting in Cluevo security tab did not resolve this. All plugins and themes are at their latest version.

Hi tanyarts, sorry to hear your having issues. I’m looking into this right now and will get back to you once I’ve found something.

We’ve looked into it and found the issue. This only happens when the module is displayed directly on page via iframe. It will be fixed in the upcoming update.

Brilliant, thanks