GravityOps Search – Search and Display Gravity Forms Entries – Lite

By BrightLeaf Digital

0+ active installationsVersion 1.2.5

Search Gravity Forms entries from a shortcode and show matching results anywhere on your site, filtered by any field and formatted your way.

Description

GravityOps Search gives Gravity Forms site builders a [gravops_search] shortcode that finds entries by any field and prints the matching values anywhere on the front end, formatted however you need.

Feature
Free
Premium

[gravops_search] shortcode: search one, several, or all forms
Yes
Yes

Filter by field ID, entry property, field label, or field type
Yes
Yes

Operators: equals, not equals, contains, like, in / not in, greater / less than
Yes
Yes

Custom display templates with HTML, placeholders, and nested shortcodes
Yes
Yes

Sorting, secondary sort, limits, unique results, default values
Yes
Yes

Admin entry links on each result
Yes
Yes

Docs and Help tabs in the GravityOps dashboard
Yes
Yes

Visual Shortcode Builder with live preview, validation, and test run
No
Yes

Builder presets and starter templates
No
Yes

Saved Shortcodes library (copy, edit in builder, delete)
No
Yes

Drop the shortcode into a page, post, GravityView field, or template and it works like a lookup for Gravity Forms entries: you choose which forms and fields to search, how to compare the values, and what to output for each match. It needs no PHP and no custom queries.

The shortcode can show a single field from the latest matching entry or build a reporting-style view that combines fields, entry properties, and custom HTML. Everything is driven by attributes, so you decide exactly which entries are included and how their data appears.

GravityOps Search is for front-end display. It does not add search tools to the Gravity Forms admin Entries screen.

GravityOps Search requires Gravity Forms.

Features

  • Target all forms (target="0"), a single form, or a comma-separated list of form IDs.
  • Filter by a comma-separated list of field IDs or entry properties with the search attribute.
  • Filter by field label (search_label) or field type (search_type) to search across forms whose field IDs differ. field_match controls whether the first or every matching field is used.
  • Pass search values in the shortcode content, separated by a pipe (|) in the same order as the search fields.
  • Require all conditions (default) or any condition with search_mode="any".
  • Search every field at once by leaving a search ID blank.
  • Control each comparison with the operators attribute: equals, not equals, contains, SQL-style like, in / not in lists, and numeric greater than / less than (or equal).
  • Display one or many fields and properties per result with the display attribute, from a simple field list to a full HTML template.
  • Use placeholders such as {13}, {13.3}, {id}, {form_id}, and {gos:id}, plus {gos:num_results} for the number of matches.
  • Control how results are joined with separator, including HTML separators or no separator (__none__).
  • Sort with sort_key, sort_direction (ASC, DESC, RAND), and sort_is_num, with secondary_sort_key and secondary_sort_direction for tie-breaking.
  • Limit results with limit, or show every match with limit="all".
  • Remove duplicate output with unique.
  • Find empty or blank values with search_empty.
  • Show fallback text when nothing matches, or per-field defaults when a value is empty, with default.
  • Wrap each result in a link to the entry in the Gravity Forms admin with link.
  • Nest GravityMath, another [gravops_search], or any other shortcode inside the output.
  • Runs alongside the legacy gfsearch snippet without conflict.
  • Visual Shortcode Builder (Premium): build [gravops_search] shortcodes with a point-and-click UI. Pick forms, add filters by ID, label, or type, choose a simple field list or a block-based template, see the live shortcode with validation hints, run it against your real entries, and save it.
  • Saved Shortcodes library (Premium): name and save shortcodes from the builder, then copy, reopen in the builder, or delete them from a dedicated tab.

How It Works

GravityOps Search reads your shortcode attributes and content to decide which entries to fetch, then formats each match according to the display attribute. target sets which forms to query: 0 for all forms, one form ID, or a comma-separated list. search lists the field IDs and entry properties to filter on, and the shortcode content supplies the matching values, separated by | in the same order.

