Content Types: Add post type management#77754
Merged
Conversation
tyxla
added
[Type] Experimental
32 tasks
|
Size Change: +49 kB (+0.63%) Total Size: 7.87 MB 📦 View Changed
ℹ️ View Unchanged
|
|
Flaky tests detected in 9d02036. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/25156451060
|
tyxla
force-pushed
the
add/post-types-management
branch
from
ab9c502 to
ca062fd
Compare
tyxla
force-pushed
the
add/post-types-management
branch
from
ca062fd to
c53bee8
Compare
|
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. |
ntsekouras
reviewed
Apr 29, 2026
ntsekouras
reviewed
Apr 29, 2026
| 'taxonomies', | ||
| 'supports', | ||
| 'public', | ||
| 'hierarchical', |
Contributor
There was a problem hiding this comment.
I feel we need less fields in the general group, but it's fine to land and iterate with the addition of more fields.
ntsekouras
approved these changes
Apr 29, 2026
Contributor
ntsekouras
left a comment
ntsekouras
left a comment
There was a problem hiding this comment.
Thanks! I think this is fine to land as v1 and iterate. It mirrors many of the architectural decisions we have discussed for taxonomies and some of the follow ups will also follow suit, like the REST PR for taxonomies, etc..
It would be good to add the follow ups (in your description) as tasks in the tracking issue.
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
2 participants
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?
Introduces the foundations of user-defined custom post type (CPT) management interface as part of the content types experiment.
Why?
To manage custom post types natively and naturally from the WP admin interface.
Part of #77600
How?
We register a private
wp_user_post_typeCPT holds one record per user-defined post type, with the slug, status, and a JSON-encoded config stored in the standard post fields.Each published record is read on init and registered via
register_post_type()with atightly-validated subset of its config.
A REST insert filter rejects slug collisions with existing post types or other records.
New package -
@wordpress/user-post-typesexposes the form data model, fields, and bulk actions. Same shape as@wordpress/user-taxonomies.New routes -
routes/post-typesandroutes/post-type-editAdditional work or considerations not included in this initial PR:
flush_rewrite_rules()on change ofhas_archive,public, or renaming the CPT slugTesting Instructions
/wp-admin/edit.php?post_type=book. Expect the post type to be registered, the block editor to load for new entries, and the Featured image panel to be available./book/. Expect the archive page to render (after permalink rules update — see known issue below).wp-admin/edit.php?post_type=bookto 404 because the post type is no longer registered.message identifying the collision.
Testing Instructions for Keyboard
Same
Screenshots or screencast
Use of AI Tools
Opus 4.7