register_post_type()

You are here:

register_post_type( string $post_typearray|string $args = array() )

Registers a post type.

Description Description

Note: Post type registrations should not be hooked before the ‘init’ action. Also, any taxonomy connections should be registered via the $taxonomies argument to ensure consistency when hooks such as ‘parse_query’ or ‘pre_get_posts’ are used.

Post types can support any number of built-in core features such as meta boxes, custom fields, post thumbnails, post statuses, comments, and more. See the $supports argument for a complete list of supported features.


Top ↑

Parameters Parameters

$post_type

(string) (Required) Post type key. Must not exceed 20 characters and may only contain lowercase alphanumeric characters, dashes, and underscores. See sanitize_key().

$args

(array|string) (Optional) Array or string of arguments for registering a post type.

  • ‘label’
    (string) Name of the post type shown in the menu. Usually plural. Default is value of $labels[‘name’].
  • ‘labels’
    (array) An array of labels for this post type. If not set, post labels are inherited for non-hierarchical types and page labels for hierarchical ones. See get_post_type_labels() for a full list of supported labels.
  • ‘description’
    (string) A short descriptive summary of what the post type is.
  • ‘public’
    (bool) Whether a post type is intended for use publicly either via the admin interface or by front-end users. While the default settings of $exclude_from_search, $publicly_queryable, $show_ui, and $show_in_nav_menus are inherited from public, each does not rely on this relationship and controls a very specific intention. Default false.
  • ‘hierarchical’
    (bool) Whether the post type is hierarchical (e.g. page). Default false.
  • ‘exclude_from_search’
    (bool) Whether to exclude posts with this post type from front end search results. Default is the opposite value of $public.
  • ‘publicly_queryable’
    (bool) Whether queries can be performed on the front end for the post type as part of parse_request(). Endpoints would include:

    • ?post_type={post_type_key}
    • ?{post_type_key}={single_post_slug}
    • ?{post_type_query_var}={single_post_slug} If not set, the default is inherited from $public.
  • ‘show_ui’
    (bool) Whether to generate and allow a UI for managing this post type in the admin. Default is value of $public.
  • ‘show_in_menu’
    (bool|string) Where to show the post type in the admin menu. To work, $show_ui must be true. If true, the post type is shown in its own top level menu. If false, no menu is shown. If a string of an existing top level menu (eg. ‘tools.php’ or ‘edit.php?post_type=page’), the post type will be placed as a sub-menu of that. Default is value of $show_ui.
  • ‘show_in_nav_menus’
    (bool) Makes this post type available for selection in navigation menus. Default is value of $public.
  • ‘show_in_admin_bar’
    (bool) Makes this post type available via the admin bar. Default is value of $show_in_menu.
  • ‘show_in_rest’
    (bool) Whether to include the post type in the REST API. Set this to true for the post type to be available in the block editor.
  • ‘rest_base’
    (string) To change the base url of REST API route. Default is $post_type.
  • ‘rest_controller_class’
    (string) REST API Controller class name. Default is ‘WP_REST_Posts_Controller’.
  • ‘menu_position’
    (int) The position in the menu order the post type should appear. To work, $show_in_menu must be true. Default null (at the bottom).
  • ‘menu_icon’
    (string) The url to the icon to be used for this menu. Pass a base64-encoded SVG using a data URI, which will be colored to match the color scheme — this should begin with ‘data:image/svg+xml;base64,’. Pass the name of a Dashicons helper class to use a font icon, e.g. ‘dashicons-chart-pie’. Pass ‘none’ to leave div.wp-menu-image empty so an icon can be added via CSS. Defaults to use the posts icon.
  • ‘capability_type’
    (string) The string to use to build the read, edit, and delete capabilities. May be passed as an array to allow for alternative plurals when using this argument as a base to construct the capabilities, e.g. array(‘story’, ‘stories’). Default ‘post’.
  • ‘capabilities’
    (array) Array of capabilities for this post type. $capability_type is used as a base to construct capabilities by default. See get_post_type_capabilities().
  • ‘map_meta_cap’
    (bool) Whether to use the internal default meta capability handling. Default false.
  • ‘supports’
    (array) Core feature(s) the post type supports. Serves as an alias for calling add_post_type_support() directly. Core features include ‘title’, ‘editor’, ‘comments’, ‘revisions’, ‘trackbacks’, ‘author’, ‘excerpt’, ‘page-attributes’, ‘thumbnail’, ‘custom-fields’, and ‘post-formats’. Additionally, the ‘revisions’ feature dictates whether the post type will store revisions, and the ‘comments’ feature dictates whether the comments count will show on the edit screen. A feature can also be specified as an array of arguments to provide additional information about supporting that feature. Example: array( 'my_feature', array( 'field' => 'value' ) ). Default is an array containing ‘title’ and ‘editor’.
  • ‘register_meta_box_cb’
    (callable) Provide a callback function that sets up the meta boxes for the edit form. Do remove_meta_box() and add_meta_box() calls in the callback. Default null.
  • ‘taxonomies’
    (array) An array of taxonomy identifiers that will be registered for the post type. Taxonomies can be registered later with register_taxonomy() or register_taxonomy_for_object_type().
  • ‘has_archive’
    (bool|string) Whether there should be post type archives, or if a string, the archive slug to use. Will generate the proper rewrite rules if $rewrite is enabled. Default false.
  • ‘rewrite’
    (bool|array) Triggers the handling of rewrites for this post type. To prevent rewrite, set to false. Defaults to true, using $post_type as slug. To specify rewrite rules, an array can be passed with any of these keys:

    • ‘slug’
      (string) Customize the permastruct slug. Defaults to $post_type key.
    • ‘with_front’
      (bool) Whether the permastruct should be prepended with WP_Rewrite::$front. Default true.
    • ‘feeds’
      (bool) Whether the feed permastruct should be built for this post type. Default is value of $has_archive.
    • ‘pages’
      (bool) Whether the permastruct should provide for pagination. Default true.
    • ‘ep_mask’
      (const) Endpoint mask to assign. If not specified and permalink_epmask is set, inherits from $permalink_epmask. If not specified and permalink_epmask is not set, defaults to EP_PERMALINK.
  • ‘query_var’
    (string|bool) Sets the query_var key for this post type. Defaults to $post_type key. If false, a post type cannot be loaded at ?{query_var}={post_slug}. If specified as a string, the query ?{query_var_string}={post_slug} will be valid.
  • ‘can_export’
    (bool) Whether to allow this post type to be exported. Default true.
  • ‘delete_with_user’
    (bool) Whether to delete posts of this type when deleting a user. If true, posts of this type belonging to the user will be moved to Trash when then user is deleted. If false, posts of this type belonging to the user will *not* be trashed or deleted. If not set (the default), posts are trashed if post_type_supports(‘author’). Otherwise posts are not trashed or deleted. Default null.
  • ‘_builtin’
    (bool) FOR INTERNAL USE ONLY! True if this post type is a native or “built-in” post_type. Default false.
  • ‘_edit_link’
    (string) FOR INTERNAL USE ONLY! URL segment to use for edit link of this post type. Default ‘post.php?post=%d’.

 