search_mode sets the matching logic. The default, `all`, requires every condition to match; `search_mode="any"` returns entries that meet at least one. To search every field for a value, leave that position's search ID blank.

Sorting, limiting, and uniqueness are applied after the search conditions. sort_key accepts a field ID, entry property, or meta key, and sort_direction accepts ASC, DESC, or RAND. sort_is_num makes numeric values compare as numbers. secondary_sort_key and secondary_sort_direction set a second ordering, for example by date and then by name. limit then sets how many entries are returned, and unique removes duplicates based on the rendered output.

default sets text to show when no entries are found or when a displayed field is empty; separate several defaults with `||` to map them to several display fields. `separator` sets how entries are joined, so you can build line-separated lists, `<li>` items, or table rows. Each `[gravops_search]` shortcode runs its own live query, so different instances can show different views of the same data.<h3>Display and Formatting</h3>

The display attribute controls the output. In its simplest form it takes a comma-separated list of field IDs or entry properties, such as display="13,14,15", and outputs those values in order for each matching entry. This suits raw values such as a list of email addresses or IDs.

For more control, display accepts a template with placeholders, such as display="Name: {13}, Email: {14}", rendered once per entry. {13} inserts field 13, and {id} and {form_id} insert entry properties. Where standard merge tags are also parsed (GravityView content fields, confirmations, notifications), use {gos:id} to avoid conflicts. {gos:id;fallback} sets a default for a single placeholder.

display also accepts HTML, including tags, attributes, and CSS classes. Wrap values in `<div>`, `<span>`, `<ul>`, `<li>`, `<a>`, or table markup to build lists, tables, or cards. Because `separator` accepts HTML too, each entry can become one list item, table row, or card that matches your theme.<h3>Nesting Shortcodes and Advanced Templates</h3>

To nest another shortcode inside display, wrap it in double curly braces: {{ ... }}. This works for GravityMath, another gravops_search, or any shortcode. The outer [gravops_search] replaces its own placeholders first, then runs the nested shortcodes, so entry values can feed calculations or secondary lookups.

When you nest a second gravops_search, each shortcode runs its own search in sequence. The outer shortcode resolves placeholders such as {13} and {gos:id} in its template, and the nested one uses its own attributes. To pass a value into another shortcode’s attribute, use gos:id without braces (for example, gos:21) to avoid merge-tag parsing conflicts.

For example, one [gravops_search] can list matching entries, a nested one can pull related entries, and a GravityMath shortcode can compute totals, all inside your own HTML.

Search Operators and Multi-Input Fields

The operators attribute sets how each search value is compared to its field. It is a comma-separated list that lines up with the search fields: search IDs first, then search_label entries, then search_type entries. Supported operators are = or is, !=, isnot, or is not, contains, like, in, not in, and the numeric gt, lt, gt=, and lt=. Fields without an operator use an exact match.

With in or not in, pass a list in the shortcode content, such as array('item one','item two','item three'), to test whether the field value is in that list.

Multi-input fields (Name, Address, Checkboxes) behave differently for display and search. For display, the base field ID ({13}) combines all inputs into one string separated by spaces, and an input ID ({13.3}) shows a single input. For search, use the base field ID for checkboxes, and the individual input IDs (such as 13.3 or 13.6) for Name and Address fields; searching Name or Address by the base ID does not work.

Performance and Access Control

Every [gravops_search] shortcode runs a live database query. limit="all", deep nesting, and large multi-form searches can slow page loads. Set a reasonable limit, avoid unnecessary nesting, and consider page caching for data-heavy pages.

The shortcode does not check permissions. Anyone who can view the page sees whatever entry data you choose to display, including personal data. Place shortcodes that show private data on pages protected by a membership plugin, password protection, or role-based visibility.

Community Help

For how-to questions and examples of what others have built, visit the GravityOps Help community.

If you opened a support thread on WordPress.org, continue that conversation there. The community is an additional place for help and ideas.

External services

