We have ran in to this bug, I think: https://tracker.moodle.org/browse/MDL-40223 Bug title: "launch value on mdl_scorm is reused when backup of course is used to make a new course"

Fix version in that bug is Moodle 2.5.4. Client site is running Totara 2.5.5, based on Moodle 2.5.3, so I think we need this bug fix.

Here is whats happening.

Client uses backup/restore to create course template backup files, which are then restored into new courses as they construct courses in preparation for the LMS go-live date. The course template includes the most standard activities and configurations they will be using in courses, including a scorm activity used as a place holder for Scorm content in each new course they restore to. The problem is that the Scorm activities in new courses that have been created/restored from the template backup file are not working. Basically the scorm popup window opens, but nothing is rendered in the scorm window. When I view the scorm window in developer tools, nothing is rendered between the scorm div content tags. This seems to only affect the learner opening the Scorm. A trainer role or administrator can load the Scorm perfectly fine.

Standard scorm activity settings include "Display package" = "New Window" and "Student Skip content structure page" = "Always". This way the scorm popup always loads directly from the course page for the learner.

While troubleshooting, I ended up looking at scorm tables in the database, and noticed that in the scorm table, the only difference between working Scorm activities and non-working Scorm activities was the scorm.launch field. As per the Moodle bug above, when I changed the launch value for the non-working Scorm to something unique, the Scorm began to launch correctly for learner role. It in fact was not unique before I did that, as is the case with many of the other Scorm activities in the scorm table.

I would appreciate advice on the best workaround until this bug as fixed, as well as info on expected fix date for this bug. It is critical for a client nearing go-live date.