[wp-trac] [WordPress Trac] #22816: Multisite WP_Query

[WordPress Trac]

#22816: Multisite WP_Query
-----------------------------+------------------------------
 Reporter:  ciapci           |       Owner:
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Multisite        |     Version:
 Severity:  major            |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------
Changes (by ciapci):

 * cc: ciapci (added)
 * status:  new => closed


Comment:

 Replying to [comment:2 wonderboymusic]:
 > Pretty much everyone who builds something like this ends up making a
 join table that has post_ids and blog_ids or makes a bunch of requests,
 smashes them together, and then stores blog_id, post_id, post_date (or any
 relevant field you want to sort on) in memory or in a table so that they
 can paginate.
 >
 > The idea you propose is definitely a good one but probably doesn't jive
 with our super-weird schema. I did this exact thing on eMusic for tag
 archives, here is some relevant code:
 https://gist.github.com/84da29af561229357f07

 Yep, you are correct too, everybody's $wpdb-ing everything they can so
 that they can get a "close enough" scenario to the desired result I
 mentioned above. But let's be serious, that is not a solution, that is not
 even close to being fully compatible with wordpress and a lot os stuff is
 not going to work with those queries because of that. I've seen the
 closest thing to a solution here:
 https://github.com/ericandrewlewis/WP_Query_Multisite , but that script is
 implemented a little shallow, it does not work properly, but is an
 interesting approach to making things done. It's a start. Still, this
 feature is needed and I'm not seeing it pop out on it's own anytime
 soon,and so I wrote about it here...

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