[wp-trac] [WordPress Trac] #44648: User creation even though an error is thrown

[WordPress Trac]

#44648: User creation even though an error is thrown
------------------------------------------+---------------------
 Reporter:  apermo                        |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  5.0
Component:  REST API                      |     Version:  4.9.7
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:
------------------------------------------+---------------------
Description changed by SergeyBiryukov:

Old description:

> I just had an issue, the issue itself pretty mush doubles like this issue
> https://core.trac.wordpress.org/ticket/40889
>
> When creating a new account including a (registered) custom meta I get
> the following error message.
>
> {{{
> {
> "code":"rest_cannot_update",
> "message":"Sorry, you are not allowed to edit the _r24b_remote_id custom
> field.",
> "data":{"key":"_r24b_remote_id","status":403}
> }
> }}}
>
> But even though throwing an error, the user is created anyway, but I
> don't get the User ID in return.
>
> Sending the unchanged request a second time will now cause this answer
>
> {{{
> {
> "code":"existing_user_login",
> "message":"Der Benutzername existiert bereits!",
> "data":null
> }
> }}}
>
> So besides the bug from the other ticket.
>
> A nested error like in my case should either make the whole creat process
> fail(or undo the successful first part of the creation) or the error
> message should contain the information that the user was created and only
> the meta field failed.

New description:

 I just had an issue, the issue itself pretty mush doubles like this issue
 #40889

 When creating a new account including a (registered) custom meta I get the
 following error message.

 {{{
 {
 "code":"rest_cannot_update",
 "message":"Sorry, you are not allowed to edit the _r24b_remote_id custom
 field.",
 "data":{"key":"_r24b_remote_id","status":403}
 }
 }}}

 But even though throwing an error, the user is created anyway, but I don't
 get the User ID in return.

 Sending the unchanged request a second time will now cause this answer

 {{{
 {
 "code":"existing_user_login",
 "message":"Der Benutzername existiert bereits!",
 "data":null
 }
 }}}

 So besides the bug from the other ticket.

 A nested error like in my case should either make the whole creat process
 fail(or undo the successful first part of the creation) or the error
 message should contain the information that the user was created and only
 the meta field failed.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44648#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform