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

Web Services not failing when there are empty required custom user profile fields

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.4, 3.2.1, 3.3
    • Fix Version/s: 3.1.5, 3.2.2
    • Component/s: User management
    • Labels:
    • Testing Instructions:
      Hide
      1. Enable Mobile services on the site
      2. Access using a non-admin account via the mobile app to the site (don't do anything more)
      3. As an admin, define a required custom user profile field.
      4. Go back to the app, try to browse to a course, you should see a "User not fully setup" exception.
      Show
      Enable Mobile services on the site Access using a non-admin account via the mobile app to the site (don't do anything more) As an admin, define a required custom user profile field. Go back to the app, try to browse to a course, you should see a "User not fully setup" exception.
    • Affected Branches:
      MOODLE_31_STABLE, MOODLE_32_STABLE, MOODLE_33_STABLE
    • Fixed Branches:
      MOODLE_31_STABLE, MOODLE_32_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-58071-master

      Description

      The changes MDL-46946 are affecting Web Services, in Web you can't do anything if you have an empty required field, but via Web Services you can retrieve any content and browse the full site via the Mobile app.

      The Mobile app is able to handle the usernotfullysetup exception, if is returned by a Web Service we display a warning to the user and open the site in a web browser so the user can fill the missing required profile.
      This is currently working for the core required profile fields so it should work the same for the custom profile fields ones.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                13/Mar/17