Data

Query Builder (Blocks)

The Query Builder lets you define reusable, named queries visually, then select one from any dynamic block instead of rebuilding the same filters over and over. A saved query is a definition stored under a slug and consumable everywhere. Where: WP Admin → Tiger Blocks → Data → Query Builder. Enable the engine under Modules & […]

2 min read Updated July 14, 2026

The Query Builder lets you define reusable, named queries visually, then select one from any dynamic block instead of rebuilding the same filters over and over. A saved query is a definition stored under a slug and consumable everywhere.

Where: WP Admin → Tiger BlocksDataQuery Builder. Enable the engine under Modules & WidgetsDynamic Content.

Choose a source

Each query starts from one source:

  • Posts — posts, pages or any CPT, with meta and taxonomy filters.
  • Related items — objects connected to the current (or a fixed) item through a Tiger Relation. This is the thing a plain WordPress query cannot do: “all Products connected to the Service being viewed,” resolved at run time.
  • Users — site users, optionally filtered by role.
  • Terms — terms of a chosen taxonomy.
  • Comments — a comment query.
  • Content Type (CCT) — rows from a Custom Content Type table.

The Related-items and CCT sources only appear when the Relations and CCT modules are active.

Filter, order and limit

  • Filters — taxonomy terms, author, meta and post status.
  • Order — sort field and direction.
  • Limit — how many items to return, plus include/exclude lists.

Reuse everywhere

Saved queries appear as a choice inside the dynamic blocks — Dynamic Loop, AJAX Grid and Data Table Pro — so one definition powers many displays and stays consistent. Developers can also run a query directly in code with Tiger_Blocks_Query::run( $slug ). Pair a saved query with the AJAX Grid’s live filter bar for a fast, no-reload archive.

Troubleshooting

The Related-items or CCT source is not in the list

Those sources depend on their modules. Enable Dynamic Content (for CCT) and make sure at least one Relation is defined; the source options are only offered when the underlying engine is available.

A relation-based query returns nothing on the page

The Related items source is contextual — it resolves against the object currently being viewed. It works on a singular template where there is a “current item” to traverse from; on a generic archive there is no context, so set a fixed source item or use it on a single-post template.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.