You may be surprised, but there is nothing strange there. First of all let’s clarify that in WordPress when you visit a frontend URL you trigger a query. Always. That query is just a standard WP_Query, just like the ones run via: $query = new WP_Query( $args ); There is only one difference: the $args … Read more
Here’s one experimental idea: Assume we got: post A with the custom field location1 as UK – London post B with the custom field location2 as France – Paris post C with the custom field location3 as USA – New York Then we could use, for example: $args = [ ‘meta_query’ => [ ‘relation’ => … Read more
You could use the query to filter the content as you intended by using the ‘meta_query’ with filtering options, and for the order part, just add/modify the following parameters: ‘orderby’ => ‘meta_value’ ‘meta_key’ => ‘location_level1_value’ ‘order’ => ‘ASC’ $wp_query = new WP_Query( array ( ‘post_type’ => ‘listing’, ‘posts_per_page’ => ‘9’, ‘post_status’ => ‘publish’, ‘meta_query’ => … Read more
You will either need to globalize $books (if you want to stick to get_template_part() ) or use require( locate_template( ‘loop-books.php’ ) ); instead of get_template_part( ‘loop’, ‘books’ );. This issue is caused by $books in loop-books.php being defined only in the scope of get_template_part().
There is no build in function to achieve what you want, at least not for complicated meta queries like this. If you need to use build in functions for this, the best will be to make use of WP_Query. To make the query faster and to skip the unwanted returned array of WP_Post properties, and … Read more
Ok, I got there at the end. I couldn’t use WP_Query class as I really needed to have my own pretty big and complex SQL. Here is what I ended up having: In functions.php I have my custom SQL and logic for counting the values needed for the WP pagination logic: function vacancies_current( ){ global … Read more
Excellent responses on WP Hackers: http://lists.automattic.com/pipermail/wp-hackers/2012-June/043213.html What you’re doing with that query, is loading EVERY matching post into memory, including the full post contents. As you can imagine, this is probably quite a lot of items. You can pass ‘fields’ => ‘ids’ into WP_Query to simply return a list of matching post_ids instead, which should … Read more
Unfortunately you cannot perform a meta_query using a LIKE comparison on the meta_key value when using WP_Query. I’ve been down this road… Instead you have a couple other options if you want to maintain like status relationships as post meta and not user meta and or meta in a custom table. Option 1 requires no … Read more
Query all post titles of a specific post type // Function that returns post titles from specific post type as form select element // returns null if found no results. function output_projects_list() { global $wpdb; $custom_post_type=”page”; // define your custom post type slug here // A sql query to return all post titles $results = … Read more
Yes, it can be done. The key is to make the format parameter different for the two queries: <!– Cats –> <div class=”animals”> <? $paged1 = isset( $_GET[‘paged1’] ) ? (int) $_GET[‘paged1’] : 1; $paged2 = isset( $_GET[‘paged2’] ) ? (int) $_GET[‘paged2’] : 1; // Custom Loop with Pagination 1 // http://codex.wordpress.org/Class_Reference/WP_Query#Usage $args1 = array( … Read more