Hi,
First of all, thank you for your help during the process — your guidance made it much easier to track down the issue.
The problem turned out to be related to the use of cmi.comments inside XTEnterPage() and exitInteraction().
My LMS serialises SCORM data into dynamically generated JavaScript, and the values written into cmi.comments contained unescaped newlines and free‑form text. That caused the LMS to produce invalid JavaScript during runtime, which then resulted in syntax errors and stopped the tracking process.
There was nothing wrong with Xerte’s logic itself — it was simply a case where the comments block (especially the generated lines like “entered page X: …” with a newline at the end) broke the LMS’s JavaScript parser.
To fix this on my side, I removed both comment‑writing blocks completely:
- the whole cmi.comments block in XTEnterPage(), and
- the equivalent one in exitInteraction().
After removing them, everything worked perfectly again.
All other SCORM data (score, completion, suspend_data, resume, interactions, etc.) continues to function exactly as expected.
If this is helpful for future versions: even a simple option in Xerte to disable comment writing, or escaping the newlines before sending them to the LMS, would avoid this type of problem in platforms that handle SCORM differently.
Thanks again for the support — happy to help you.
Roberto
Onderwerp Auteur
