Experiment: Update view content types actions#78159
Merged
Merged
Conversation
|
Size Change: -132 B (0%) Total Size: 7.93 MB 📦 View Changed
ℹ️ View Unchanged
|
Mamaduka
approved these changes
May 11, 2026
Member
Mamaduka
left a comment
There was a problem hiding this comment.
I think ordering in the actions dropdown needs some adjustments, but otherwise this looks good.
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Complementary to: #78157
This PR makes the view terms/posts actions non-primary and prioritizes the post type's
view_itemslabel if set. I don't think it's worth it to convert this action into a hook to get the label from the store and handle cache invalidations ourselves, so I added the plain JS fallback forhierarchicalpost types likeget_post_type_labelsdoes.Testing instructions
Content typesexperiment.Settings → Content typesand create a post type and also clickauto-fill labelsin the labels card.