[wp-hackers] Limitations and Patch for WP_Query Taxonomy Stuff

Dion Hulse (dd32) wordpress at dd32.id.au
Wed Dec 30 21:02:37 UTC 2009

On Thu, 31 Dec 2009 03:53:42 +1100, Joe Hoyle <joehoyle at gmail.com> wrote:
> After mulling over that for a while, it got me thinking. Whats the point  
> in even having category__in, and tag__in duplicated in the query class  
> (not to mention category__not_in, category__and, category__slug_in or  
> whatever etc etc...). Why not have this querying by taxonomy (be it  
> categories, tags, manufacturers, companies etc etc) all dealt with by  
> the same code. The only issue then is the annoying difference between  
> tag__in, and the taxonomy name which is post_tag. We have an array of  
> registered taxonomies (post_tag, category, manufacturers) simply check  
> the query vars for an registered taxonomies: *__in, *__not_in,  
> *__slug_in, *__and blah blah blah. This we I can query by any amount of  
> terms in any amount of taxonomies be they custom or "normal".

I have thought the same a few times now.. The only side effect i could  
possibly think of is that the category ones have a bit of proprocessing  
for back compat, to determine what has been passed (int, slug, name,  
who-knows-what) IIRC
Dion Hulse / dd32

  e: contact at dd32.id.au
  msn: msn at d32.id.au
  skype: theonly_dd32
Web: http://dd32.id.au/

More information about the wp-hackers mailing list