Default value: array()


Top ↑

Return Return

(WP_Post_Type|WP_Error) The registered post type object on success, WP_Error object on failure.


Top ↑

More Information More Information

You can use this function in themes and plugins. However, if you use it in a theme, your post type will disappear from the admin if a user switches away from your theme. See Must Use Plugins If you want to keep your changes e.g. post type, even if you switch between your themes.

Taxonomies Taxonomies

When registering a post type, always register your taxonomies using the taxonomies argument. If you do not, the taxonomies and post type will not be recognized as connected when using filters such as parse_query or pre_get_posts. This can lead to unexpected results and failures.

Even if you register a taxonomy while creating the post type, you must still explicitly register and define the taxonomy using register_taxonomy().

Reserved Post Types Reserved Post Types

The following post types are reserved and are already used by WordPress.

  • post
  • page
  • attachment
  • revision
  • nav_menu_item
  • custom_css
  • customize_changeset
  • oembed_cache
  • user_request
  • wp_block

In addition, the following post types should not be used as they interfere with other WordPress functions.

  • action
  • author
  • order
  • theme

In general, you should always prefix your post types, or specify a custom `query_var`, to avoid conflicting with existing WordPress query variables.

More information: Post Types.

Top ↑

Parameter detail information Parameter detail information

Top ↑

description description

(string) (optional) A short descriptive summary of what the post type is.

 

Default: blank

The only way to read that field is using this code:

$obj = get_post_type_object( 'your_post_type_name' ); 
echo esc_html( $obj->description );

Top ↑

public public

(boolean) (optional) Controls how the type is visible to authors (show_in_nav_menusshow_ui) and readers (exclude_from_searchpublicly_queryable).

 

