Hopefully you’ve figured this out by now, but if you haven’t you should be able to use the “posts_orderby” filter to dial in a specific order for your query. I’m not going to give a full solution here, but you can refer to this post for more: http://mitcho.com/blog/how-to/external-orders-in-wordpress-queries/ EDIT: Here’s the Documentation – basically you … Read more
The WP_Query object accepts a post meta argument. Generally speaking you want to do the following: $my_query = new WP_Query( array( ‘post_type’ => ‘post’, ‘meta_query’ => array( array( ‘key’ => ‘project_cat’, ‘value’ => ‘my-value’, ) ), // Other query properties ) ); Where ‘my-value’ is your ‘specified value’. Example usage: add_action( ‘pre_get_posts’ , ‘my_pre_get_posts’ ); … Read more
You can try a trick with querying post data directly and setting filter field of post objects to sample before passing it to get_permalink() to reduce memory usage. See get_permalink memory usage issue for detailed reasoning behind it.
In addition to birgire’s solution, as of WordPress 3.7, you can use Date parameters. Your arguments would look like this to filter posts from the last 7 days: $args = array( ‘post_type’ => ‘post’, ‘post_status’ => ‘publish’, ‘orderby’ => ‘date’, ‘order’ => ‘DESC’, // Using the date_query to filter posts from last week ‘date_query’ => … Read more
This code is incorrect! You have ‘taxonomy’ => ‘post-format’ But it really needs to be: ‘taxonomy’ => ‘post_format’ Without the underscore, the query will be invalid. I just tested this on my WordPress 3.1 install after pulling my hair out for hours. Hope that helps!!
If you can explain it in SQL, you can query for it! There are three places where we want to change the default query: SELECT wp_posts.* FROM wp_posts INNER JOIN wp_postmeta ON (wp_posts.ID = wp_postmeta.post_id) WHERE 1=1 AND wp_posts.post_type=”post” AND (wp_posts.post_status=”publish”) AND wp_postmeta.meta_key = ‘startDate’ AND CAST(wp_postmeta.meta_value AS CHAR) < ‘2011-03-23’ GROUP BY wp_posts.ID ORDER … Read more
What you want is possible but will require you to delve into SQL which I like to avoid whenever possible (not because I don’t know it, I’m an advance SQL developer, but because in WordPress you want to use the API whenever possible to minimize future compatibility problems related to future potential database structure changes.) … Read more
Edit: See below for proper way to query category and tag intersections. global $wp_query; $args = array( ‘category__and’ => ‘category’, //must use category id for this field ‘tag__in’ => ‘post_tag’, //must use tag id for this field ‘posts_per_page’ => -1); //get all posts $posts = get_posts($args); foreach ($posts as $post) : //do stuff endforeach;
When I added the drawbacks to the Codex, I was mainly thinking of using the ‘request’ filter as an alternative to query_posts(). That filter is only run for the main query, so that solves the problem with ‘pre_get_posts’, which fires for every query. The downside is that you don’t have access to query flags like … Read more
Essential question Let’s dig into the trio: ::query_posts, ::get_posts and class WP_Query to understand ::query_posts better. The cornerstone for getting the data in WordPress is the WP_Query class. Both methods ::query_posts and ::get_posts use that class. Note that the class WP_Query also contains the methods with the same name: WP_Query::query_posts and WP_Query::get_posts, but we actually … Read more