Member Saving Issues

[bszyman]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.1.1

Bug summary

I'm noticing consistent buggy behavior when editing members in the Umbraco backoffice. Saves will fail with a generic "Unknown Error. Please see the log for more details" message.

I view the log, but don't see any entires out of the ordinary/related.

I notice that this issue also occurs in my v14 websites, too.

Specifics

Url: /umbraco/section/member-management/workspace/member/edit//invariant/view/info

I notice that if I toggle the "Approved" toggle to On, it'll save just as it should, all data is present.

Additionally, if I toggle "Approved" to on, save the member, browse away, and browse back, the toggle will be set back into an Off state again.

I haven't dug into the code, but I suspect that this toggle is required to be true by the backend api instead of allowing both false and true. Can't explain why it's not saving after it's be toggled to On, however.

Steps to reproduce

Navigate to the Members tab
Open a Member
Edit the value of a field and click Save.

Instead of saving, an error will show.

Navigate away and attempt to edit the same user with the same data, but before clicking Save, toggle the Approved toggle to an On state.

The member and data you entered will save successfully.

Expected result / actual result

The On or Off value for the "Approved" toggle in the member editor should persist properly to the database between editing sessions.

The PUT API method that gets called during save should accept false as a valid value for the isApproved field.

I'm in a bit of a cram at the moment, I'll look into this further when I'm freed up and see if I can create a fix and send it in a PR.

[github-actions]

Hi there @bszyman!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