meta_query is an array of meta clauses. For example: $q = new WP_Query( array( ‘meta_query’ => array( ‘relation’ => ‘AND’, array( ‘key’ => ‘state’, ‘value’ => ‘Wisconsin’, ), array( ‘key’ => ‘city’, ‘compare’ => ‘EXISTS’, ), ), ) ); You can use an associative array, with a key for each meta clause: $q = new … Read more
Your actual question is basically when to run a custom query and when to make use of the main query. Lets break it down in three parts PART ONE When to run a custom query (This is not a definitive list) To create custom content sliders To create a featured content area in a page … Read more
Just change the post_type bit to: ‘post_type’ => array(‘testimonial’, ‘other_post_type’, ‘another-post-type’), Assuming that taxonomy is valid across all 3 post types. Otherwise you’ll have to leave that out. Why? You can pass an array to post_type field.
These are the query parameters i use…works for me when i loop through the results array( ‘post_parent’ => $post->ID, ‘post_status’ => ‘inherit’, ‘post_type’=> ‘attachment’, ‘post_mime_type’ => ‘image/jpeg,image/gif,image/jpg,image/png’ ); For more detail, please see official documentation for WP_Query’s status parameters
You have missed one, $GLOBALS[‘wp_query’]. For all purposes, $GLOBALS[‘wp_query’] === $wp_query. $GLOBALS[‘wp_query’] is however better for readability and should be used instead of $wp_query, BUT, that remains personal preference Now, in a perfect world where unicorns rule the world, $GLOBALS[‘wp_the_query’] === $GLOBALS[‘wp_query’] === $wp_query. By default, this should be true. If we look at where … Read more
So, you might consider automating the multiple queries. First, get the list of terms in your custom taxonomy, using get_terms(): <?php $member_group_terms = get_terms( ‘member_group’ ); ?> Then, loop through each one, running a new query each time: <?php foreach ( $member_group_terms as $member_group_term ) { $member_group_query = new WP_Query( array( ‘post_type’ => ‘member’, ‘tax_query’ … Read more
In my opinion, deprecating numberposts would not make sense, as numberposts is used to query x amount of posts, whilst posts_per_page is used to denote how many posts per page are being shown during pagination. If you were to deprecate numberposts in favor of simply posts_per_page, then pagination would not exist. ie: “numberposts” => 50, … Read more
There is a sad truth: you can never ever be sure that some code will not break your code, and there is nothing you can do to prevent that. Especially in WordPress, where everything is global. That said, yes, global $post is one of the most used global var, so using special care for it … Read more
you need to use ‘orderby’ => ‘meta_value_num’, also if you are ordering dates, the best advice is to put them in an easy to order way such as 2012-12-31
Please reference the Codex entry for post/page parameters for WP_Query(). The ‘p’ parameter takes a single post ID, as an integer. To pass an array of posts, you need to use ‘post__in’: $myarray = array(144, 246); $args = array( ‘post_type’ => ‘ai1ec_event’, ‘post__in’ => $myarray ); // The Query $the_query = new WP_Query( $args );