Search Results

The main query still pulls in the standard 10 posts, but since I'm not displaying these, I'd like to eliminate the query being made to the database entirely. … I could use pre_get_posts to minimise and reduce the query, but that still leaves me with a very fast query, how do I eliminate it entirely? …

Functions such as is_page_template etc rely on the main query, but we're in a pre_get_posts filter, you don't know if that query has been set yet, or if you're filtering that query or another. … WordPress decides which template is loaded based on the main query. If it's the main query, and is_search is true, then search.php will be loaded. …

Is it a good practice to use wpdb->query() function each time by passing my query to the function instead of using the dedicated functions like insert() and delete() etc? … It takes a table creation query as a parameter, and it has to be formatted in a particular way or it won't work. wpdb->query is inappropriate for creating tables. …

The Problem What you're having problems grasping is "How do I do X?" This isn't a 1 step action, it's a multistep process, and it needs to be broken apart. You don't need to do this: get all the po …

I saw in your original code you completely discard the original main query ( yet another reason query_posts is terrible ). … So if this is your home page, you could do this: function audio_only( $query ) { if ( $query->is_home() && $query->is_main_query() ) { $query->set( 'post_format', 'post-format-audio' ); …

> array( 'quotes' ), ), array( 'taxonomy' => 'post_format', 'field' => 'slug', 'terms' => array( 'post-format-quote' ), ), ), ); $query …

Even if there was a main query it would not be the same main query. … get_query_var won't work, there is no main query to get a query var from! ). …

No, there isn't. WordPress does not provide page caching mechanisms, and has no APIs for it. There is no generic way to say example.com/page is now stale and needs recreating. Nor is there any generic …

This is bad as it discards the main query and launches a second query. The cost of the first query still occurs, but it's discarded so it's a waste of time. … Consider using pre_get_posts instead to intercept the main query and change it …

Moving to a custom taxonomy will improve your query speed by orders of magnitude. … a post, and you don't need to filter/query for that data, use post meta And don't be afraid to use both or approximations if you have a more complicated value such as a price …

I'm hitting the table 2 times (if the field exists) to get its value. No, you aren't, and there is no evidence for this. You may not be hitting the database at all if it has autoload enabled. WordPr …

If you pass anything using this GET variable, Wordpress will modify the query accordingly assuming its a category. This is bad news. …

That way when you want to do your list, you query the second hidden taxonomy, which acts as a cache of sorts. …

You've made no attempt to check for errors, e.g. $result may be false, also your code would fail if there was more than one result returned. So instead of using a custom table, and reinventing the wh …

For reference, before: 45q, after: 42q The code is very similar to the code used by @birgire function _tomjn_home_cancel_query( $query, \WP_Query $q ) { if ( !$q->is_admin() && ! … $q->is_feed() && $q->is_home() && $q->is_main_query() ) { $query = false; $q->set( 'fields', 'ids' ); } return $query; } add_filter( 'posts_request', '_tomjn_home_cancel_query', …