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

SCORM Activities Not Restoring Correctly - data is reversed in backup

    Details

    • Testing Instructions:
      Hide

      Create a course with a SCORM package and back it up.
      Open the scorm.xml file in the backup and look at the order of the <scoes> items
      the ids listed should be in ascending order as stored in the db. eg 1, 2, 3, not in descending order (3, 2, 1)

      Restore that backed up course and check the order of the fields stored in the db for the scorm_scoes table is the same as the order in the original course. (ping me on jabber if you need more info)

      eg data from scorm_scoes looks like this:

      id scorm manifest
      3 24 name
      4 24 name
      5 24 name

      but when backed up it reverses the order of the records in the xml like this:
      5 24 name
      4 24 name
      3 24 name

      Show
      Create a course with a SCORM package and back it up. Open the scorm.xml file in the backup and look at the order of the <scoes> items the ids listed should be in ascending order as stored in the db. eg 1, 2, 3, not in descending order (3, 2, 1) Restore that backed up course and check the order of the fields stored in the db for the scorm_scoes table is the same as the order in the original course. (ping me on jabber if you need more info) eg data from scorm_scoes looks like this: id scorm manifest 3 24 name 4 24 name 5 24 name but when backed up it reverses the order of the records in the xml like this: 5 24 name 4 24 name 3 24 name
    • Affected Branches:
      MOODLE_23_STABLE
    • Fixed Branches:
      MOODLE_21_STABLE, MOODLE_22_STABLE, MOODLE_23_STABLE
    • Pull Master Branch:
      master_MDL-34233

      Description

      When restoring a course backup, SCORM activities do not display content without opening up the settings for that activity and then clicking "Save and Display". Inspecting 'mdl_scorm_scoes' revealed that each of the newly created scoes have two records, one for the "_ORG" element (Articulate) and one for the "_SCO". When first restored, the "_SCO" record is always created first, with the "_ORG" record immediately following. Moodle doesn't seem to like that as it will not load the content without the "_ORG" record being first and "_SCO" second. Manually switching the ids of these two records in the DB for an affected SCO fixes the issue, as does opening up the SCO's settings page and then clicking "Save and Display".

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    10/Sep/12