[wp-trac] [WordPress Trac] #10667: Integration of Search API into core

[WordPress Trac]

#10667: Integration of Search API into core
----------------------------+-----------------------------------------------
 Reporter:  jshreve         |       Owner:             
     Type:  task (blessed)  |      Status:  new        
 Priority:  normal          |   Milestone:  3.0        
Component:  General         |     Version:  2.9        
 Severity:  normal          |    Keywords:  needs-patch
----------------------------+-----------------------------------------------

Comment(by andy):

 I think I like it better as a filter. I wrote it that way first but I'm
 not sure why I didn't keep it that way.

 Replying to [comment:12 filosofo]:
 > I don't know why you'd want to replace the class in only one place,
 particularly since many themes call query_posts() directly.

 For example, a search plugin could use this. That would probably only want
 to replace/extend the core instance and only when isset($_GET['s']).

 Sometimes you're going to want to ignore the core posts query results so
 you might as well bypass all of WP_Query::get_posts. Heck, why not just
 stub it out in WP::main. That's why I showed up wanting to be able to
 replace or extend these classes.

 While I'm at it, I'm thinking of how to fix wpdb so it can be extended.
 HyperDB is a PITA to keep synced with wpdb. It would be better if it
 extended wpdb.

 So this should be two new tickets then.

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