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

reCAPTCHA should be moved below custom profile fields during self registration

    XMLWordPrintable

Details

    • MOODLE_28_STABLE
    • MOODLE_29_STABLE
    • master_MDL-49638
    • Hide

      1. Activate self-registration & configure reCAPTCHA.
      2. Create a custom profile field.
      3. Log out & go to the signup page.
      Expected result: The reCAPTCHA should appear below the custom profile fields on the signup page.
      Regression test

      1. Ensure that you cannot create an account if you fill in the captcha incorrectly or leave it blank
      2. Ensure that you can successfully create an account if you fill in the captcha correctly
      Show
      1. Activate self-registration & configure reCAPTCHA. 2. Create a custom profile field. 3. Log out & go to the signup page. Expected result: The reCAPTCHA should appear below the custom profile fields on the signup page. Regression test Ensure that you cannot create an account if you fill in the captcha incorrectly or leave it blank Ensure that you can successfully create an account if you fill in the captcha correctly

    Description

      The reCAPTCHA field should be shown below the custom profile fields section on the sign up page.

      Currently, the reCAPTCHA field shows up directly below the "More details" section, but I believe we forgot to take the custom profile fields into account.

      If custom profile fields are defined, they appear below the reCAPTCHA on the sign up page. This looks really odd, especially when the custom fields are required.

      Attachments

        Issue Links

          Activity

            People

              icefresh Mike
              icefresh Mike
              John Okely John Okely
              Dan Poltawski Dan Poltawski
              Mark Nelson Mark Nelson
              Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                11/May/15