I ended up using something like this: function filter_where( $where=”” ) { global $post, $prev_next; $the_ID = $post->ID; $where .= ” AND wp_posts.ID “; $where .= $prev_next==’next’ ? “< $the_ID” : “> $the_ID”; return $where; } add_filter( ‘posts_where’, ‘filter_where’ ); $nextProjQuery = new WP_Query( $filtered_query_args ); remove_filter( ‘posts_where’, ‘filter_where’ );
The post_excerpt column is a string and is not filterable using “IS NOT NULL” . To query for an empty string you can use the != operator. function posts_where_excerpt_not_empty( $where ) { $where .= ” AND post_excerpt != ” “; return $where; } Also get_posts suppresses filters by default so you will need to call … Read more
Well I managed to solve this sort of… The answer was to use separate search input boxes for each custom field being searched. Here is my working solution if anyone ever stumbles across this. function display_all_products() { global $term; $term = trim(strip_tags($_POST[‘s’])); $refnoterm = trim(strip_tags($_POST[‘ref’])); $yrterm = trim(strip_tags($_POST[‘yr’])); if(!empty($_POST[‘s’]) || !empty($_POST[‘ref’]) || !empty($_POST[‘yr’])) { if(!empty($_POST[‘s’])) … Read more
Think about your query. You are asking that $wpdb->postmeta.meta_key be both “foo” and “bar”. That will never happen. If you ran this in a context where you’d get to read MySQL debugging data (PhpMyAdmin’s SQL console will do this) you would probably see a warning about an “impossible where clause”. You need to JOIN on … Read more
You want to make sure you’re only messing with the main query and not subsequent queries called from a plugin or in a template on the search page. In other words… if( !is_admin() && $query->is_search ) { should be if( !is_admin() && $query->is_search && $query->is_main_query() ) { See http://codex.wordpress.org/Function_Reference/is_main_query
After some hard work and research, I finally came up with this working solution. Please feel free to improve on this code and post an alternative answer. For some reason, the query seems to be running more than once (three to four times in my case). Here, I am making use of three hooks, posts_search, … Read more
Well, after trying different things, I came up with the following. When we use posts_join there is no need to add the prefix $wpdb-> plus the table being queried. We just need the column name. In this case, we just need name and taxonomy, like this: BEFORE $where .= ” OR ($wpdb->term_taxonomy.taxonomy IN (‘category’) AND … Read more
I was afraid you wanted that one. You can’t really do that. Follow the link for some workarounds. You could also set a variable or a constant in functions.php, or create a theme option for this. Then use that in your function. function smbd_cats_by_days ($where=””) { // global $days_limit; // if a variable // $days_limit … Read more
Here is a rough outline of how you’d go about making a UNION work with WP_Query. add_filter( ‘posts_request’, function ($clauses) { $clauses = str_replace(‘SQL_CALC_FOUND_ROWS’,”,$clauses,$scfr); $scfr = (0 < $scfr) : ‘SQL_CALC_FOUND_ROWS’ : ”; $clause2 = $clauses; // manipulate this return “SELECT {$scfr} u.* FROM (({$clauses}) UNION ({$clause2})) as u”; }, 1, 2 ); Set up … Read more
You can set your own custom query vars in a query, then use that value to set a class variable that you later read in the filter: class WPA69844_where { var $days; public function __construct(){ add_action( ‘parse_query’, array( $this, ‘parse_query’ ) ); } public function parse_query( $query ) { if( isset( $query->query_vars[‘my_days_var’] ) ): $this->days … Read more