Introduce new filter "render_block_core_navigation_link_allowed_post_status" #63181
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.
This PR introduces a new Filter for rendering the "Navigation Link"-Block to whitelist post_status to not restrict the output to only "public" post_status.
See more information in: #33215
Why?
Since Gutenberg 9.8.0 (see commit: 1936a04 | issue: #27207) the "Navigation Link"-Block limits the output to only "public" post_status.
While it is possible to hook into
WP_Query
and theWP_REST_Post_Search_Handler
viarest_post_search_query
to extend the$query_args
with custompost_status
in the REST Response, the rendering part will still limit topost_status = "publish
.With this new filter
render_block_core_navigation_link_allowed_post_status
it is now possible to also whitelist multiple post_status for rendering in frontend.Testing Instructions
post_status = "private"
.post_status = "private"
and insert