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

IMSCC backup doesn't use configured temp directory

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.4.6, 2.5.2, 2.6
    • Fix Version/s: 2.4.7, 2.5.3
    • Component/s: Backup: IMS-CC
    • Labels:
    • Testing Instructions:
      Hide

      1) Set $CFG->tempdir in your testing environment pointing to a dir, ideally in another disk/partition.

      2) Get any course with a few activities and backup it as "IMS Common Cartridge 1.1".

      3) The process ends without error and the imscc package is generated. You can see it generated in the user private backup area with extension imscc.

      Show
      1) Set $CFG->tempdir in your testing environment pointing to a dir, ideally in another disk/partition. 2) Get any course with a few activities and backup it as "IMS Common Cartridge 1.1". 3) The process ends without error and the imscc package is generated. You can see it generated in the user private backup area with extension imscc.
    • Affected Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE
    • Pull Master Branch:
      MDL-41660-imscc-tempdir

      Description

      The imscc backup doesn't respect the $CFG->tempdir setting.

      To reproduce:

      Set $CFG->tempdir to something other than the default location and backup a course using IMS CC format. The conversion stage of the backup will use the default temp directory ("$CFG->dataroot/temp"), and not the configured $CFG->tempdir.

      If the $CFG->tempdir is on a different filesystem than the moodle data root, then the backup will actually fail with error "error/failed_move_converted_into_place". This is due to rename() not working across filesystem boundaries.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

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