[wp-trac] [WordPress Trac] #64153: REST API: 403 error occur when resolving or reopening note

[WordPress Trac]

#64153: REST API: 403 error occur when resolving or reopening note
--------------------------+---------------------
 Reporter:  wildworks     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.9
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------
Description changed by wildworks:

Old description:

> Originally reported on
> https://github.com/WordPress/gutenberg/issues/72690
>
> When resolving or reopening a note, the comment meta `_wp_note_status` is
> updated. This itself works correctly, but a 403 error occurs.
>
> My understanding is that because the meta key has an underscore prefix,
> it is treated as a protected meta key. Therefore, I believe that the
> `auth_callback` that was deleted [https://github.com/WordPress/wordpress-
> develop/pull/10280#discussion_r2433226393 here] is still necessary.

New description:

 Originally reported on https://github.com/WordPress/gutenberg/issues/72690

 When resolving or reopening a note, the comment meta `_wp_note_status` is
 updated. This itself works correctly, but a 403 error occurs with a
 message `Sorry, you are not allowed to edit the _wp_note_status custom
 field.`.

 My understanding is that because the meta key has an underscore prefix, it
 is treated as a protected meta key. Therefore, I believe that the
 `auth_callback` that was deleted [https://github.com/WordPress/wordpress-
 develop/pull/10280#discussion_r2433226393 here] is still necessary.

--

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