-
Bug
-
Resolution: Fixed
-
Minor
-
4.4.4, 4.5, 5.0.1
-
MOODLE_404_STABLE, MOODLE_405_STABLE, MOODLE_500_STABLE
-
MOODLE_405_STABLE, MOODLE_500_STABLE
-
MDL-83448-405 -
MDL-83448-500 -
MDL-83448-main -
Setup
We will be registering these sites at Moodle's official stats.moodle.org site.
We need the following:
- A publicly accessible site (use Ngrok or other tunnelling service)
- Two unique site URLs (to mimic a cloned/moved site)
Ngrok's free service randomly generates a URL each time it is run, which is perfect for this test. Other tunnelling services may provide a similar feature.
Testing public sites
- Update your config wwwroot with your first public URL
- Log in as admin
- Go to Site admin > Registration
- Fill out all the required inputs
- Check the "Privacy notice and data processing agreement"
- Click on "Register your site"
- Verify that you were taken to "Site registration confirmed" page
- Click on "Continue" button
- Verify that you have a notification alert saying your site has been registered.
- Go to the bottom page and
- Verify that now you see "Update registration" button and "Unregister" link underneath the "Required" label.
- Change your site to use another public URL (update wwwroot in config too)
- Go back to Site admin > Registration and refresh the page
- Verify that you now see a red notification alert saying "Don't miss out on important updates and security alerts."
- Go to the bottom of the page and
- Verify that you now see "Register your site"
- Click on "Register your site" again
- Verify that you have a notification alert saying your site has been registered.
Testing private site new install or site upgrade
- Create a fresh install of Moodle
- Please add the following code in your config.php
$CFG->site_is_public = false;
- Log in as admin
- Click on "Site administration" once you're redirected to your home page
- Verify that you were not redirected to the site registration page
- Verify that there is no notification prompting you to register your site (see below)
Setup We will be registering these sites at Moodle's official stats.moodle.org site. We need the following: A publicly accessible site (use Ngrok or other tunnelling service) Two unique site URLs (to mimic a cloned/moved site) Ngrok's free service randomly generates a URL each time it is run, which is perfect for this test. Other tunnelling services may provide a similar feature. Testing public sites Update your config wwwroot with your first public URL Log in as admin Go to Site admin > Registration Fill out all the required inputs Check the "Privacy notice and data processing agreement" Click on "Register your site" Verify that you were taken to "Site registration confirmed" page Click on "Continue" button Verify that you have a notification alert saying your site has been registered. Go to the bottom page and Verify that now you see "Update registration" button and "Unregister" link underneath the "Required" label. Change your site to use another public URL (update wwwroot in config too) Go back to Site admin > Registration and refresh the page Verify that you now see a red notification alert saying "Don't miss out on important updates and security alerts." Go to the bottom of the page and Verify that you now see "Register your site" Click on "Register your site" again Verify that you have a notification alert saying your site has been registered. Testing private site new install or site upgrade Create a fresh install of Moodle Please add the following code in your config.php $CFG ->site_is_public = false; Log in as admin Click on "Site administration" once you're redirected to your home page Verify that you were not redirected to the site registration page Verify that there is no notification prompting you to register your site (see below) -
Code verified against automated checks. 
Checked
MDL-83448using repository: https://github.com/stevandoMoodle/moodle.git
MOODLE_404_STABLE (0 errors / 0 warnings) [branch: MDL-83448-404 | CI Job]- MOODLE_405_STABLE (0 errors / 0 warnings) [branch: MDL-83448-405 | CI Job]
- main (0 errors / 0 warnings) [branch: MDL-83448-main | CI Job]
More information about this report
Built on: Tue Mar 18 05:18:20 UTC 2025
Code verified against automated checks. Checked MDL-83448 using repository: https://github.com/stevandoMoodle/moodle.git MOODLE_404_STABLE (0 errors / 0 warnings) [branch: MDL-83448-404 | CI Job ] MOODLE_405_STABLE (0 errors / 0 warnings) [branch: MDL-83448-405 | CI Job ] main (0 errors / 0 warnings) [branch: MDL-83448-main | CI Job ] More information about this report Built on: Tue Mar 18 05:18:20 UTC 2025 -
-
6
-
Team Dragons 2025 Sprint 1.2, Team Dragons 2025 Sprint 1.3, Team Hedgehogs 2025 Sprint 2.0, Team Hedgehogs 2025 Sprint 2.1
It is common practice to:
- Clone/copy a production site to a staging or non-production site, for testing etc.
- Promote by copy/clone a staging site to production
In both cases these sites will have the same data (DB and filedir) but will have a different URL. Also the production site could be registered.
Currently, it appears that the registration process does not recognise the cloned site as being different from the original site. In cases where the original site is registered.
This leads to a workflow where the options are to update the registration of the cloned site, or unregister the source site.
Instead, the options should be to register the cloned site or skip registration. Which is the same workflow for a newly installed or unregistered upgraded site.
In the less common case where a production site has changed URL's, it isn't necessary to explicitly accommodate this workflow. If the site is registered (as a new site) the admin still gets the benefit of registration. The registration database will mark the original URL as an unreachable site after a period of time and the new registration data from the site will be added to the database. So there is not net difference.
In cases where a non production site is constantly/regularly updated from production. To save the non production site from displaying a registration prompt, admins have the existing option to set: `$CFG->site_is_public = false;` in the config.php file.
- will help resolve
-
MDLSITE-7710 Enable admins to register their site without having to ask for an existing registration to be deleted
-
- Resolved
-
