Docs: Improve the usefulness, accuracy, and syntax of the `register_post_type()` DocBlock summary and description.

See #32246.

Built from https://develop.svn.wordpress.org/trunk@37882


git-svn-id: http://core.svn.wordpress.org/trunk@37823 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
Drew Jaynes 2016-06-28 06:27:32 +00:00
parent f5bf3676b1
commit 9ef5fb0a17
2 changed files with 12 additions and 5 deletions

View File

@ -882,11 +882,18 @@ function get_post_types( $args = array(), $output = 'names', $operator = 'and' )
}
/**
* Register a post type. Do not use before init.
* Registers a post type.
*
* A function for creating or modifying a post type based on the
* parameters given. The function will accept an array (second optional
* parameter), along with a string for the post type name.
* Note: Post type registrations should not be hooked before the
* {@see 'init'} action. Also, any taxonomy connections should be
* registered via the `$taxonomies` argument to ensure consistency
* when hooks such as {@see 'parse_query'} or {@see '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.
*
* @since 2.9.0
* @since 3.0.0 The `show_ui` argument is now enforced on the new post screen.

View File

@ -4,7 +4,7 @@
*
* @global string $wp_version
*/
$wp_version = '4.6-alpha-37881';
$wp_version = '4.6-alpha-37882';
/**
* Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.