Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.4, 2.6
    • Fix Version/s: 2.6
    • Component/s: Backup
    • Labels:
    • Testing Instructions:
      Hide

      1. In server settings, set debugging level to DEVELOPER.

      2. Using a small test course such as the 'XS' test course, do a backup of the course.

      EXPECTED: Below the Continue button, the final screen displays a heading and scrollable log text headed 'Technical information and warnings', which includes some debugging output about 'setting controller status' and the like.

      3. Restore the backup to a new course.

      EXPECTED: The final screen displays similar log information.

      4. Import the original course into the new one.

      EXPECTED: The final screen displays log information. There's twice as much because this includes both a backup and a restore.

      5. Set the server debug level to one less than DEVELOPER (ALL) and repeat steps 2, 3, and 4.

      EXPECTED: Now that debugging information is not included and the logs are empty, no log information is displayed on the final screen.

      Show
      1. In server settings, set debugging level to DEVELOPER. 2. Using a small test course such as the 'XS' test course, do a backup of the course. EXPECTED: Below the Continue button, the final screen displays a heading and scrollable log text headed 'Technical information and warnings', which includes some debugging output about 'setting controller status' and the like. 3. Restore the backup to a new course. EXPECTED: The final screen displays similar log information. 4. Import the original course into the new one. EXPECTED: The final screen displays log information. There's twice as much because this includes both a backup and a restore. 5. Set the server debug level to one less than DEVELOPER (ALL) and repeat steps 2, 3, and 4. EXPECTED: Now that debugging information is not included and the logs are empty, no log information is displayed on the final screen.
    • Affected Branches:
      MOODLE_23_STABLE, MOODLE_26_STABLE
    • Fixed Branches:
      MOODLE_26_STABLE
    • Pull Master Branch:
      MDL-38196-master

      Description

      When you do a back up or restore, there is a log which may contain warning messages. If the log is not empty, it should be displayed after backup or restore completes.

      • Currently the log is written, but not displayed anywhere.
      • Some components add warnings in this log if there are problems. It would be useful if administrative staff could actually see the warnings.
      • Note: It is already possible in the API to intercept and display this log. We do this in our roll-forward process. However, the same information would be useful if doing a standard backup or restore.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  18/Nov/13