Older course re-exported with 18.0.2 no longer tracking last page visited in LMS
March 27, 2019 12:00 AM
Hi all,
Any idea why a Lectora 16 course that worked fine in our LMS (SumTotal) would start having issues when edited and uploaded as a new course using Lectora 18.0.2? The course has a timer using the AICC_Time variable, and we have the "last viewed page" prompt checked.
However, with the new upload, the timer resets every time and the learner always starts back at page 1 no matter the progress. I'm publishing using SCORM 1.2 and I've tried seamless, non-seamless, and also HTML5 only. Also multiple browsers. Same issue each time.
Any ideas?
Thanks, Dominic
Discussion (8)
Hi Dominic,
Can you reproduce the issue in a small course with just a few pages? If so please attach/upload the published zip file here. Also export the title as zip file and upload it here. We will take a look at it.
Thanks,
Robert.
For some reason, I can't upload the zip files. They are under the maximum size, but they keep failing to post. Can I send them directly to you?
Hi Dominic,
Did you test your course in scorm cloud? That could help you identify if the problem lies with the scorm package or the LMS.
Check also this thread, I face the same issue, but in my case I use Moodle. However, my scorm package seems to work as it should in scorm cloud.
Best,
Kostas
Thanks Kostas. I've never used Scorm Cloud. Are you talking about this software: https://rusticisoftware.com/products/scorm-cloud/
Hi Dominic,
Yes this is the one. You can make an account for free, but there are some limitations e.g. 100 mb max file size. In this page you can find more info on how you can troubleshoot with scorm cloud.
I hope that helps.
Kostas
Hey everyone. I just wanted to give an update in case anyone else is having this issue. I heard back from Trivantis Support, and they gave me the following solution. It seems to have solved the issue for me. Dominic
"If you download the file from the following link and replace the existing "scofunctions.js" in your SCORM package you should see cmi.core.session_time populate. We have identified a bug that is causing this issue and will be addressing it in the next update for Lectora 18. Until the next update you will need to replace the "scofunctions.js" file in your SCORM package with the file we provided.
https://trivantissupport.sharefile.com/d-s4c5b4c719a041a1a
Excellent. Happy it helped you too. Took over a month to get that response, but at least we finally have an answer!
Hi Dominic,
Thank you for sharing the file.
Although in my case I had not used a timer, the js file you shared solved also my problem! It seems it is a wider issue, which is not strictly related to the addition of the timer.
Thanks again, I really appreciate it.
Kostas
Discussions have been disabled for this post