Changelog do GravityView – DataTables Extension

Melhoria

• In some setups, such as a View with a Calendar widget from GravityCalendar 2.23.1 or older, a DataTables View embedded outside the page content (for example, by the theme) searched with "Contains" for most Search Operators, including "Not Equal" and "Not In" (requires GravityView 3.8.0 or newer).
• On sites with permalinks set to "Plain", Single Entry, Edit Entry, and Delete Entry links in the table opened a page of raw data.
• The Calendar widget showed no events in DataTables Views on sites running GravityCalendar 2.23.1 or older.
• The table showed "This table could not load": On some sites where another plugin or the theme printed stray output, such as blank lines after a closing PHP tag;; After changing page, sorting, or searching when the server took more than 30 seconds to respond, before the results eventually appeared.
• On Views that union forms with Multiple Forms, the table ignored the field mapping for entries from the added form, leaving mapped columns empty or showing fields the View was not set to display, including in Copy, CSV, and Print exports and in Preloaded (Client-side) search.
• PHP deprecation notice ("Implicitly marking parameter $request as nullable is deprecated") on PHP 8.4 or newer.

Melhoria

• DataTables now requires PHP 7.4 and WordPress 6.5 or newer.
• Screen reader navigation, with the table's entries now identified as a named region, as in GravityView's other layouts.
• Date Filter Type setting in the View editor, which is now hidden rather than dimmed when processing is set to Ajax (server-side), so keyboard users can't reach it.
• Views with the "Hide View data until search is performed" setting enabled still showed entries before a search, including in client-side processing mode.
• Issues with the Search Bar widget's Clear button: After a search field was changed, the button switched to "Reset" but cleared the entire form and reloaded the results instead of restoring the values the page loaded with, as it does in GravityView's other layouts;; Clearing removed a field's default value instead of restoring it;; Clearing left fields using the Radio input type with no option selected instead of "All", and kept the selected link highlighted in fields using the Links input type.
• A table could display another table's search results when the same View was embedded more than once on a page (requires GravityView 3.7.0 or newer).
• DataTables templates now fire the gk/gravityview/template/entries/before and gk/gravityview/template/entries/after actions around the table, as GravityView's other layouts do.
• On GravityView versions that provide the /refresh endpoint, tables now load their rows through it instead of a separate request, and the gravityview/datatables/output filter is applied to those rows as well.

Melhoria

• Searching a table could exhaust the site's memory on large forms, particularly with "Show entries" set to All.

Melhoria

• A page cache that served a copy saved before the View's columns were changed showed values under the wrong headings, or dropped and blanked them, the table now reports that the page is out of date instead of displaying data that does not line up.
• Sorting issues in Views using "Preloaded (Client-side)" processing: A Number column formatted as Currency did not sort at all, with the heading showing its sort arrow but no row moving;; A Number column using a comma for its decimal point ordered by the digits rather than by the amount;; A Time column ordered alphabetically, placing afternoon times ahead of morning ones.

Melhoria

• A "Column Widths" setting on the DataTables tab for columns using a Percent Width, choosing between "Widen the table and scroll sideways" (default setting that keeps every value readable) and "Keep the column at its set width" (holds your configured widths at any screen size, letting a wider value overlap the next column).
• A Percent Width is now the share of the table a column aims for rather than one it is held to, so columns whose values need more room can take it once the rows load, choose "Keep the column at its set width" to have the percentages honored exactly.
• Exports repeated a value's link address after it, a name linked to its entry exported as Jane Doe ( and phone or email columns exported their own address alongside the value (File Upload, Website, Entry Link and Edit Link columns still export the address, since there the address is the value).
• Column alignment issues, most visible on mobiles devices: Columns were narrower than the values they held, breaking headings one letter per line and running values across the column beside them;; Column headings and the footer stayed behind when the table was scrolled sideways, leaving every heading over the wrong column;; Column headings and the footer kept a width the rows no longer had when a web font finished loading after the table drew, including tables using a floating header, where…

Melhoria

• Field settings to pin a column to the left or right edge of the table, and to choose which columns collapse first in Responsive mode.
• A "Clear Filters" button that empties every field filter at once, enabled in View Settings on the DataTables tab.
• Expands exports to cover every matching entry, honoring the active search, filters and sorting.
• Shows a message and a Retry button when a table cannot load its data, instead of appearing to load forever. Administrators also see which plugin caused the failure.
• Truncates a long field filter label with an ellipsis instead of cutting it mid-word, and carries the full text for hovering and for screen readers.
• Removes the Page Links, Pagination Info and Page Size widgets from DataTables Views; any already added stop rendering. The table's own page-size menu does what Page Size did without reloading the page, and the other two never displayed anything.
• Registers field settings on gk/gravityview/template/options instead of the deprecated gravityview_template_field_options.
• Extends the REST and inspector schema to cover the whole DataTables settings group, including processing_mode, so a client can discover whether a View uses server-side or client-side processing.
• Passes the View's own strings, merged over the bundled locale, to gravityview/datatables/config/language rather than the locale alone.

