Forum Discussion
Storyline v3.82 SCORM 1.2 initialisation issue
Thanks for the response. We have a customer seeing the same issue with a SCORM 2004 package published in v3.83. Removing the error on the LMS side for us would not be possible. The content would have to be coded to ignore the required error from the LMS in response to the 2nd Initialize call. I will also put in a ticket with the affected content.
If you're hot on JavaScript, you could edit the SCORM_CallLMSInitialize() function in lms \scormdriver.js in the published Storyline output. Add a global boolean flag which can be used to determine if this is the first or subsequent call to the function. If subsequent then just return true. A handle to the API adaptor has already been retrieved at this point so it should work okay assuming that the double-initialise doesn't completely reload the js file.
NOTE: I'm looking at published SCORM 1.2 output rather than SCORM 2004 so names, functions and files may differ.