Moodle
  1. Moodle
  2. MDL-21432 META: Backup & restore 2.0
  3. MDL-23686

Is there to be a more precise listing of error messages in Moodle 2.0 for such things as Backup and Restore?

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: Backup, Documentation
    • Labels:
      None
    • Environment:
      Any
    • Database:
      Any
    • URL:
      None
    • Affected Branches:
      MOODLE_20_STABLE

      Description

      An error generated in a Restore and the process stops but it is not specifically stating what the error is. Seeking further documentation the User is taken to a stub, but if the User could identify the error, then it would be fixed at that point. However, the underlying error may be generated by trying to restore from a 1.9.8 backup to Moodle 2.0.

        Gliffy Diagrams

          Activity

          Hide
          Helen Foster added a comment -

          Colin, thanks for your report. Reassigning to our backup component lead, Eloy.

          Re. restoring from 1.9 to 2.0, as far as I know, this has not yet been implemented. The workaround is to upgrade the 1.9 site complete with courses to 2.0.

          Show
          Helen Foster added a comment - Colin, thanks for your report. Reassigning to our backup component lead, Eloy. Re. restoring from 1.9 to 2.0, as far as I know, this has not yet been implemented. The workaround is to upgrade the 1.9 site complete with courses to 2.0.
          Hide
          Eloy Lafuente (stronk7) added a comment -

          I'm moving this to be one subtask of the moodle 2.0 meta: backup & restore (MDL-21432)

          Also, I'm assigning this to Sam, as far as I think we have one conflict here between the UI and the restore controller causing the moodle 1.x format not being detected (and informed) because the UI stuff gets executed before the controller checking of format.

          This causes the restore process to "die" with "file not found message", where it should be "moodle 1.x format detected, still not possible to restore this" or so.

          IMO we should try to instantiate the restore_controller earlier (before trying to get backup information and everything else), so the controller performs the format checks and end with status STATUS_REQUIRE_CONV or STATUS_SETTING_UI and format controller->get_format() containing the found format (imscc, moodle1...).

          That way, the UI will be able (when implemented), to call controller->convert() in order to transform the backup into a moodle2 one. For now it just must show error msg and stop.

          Any thought, Sam, can that be done in that way? First instantiate controller and look for status/format before loading info?

          Ciao

          Show
          Eloy Lafuente (stronk7) added a comment - I'm moving this to be one subtask of the moodle 2.0 meta: backup & restore ( MDL-21432 ) Also, I'm assigning this to Sam, as far as I think we have one conflict here between the UI and the restore controller causing the moodle 1.x format not being detected (and informed) because the UI stuff gets executed before the controller checking of format. This causes the restore process to "die" with "file not found message", where it should be "moodle 1.x format detected, still not possible to restore this" or so. IMO we should try to instantiate the restore_controller earlier (before trying to get backup information and everything else), so the controller performs the format checks and end with status STATUS_REQUIRE_CONV or STATUS_SETTING_UI and format controller->get_format() containing the found format (imscc, moodle1...). That way, the UI will be able (when implemented), to call controller->convert() in order to transform the backup into a moodle2 one. For now it just must show error msg and stop. Any thought, Sam, can that be done in that way? First instantiate controller and look for status/format before loading info? Ciao
          Hide
          Michael de Raadt added a comment -

          Thanks for reporting this issue.

          We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported.

          If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

          Michael d.

          TW9vZGxlDQo=

          Show
          Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d. TW9vZGxlDQo=
          Hide
          Michael de Raadt added a comment -

          I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported.

          This is being done as part of a bulk annual clean-up of issues.

          If you still believe this is an issue in supported versions, please create a new issue.

          Show
          Michael de Raadt added a comment - I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported. This is being done as part of a bulk annual clean-up of issues. If you still believe this is an issue in supported versions, please create a new issue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: