[wp-trac] [WordPress Trac] #30892: Renaming Custom Post Types

[WordPress Trac]

#30892: Renaming Custom Post Types
-------------------------------+------------------------------
 Reporter:  eclare             |       Owner:
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  trunk
 Severity:  normal             |  Resolution:
 Keywords:  close              |     Focuses:  administration
-------------------------------+------------------------------

Comment (by mdgl):

 Agreed the terminology of "post type", "content type" and even "post
 format" is all a bit confusing, as is the underlying implementation.
 Before we rush into renaming things, though I think we are still missing
 something.

 I'd like to see us introduce a separate "content type" field to properly
 describe the encoding of the data contained within a post type (i.e. the
 how to interpret "the content"). Presently, the content of all post types
 is assumed to be an messy combination of some kind of HTML with embedded
 shortcodes, "texturised" and "smiley" elements and with special meaning to
 blank lines for `wpautop()`. This "WP-Mush" content type causes much
 confusion as well as numerous problems as hundreds of other bug reports
 will attest.

 If we made the content type for posts explicit (really a MIME type for
 "the content"), we could start to clean up some of this mess, avoid
 confusing users by mangling their content and give more flexibility to
 CPTs to store and display content of their own choosing, even use their
 own custom content editors in the admin tool.

 We would then have the following elements (names could be changed to
 suit):

 * post type = name of the overall information object for administration
 purposes
 * content type = way in which the content is encoded within the post type
 (i.e. MIME type for post content), used to select both editor and display
 pipeline
 * post format = way for themes to interpret the content for display if
 content type is "WP-Mush"

 Sadly the current "mime type" field would need to remain to refer to the
 content type of attachments, even though this would more properly belong
 within the post meta.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30892#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform