Tiger Query Grid is the plugin’s visual query-builder widget: it lets you assemble a WP_Query out of Elementor controls — post type, ordering, and a repeater of meta/taxonomy conditions with AND/OR logic — then render each matching result either as a simple auto-generated card or through a fully custom Elementor template. It exists for the case Tiger Post can’t cover: filtering content by custom field values or taxonomy terms with real comparison operators, and controlling exactly how each result looks via a loop-item template rather than a fixed card layout. Internally it marks itself dynamic content (is_dynamic_content() returns true), so Elementor knows to re-render it rather than cache it statically.
Building the Query
The Query section starts with an optional Query source switch (only shown if the Query Builder module is active): Build here keeps everything inline, or Saved Tiger Query hands the whole query off to a reusable named query picked from Saved query — including queries whose source is Users, Terms, Comments, or CCT rows rather than posts, in which case the widget renders a simplified linked-card grid of those normalized results instead of a WP_Query loop. When building inline, you pick Post type (populated from every public post type), Items (1–100, default 9), Order by (Date, Title, Menu order, Random, Meta value, or Meta value (number) — the latter two reveal an Order-by meta key text field), and Order (Descending/Ascending).
The real power is the Match control (All conditions (AND) / Any condition (OR)) paired with the Conditions repeater. Each condition row has a Type (Custom field or Taxonomy), a Field / taxonomy key text input, an Operator (=, ≠, >, <, ≥, ≤, contains, in a comma-separated list, not in, or exists), and a Value field. Taxonomy conditions match by term slug and only support IN/NOT IN under the hood regardless of the operator picked; meta conditions map straight onto WP_Query’s meta_query clauses, including EXISTS (which ignores the Value field entirely). On top of the inline conditions, the shared Include/Exclude filter section (categories, tags, authors, post IDs — the same component Tiger Post uses) is also available and gets merged into the final query args.
Layout and Result Templates
The Layout section’s key control is Result template: leave it on “— Card (title + image) —” for an automatic card (post thumbnail scaled to a fixed 3:2 box with object-fit:cover, plus a linked title), or pick any Elementor Loop Item template (or a Tiger Template post) to render each result through your own design — inside that template, dynamic widgets resolve per-result against a global $tiger_loop_post_id. Columns and Gap are both responsive controls; note the widget pins their actual CSS values inline on the front end (scoped to a generated per-instance grid ID) rather than relying purely on Elementor’s wrapper-scoped selectors, specifically because Theme Builder-rendered instances strip the usual .elementor-element-{id} wrapper class, which would otherwise collapse the grid to one column. No-results text is a dynamic-tag-enabled message shown when the query returns nothing.
Style Controls
The Card style section covers padding and border-radius (both responsive), plus a full Normal/Hover tab pair with background (classic or gradient), border, and box-shadow group controls. The Hover tab additionally offers a Lift (Y) slider (a negative-only translateY range for a card-raise effect) and a Transition (ms) slider that’s pinned onto the resting card state so both hover-in and hover-out animate smoothly.
When to Use Tiger Query Grid vs. Related Widgets
Use Tiger Query Grid whenever the listing needs to be filtered by custom field values or taxonomy terms with actual comparison logic (greater-than, contains, exists, AND/OR combinations) — none of the other post-listing widgets in this catalog expose that. Use it over Tiger Post when you need full design control per result via a loop-item template instead of a fixed card. Compare it against Tiger CCT Grid, which is the equivalent tool but for Custom Content Type rows instead of WP posts — if your data lives in a CCT rather than a post type, use CCT Grid, not Query Grid. Prefer AJAX Grid or AJAX Filter when you need client-side, no-reload filtering/pagination controls exposed to the visitor; Tiger Query Grid’s filtering is entirely configured by the builder in the editor, with no front-end filter UI of its own.
Practical Tips
- When using EXISTS as the operator, the Value field is ignored — you only need Field / taxonomy key filled in, since EXISTS just checks for the presence of the meta key.
- If a Saved Tiger Query’s source is Users, Terms, Comments, or CCT, the widget silently switches to its object-results renderer — the Result template picker and per-post styling won’t apply to that grid; only the simplified title/type card layout does.
- Set the Order-by meta key precisely — it’s a raw text field with no autocomplete, so a typo silently produces unsorted or empty ordering rather than an error.
- For custom post types with their own taxonomies, remember taxonomy conditions require the exact taxonomy key (e.g.,
product_cat), not the taxonomy’s display label.