[wp-trac] [WordPress Trac] #27043: tax_query limited from 3.6 to 3.7

[WordPress Trac]

#27043: tax_query limited from 3.6 to 3.7
-------------------------------+------------------------------
 Reporter:  AdamCapriola       |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Taxonomy           |     Version:  3.8.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by AdamCapriola):

 Replying to [comment:1 helen]:
 > What does "stopped working" mean? You get incorrect results, no results,
 no response at all? Getting any errors anywhere, perhaps something like a
 memory limit or even taking down MySQL? And is the generated SQL the same
 between the two?
 >
 > For what it's worth, I've taken down MySQL going too far with tax
 queries that need to be transformed - worked around it by using
 `term_taxonomy_id` instead.
 By "stopped working" I mean that no results are returned (I get the "no
 search results" text). Prior to 3.7, results were returned as expected.
 (Sorry for not being clearer about that!)

 I am not getting any errors as far as I know. MySQL isn't being taken
 down, I don't think (that's happened to me before, but not with the
 queries I'm testing, which are relatively simple and have worked fine in
 the past). I will have to get back to you on whether the SQL being
 generated by the two is the same (I'll need to set up sandbox dev sites
 when I have some time).

 Replying to [comment:2 wonderboymusic]:
 > what is `WP_Query::__set_state()`?
 I'm not exactly sure to be honest, that's was part of what spit out when I
 added `var_export($query);` before `return $query;` in the
 `ac_filter_search` function.

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