Default: false
  • true’ – Implies exclude_from_search: falsepublicly_queryable: trueshow_in_nav_menus: true, and show_ui:true. The built-in types attachmentpage, and post are similar to this.
  • false’ – Implies exclude_from_search: truepublicly_queryable: falseshow_in_nav_menus: false, and show_ui: false. The built-in types nav_menu_item and revision are similar to this. Best used if you’ll provide your own editing and viewing interfaces (or none at all).
If no value is specified for exclude_from_searchpublicly_queryableshow_in_nav_menus, or show_ui, they inherit their values from public.

Top ↑

publicly_queryable publicly_queryable

(boolean) (optional) Whether queries can be performed on the front end as part of parse_request().

 

Default: value of public argument
Note: The queries affected include the following (also initiated when rewrites are handled)

 

  •  ?post_type={post_type_key}
  •  ?{post_type_key}={single_post_slug}
  •  ?{post_type_query_var}={single_post_slug}
Note: If query_var is empty, null, or a boolean FALSE, WordPress will still attempt to interpret it (4.2.2) and previews/views of your custom post will return 404s.

Top ↑

show_ui show_ui

(boolean) (optional) Whether to generate a default UI for managing this post type in the admin.

 

Default: value of public argument
  • ‘false’ – do not display a user-interface for this post type
  • ‘true’ – display a user-interface (admin panel) for this post type
Note: _built-in post types, such as post and page, are intentionally set to false.

Top ↑

show_in_nav_menus show_in_nav_menus

(boolean) (optional) Whether post_type is available for selection in navigation menus.

 

Default: value of public argument

Top ↑

show_in_menu show_in_menu

(boolean or string) (optional) Where to show the post type in the admin menu. show_ui must be true.

 

Default: value of show_ui argument
  • ‘false’ – do not display in the admin menu
  • ‘true’ – display as a top level menu
  • ‘some string’ – If an existing top level page such as ‘tools.php’ or ‘edit.php?post_type=page’, the post type will be placed as a sub menu of that.
Note: When using ‘some string’ to show as a submenu of a menu page created by a plugin, this item will become the first submenu item, and replace the location of the top-level link. If this isn’t desired, the plugin that creates the menu page needs to set the add_action priority for admin_menu to 9 or lower.
Note: As this one inherits its value from show_ui, which inherits its value from public, it seems to be the most reliable property to determine, if a post type is meant to be publicly useable. At least this works for _builtin post types and only gives back post and page.

Top ↑

show_in_admin_bar show_in_admin_bar

(boolean) (optional) Whether to make this post type available in the WordPress admin bar.

 

Default: value of the show_in_menu argument

Top ↑

capability_type capability_type

(string or array) (optional) The string to use to build the read, edit, and delete capabilities. May be passed as an array to allow for alternative plurals when using this argument as a base to construct the capabilities, e.g. array(‘story’, ‘stories’) the first array element will be used for the singular capabilities and the second array element for the plural capabilities, this is instead of the auto generated version if no array is given which would be “storys”. The ‘capability_type’ parameter is used as a base to construct capabilities unless they are explicitly set with the ‘capabilities’ parameter. It seems that `map_meta_cap` needs to be set to false or null, to make this work (see note 2 below).

 

Default: “post”
Example with “book” or “array( ‘book’, ‘books’ )” value, it will generate the 7 capabilities equal to set capabilities parameter to this :
'capabilities' => array(
  'edit_post'          => 'edit_book', 
  'read_post'          => 'read_book', 
  'delete_post'        => 'delete_book', 
  'edit_posts'         => 'edit_books', 
  'edit_others_posts'  => 'edit_others_books', 
  'publish_posts'      => 'publish_books',       
  'read_private_posts' => 'read_private_books', 
  'create_posts'       => 'edit_books', 
),
Note 1: The “create_posts” capability correspond to “edit_books” so it become equal to “edit_posts”.
Note 2: See capabilities note 2 about meta capabilities mapping for custom post type.
You can take a look into the $GLOBALS['wp_post_types']['your_cpt_name'] array, then you’ll see the following:
[cap] => stdClass Object
	(
		// Meta capabilities
		[edit_post] => edit_book
		[read_post] => read_book
		[delete_post] => delete_book

		// Primitive capabilities used outside of map_meta_cap():
		[edit_posts] => edit_books
		[edit_others_posts] => edit_others_books
		[publish_posts] => publish_books
		[read_private_posts] => read_private_books

		// Primitive capabilities used within map_meta_cap():
		[create_posts] => edit_books
	)
