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

Move presets feature to core or core_adminpresets

XMLWordPrintable

    • MOODLE_400_STABLE
    • MOODLE_400_STABLE
    • MDL-73397-master
    • Hide

      Scenario 1: New installation

      1. Install a new Moodle site with the patch.
      2. Login as admin.
      3. Go to "Site administration> Site admin presets" (it should appear below "Advanced features").
      4. Check there are 2 presets created (Starter and Full).
      5. Go to "Site administration > Security > Site security settings ".
      6. Check there is a section "Site admin presets" at the end.
      7. Check the "Settings with passwords" setting is not empty.

       

      Scenario 2: Upgrade from 3.11

      1. Install a new Moodle 3.11 site without the patch.
      2. Apply the patch and run the upgrade process.
      3. Login as admin.
      4. Go to "Site administration> Site admin presets" (it should appear below "Advanced features").
      5. Check there are 2 presets created (Starter and Full).
      6. Go to "Site administration > Security > Site security settings ".
      7. Check there is a section "Site admin presets" at the end.
      8. Check the "Settings with passwords" setting is not empty.

       

      Scenario 3: Upgrade from master 

      The following steps should be run on a Moodle site based on master before applying the patch. For instance, you can run "git checkout 508fe3937edc3b0de058a1d4f001bc93600dd01d" and then install the site.

      1. Install a new Moodle site based on master without the patch.
      2. Login as admin.
      3. Go to "Site administration> Site admin presets" (it should appear below "Advanced features").
      4. Create a new preset (you can call it "Preset1").
      5. Apply the "Starter" preset.
      6. Go to "Site administration > Advanced features".
      7. Check some of the advanced features, such as comments, tags or badges, are disabled.
      8. Apply the patch and run the upgrade process.
      9. Go to "Site administration> Site admin presets".
      10. Check there are 3 presets (Starter,  Full and Preset1).
      11. Check the option "Show version history" is displayed in the "Actions" menu for the "Starter" preset.
      12. Go to "Site administration > Security > Site security settings ".
      13. Check there is a section "Site admin presets" at the end.
      14. Check the "Settings with passwords" setting is not empty.
      15. Run the following SQL and check it's empty: 

        SELECT * 
        FROM mdl_config_plugins
        		 
        WHERE plugin='tool_admin_presets' AND (name='lastpresetapplied' OR name='sensiblesettings')

      16. Run the following SQL and check it contains 2 rows (one for the lastpresetapplied and another for the sensiblesettings): 

        SELECT * 
        FROM mdl_config_plugins
        		 
        WHERE plugin='adminpresets' AND (name='lastpresetapplied' OR name='sensiblesettings')

       

      Scenario 4: CLI install. Apply STARTER

      1. Open a terminal and run the following command. You'll probably need to modify some values, such as wwwroot, dbname, dbuser and dbpass to your local installation:  

        sudo -u www-data php admin/cli/install.php --lang=en --wwwroot=[http://localhost/m/integration_master] --dbtype=pgsql --dbname=integrationmaster --dbuser=postgres --dbpass=postgres --prefix=aa_ --fullname=Test --shortname=Test --adminpass=test --adminemail=admin@moodle.invalid --sitepreset=starter --agree-license --non-interactive --allow-unstable

      2. Check the installation process finishes without errors.
      3. Login as admin.
      4. Go to "Site administration > Site admin presets".
      5. Check the "Show version history" option is displayed in the "Starter" actions menu.
      6. Go to "Site administration > Advanced features".
      7. Check "Enable comments", "Enable tags functionality", "Enable notes", "Enable blogs", "Enable badges" and "Enable competencies" features are disabled.
      8. Go to "Site administration > Plugins > Manage activities".
      9. Check, at least, Chat, Database and Lesson are disabled.
      10. Go to "Site administration > Security > Site security settings ".
      11. Check there is a section "Site admin presets" at the end.
      12. Check the "Settings with passwords" setting is not empty.
      Show
      Scenario 1: New installation Install a new Moodle site with the patch. Login as admin. Go to "Site administration> Site admin presets" (it should appear below "Advanced features"). Check there are 2 presets created (Starter and Full). Go to "Site administration > Security > Site security settings ". Check there is a section "Site admin presets" at the end. Check the "Settings with passwords" setting is not empty.   Scenario 2: Upgrade from 3.11 Install a new Moodle 3.11 site without the patch. Apply the patch and run the upgrade process. Login as admin. Go to "Site administration> Site admin presets" (it should appear below "Advanced features"). Check there are 2 presets created (Starter and Full). Go to "Site administration > Security > Site security settings ". Check there is a section "Site admin presets" at the end. Check the "Settings with passwords" setting is not empty.   Scenario 3: Upgrade from master  The following steps should be run on a Moodle site based on master before applying the patch. For instance, you can run "git checkout 508fe3937edc3b0de058a1d4f001bc93600dd01d" and then install the site. Install a new Moodle site based on master without the patch. Login as admin. Go to "Site administration> Site admin presets" (it should appear below "Advanced features"). Create a new preset (you can call it "Preset1"). Apply the "Starter" preset. Go to "Site administration > Advanced features". Check some of the advanced features, such as comments, tags or badges, are disabled. Apply the patch and run the upgrade process. Go to "Site administration> Site admin presets". Check there are 3 presets (Starter,  Full and Preset1). Check the option "Show version history" is displayed in the "Actions" menu for the "Starter" preset. Go to "Site administration > Security > Site security settings ". Check there is a section "Site admin presets" at the end. Check the "Settings with passwords" setting is not empty. Run the following SQL and check it's empty: SELECT * FROM mdl_config_plugins WHERE plugin='tool_admin_presets' AND (name='lastpresetapplied' OR name='sensiblesettings') Run the following SQL and check it contains 2 rows (one for the lastpresetapplied and another for the sensiblesettings): SELECT * FROM mdl_config_plugins WHERE plugin='adminpresets' AND (name='lastpresetapplied' OR name='sensiblesettings')   Scenario 4: CLI install. Apply STARTER Open a terminal and run the following command. You'll probably need to modify some values, such as wwwroot, dbname, dbuser and dbpass to your local installation:  sudo -u www-data php admin/cli/install.php --lang=en --wwwroot=[http://localhost/m/integration_master] --dbtype=pgsql --dbname=integrationmaster --dbuser=postgres --dbpass=postgres --prefix=aa_ --fullname=Test --shortname=Test --adminpass=test --adminemail=admin@moodle.invalid --sitepreset=starter --agree-license --non-interactive --allow-unstable Check  the installation process finishes without errors. Login as admin. Go to "Site administration > Site admin presets". Check  the "Show version history" option is displayed in the "Starter" actions menu. Go to "Site administration > Advanced features". Check  "Enable comments", "Enable tags functionality", "Enable notes", "Enable blogs", "Enable badges" and "Enable competencies" features are disabled. Go to "Site administration > Plugins > Manage activities". Check , at least, Chat, Database and Lesson are disabled. Go to "Site administration > Security > Site security settings ". Check there is a section "Site admin presets" at the end. Check the "Settings with passwords" setting is not empty.
    • Moppies Kanban

      As Paul raised and Eloy confirmed in MDL-73145: "The presets feature should be straight core or core_adminpresets component (so it can interact with the rest of core) and an API (so it can spread over other plugins). The current (tool_adminpresets) plugin only would provide the "UI" to interact with the core presets stuff."

      This issue should address it.

        1. Scenario 1 New installation_Screenshot.png
          Scenario 1 New installation_Screenshot.png
          126 kB
        2. Scenario 2 Upgrade from 3.11_Screenshot.png
          Scenario 2 Upgrade from 3.11_Screenshot.png
          153 kB
        3. Scenario 3 Upgrade from master_Screenshot.png
          Scenario 3 Upgrade from master_Screenshot.png
          533 kB
        4. Scenario 4 CLI install Apply STARTER_Screenshot.png
          Scenario 4 CLI install Apply STARTER_Screenshot.png
          402 kB

            sarjona Sara Arjona (@sarjona)
            sarjona Sara Arjona (@sarjona)
            Amaia Anabitarte Amaia Anabitarte
            Shamim Rezaie Shamim Rezaie
            Gladys Basiana Gladys Basiana
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days, 3 hours
                3d 3h

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