[wp-trac] [WordPress Trac] #16025: Page and custom taxonomy query var 404s

[WordPress Trac]

#16025: Page and custom taxonomy query var 404s
--------------------------+------------------
 Reporter:  duck_         |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.1
Component:  Query         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  close         |
--------------------------+------------------

Comment (by acsnaterse):

 As discussed per IRC this could/should be expected behavior, but  I tend
 to disagree for the following reason..

 I understand that this URL says: give me page X which has customtax 'foo'.
 Well, there wasn't page with that customtax 'foo', so the 404 should be
 expected. The problem was that I should use CPT archives. However that
 seems not to be a  working solution,

 http://example/product/ gives me perfectly the 'product' (which is the
 CPT) archive page.

 The reason why I used the customtax GET param was because of some
 filtering. I just want to retrieve the customtax GET param and add it in
 the query_posts args array, so I only get the products that has this 'foo'
 customtax.

 But when I use http://example/product/?customtax=foo, it immediately
 redirects to http://example/customtax/foo which is unwanted for me since I
 want to use the GET params, but also it gives a 404, which is unexpected
 anyway I guess.


 Then the second case: when I want to filter on more customtaxo's it will
 also break (as in: it gives a 404). For example:
 http://example/product/?customtax=foo&customtax2=foo2 gives a 404 too.


 So my first question is: is this all expected behavior? Or should it work
 I expected (without 404 obviously)? And if this is expected behavior, what
 should be the proper way to create such a filter mechanism (with GET
 params) ?

 Second question: if this is expected behavior, should it return a 404, or
 just return no posts? My feeling says (since it's kind of filtering), it
 would return 0 posts.



 PS: again, this all worked in 3.0.3

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16025#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software