本文是《掌握 WP_Query》专题的第 18 篇，共 19 篇：
- 掌握 WP_Query : 入门介绍
- 掌握 WP_Query：教你使用Loop循环
- 掌握 WP_Query：相关的函数
- 掌握 WP_Query：行动器和过滤器
- 掌握 WP_Query：WP_Query类的属性和方法
- WP_Query 参数：文章、页面和文章类型
- WP_Query 参数：分类和标签
- WP_Query 参数：分类法（Taxonomies）
- WP_Query 参数：自定义字段（Custom Fields）
- WP_Query 参数：日期
- WP_Query 参数：状态、排序和分页
- WP_Query 参数：作者、搜索、密码、权限、缓存和返回字段
- 掌握 WP_Query：10个有用的例子
- 结合 WP_Query 与主查询（the Main Query）
- 掌握 WP_User_Query
- 掌握 WP_Comment_Query
- 掌握 WP_Meta_Query 和 WP_Date_Query
- WordPress 4.1的查询改进
- 掌握 WP_Query：结尾
在过去的一年里，很多人都写到 WordPress 改进了用户界面：最受关注的变化是提高写作经验。但如果你是开发者，你可能更想知道 WordPress 底层有哪些改进。在这里，我将演示对开发者最有趣的变化之一：改进某些类型的查询。
Within the last year, much has been written about the improvements to the WordPress user interface: the most talked about change has been the improved writing experience.
But if you're a developer you'll be wanting to know less about that and more about what's changed under the hood. Here I'll demonstrate one of the most interesting changes for developers: improvements to certain types of queries.
The main changes are as follows:
- Support for nested queries has been added for queries on post metadata, dates, and taxonomy terms.
- Extra parameters have been added for querying comments.
- And some bugs have been fixed too!
Let's have a look at the changes.
In previous versions of WordPress, you could use an
OR statement to define queries for taxonomy terms, dates, and metadata. So for example, the following arguments will be used in a query on a recipe site which outputs quick breakfast recipes:
<?php $args = array( 'post_type' => 'post', 'tax_query' => array( 'relation' => 'AND', array( 'taxonomy' => 'speed', 'field' => 'slug', 'terms' => array( 'quick' ) ), array( 'taxonomy' => 'meal', 'field' => 'slug', 'terms' => array( 'breakfast' ) ) ) ); $query = new WP_Query( $args ); ?>
This looks for the
'meal' taxonomies and outputs posts with the
'breakfast' terms respectively.
But what if you wanted to write a more complex query? Let's say you wanted quick recipes for breakfast and slow recipes for lunch (maybe for someone who wants to get breakfast done quickly so they have more time to cook lunch!). You don't want to use a simple
AND statement to join all the elements of your query, since then you would get slow recipes for breakfast and lunch, for example. And you don't want to use an
OR statement linking all the terms, as you'll get all manner of recipes which only have one of the queried terms along with other ones you want to filter out.
The good news is that now you can do this. To query quick recipes for breakfast and slow recipes for lunch, you'd use the following:
<?php $query = new WP_Query( array( 'tax_query' => array( 'relation' => 'OR', array( 'relation' => 'AND', array( 'taxonomy' => 'meal', 'field' => 'slug', 'terms' => array( 'breakfast' ) ), array( 'taxonomy' => 'speed', 'field' => 'slug', 'terms' => array( 'quick' ) ) ), array( 'relation' => 'AND', array( 'taxonomy' => 'meal', 'field' => 'slug', 'terms' => array( 'lunch' ) ), array( 'taxonomy' => 'speed', 'field' => 'slug', 'terms' => array( 'slow' ) ) ) ) ) ); $query = new WP_Query( $args ); ?>
Here I've used two nested arrays:
- The outer array uses
OR, because we're looking for posts which are either quick breakfast recipes or slow lunch recipes.
- The first nested array looks for posts which are quick breakfast recipes, using
ANDbecause you want the post to have both terms.
- The second nested array looks for slow lunch recipes, again using
Of course you could vary your queries to include multiple taxonomy terms and values, and get as complex as you need.
Applying Nested Queries: Taxonomy Terms, Metadata, and Dates
The example I've given above uses taxonomy terms, but this feature has also been added to date and metadata queries. Metadata is potentially where things could get interesting, as you have the scope for so many values.
The syntax works in exactly the same way for date and metadata queries. For meta queries you replace
meta_query and use
'value' as the parameters. For date queries you replace
date_query and use the date parameters provided in the WordPress Codex.
To query comments, you use the
WP_Comment_Query class in place of the more commonly used
WP_Query class. This class has had eight new parameters added to it:
'author__in': identify comment author (or an array of authors)
'author__not_in': identify comments not by a certain author (or array of authors)
'post_author__in': identify author (or array of authors) of the post the comment was made on
'post_author__not_in': exclude comments made on posts written by particular author or array of authors
'comment__in': comments with a certain ID or array of IDs
'comment__not_in': exclude comments with a certain ID or array of IDs
'post__in': comments made on a post or array of posts (using the post ID)
'post__not_in': exclude comments made on a post or array of posts (using the post ID)
The values used for these are the author ID, comment ID or post ID as appropriate.
Note that the
WP_Comment_Query class now supports nested queries as well.
There have also been a couple of bug fixes which you might find helpful:
- A bug that caused queries to fail when a
date_querywas used along with a
meta_queryhas been fixed.
‘orderby' => 'meta_value’was used when passing a
WP_Query, this used to break the query. This has been fixed.
If you want the lowdown on all the details, you can find it on the make WordPress core site.
These improvements to queries take WordPress a step further to full CMS capability. The ability to use nested queries means that you can output content in much more flexible and complex ways. It will be interesting to see how people use them!