0

When creating a new user over api - this works fine when there are not user->fields with required fields present. However, as soon as you mark a field as required - you must include that item in the json with a value.

In my case - I have a radio button that I am using for Terms Of Service. The user must set this value to 1 (Agreed) before being able to access the rest of the site.

I have 'Required'=yes, 'Editable In'=Site

With these settings - the Admin is not required to set these values in the admin area when creating new users - so I would think that we would want the same thing with the API - if 'Editable In'=Site - then don't enforce this field from being set.

I believe this to be a bug. Thoughts? Work-Arounds?

API RESPONSE:

    {
    "errors": [
        {
            "title": "Invalid field: I have read and agree with the Terms Of Service (TOS)"
        }
    ]
}

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.