Melhoria

• Tightened the access checks applied before a View's entries are returned to the browser.
• Logged-out visitors saw "Loading data…" indefinitely, with no explanation, when a full-page cache served a page whose security token had since expired.
• After a failed request, a later search that genuinely returned no results was labeled as a server error.
• When rows were grouped by a column ("RowGroup"), clicking its header for descending order flipped the arrow but left the rows unchanged, the groups now reverse, and sorting any other column still keeps the rows grouped.
• A sort parameter in the page address discarded every column the visitor sorted for as long as it stayed in the address bar, clicking a column header now takes precedence, and where the sorted field is a column the table also starts on the order the address asks for.

Melhoria

• Page rendering performance: the table configuration is now built once per View and shared across DataTables features instead of being rebuilt by each feature.
• Client-side search performance when multiple Views are displayed on the same page.
• Tables did not display when the same View was embedded more than once on a page.
• Responsive, FixedHeader, and FixedColumns settings were applied to the wrong table when multiple Views were displayed on the same page.
• A View using client-side processing conflicted with other tables on the page that use the DataTables library.
• The table information text did not report the total number of entries when results were filtered by a search ("Showing X to Y of Z entries (filtered from N total entries)").
• On a View with URL-based Filter & Sort conditions (e.g. {get:city}), the DataTables AJAX refresh could return no entries (clearing the results and any Calendar widget) when the page was served from a full-page cache. The AJAX request now also carries the live URL query so the filters resolve regardless of the cached markup.
• DataTables now uses current GravityView hooks instead of ones deprecated in GravityView 2.55.
• The gk.datatables.options JavaScript filter now receives a per-table copy of the configuration. Mutating the filtered object no longer modifies the shared window.gvDTglobals entries; return the modified object instead.

Melhoria

• Single-entry links (View, Edit, Delete) on Views with a large number of columns could fail with an "HTTP 414 Request-URI Too Long" error, because DataTables request parameters were appended to each link's URL.
• Search Bar Clear button issues: Clearing a search reset the results but left date picker fields populated, making the search appear still active;; After clearing a search, the Clear button could not reappear when changing inputs or searching again until the page was reloaded.
• A "translation loading was triggered too early" PHP notice in WordPress 6.7+.

Melhoria

• DataTables View settings can now be read, configured, and discovered through GravityView's REST inspector API and the GravityKit Abilities API, so the GravityKit MCP can manage them.
• Replaces DataTables' custom entry search with GravityView's built-in search (GravityView 2.57 and newer).

Melhoria

• Export buttons (Copy, CSV, Excel, Print) and other DataTables scripts did not load when a View was placed outside the main page content, such as in a theme template, widget, or page builder.

Melhoria

• Server-side per-column filtering for Gravity Forms fields with multiple sub-inputs, such as Name, Address, and Email with Confirmation enabled.
• Per-column filter inputs on DataTables columns bound to Gravity Forms Hidden fields were rendered as and therefore invisible to the user.

Melhoria

• DataTables pagination state persisted when switching between different search filter values, causing tables to open on the wrong page or show no results.

Melhoria

• GravityEdit inline edit popups for radio buttons, checkboxes, and other complex fields were empty when DataTables was set to Preloaded (client-side) processing mode.

Melhoria

• DataTables getting stuck on "Loading data…" when the sort_field shortcode attribute points to a column not visible in the View.
• PHP warning triggered when a View renders a field that no longer exists in the Gravity Forms form.
• PHP notice logged due to an unregistered gv-datatables script dependency on Single Entry and Edit Entry pages.

Melhoria

• The search_field and search_operator attributes were being ignored when embedding a DataTables View via shortcode.

Melhoria

• Sorting now works correctly when the sort field configured in View Settings is not a visible column in the DataTables table.

Melhoria

• Support for Gravity Flow Workflow Approval Links field.
• Rows were not properly grouped under a single heading when using RowGroup with Inline Edit enabled.
• The {sequence} merge tag restarting on each page instead of continuing across pages.
• JavaScript error that could prevent DataTables from loading on certain site configurations.

Melhoria

• URL query parameters were not updated with all Multi Select field selections when searching, causing the table to be improperly filtered after reloading the page.

Melhoria

• Footer calculations for fields configured to include all View entries only counted those visible on the current page when using client-side processing mode.

Melhoria

• Support for searching Date and Entry Date fields using single or range inputs in client-side processing mode.
• Number field search using ranges not working in client-side processing mode.
• Clearing search no longer reload the pages.
• JavaScript errors that occurred when the same View was rendered multiple times on a page.

Melhoria

• This is a hotfix release to revert to 3.5.2; the 3.5.3 release introduced multiple issues that we will return to in a future release.

Melhoria

• Views using the DataTables layout were not working in Dashboard Views.

Melhoria

• Conflict with the Yoast SEO plugin that could prevent DataTables from rendering.