The "Which posts" section of a rule holds its conditions. A sharing rule only shares posts that match. A "never share" rule only blocks posts that match.
How conditions work
A rule has at least one condition. Click "+ Add condition" to add more. Above the list you choose whether posts must match "all" or "any" of the conditions.
Each condition has a field, a comparison and one or more values. A new sharing rule starts with a post type condition.
Fields
| Field | Comparisons | Values |
|---|---|---|
| Post type | is | One or more post types, for example Posts |
| Category, Tag, or any other taxonomy on your site | is any of, is all of, is none of | One or more terms. For categories you can tick "Include subcategories". Other nested taxonomies offer "Include nested terms". |
| Author | is | One or more authors |
| Custom field | equals, does not equal, exists, does not exist | The field name and, for equals and does not equal, a value |
A rule can only read the custom fields listed under "Advanced", "Custom fields used in this rule". Separate names with commas. The same list allows {{ meta:name }} placeholders in the message.
Examples
- Only news: Category is any of News.
- Recipes by one author: Category is any of Recipes, and Author is that person, with "all" selected.
- Everything except one tag: Tag is none of the tag you want to leave out. For posts that must never go out, a "never share" rule is the safer choice, because it wins over every sharing rule.
Conditions as JSON
The editor under "Which posts" writes the conditions as JSON for you. For nested groups, open "Advanced" and edit "Conditions as JSON" by hand. A rule can have up to 50 conditions nested 5 levels deep. If a rule uses conditions the simple editor cannot show, it says so and offers "Show the JSON" or "Replace them with simple conditions".
What the test shows
The rule test explains why a post does not match, for example "It is by X, and this rule covers other authors." or "Its custom field X does not match."