Some of the capability types that can be used (probably not exhaustive list):

 

  • post (default)
  • page
These built-in types cannot be used:

 

  • attachment
  • mediapage
Note 3: If you use capabilities parameter, capability_type complete your capabilities.

Top ↑

capabilities capabilities

(array) (optional) An array of the capabilities for this post type.

 

Default: capability_type is used to construct
By default, seven keys are accepted as part of the capabilities array:

 

  • edit_post, read_post, and delete_post – These three are meta capabilities, which are then generally mapped to corresponding primitive capabilities depending on the context, for example the post being edited/read/deleted and the user or role being checked. Thus these capabilities would generally not be granted directly to users or roles.
  • edit_posts – Controls whether objects of this post type can be edited.
  • edit_others_posts – Controls whether objects of this type owned by other users can be edited. If the post type does not support an author, then this will behave like edit_posts.
  • publish_posts – Controls publishing objects of this post type.
  • read_private_posts – Controls whether private objects can be read.
Note 1: those last four primitive capabilities are checked in core in various locations.
There are also eight other primitive capabilities which are not referenced directly in core, except in map_meta_cap(), which takes the three aforementioned meta capabilities and translates them into one or more primitive capabilities that must then be checked against the user or role, depending on the context. These additional capabilities are only used in map_meta_cap(). Thus, they are only assigned by default if the post type is registered with the ‘map_meta_cap’ argument set to true (default is false).

 

  • read – Controls whether objects of this post type can be read.
  • delete_posts – Controls whether objects of this post type can be deleted.
  • delete_private_posts – Controls whether private objects can be deleted.
  • delete_published_posts – Controls whether published objects can be deleted.
  • delete_others_posts – Controls whether objects owned by other users can be can be deleted. If the post type does not support an author, then this will behave like delete_posts.
  • edit_private_posts – Controls whether private objects can be edited.
  • edit_published_posts – Controls whether published objects can be edited.
  • create_posts – Controls whether new objects can be created
Note 2: In fact, when some user have a role with just the post type capabilies it isn’t enough for create new object… It’s because meta capabilities for custom post types were not being automatically mapped, so we couldn’t have granular control over permissions. To map meta capabilities for custom post types we can use map_meta_cap hook as it’s explain here : http://justintadlock.com/archives/2010/07/10/meta-capabilities-for-custom-post-types.

If you assign a 'capability_type' and then take a look into the $GLOBALS['wp_post_types']['your_cpt_name'] array, then you’ll see the following:

[cap] => stdClass Object
(
	// Meta capabilities

	[edit_post]		 => "edit_{$capability_type}"
	[read_post]		 => "read_{$capability_type}"
	[delete_post]		 => "delete_{$capability_type}"

	// Primitive capabilities used outside of map_meta_cap():

	[edit_posts]		 => "edit_{$capability_type}s"
	[edit_others_posts]	 => "edit_others_{$capability_type}s"
	[publish_posts]		 => "publish_{$capability_type}s"
	[read_private_posts]	 => "read_private_{$capability_type}s"

	// Primitive capabilities used within map_meta_cap():

	[read]                   => "read",
	[delete_posts]           => "delete_{$capability_type}s"
	[delete_private_posts]   => "delete_private_{$capability_type}s"
	[delete_published_posts] => "delete_published_{$capability_type}s"
	[delete_others_posts]    => "delete_others_{$capability_type}s"
	[edit_private_posts]     => "edit_private_{$capability_type}s"
	[edit_published_posts]   => "edit_published_{$capability_type}s"
	[create_posts]           => "edit_{$capability_type}s"
)

Note the “s” at the end of plural capabilities.

Top ↑

map_meta_cap map_meta_cap

(boolean) (optional) Whether to use the internal default meta capability handling.

 

Default: null
Note: If set it to false then standard admin role can’t edit the posts types. Then the edit_post capability must be added to all roles to add or edit the posts types.

Top ↑

hierarchical hierarchical

(boolean) (optional) Whether the post type is hierarchical (e.g. page). Allows Parent to be specified. The ‘supports’ parameter should contain ‘page-attributes’ to show the parent select box on the editor page.

 

