[wp-trac] [WordPress Trac] #36217: WP_Post_Type class

[WordPress Trac]

#36217: WP_Post_Type class
-------------------------------------------------+-------------------------
 Reporter:  swissspidy                           |       Owner:  swissspidy
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  4.6
Component:  Posts, Post Types                    |     Version:  2.9
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch needs-unit-   |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by flixos90):

 Replying to [comment:23 schlessera]:
 > First of all, if we are rethinking the data structures, I would also
 vote for changing from "Post_<something>" to "Content_<something>", as
 WordPress wants to be a '''Content''' Management System, not only a Blog
 (= '''Post''' Management System).

 I don't think we should change the naming conventions here. Although I see
 your point with the **Content** Management System, to me, "Content" refers
 to something more general as I think that both posts and terms are a kind
 of content. I would rather use a `Content_<something>` for possible
 abstract classes in the future (like `WP_Post_Type` and `WP_Taxonomy`
 being derived from a `WP_Content_Type` for example). However, as we
 decided not to go with abstract classes, at least for this release, I'd
 still like to leave that as a possibility.

 Also, the terminology of posts is widely established in the community and
 a change like that would probably lead to confusion as we cannot change it
 everywhere in the Core code (inconsistency).

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