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

Prompt to register site after upgrade

XMLWordPrintable

    • MOODLE_402_STABLE
    • MOODLE_402_STABLE
    • master_MDL-77300
    • Hide

      Ensure you are using a publicly available URL for your site $CFG->wwwroot, e.g. Ngrok

      1. Install site and login as admin
      2. When the admin menu is accessed you should see the registration form. (this is the same behaviour prior to the patch)
      3. Click the "skip" link, don't register the site.
      4. Bump the Moodle version number in `version.php` e.g from 2023021700.00 to 2023021700.01
      5. upgrade the site from the CLI
      6. When the admin menu is accessed after upgrade you should see the registration form. (new behaviour)
      7. Click the "skip" link, don't register the site.
      8. Bump the Moodle version number in `version.php` e.g from 2023021700.01 to 2023021700.02
      9. Upgrade the site from the web ui
      10. When the admin menu is accessed after upgrade you should see the registration form. (new behaviour)
      11. Click the "skip" link, don't register the site.
      12. Set site to be not public `config.php`: $CFG->site_is_public = false;`
      13. Bump the Moodle version number in `version.php` e.g from 2023021700.02 to 2023021700.03
      14. upgrade the site from the CLI
      15. When the admin menu is accessed after upgrade you should NOT see the registration form.
      16. Bump the Moodle version number in `version.php` e.g from 2023021700.03 to 2023021700.04
      17. Upgrade the site from the web ui
      18. When the admin menu is accessed after upgrade you should NOT see the registration form.
      Show
      Ensure you are using a publicly available URL for your site $CFG->wwwroot , e.g. Ngrok Install site and login as admin When the admin menu is accessed you should see the registration form. (this is the same behaviour prior to the patch) Click the "skip" link, don't register the site. Bump the Moodle version number in `version.php` e.g from 2023021700.00 to 2023021700.01 upgrade the site from the CLI When the admin menu is accessed after upgrade you should see the registration form. (new behaviour) Click the "skip" link, don't register the site. Bump the Moodle version number in `version.php` e.g from 2023021700.01 to 2023021700.02 Upgrade the site from the web ui When the admin menu is accessed after upgrade you should see the registration form. (new behaviour) Click the "skip" link, don't register the site. Set site to be not public `config.php`: $CFG->site_is_public = false;` Bump the Moodle version number in `version.php` e.g from 2023021700.02 to 2023021700.03 upgrade the site from the CLI When the admin menu is accessed after upgrade you should NOT see the registration form. Bump the Moodle version number in `version.php` e.g from 2023021700.03 to 2023021700.04 Upgrade the site from the web ui When the admin menu is accessed after upgrade you should NOT see the registration form.
    • 1
    • Team Hedgehog Sprint 2.2

      Currently the form to register a site only appears once after install. If skip is selected then the form is never shown again.

      An admin can choose to register a site at a later date and there is a registration call to action on admin pages for unregistered sites. However, neither of these are particularly effective at getting administrators to register.

      Registered sites provide key (anonymous) information to Moodle HQ, so it is important that site admins register their sites.

      This patch displays the site registration form to admins after every upgrade. To further encourage them to register their site.

      The new registration prompt will NOT display if:

      • The site is already registered
      • The site is not set to be public: `$CFG->site_is_public = false;`

      It will also only display for core upgrades only, not plugin upgrades or installations. If skipped it won't display again until the next core upgrade (or if the site was registered).

      So it will not nag developers who upgrade all the time as part of their dev/test workflows and plugin installs/ upgrades won't trigger it either for admins.

       

            matt.porritt@moodle.com Matt Porritt
            matt.porritt@moodle.com Matt Porritt
            Paul Holden Paul Holden
            Andrew Lyons Andrew Lyons
            Kim Jared Lucas Kim Jared Lucas
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours, 22 minutes
                4h 22m

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