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

Simplify moodle.net registration form, add new mailing list, show during installation

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • 3.4
    • 3.4
    • Hub
    • MOODLE_34_STABLE
    • MOODLE_34_STABLE
    • wip-MDL-60108-master
    • Hide

      For all tests you need a domain available from internet. You will need multiple sites that you will install and upgrade. Use different URLs for sites unless test asks to register new site at the same address.

      Test 1. Upgrade of registered site (CLI)

      1. Install a site with a stable moodle version
      2. Create a manager user
      3. Register it (Site administration > Registration)
      4. Upgrade to integration master using CLI
      5. Login as a manager
      6. Make sure you can browse "Site administration" without problems
      7. Login as admin
      8. You should be redirected to the registration form (from /index.php , /admin/index.php, /admin/search.php but not from other pages)
      9. Registration form should say "Registration information has been changed. Please confirm it using the 'Update registration' button.", the "More information" should be expanded, the new fields highlighted with yellow ("Updates about Moodle news and features" and Mobile info)
      10. Do not update registration yet
      11. Check that this form and highlighting looks ok in both Clean and Boost
      12. Run scheduled task "Site registration" ( /admin/tool/task/schedule_task.php?task=core\task\registration_cron_task ) - you should see a message that registration was not updated
      13. Go to /admin/search.php
      14. Update registration manually
      15. Make sure you are now on /admin/search.php and now it works
      16. Run "Site registration" scheduled task again, it should update the registration

      Test 2. Upgrade of registered site (web)

      1. Install a site with a stable moodle version
      2. Register it (Site administration > Registration)
      3. Upgrade to integration master using web interface
      4. Upgrade should proceed as usual, you should be offered the new settings to confirm
      5. After you confirm new settings you should be redirected to the registration form that asks you to update new data (do not update yet)
      6. Run cron in CLI - it should run properly (not saying that "upgrade is pending"). However the site registration task should not run (this was already tested in test1)
      7. Go back to the browser and submit the registration form
      8. You should now be redirected to the functional /admin/index.php

      Test 3. Upgrade of unregistered site

      1. Install a site with a stable moodle version
      2. Upgrade to integration master using CLI
      3. Login as admin
      4. Go to "Site administration" (both /admin/index.php and /admin/search.php)
      5. You should NOT be redirected to registration page

      Test 3. New installation (web)

      1. Checkout integration master and do a fresh install using web interface.
      2. You will be asked to enter information about admin user and then front page settings
      3. After that you should be redirected to the registration page that says "Complete your registration"
      4. Navigate away from it (or click "Skip")
      5. Make sure that you can access Site administration tree

      Test 4. New installation (CLI)

      1. Checkout integration master and do a fresh install using CLI
      2. Login as admin
      3. As soon as you go to the "Site administration" you should be redirected to "Complete your registration" page

      Before MDLSITE-5228 is merged into moodle.net this step will fail.
      This is also a reason why there are no tests yet testing actual registration with different emails

      Show
      For all tests you need a domain available from internet. You will need multiple sites that you will install and upgrade. Use different URLs for sites unless test asks to register new site at the same address. Test 1. Upgrade of registered site (CLI) Install a site with a stable moodle version Create a manager user Register it (Site administration > Registration) Upgrade to integration master using CLI Login as a manager Make sure you can browse "Site administration" without problems Login as admin You should be redirected to the registration form (from /index.php , /admin/index.php, /admin/search.php but not from other pages) Registration form should say "Registration information has been changed. Please confirm it using the 'Update registration' button.", the "More information" should be expanded, the new fields highlighted with yellow ("Updates about Moodle news and features" and Mobile info) Do not update registration yet Check that this form and highlighting looks ok in both Clean and Boost Run scheduled task "Site registration" ( /admin/tool/task/schedule_task.php?task=core\task\registration_cron_task ) - you should see a message that registration was not updated Go to /admin/search.php Update registration manually Make sure you are now on /admin/search.php and now it works Run "Site registration" scheduled task again, it should update the registration Test 2. Upgrade of registered site (web) Install a site with a stable moodle version Register it (Site administration > Registration) Upgrade to integration master using web interface Upgrade should proceed as usual, you should be offered the new settings to confirm After you confirm new settings you should be redirected to the registration form that asks you to update new data ( do not update yet ) Run cron in CLI - it should run properly (not saying that "upgrade is pending"). However the site registration task should not run (this was already tested in test1) Go back to the browser and submit the registration form You should now be redirected to the functional /admin/index.php Test 3. Upgrade of unregistered site Install a site with a stable moodle version Upgrade to integration master using CLI Login as admin Go to "Site administration" (both /admin/index.php and /admin/search.php) You should NOT be redirected to registration page Test 3. New installation (web) Checkout integration master and do a fresh install using web interface. You will be asked to enter information about admin user and then front page settings After that you should be redirected to the registration page that says "Complete your registration" Navigate away from it (or click "Skip") Make sure that you can access Site administration tree Test 4. New installation (CLI) Checkout integration master and do a fresh install using CLI Login as admin As soon as you go to the "Site administration" you should be redirected to "Complete your registration" page Before MDLSITE-5228 is merged into moodle.net this step will fail. This is also a reason why there are no tests yet testing actual registration with different emails
    • 3.4 Sprint 5

      1. Simplify registration form:
        • site name and description should not be required,
        • remove geolocation, postal address, phone, admin name, etc
        • reword some strings
        • collapse information that is sent to moodle.net so that form fits on one page
      2. Mailing lists:
        • split current list into security and communication subscriptions
        • allow to specify different email addresses for both lists
      3. add registration data versioning, during upgrade ask admin to confirm the new data in the registration form (if the site was previously registered), suspend automatic update until manually confirmed
      4. show registration form as the last step of the installation

            marina Marina Glancy
            marina Marina Glancy
            Adrian Greeve Adrian Greeve
            David Monllaó David Monllaó
            Ryan Wyllie Ryan Wyllie
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

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