Notes: Prevent 403 error for low capability users#72767
Conversation
|
Size Change: +35 B (0%) Total Size: 2.37 MB
ℹ️ View Unchanged
|
| const { __experimentalDiscussionSettings } = getSettings(); | ||
| const defaultAvatar = __experimentalDiscussionSettings?.avatarURL; |
There was a problem hiding this comment.
Maybe we should just use a static fallback avatar here, an SVG or something.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Thanks for the review, @t-hamano! |
Co-authored-by: Mamaduka <[email protected]> Co-authored-by: t-hamano <[email protected]>
|
I just cherry-picked this PR to the wp/6.9 branch to get it included in the next release: f7141a1 |
What?
PR updates the
CommentAuthorInfocomponent to avoid403error when trying to fetch site settings for lower capability users.I've also added an early return when the component already receives user data. There's no need to select fallbacks in this case. This also reduces the number of
block-editorstore subscriptions created per note.Testing Instructions
403 Forbiddenerror is logged.Testing Instructions for Keyboard
Same.
Screenshots or screencast