GravityView v3.7.0 WordPress Plugin

What’s New (Changelog) in GravityView v3.7.0

= v3.7.0 on October 8, 2026 =
This release makes "Search Everything" and sorting use what fields display rather than what they store, fixes several security issues around entry visibility and exports (we recommend updating), and resolves many issues with embedded Views, search, multi-page Edit Entry, and combined forms.

#### Improved
* Broader "Search Everything" matching that covers what fields display, not just what they store:
- Names of users, posts, entries, and database table rows that Dynamic Lookup, GP Populate Anything, and GP Nested Forms fields store by ID;
- Labels of choice fields, such as Drop Down and Checkboxes;
- Fields inside Repeater fields.
* Sorting by fields that store the ID of a user, post, entry, or database table row, which now orders entries by the displayed name, including in Views that combine forms with the [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension.

#### Security
* Views embedded with a `{user:...}` merge tag in their search (such as `search_value="{user:ID}"`) showed every entry to logged-out visitors instead of none.
* The Entry and Entry Field blocks, the `[gventry]` and `[gvfield]` shortcodes, entry embeds (oEmbed), and the REST API's single entry route could display entries that the View's filters exclude, such as entries hidden by Advanced Filtering conditions or by the "Show only entries created by the currently logged-in user" setting.
* Entries not listed on a page could be opened in its lightbox when the page also contained an escaped `[[gravityview]]` shortcode or a secured View embedded without its secret.
* The Single Entry page heading of a View embedded in a reusable block could show the title of an entry the visitor wasn't allowed to view.
* Search Bar fields restricted to logged-in users could still filter results for logged-out visitors.
* A GravityView Search widget left in the WordPress Inactive Widgets area still allowed visitors to search by its fields.
* Some values in CSV and TSV exports, including bulk action exports and the attachments manifest, could run as spreadsheet formulas when the file was opened in a spreadsheet application.

#### Fixed
* Pages with a Search Bar widget loaded more slowly after the GravityView 3.5.0 update, increasingly so with each search field, form field, and user on the site.
* Custom CSS that arranged List or Layout Builder entries into columns with the Legacy theme, such as the grid CSS from our documentation, displayed every entry in a single column after the GravityView 3.5.0 update.
* Entry links set to open in a lightbox, such as `[gv_entry_link lightbox="true"]`, opened a full page instead in [DataTables](https://www.gravitykit.com/products/datatables/) 3.14.0 and later and in Views that refresh results without reloading the page.
* Single Entry Title issues:
- Single Entry pages and the entry lightbox had an empty title, and the Breadcrumbs block showed "(no title)", when the Single Entry Title setting was empty (the default) or its merge tags had no value for the entry — Single Entry pages now fall back to the page's title;
- Single Entry pages of an embedded View with a Single Entry Slug showed the page's title instead of the Single Entry Title, and GravityView Social Sharing & SEO gave them the page's SEO title and the wrong canonical URL;
- Views embedded with a merge tag in their search (such as `search_value="{user:ID}"`) showed the page's title instead of the Single Entry Title and couldn't open entries in a lightbox.
* Issues on pages that display more than one View or entry embed:
- When the same View was embedded more than once, an embed could show another embed's search, page size, or other shortcode settings, lose its widgets, or refuse to open its own entries in a lightbox;
- When the same View was embedded more than once, its Single Entry pages displayed the entry once per embed;
- A View lost its Search Bar widget, pagination, and other widgets when it followed an Entry block or `[gventry]` shortcode showing a Map View entry, or an entry displayed through a theme's legacy single entry template;
- A View embedded in another View's field, such as a Custom Content field, pushed the parent View's remaining entries outside the View.
* Issues in Views that combine forms using the Multiple Forms extension:
- With entry caching enabled, Views combining many forms through joins or unions could show another View's entries and ignore searches;
- With entry caching disabled, a page showing two Views of the same form, one of which combined other forms, could display the first View's entries in the second View;
- Sorting by a field that one of the combined forms lacks ordered that form's entries by entry ID and applied the second sort field as the first;
- The Entry and Entry Field blocks and the `[gventry]` and `[gvfield]` shortcodes showed nothing for entries from a form combined through a union.
* Issues with the First and Last entry options:
- The Entry Link block and `[gv_entry_link]` shortcode set to First or Last could link to an entry from a different View on the same page, and Last stopped at the end of the View's first page;
- The Entry and Entry Field blocks and the `[gventry]` and `[gvfield]` shortcodes showed the first entry when set to Last, and both First and Last shifted with the View's current page.
* Search Bar widget issues:
- Chained Selects fields didn't appear, and searching by them listed every entry;
- Dropdowns didn't show the Drop Down field's Placeholder as their first option;
- With "Search Everything" limited to visible fields, searching by a field the View didn't display (including through a GravityView Search widget) returned every entry.
* "Search Everything" issues:
- Required (`+`) words matched an entry only when they all appeared in the same field;
- In Views with joined forms, rows containing an excluded (`-`) word in one of the forms were still shown;
- In Views that combine entries from several forms, an excluded (`-`) word returned no entries, and limiting the search to visible fields didn't apply to the added forms;
- When limited to visible fields, an excluded (`-`) word still filtered out entries that contained it in a hidden field, and fields inside a visible Repeater field weren't searched;
- `%` and `_` acted as wildcards, matching any text or any single character, instead of being treated as plain characters.
* Search issues with fields that store IDs, such as Dynamic Lookup, GP Populate Anything, and GP Nested Forms fields:
- Searching by the displayed name found nothing because it was compared with the stored ID;
- Picking a Dynamic Lookup value from a Search Bar dropdown, radio button, or link also matched entries whose stored IDs contained it (for example, `7` also matched `78`) — choices now match exactly, and Lookups that store several IDs match any one of them;
- Searching a Dynamic Lookup field that uses the Checkbox input or a multi-select Select input found no entries.
* With "Allow searching beyond the start and end date range" enabled, Single Entry pages could show entries outside the View's date range when the page address included a date search.
* Issues with multi-page forms in Edit Entry:
- Next and Previous saved the entry but stayed on the same page when the button text didn't match GravityView's translation for the user, such as for users in another language or when the View's Next or Previous text was customized;
- Page links, such as those added by GP Multi-Page Navigation, opened the next page instead of the one clicked;
- When a submission failed validation, a different page opened and the error stayed hidden on the page that had it;
- Fields on pages after the first were saved without validation (for example, an Email field with an invalid address), including through GP Multi-Page Navigation's page links.
* Edit Entry flagged an unchanged Date or Time field with No Duplicates enabled as a duplicate, preventing the entry from being saved.
* Links to specific View editor tabs, such as "Add fields to Single Entry" in the notice shown when a layout hasn't been configured, opened the wrong tab.
* Issues with merge tag modifiers added by GravityView, which modified a field's stored value instead of its displayed value:
- Text modifiers on Radio, Drop Down, and other choice fields changed the choice's value instead of its label (for a "By Phone" choice with the value `phone`, `:strtoupper` showed `PHONE` instead of `BY PHONE`);
- Some modifiers removed HTML escaping from text fields;
- `:format:Y-m-d` on a Date field showed the field's display format (such as `03/09/2026`) when the stored date was already in the requested format;
- Gravity Forms modifiers in the same merge tag, such as `{Contact Method:1:value,strtoupper}`, were ignored.

#### Developer Updates
* First and Last lookups in `[gventry]`, `[gvfield]`, `[gv_entry_link]`, and the Entry blocks now run the `gravityview/view/entries` filter, which receives the looked-up position as a new fourth argument (`null` for the View's page), and return nothing if a callback removes the boundary entry instead of moving on to the next one.
* Added `gk/gravityview/view/boundary-entry/run-entries-filter` filter to stop First and Last lookups from running the `gravityview/view/entries` filter.
* Added `gk/gravityview/edit-entry/redirect` filter to change where Edit Entry redirects users after an update.
* Added `gk/gravityview/fields/gravityview-view/pre-render` filter to replace a View field's output before it renders the embedded View.
* Added `gk/gravityview/shortcode/is-reembedded` filter to let a View rendered inside another View's page show its Single Entry pages and widgets.
* Added `View::get_entry()`, which returns an entry only if the View lists it, and `View::lists_entry()`, which checks an already-loaded entry against the View's filters and is now used by `GVCommon::check_entry_display()`.
* `GVCommon::check_entry_display()` now allows an Embed Only View's entries on pages that belong to a different View, while the View's own URL stays closed.
* `gravityview()->request->is_entry()` called without a form ID now looks up custom entry slugs only in the form of the requested View.
* Items added through the `gk/gravityview/search/searchable-fields/allowed` filter can set `is_search_key` to `true` to keep a non-field search key, such as a map area, searchable when "Search Everything" is limited to visible fields.
* The REST API's single entry route now returns 404 for every entry the View doesn't show, including unapproved entries and entries from other forms, which previously returned 403.
* Fixed a PHP warning logged on every page after the first when editing multi-page forms in Edit Entry.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.36.0.