Opened 11 hours ago
Last modified 37 minutes ago
#64153 new defect (bug)
REST API: 403 error occur when resolving or reopening note
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | 6.9 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Editor | Keywords: | |
| Focuses: | Cc: |
Description (last modified by )
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 here is still necessary.
Change History (4)
#4
in reply to:
↑ 3
@
37 minutes ago
Replying to wildworks:
Strangely, this issue is reproducible in the release version of Beta 1, but it does not occur when building the
wordpress-developrepository locally. The problem might have already been fixed in the trunk. I'd like to test it again once Beta2 is released.
I came to report this same problem and had the same findings as @wildworks.
Strangely, this issue is reproducible in the release version of Beta 1, but it does not occur when building the
wordpress-developrepository locally. The problem might have already been fixed in the trunk. I'd like to test it again once Beta2 is released.