GravityOps Search - Search and Display Gravity Forms Entries

No. GravityOps Search does not modify or enhance the admin-side Entries screen in any way. It is designed exclusively for front-end searching: you place a shortcode on a page, post, or view, and the plugin retrieves matching Gravity Forms entries and displays the data exactly as you format it.

Use the [gravops_search] shortcode. You specify which forms to target, which field IDs or entry properties to search, which values to match, and how to output the results. The shortcode runs a live query against Gravity Forms entries and prints the matching results anywhere shortcodes are supported.

Yes. You can target a single form, several forms, or all forms. Just pass a comma-separated list of form IDs in the target attribute, or use target=\"0\" to query every form on the site. This allows you to build global lookups and multi-form reporting views.

Yes. The search attribute accepts a comma-separated list of field IDs or entry properties. The shortcode content (inside the opening and closing tags) supplies the values, separated with a pipe (|) in the same order. You can match on a single field, several fields together, or a mix of fields and entry meta.

Use the operators attribute to define comparison behavior for each field. Supported operators include exact match, not-equal, contains, wildcard-style “like”, numeric comparisons (greater-than / less-than), and array-based “in” or “not in” checks. When no operator is provided for a field, the default behavior is exact matching.

Yes. By default, the shortcode requires entries to match all conditions. Set search_mode=\"any\" to return entries that satisfy at least one of the provided search fields and values.

Use the display attribute. You can provide:

• A comma-separated list of field IDs.
• A custom template string with placeholders like {15} or {id}.
• Full HTML markup for custom layouts (lists, cards, rows, tables). This gives you complete control over how each entry appears on the front end.

Yes. The display template supports text, HTML tags, attributes, classes, and multiple placeholders. You can mix fields, entry properties, links, labels, or structured markup to build clean, styled results that match your site’s theme.

Yes. The plugin supports nested shortcodes using {{ ... }} syntax to avoid parsing conflicts. You can nest GravityMath, additional [gravops_search] shortcodes, or any shortcode that produces text or numbers. Nested shortcodes receive processed values, enabling chained lookups and computed displays.

Yes. Multi-input fields can be displayed as either:

• Combined values using the base field ID ({13}), or
• Individual inputs using dot notation ({13.3}). For searching, checkboxes should be matched using the base field ID, while other multi-input fields should be matched using specific input IDs.

Yes. You can search for empty fields using search_empty=\"true\" and passing an empty value for that position in the shortcode content. This is useful for finding incomplete submissions or missing data.

Yes. Use sort_key, sort_direction, and optionally sort_is_num to sort by numeric or text values. You can also add secondary_sort_key and secondary_sort_direction for tie-breaking. For random ordering, use sort_direction=\"RAND\".

Yes. Use the limit attribute. You can return a specific number or use limit=\"all\" to show all matches. When combined with sorting, this allows you to show the newest, oldest, largest, smallest, or otherwise top-ranked results.

Yes. Setting unique=\"true\" returns only unique results after formatting. This is ideal for building deduplicated lists such as unique emails, product IDs, or user identifiers pulled from multiple entries.

You can provide fallback text using the default attribute. This text displays instead of an empty result, keeping your front-end layout informative and user-friendly.

The plugin displays whatever data you ask it to display. If you include fields with personal or private information, anyone who can access the page will see that data. To restrict visibility, place the shortcode inside protected pages controlled by your membership or role-based access tools.

Each shortcode triggers a live database query. Normal usage is fast, but heavy configurations—large multi-form searches, deep nesting, or unlimited results—may impact performance. Use reasonable limits where possible and consider caching the page output if you’re displaying large data sets.

Yes. You can use the shortcode inside GravityView fields, calculations, template blocks, or custom layouts. Nested shortcode support lets you combine data filters, math, and dynamic rendering cleanly.

Yes. GravityOps Search supports environments where the old gfsearch snippet is present. You can continue using it for legacy shortcodes while using [gravops_search] for new builds. They can run simultaneously without conflict.

No. The entire search, filtering, and output process is achieved through shortcode attributes. You can build simple or highly advanced data displays without writing any PHP.