Default: false
Note: this parameter was intended for Pages. Be careful when choosing it for your custom post type – if you are planning to have very many entries (say – over 2-3 thousand), you will run into load time issues. With this parameter set to true WordPress will fetch all IDs of that particular post type on each administration page load for your post type. Servers with limited memory resources may also be challenged by this parameter being set to true.

Top ↑

supports supports

(array/boolean) (optional) An alias for calling add_post_type_support() directly. As of 3.5, boolean false can be passed as value instead of an array to prevent default (title and editor) behavior.

 

Default: title and editor
  • ‘title’
  • ‘editor’ (content)
  • ‘author’
  • ‘thumbnail’ (featured image, current theme must also support post-thumbnails)
  • ‘excerpt’
  • ‘trackbacks’
  • ‘custom-fields’
  • ‘comments’ (also will see comment count balloon on edit screen)
  • ‘revisions’ (will store revisions)
  • ‘page-attributes’ (menu order, hierarchical must be true to show Parent option)
  • ‘post-formats’ add post formats, see Post Formats
Note: When you use custom post type that use thumbnails remember to check that the theme also supports thumbnails or use add_theme_support function.

Top ↑

register_meta_box_cb register_meta_box_cb

(callback ) (optional) Provide a callback function that will be called when setting up the meta boxes for the edit form. The callback function takes one argument $post, which contains the WP_Post object for the currently edited post. Do remove_meta_box() and add_meta_box() calls in the callback.

 

Default: None

Top ↑

taxonomies taxonomies

(array) (optional) An array of registered taxonomies like category or post_tag that will be used with this post type. This can be used in lieu of calling register_taxonomy_for_object_type() directly. Custom taxonomies still need to be registered with register_taxonomy().

 

Default: no taxonomies

Top ↑

has_archive has_archive

(boolean or string) (optional) Enables post type archives. Will use $post_type as archive slug by default.

 

Default: false
Note: Will generate the proper rewrite rules if rewrite is enabled. Also use rewrite to change the slug used. If string, it should be translatable.

Top ↑

rewrite rewrite

(boolean or array) (optional) Triggers the handling of rewrites for this post type. To prevent rewrites, set to false.

 

Default: true and use $post_type as slug
$args array

 

  • 'slug' => string Customize the permalink structure slug. Defaults to the $post_type value. Should be translatable.
  • 'with_front' => bool Should the permalink structure be prepended with the front base. (example: if your permalink structure is /blog/, then your links will be: false->/news/, true->/blog/news/). Defaults to true
  • 'feeds' => bool Should a feed permalink structure be built for this post type. Defaults to has_archive value.
  • 'pages' => bool Should the permalink structure provide for pagination. Defaults to true
  • 'ep_mask' => const As of 3.4 Assign an endpoint mask for this post type. For more info see Rewrite API/add_rewrite_endpoint, and Make WordPress Plugins summary of endpoints.
    • If not specified, then it inherits from permalink_epmask(if permalink_epmask is set), otherwise defaults to EP_PERMALINK.
Note: If registering a post type inside of a plugin, call flush_rewrite_rules() in your activation and deactivation hook (see Flushing Rewrite on Activation below). If flush_rewrite_rules() is not used, then you will have to manually go to Settings > Permalinks and refresh your permalink structure before your custom post type will show the correct structure.

Top ↑

query_var query_var

(boolean or string) (optional) Sets the query_var key for this post type.

 

Default: true – set to $post_type
  • ‘false’ – Disables query_var key use. A post type cannot be loaded at /?{query_var}={single_post_slug}
  • ‘string’ – /?{query_var_string}={single_post_slug} will work as intended.
Note: The query_var parameter has no effect if the ‘publicly_queryable’ parameter is set to false. query_var adds the custom post type’s query var to the built-in query_vars array so that WordPress will recognize it. WordPress removes any query var not included in that array.
If set to true it allows you to request a custom posts type (book) using this: example.com/?book=life-of-pi
If set to a string rather than true (for example ‘publication’), you can do: example.com/?publication=life-of-pi

Top ↑

can_export can_export

(boolean) (optional) Can this post_type be exported.

 

Default: true

Top ↑

delete_with_user delete_with_user

(boolean) (optional) Whether to delete posts of this type when deleting a user. If true, posts of this type belonging to the user will be moved to trash when then user is deleted. If false, posts of this type belonging to the user will not be trashed or deleted. If not set (the default), posts are trashed if post_type_supports('author'). Otherwise posts are not trashed or deleted.

 

Default: null

Top ↑

show_in_rest show_in_rest

