[wp-trac] [WordPress Trac] #9674: Better support for custom post types

WordPress Trac wp-trac at lists.automattic.com
Thu Dec 31 00:45:03 UTC 2009


#9674: Better support for custom post types
------------------------------------+---------------------------------------
 Reporter:  wnorris                 |        Owner:  ryan    
     Type:  task (blessed)          |       Status:  reopened
 Priority:  normal                  |    Milestone:  3.0     
Component:  Administration          |      Version:  2.9     
 Severity:  normal                  |   Resolution:          
 Keywords:  has-patch tested early  |  
------------------------------------+---------------------------------------

Comment(by mikeschinkel):

 '''@ryan:''' I just found/read @janeforshort's comments which I'll include
 here:

 ''@janeforshort: Per Ryan's comment, some of the thinking behind using
 'content types' rather than 'post types' as a label is because the end
 user generally thinks of post types in terms of having a different
 template for a specific type of post, like a review, recipe, blog post,
 aside, etc., and doesn't think about it in CMS terms (products, listings,
 etc).''

 I see her point for existing Wordpress sites but honestly think once
 custom post types because more exposed in Wordpress then that point become
 moot.

 I'm pretty sure people don't think much about templates vs. posts, they
 think about reviews, recipes, blog posts, asides, products, listings, etc.
 Once they can go in an create a custom post type called "review",
 "recipe", "product" or "listing" rather than have to create a post
 template that makes a (blog) post behave like one of them then users will
 do that because doing so will provide them more appropriate functionality.

 (BTW, I don't see how a review or a recipe is conceptually any different
 than a product or a listing.  They all have custom attributes that
 identify them separately from a generic post.)

 What's more there will mostly be a one-to-one correspondence between
 custom post types and custom post templates just as there already are
 different templates for each of posts, pages and attachments and for my
 plugin each custom post type gets its own custom post type template.  So
 rather than argue for a new term I really think ''@janeforshort's'' point
 argues to ''keep'' the term "post type" if, as she says, people think in
 terms a "post type" meaning "a different template."; that's exactly the
 association we'll want them to have, i.e.

    ''Using a custom post type equates to using a template for a custom
 type of content''

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9674#comment:76>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list