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

Restore of 1.9 backups with missing question data is not robust

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1.3, 2.2
    • Fix Version/s: 2.1.4, 2.2.1
    • Component/s: Backup, Questions
    • Labels:
      None
    • Testing Instructions:
      Hide

      1. Restore the attached backup (backup-edited2.zip).
      2. Verify that the backup can be restored, even though there is data missing from the question definition.

      (Note there is still a notice. However this example data (which came from a real user) is total garbage, so I think we have to tolerate a notice when trying to restore it.)

      Show
      1. Restore the attached backup (backup-edited2.zip). 2. Verify that the backup can be restored, even though there is data missing from the question definition. (Note there is still a notice. However this example data (which came from a real user) is total garbage, so I think we have to tolerate a notice when trying to restore it.)
    • Workaround:
      Hide

      Hunt down the broken question, and delete or fix it on the 1.9 system before generating the backup.

      Show
      Hunt down the broken question, and delete or fix it on the 1.9 system before generating the backup.
    • Affected Branches:
      MOODLE_21_STABLE, MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_21_STABLE, MOODLE_22_STABLE
    • Pull from Repository:
    • Pull Master Branch:

      Description

      Try to restore the attached backup file into Moodle 2.1 or 2.2. It gives a fatal error.

      Trying to restore into 1.9 just gives a notice but allows the rest of the course to be restored. Moodle 2.1+ should be made similarly tolerant.

        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:
                    9/Jan/12