Release v3.5.0
Gravity View v3.5.0
What's new in v3.5.0
Gravity View v3.5.0 was released on . The best way to display Gravity Forms entries on your website GravityView is the best way to display Gravity Forms entries on your website. See the full changelog below and compare with the complete version history.
Release details
Released
7.3 MB
File available
Changelog
Other
- This release adds default values for Search Bar fields, improves screen reader navigation, and fixes several search, sorting, and display issues.
- *Note: GravityView now requires WordPress 6.5 or newer.**
- #### 🚀 Added
- Default Value setting for Search Bar fields, which pre-fills the field and filters the View until a visitor searches, offering a picker of choices for fields that have them.
- "No value" option setting for radio button search fields, adding a choice that clears the field since radio buttons cannot otherwise be deselected.
- #### ✨ Improved
- Screen reader navigation:
- The Search Bar is a search landmark, the entries are a named region, and the View title names both;
- Pagination arrows and First/Last links have accessible names;
- Radio, checkbox, date, date range, and number range Search Bar fields announce their field name, which screen readers previously skipped;
- Links search fields read as a named list of choices, announcing the field name and the active option.
- Readable query keys in search, sort, and pagination links (for example, `sort[3]` rather than `sort%5B3%5D`).
- Vantage theme styling of DataTables Views: pagination buttons match the rest of GravityView, the page-length control sits at the end of the toolbar, and focus outlines are fully visible.
- Keyboard and screen reader accessibility of conditional logic: focus stays in place when adding or removing a condition, the AND/OR switch is a single control, and date fields and buttons identify the field they belong to.
- Wider Custom Value box in narrow settings panels.
- #### 🐛 Fixed
- The User Activation field showed "Invalid activation key" instead of the Activate User button on multisite subsites.
- Issues in Views that combine entries from multiple forms ([Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension):
- A Search Bar field from a joined form searched the View's main form instead, matching the wrong entries or none at all;
- Filters on a joined form's fields did not work with relative dates such as "yesterday";
- Sorting by a field did nothing on sites running Gravity Forms older than 3.0.0.1.
- Vantage theme issues in the Search Bar:
- A single-checkbox search field showed its checkbox below the field name instead of beside it;
- Fields in the Advanced Search section ignored the Search Bar's grid, losing their column widths, spacing, and single-column layout on mobile.
- Choosing an option in a Links search field cleared the other search fields' values.
- Views added to a block theme's template or template part through the Site Editor were not recognized as part of the page.
- The `:diff` merge tag modifier (for example, `{date_created:diff}`) was off by the site's UTC offset, so an entry created two hours ago could show as "2 hours from now".
- A `form:` merge tag showed a value from the main form when the target form no longer had that field.
- Filters on product prices matched the wrong entries, especially with currencies that use a comma for decimals or place the symbol first (such as Pound Sterling).
- The page scrolled when a date picker calendar was opened or closed.
- #### 💻 Developer Updates
- Search Bar fields from a joined form now render the matching `filter_ : ` key.
- The `gk/gravityview/view/entries/query/sorting-parameters` filter now provides a `form_id` key on each sorting parameter, identifying the form the sort column belongs to.
- The `{gv_entry_link}` merge tag wrote a deprecation notice to the debug log every time it rendered.
- Search Bar fields that hold a group of inputs (radio, checkbox, chained select, date, date range, number range, and entry date) now render as ` ` with a ` ` instead of a ` ` with a ` `:
- Class names, IDs, input names, and the per-choice `.gv-check-radio` labels are unchanged;
- Custom CSS works with both versions when it leaves the element name off the class (`.gv-search-box`, not `div.gv-search-box`) and targets both field-name elements (`.gv-search-box > label, .gv-search-box > legend`).
- #### 🔧 Updated
- [Foundation](https://www.gravitykit.com/foundation/) to version 1.33.0.
Added
- the `GET /wp-json/gravityview/v1/views/{view_id}/refresh` endpoint, used by GravityKit layouts and extensions to fetch a View's entries, entry total, and page window for a given query, and enabled per layout with the `gk/gravityview/view/refresh/live` filter (documented in `docs/view-refresh.md`).
- sorting by a joined form's field on any layout with a `sort[ : ]` URL parameter, ignoring keys that name a form the View does not join.
- the `gk/gravityview/view/output` filter to modify a View's fully rendered HTML before it is returned.
- the `gk/gravityview/search/field/default-value` filter to provide or override a Search Bar field's default value.
Compatibility
- Requires WordPress
- 6.5
- Tested up to
- 7.1.3
- Requires PHP
- 7.4.0
Verified safe
Gravity View v3.5.0 scanned clean with no security threats detected.
View full scan report