Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-40223

launch value on mdl_scorm is reused when backup of course is used to make a new course.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.3.4, 2.4.4, 2.4.7, 2.5.3, 2.6
    • 2.4.8, 2.5.4, 2.6.1
    • SCORM
    • MOODLE_23_STABLE, MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
    • MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
    • master_MDL-40223
    • Hide

      Update the mdl_scorm.launch value to be a unique value. Return to the SCORM activity and the content will launch.

      Show
      Update the mdl_scorm.launch value to be a unique value. Return to the SCORM activity and the content will launch.
    • Hide
      Before upgrade.
      1. Break one of your existing scorm pacakges by modifying the scorm->launch field (scorm table, launch param) - set to an integer that is incorrect (like 999999)
      2. Run upgrade then check to make sure launch param has been updated to something more normal (it may not match the same sco-id as previously but as long as it points to the id of the first launchable sco from the mdl_scorm_scoes table and entering the SCORM as a student after the upgrade still works.
      Test of backup/restore.
      1. Create a course.
      2. Add a SCORM activity and upload a SCORM 1.2 content piece.
      3. Add 2 or 3 more of the same.
      4. Go to the SCORM activity and verifies it launches.
      5. Backup the course.
      6. Restore the course as a new course in the system.
      7. Go to the SCORM activity.
      8. Make sure it works as expected.
      9. Go to your database and check the mdl_scorm table's launch value for the new scorm row is different than the launch value for the scorm in the course you backed up.
      Show
      Before upgrade. Break one of your existing scorm pacakges by modifying the scorm->launch field (scorm table, launch param) - set to an integer that is incorrect (like 999999) Run upgrade then check to make sure launch param has been updated to something more normal (it may not match the same sco-id as previously but as long as it points to the id of the first launchable sco from the mdl_scorm_scoes table and entering the SCORM as a student after the upgrade still works. Test of backup/restore. Create a course. Add a SCORM activity and upload a SCORM 1.2 content piece. Add 2 or 3 more of the same. Go to the SCORM activity and verifies it launches. Backup the course. Restore the course as a new course in the system. Go to the SCORM activity. Make sure it works as expected. Go to your database and check the mdl_scorm table's launch value for the new scorm row is different than the launch value for the scorm in the course you backed up.

    Description

      When you have a course with SCORM activities and you take a backup of that course and then restore to make a new course with that backup. Some content will not launch in the new course. This appears to be due to the launch field on mdl_scorm being the same value as it is in the initial course.

      When I took a look in the DB I found these items share the same launch value in mdl_scorm. I updated the mdl_scorm.launch value to be a unique value. I then went back to the course and went to the SCORM activity and the content launched.

      Before upgrade.
      Break one of your existing scorm pacakges by modifying the scorm->launch field (scorm table, launch param) - set to an integer that is incorrect (like 999999)
      Run upgrade then check to make sure launch param has been updated to something more normal (it may not match the same sco-id as previously but as long as it points to the id of the first launchable sco from the mdl_scorm_scoes table and entering the SCORM as a student after the upgrade still works.

      Test of backup/restore.
      Create a Course
      Add an SCORM activity and upload a SCORM 1.2 content piece
      Add 2 or 3 more of the same
      Go to the SCORM activity and verifies it launches
      Backup the Course
      Restore the Course as a new course in the system
      Go to the SCORM activity
      Content Does not launch

      Attachments

        Issue Links

          has been marked as being related by

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-43517 SCORM issues after Backup and Restore

          • Major - Major loss of function, incorrect output
          • Closed

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-43043 scorm - check launch param after scorm update in 2.4/2.5

          • Minor - Minor loss of function where workaround is possible
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-42064 SCORM modules do not load as popups, stay grey, maybe lose connection

          • Major - Major loss of function, incorrect output
          • Closed

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-42080 Problems with SCORM after restoring them with a course backup

          • Minor - Minor loss of function where workaround is possible
          • Closed
          will help resolve

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-37529 SCORM tracking data inaccessible due to incorrect 'scoid' mapping when content structure page is skipped and display package is set to 'New window'

          • Minor - Minor loss of function where workaround is possible
          • Closed

          Activity

            People

              danmarsden Dan Marsden
              kmccarthy Kevin McCarthy
              Mark Nelson Mark Nelson
              Damyon Wiese Damyon Wiese
              Ankit Agarwal Ankit Agarwal
              Dan Marsden, Matteo Scaramuccia, Ilya Tregubov, Kevin Percy, Mathew May, Mihail Geshoski, Shamim Rezaie
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                13/Jan/14