Details

    • Database:
      MySQL
    • Testing Instructions:
      Hide
      1. Create a 1.9 site.
      2. Log in as an administrator.
      3. Visit <yoursite>/admin/settings.php?section=frontpagesettings and set 'List of courses' for frontpageloggedin setting and save.
      4. Visit the front page and turn editing on.
      5. Add a database activity with any name and introduction.
      6. Click on the database once it has been created.
      7. Click on 'Add Entry' and add a few entries.
      8. Click on the 'Presets' tab and click 'Save' next to 'Save as presets'.
      9. Do the last step multiple times saving under a different name each time, remember the names you used to create the presets.
      10. Log in as another user and perform step 8 using the same preset names you used earlier.
      11. You might want to take a database dump at this time of your 1.9 site.
      12. Upgrade to version 2.2 and check that the presets you created site wide remain. Note, in 2.x you can not create a preset using an existing name by another user, though you could in 1.9. This is why we created multiple presets with the same name for different users to ensure the upgrade can handle this scenario.
      13. Clear the database and use the database dump to restore it back to 1.9 and upgrade to the other Moodle versions that have this fix applied.
      Show
      Create a 1.9 site. Log in as an administrator. Visit <yoursite>/admin/settings.php?section=frontpagesettings and set 'List of courses' for frontpageloggedin setting and save. Visit the front page and turn editing on. Add a database activity with any name and introduction. Click on the database once it has been created. Click on 'Add Entry' and add a few entries. Click on the 'Presets' tab and click 'Save' next to 'Save as presets'. Do the last step multiple times saving under a different name each time, remember the names you used to create the presets. Log in as another user and perform step 8 using the same preset names you used earlier. You might want to take a database dump at this time of your 1.9 site. Upgrade to version 2.2 and check that the presets you created site wide remain. Note, in 2.x you can not create a preset using an existing name by another user, though you could in 1.9. This is why we created multiple presets with the same name for different users to ensure the upgrade can handle this scenario. Clear the database and use the database dump to restore it back to 1.9 and upgrade to the other Moodle versions that have this fix applied.
    • Affected Branches:
      MOODLE_19_STABLE, MOODLE_20_STABLE, MOODLE_21_STABLE, MOODLE_24_STABLE
    • Fixed Branches:
      MOODLE_22_STABLE, MOODLE_23_STABLE, MOODLE_24_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-29334_master

      Description

      None of the site-wide database activity presets we added to our Moodleinstallation is there anymore after upgrading. The function data_get_available_presets in mod/data/lib.php returns only the preset that exist within the mod/data directory. The function data_get_available_site_presets returns nothing. DATA_PRESET_FILEAREA is set to 'site-preset' but there are no files in the database with SELECT * FROM `mdl_files` WHERE `filearea` = 'site_presets'.
      In the dataroot of the installation all the presets are there as before in ..../dataroot/data/preset/courseid
      It seems as if with these files nothing happened during upgrade?

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    14/Jan/13