taxonomy-controls.js: Change REST context to "view" when fetching taxonomy terms. #43274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
taxonomy-controls.js: Change REST context to "view" when fetching taxonomy terms.
Why?
When the query-loop block is used for a post type and a custom taxonomy exists but
edit_terms
permission isn't granted,the following request is issued
/wp-json/wp/v2/my_taxonomy?per_page=100&context=
edit
resulting in a 403 and keeping thetaxonomy selector to appear although it's just a read operation on terms.
How?
Changing
getEntityRecords( 'taxonomy', slug, termsQuery );
to passcontext=view
Testing Instructions
post
having particular permissions:Somehow related
Not unlike #37368 or #33569 and related to #33003 / #37489