[wp-trac] [WordPress Trac] #35848: WordPress 4.4 Handling Custom Taxonomies and Tax Queries Correctly

WordPress Trac noreply at wordpress.org
Sun Feb 21 16:59:24 UTC 2016


#35848: WordPress 4.4 Handling Custom Taxonomies and Tax Queries Correctly
-------------------------------+------------------------------
 Reporter:  vrazer             |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Query              |     Version:  4.4
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by boonebgorges):

 * keywords:   => reporter-feedback


Comment:

 Hi @vrazer - Thanks for the ticket, and welcome to WordPress Trac.

 At a first pass, I'm unable to reproduce the issue. in both 4.3 and 4.4,
 The query `?customtax1=term1&customtax3=term2&customtax2=term4` will query
 for posts that match all of the query params. That is, any post objects
 with *all* of the queried terms. The query is post-type agnostic; when
 `is_tax`, and no `post_type` is provided, the `post_type` list will be
 populated with all post types against which the queried taxonomies are
 registered.

 Can you give more details about your post types, taxonomies, and data?
 I've been testing with a bunch of CPTs and various ways of registering
 taxonomies, but it's possible that I'm misunderstanding your report.
 Specifically, I'm registering CPTs and taxonomies like this:

 {{{
 register_post_type( 'foo', array( 'public' => true ) );
 register_post_type( 'bar', array( 'public' => true ) );

 register_taxonomy( 'tax1', array( 'foo', 'bar' ) );
 register_taxonomy( 'tax2', array( 'foo', 'bar' ) );
 }}}

 and then creating a number of different posts and associating terms with
 them in various combinations. But maybe there's something specific about
 the way you're registering the taxonomies (or something else) that's
 causing this?

 If you're able to bisect to find the specific changeset that caused the
 regression, it would be extremely helpful.

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


More information about the wp-trac mailing list