Searches run against your own database. Your entries and search terms are never sent anywhere.

The plugin connects to outside services only in these cases:

  • GravityOps product catalog. When an administrator uses the WordPress admin (or shortly afterwards, through WP-Cron), the shared GravityOps library downloads the GravityOps product catalog (names, versions, icons, links and announcements) from brightleafdigital.io, at most about twice a day. The request sends no personal data or site content; like any web request, it reveals your server’s IP address.
  • Newsletter signup. Only if you choose to subscribe to GravityOps Weekly, the email address you enter is sent to brightleafdigital.io.
  • Feedback prompts. Only if you choose to answer the short GravityOps survey or open the review prompt, your answers, or the plugin and version being reviewed, are sent to brightleafdigital.io.
  • Support access. Only if you grant BrightLeaf Digital support access, TrustedLogin creates a temporary login and notifies BrightLeaf Digital through TrustedLogin and brightleafdigital.io.
  • Freemius. Licensing and updates for the premium version run through Freemius. In the free version, Freemius receives information only if you opt in when activating the plugin: your name and email address, your site’s URL, your WordPress, PHP and plugin versions, and plugin events such as activation and deactivation. You can skip the opt-in and the plugin works the same.

BrightLeaf Digital: Privacy Policy. TrustedLogin: Authorized User Terms, Privacy Policy. Freemius: Terms, Privacy Policy.

Installation

  1. Install GravityOps Search:
    • In WordPress, go to Plugins → Add New → Upload Plugin.
    • Upload the ZIP file and click Install Now.
    • After installation, click Activate.
  2. Use the shortcode anywhere you need to search entries:
    • Edit a page, post, widget, or template that accepts shortcodes.
    • Insert the [gravops_search] shortcode with the attributes you need.
    • Save or update the page.
  3. View the page on the front end:
    • Matching Gravity Forms entries will now display according to your shortcode’s filters and layout.

FAQ

Do I need to write PHP or custom code?

No. Searching, filtering, and output are all set with shortcode attributes. Premium adds a Visual Shortcode Builder so you can build the shortcode without writing its syntax by hand.

Does this plugin search the Gravity Forms admin entries screen?

No. GravityOps Search does not change the admin Entries screen. It is built for the front end: you place a shortcode on a page, post, or view, and it displays matching entries the way you format them.

How do I run a search?

Use the [gravops_search] shortcode. Set which forms to target, which fields or entry properties to search, the values to match, and how to output the results. The shortcode runs a live query and prints the results anywhere shortcodes are supported.

Can I search multiple Gravity Forms at once?

Yes. Pass a comma-separated list of form IDs in the target attribute, or use target="0" to query every form on the site. If the same kind of field has different IDs on each form, use search_label or search_type with search_mode="any".

Can I filter by more than one field or property?

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

How does the plugin compare values?

Use the operators attribute to set the comparison for each field: exact match, not equal, contains, like, numeric greater than / less than, and in or not in lists. Fields without an operator use an exact match.

Can I return entries that match any of the conditions instead of all?

Yes. By default every condition must match. Set search_mode="any" to return entries that match at least one.

How do I control how results are displayed?

Use the display attribute. It accepts:
– A comma-separated list of field IDs.
– A template with placeholders like {15} or {id}.
– HTML markup for lists, cards, rows, or tables.

Can I include multiple fields, labels, or HTML in the output?

Yes. The display template supports text, HTML tags, attributes, classes, and any number of placeholders, so results can match your theme.

Can I nest other shortcodes inside the display template?

Yes. Wrap nested shortcodes in {{ ... }}. You can nest GravityMath, another [gravops_search], or any shortcode that outputs text or numbers. Nested shortcodes receive the already-replaced values, which allows chained lookups and calculations.

Does the plugin support multi-input fields like Name, Address, and Checkboxes?

Yes. For display, use the base field ID ({13}) for the combined value or an input ID ({13.3}) for one input. For search, match checkboxes by the base field ID and other multi-input fields by their input IDs.