(boolean) (optional) Whether to expose this post type in the REST API. Must be true to enable the Gutenberg editor.

 

Default: false

Top ↑

rest_base rest_base

(string) (optional) The base slug that this post type will use when accessed using the REST API.

 

Default: $post_type

Top ↑

rest_controller_class rest_controller_class

(string) (optional) An optional custom controller to use instead of WP_REST_Posts_Controller. Must be a subclass of WP_REST_Controller.

 

Default: WP_REST_Posts_Controller

Top ↑

_builtin _builtin

(boolean) (not for general use) Whether this post type is a native or “built-in” post_type. Note: this entry is for documentation – core developers recommend you don’t use this when registering your own post type

 

Default: false
  • ‘false’ – default this is a custom post type
  • ‘true’ – this is a built-in native post type (post, page, attachment, revision, nav_menu_item)

Top ↑

Flushing Rewrite on Activation Flushing Rewrite on Activation

To get permalinks to work when you activate the plugin use the following example, paying attention to how my_cpt_init() is called in the register_activation_hook callback:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
add_action( 'init', 'my_cpt_init' );
function my_cpt_init() {
    register_post_type( ... );
}
 
register_activation_hook( __FILE__, 'my_rewrite_flush' );
function my_rewrite_flush() {
    // First, we "add" the custom post type via the above written function.
    // Note: "add" is written with quotes, as CPTs don't get added to the DB,
    // They are only referenced in the post_type column with a post entry,
    // when you add a post of this CPT.
    my_cpt_init();
 
    // ATTENTION: This is *only* done during plugin activation hook in this example!
    // You should *NEVER EVER* do this on every page load!!
    flush_rewrite_rules();
}

For themes, you’ll need to use the after_switch_theme hook instead. Like so:

1
2
3
4
5
6
7
8
9
10
add_action( 'init', 'my_cpt_init' );
function my_cpt_init() {
    register_post_type( ... );
}
 
add_action( 'after_switch_theme', 'my_rewrite_flush' );
function my_rewrite_flush() {
    my_cpt_init();
    flush_rewrite_rules();
}

 

Note that although the $public attribute is optional, the inputs passed to the register_post_type() function are exactly what is queried by the get_post_types() function. So if you verbosely set the equivalent options for publicly_queriableshow_uishow_in_nav_menus, and exclude_from_search, this will not be handled the same as if you had set the $public attribute. See bug 18950.


Top ↑

Source Source

File: wp-includes/post.php

1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
function register_post_type( $post_type, $args = array() ) {
    global $wp_post_types;
 
    if ( ! is_array( $wp_post_types ) ) {
        $wp_post_types = array();
    }
 
    // Sanitize post type name.
    $post_type = sanitize_key( $post_type );
 
    if ( empty( $post_type ) || strlen( $post_type ) > 20 ) {
        _doing_it_wrong( __FUNCTION__, __( 'Post type names must be between 1 and 20 characters in length.' ), '4.2.0' );
        return new WP_Error( 'post_type_length_invalid', __( 'Post type names must be between 1 and 20 characters in length.' ) );
    }
 
    $post_type_object = new WP_Post_Type( $post_type, $args );
    $post_type_object->add_supports();
    $post_type_object->add_rewrite_rules();
    $post_type_object->register_meta_boxes();
 
    $wp_post_types[ $post_type ] = $post_type_object;
 
    $post_type_object->add_hooks();
    $post_type_object->register_taxonomies();
 
    /**
     * Fires after a post type is registered.
     *
     * @since 3.3.0
     * @since 4.6.0 Converted the `$post_type` parameter to accept a `WP_Post_Type` object.
     *
     * @param string       $post_type        Post type.
     * @param WP_Post_Type $post_type_object Arguments used to register the post type.
     */
    do_action( 'registered_post_type', $post_type, $post_type_object );
 
    return $post_type_object;
}


Top ↑

Changelog Changelog

Changelog
VersionDescription
5.3.0The supports argument will now accept an array of arguments for a feature. .
4.7.0Introduced show_in_restrest_base and rest_controller_class arguments to register the post type in REST API.
4.6.0Post type object returned is now an instance of WP_Post_Type.
4.4.0The show_ui argument is now enforced on the post type listing screen and post editing screen.
3.0.0The show_ui argument is now enforced on the new post screen.
2.9.0Introduced.
Was this article helpful?
Dislike 0
Views: 1

Cart

Log in

Create an Account
Back to Top