Create new custom post types directly into the admin

[mickiboy]

For non-technical people, it is easier to create new custom post types directly into the admin, instead of editing the theme file and typing in the code.

[greenshady]

That's what plugins are for. The basic functionality should be in core. For extra features such as an admin interface to create custom post types, a plugin should be made.

[nacin]

Closing as wontfix. What follows is by no means a complete list of reasons:

If this is ever indicated as desired by the core development team, it would be the result of planning sessions and extensive discussion, and would be a blessed task as a major feature for a future release. There's no need to leave this ticket open for when or if that ever happens.

Plugins and themes should be handling custom post type creation. A plugin or theme needs to actually expose them anyway. Additionally, 3.0+ management plugins already exist.

Also, it's extremely easy to create a custom post type. If you have the skills to develop the theme that actually uses a custom post type, you will know enough to be able to register the post type. See also the preceding paragraph.

[kovshenin]

Perhaps the reason would be that custom post types alone are not as good without the ability to add individual custom taxonomy, custom metaboxes and custom edit screen columns. This means that we'll also need an interface for those three.

[lukecavanagh]

I do not see the issue with having an UI for end-users to be able to create custom post types from WP admin or in the Customizer.

Granted there are solid plugin options already like
​https://github.com/pods-framework/pods
​https://github.com/WebDevStudios/custom-post-type-ui

[rmccue]

@lukecavanagh CPTs are registered in code, and are not a data object. The plugins you mentioned change that by registering in code based on data, but this is unlikely to be the approach ever taken by core if we did decide to do it.

Additionally, please don't comment on tickets that have been closed for 7 years. Instead, open a new issue.

[lukecavanagh]

I thought just because a ticket was marked as closed, that it was still okay to comment in it. Opened a new ticket #40484.

[sumitbagthariya16]

#46552 was marked as a duplicate.