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

Restore of 1.9 backups with missing question data is not robust

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.1.4, 2.2.1
    • 2.1.3, 2.2
    • Backup, Questions
    • None
    • MOODLE_21_STABLE, MOODLE_22_STABLE
    • MOODLE_21_STABLE, MOODLE_22_STABLE
    • 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.
    • 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.)

      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.

            timhunt Tim Hunt
            timhunt Tim Hunt
            David Mudrák (@mudrd8mz) David Mudrák (@mudrd8mz)
            Sam Hemelryk Sam Hemelryk
            Sam Hemelryk Sam Hemelryk
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.