Can I search for empty or missing values?

Yes. Set search_empty="true" and leave the value for that position empty in the shortcode content. This finds incomplete submissions or missing data.

Can I control the order of results?

Yes. Use sort_key, sort_direction, and sort_is_num, plus secondary_sort_key and secondary_sort_direction for tie-breaking. For random order, use sort_direction="RAND".

Can I limit how many entries are returned?

Yes. Set limit to a number, or limit="all" to show every match. The default is 1. Combined with sorting, this shows the newest, oldest, largest, or smallest results.

Can I display only unique values?

Yes. unique="true" removes duplicate results after formatting, which is useful for lists of unique emails, product IDs, or user names.

What happens if no entries match the search?

Set fallback text with the default attribute. It is shown instead of an empty result.

Does the plugin protect sensitive data?

No. It displays whatever you ask it to, and anyone who can view the page sees that data. Put shortcodes that show personal data on pages protected by a membership plugin or role-based access.

Will this plugin slow down my site?

Each shortcode runs a live database query. Normal use is fast, but large multi-form searches, deep nesting, or limit="all" on big forms can slow a page. Use reasonable limits and consider page caching.

Is this compatible with GravityView, GravityMath, and similar tools?

Yes. You can use the shortcode inside GravityView fields and custom layouts, and nest GravityMath or other shortcodes inside its output.

Can I still use the old gfsearch snippet?

Yes. The plugin registers its own [gravops_search] shortcode and leaves [gfsearch] alone, so both can run on the same site. Use the snippet for existing shortcodes and [gravops_search] for new builds.

Screenshots

Changelog

1.2.5 | Nov 17, 2026

  • Fixed a rare critical error in the WordPress admin that could appear right after activating or deactivating another plugin.
  • Fixed a critical error when uninstalling the free version, or the premium version without an active license, so the plugin’s saved data is now cleaned up in every case.
  • Updated the GravityOps shared library: the short GravityOps survey can now also be shown to administrators on sites that don’t have Gravity Forms installed.

1.2.4 | Nov 15, 2026

  • Leaving a search ID blank now searches every field for that value, as documented and as the Shortcode Builder’s “Search ANY field” option expects. Previously the value was ignored and every entry was listed.
  • Rewrote the plugin description, FAQ and tags for WordPress.org, added screenshots, and documented the search_label, search_type and field_match attributes and the {gos:num_results} placeholder.
  • Uninstalling the plugin now also removes the review request’s saved settings.
  • Turned on affiliate program support in the licensing system, so the Affiliation page works as intended.
  • Updated the GravityOps shared library: the one-time request to rate the plugin can now also appear after two weeks of use, not only after heavy use. Dismissing it still stops it for good.

1.2.3 | Nov 10, 2026

  • Added a Community Help section to the readme pointing to the GravityOps Help community.
  • Added an External services section to this readme describing when the plugin connects to outside services.
  • Updated the GravityOps shared library: the GravityOps dashboard now gets its product list, categories, links and announcements from BrightLeaf Digital’s signed online catalog, so new tools appear without a plugin update. Free versions offer an optional GravityOps Weekly newsletter signup, seasonal offers can appear on the plugin’s settings screen, and updating from the dashboard keeps a network-activated plugin network-active. Code Snippet Manager now appears on the dashboard, and premium updates explain when a license is required.

1.2.2 | Oct 11, 2026

  • Updated Freemius SDK to the latest version.
  • Tested with WordPress 7.1.
  • Updated the GravityOps shared library to 2.0.11, bringing a consistent Feeds screen across the suite, more reliable feed activation toggles and feed links, the Docs tab placed before Help, dashboard links that open in a new tab, and updated third-party components.

1.2.1 | Aug 3, 2026

  • GravityOps now asks for one short suite-wide survey instead of one survey per plugin, using a compact invitation and a dedicated dashboard form.
  • Closing a survey or review prompt now saves “not interested” immediately without reloading the page.