Kindly EditDocumentationTry the editor

Conditional visibility

Show content for matching visitors or page contexts with server-side conditions.

Build a rule#

Conditions are groups of tests. Every test within a group must match; any matching group can show the element. Individual tests can be negated. The stored structure is data-ke-show with any groups containing all tests.

Supported tests include sign-in status, role, registration date, date, day, time, author, parent, taxonomy term, publication or modification date, archive context, and referrer. The validator limits the structure to 20 groups and 20 tests per group.

Editor and public behavior#

The editor keeps conditional content available so you can select and change it. Preview does not impersonate every visitor condition. On public rendering, an element whose conditions fail is omitted from the output HTML.

Visitor, time, and referrer-dependent output can set no-cache behavior. Verify the entire hosting and CDN cache path when using personalized conditions. A cached page served outside WordPress can defeat an otherwise correct runtime decision.

Use conditions appropriately#

Conditions control presentation. They are not a replacement for authorization on downloads, API endpoints, account records, or other protected resources. Keep permission checks at the resource itself.

Conditional words are removed from plain excerpts and SEO fallback text so a hidden block is not casually exposed through those summaries. Explicit SEO text remains an authored field that you should review separately.

Verify both outcomes#

Test a matching and a nonmatching context. Record the timezone assumptions for time conditions. Test signed-out output in a fresh browser context and check the actual response HTML when omission matters.

About this page

Documents Kindly Edit 0.9.16. Source: includes/conditions.php, assets/conditions-panel.js. Theme choices and account permissions can change which controls appear.

Type a word or phrase to search the full documentation.