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

IMS Common Cartridge option missing with Asynchronous backups enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 3.10.11, 3.11.7, 4.0.6
    • Backup: IMS-CC
    • MOODLE_310_STABLE, MOODLE_311_STABLE, MOODLE_400_STABLE

      DESCRIPTION
      The IMS Common Cartridge option when taking a course backup is not present when Asynchronous backups enabled

      STEPS TO REPLICATE
      1. Create a course
      2. Start to take backup of course (/backup/backup.php?id=)
      3. See that IMS Common Cartridge 1.1 is first option available in backup selections *Do not need to complete backup, though useful to confirm the .imscc file type becomes available
      4. Navigate to the Site Admin>Manage Courses and Categores> Backups> Asynchronous backup/restore
      5. Enable Asnychronous backups
      6. Navigate back to course and take new backup

      OBSERVED BEHAVIOR:
      IMS Common Cartridge 1.1 option to select on the backup screen is not present

      EXPECTED BEHAVIOR:
      IMS Common Cartridge 1.1 option is available. If async does not allow for IMS export, then either an error should occur OR the IMS Common Cartridge option is seen but becomes unavailable with async enabled AND information is listed in the asynchronous setting description alerting the user that it is not compatible with IMS.

      REPLICATION LOCATIONS
      https://core2-sandbox.mrooms.net/ Moodle 3.10.6 (Build: 20210729)
      https://core2next-sandbox.mrooms.net/ Moodle 3.11.5 (Build: 20220117)

      https://jhicks-sandbox.mrooms.net/ Moodle 3.11.5 (Build: 20220117)

      CLIENT IMPACT
      4

            Unassigned Unassigned
            jhicks Jeffrey Hicks
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:

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