[wp-trac] [WordPress Trac] #19471: Support use of custom post types in category and tag archives

[WordPress Trac]

#19471: Support use of custom post types in category and tag archives
--------------------------+-------------------------
 Reporter:  chrisjean     |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Query         |     Version:  3.0
 Severity:  normal        |  Resolution:  maybelater
 Keywords:  has-patch     |     Focuses:
--------------------------+-------------------------

Comment (by mdgl):

 Replying to [comment:37 jorbin]:
 > The above patch is still to automatic.  Despite being a bug to many,
 this has been the default behavior for a number of years and any change to
 the default output would end up being a break in backwards compatibility.

 How would the proposed patch break backwards compatibility?  As far as I
 can see, the patch will do nothing unless the developer has explicitly
 declared that the `category` or `post_tag` be associated with a custom
 post type.  Why would the developer do that?  What behaviour is he/she
 expecting?

 As it stands, if you do make use of the "standard" taxonomies in this way,
 nothing will happen because by default queries will never find any
 matching custom post types.  Why would the developer want that behaviour
 (i.e. associate the taxonomy with a post type but not have any of those
 post types returned on a query for that taxonomy)?

 > The solution, as Nacin alludes to in comment:20 is to bake this into
 register_taxonomy_for_object_type. An additional solution would be needed
 for author pages.

 I don't understand.  Bake what exactly into
 `register_taxonomy_for_object_type()`?

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