[wp-trac] [WordPress Trac] #36217: WP_Post_Type class
WordPress Trac
noreply at wordpress.org
Tue Jun 7 10:40:15 UTC 2016
#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 schlessera):
> as I think that both posts and terms are a kind of content
In my view, terms are "meta"content, something that qualifies the content
itself. They don't serve any purpose in isolation, only when attached o
real content.
> like WP_Post_Type and WP_Taxonomy being derived from a WP_Content_Type
for example
Conceptually, a `WP_Post_Type` and a `WP_Taxonomy` share very little,
other than that they both have an ID and a name, and that they are both
stored in the same DB. You can attach one to the other (as you can attach
a group to a user), but that does not make them descendents of a same
parent. That's why most CMS systems opt to define these as `leafs` within
the overarching CMS `tree`.
I would think that calling `WP_Taxonomy` a type of `Content` will add to
the confusion about what taxonomies even are and how they are used.
> 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).
Yes, unfortunately, because this leads to the misconception of many people
that WordPress is a blogging platform, and not much more.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36217#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list