Black Friday: 30% OFF em todos os planos, já aplicado no carrinho Ver planos
Entrar Carrinho

GravityView DataTables Changelog

Todas as versões registradas, da mais nova para a mais antiga, com o que mudou em cada uma.

Última 3.14.215 versões

Sem data · 15 versões

  1. 3.14.2

    Última
    6 alterações
    Alterações
    • This release improves security, fixes tables that showed every entry in some placements, and fixes DataTables Views in PDFs.
    • 🔒 Security
    • Tables could show entries outside their search settings, or load "Embed only" Views outside the pages that embed them (requires GravityView 3.9.0 or newer).
    • When logging is turned on, log messages written while a table loads now record only the amount of stray output and the file and line of any error, instead of text that could contain entry values.
    • Tables placed outside the page content, such as by the theme or in another View's Single Entry layout, showed every entry, and "Embed only" tables showed "This table could not load" (requires GravityView 3.8.1 or newer).
    • In PDFs from [PDF for GravityView]
  2. 3.14.1

    9 alterações
    Alterações
    • This update fixes several issues with loading, searching, and entry links in tables, and improves compatibility with GravityCalendar, Multiple Forms, and PHP 8.4.
    • 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.
  3. 3.14.0

    14 alterações
    Alterações
    • This release improves accessibility and fixes several search issues, including problems with the Search Bar widget's Clear button and with Views embedded more than once on a page.
    • Note: DataTables now requires PHP 7.4 and WordPress 6.5 or newer.
    • ✨ Improved
    • 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).
    • 💻 Developer Updates
    • 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.
  4. 3.13.2

    2 alterações
    Alterações
    • This release resolves a memory exhaustion issue that could occur when searching tables on large forms.
    • Searching a table could exhaust the site's memory on large forms, particularly with "Show entries" set to All.
  5. 3.13.1

    6 alterações
    Alterações
    • This update fixes tables rendered from a stale page cache after a View's columns changed, and sorting of Currency, comma-decimal Number, and Time columns in client-side Views.
    • 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.
  6. 3.13.0

    9 alterações
    Alterações
    • This release adds a "Column Widths" setting controlling how Percent Width columns behave on narrow screens, and fixes exports repeating link addresses after values along with several column alignment issues.
    • 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).
    • ✨ Improved
    • 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 headings stayed out of line even after the header dropped back into place.
  7. 3.12.0

    10 correções30 alterações
    Corrigido
    • Fixes a View restricted using the "Search Value" setting exposing additional entry data outside the search. Please update.
    • Fixes a table too wide for the space around it being cut off or pushing the whole page sideways, instead of scrolling within its own area.
    • Fixes CSV files containing accented text not displaying properly in Excel.
    • Fixes sorting issues
    • Fixes searching issues
    • Fixes field filter issues
    • Fixes column width issues
    • Fixes issues on pages that embed the same View more than once: "Clear" reset every copy, searching from the second acted on the first, and all copies shared one saved table state.
    • Fixes FixedHeader forcing the horizontal-scroll layout, and its floating header drifting out of line with its columns.
    • Fixes settings that were not being applied
    Alterações
    • A huge bug fix update, columns can now be pinned, and exports now contain every entry rather than just the current page. Includes security improvements; please update!
    • GravityView 2.57 or newer is now required.
    • 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.
    • ✨ Improved
    • 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.
    • 🔒 Security
    • 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.
    • A View sorted by "Random" repeating rows as you page through. It now loads all matching entries at once, which adds to the initial load time on a View with many entries
    • The View's Sort Field setting not being applied
    • A direction set on a shortcode or block being ignored
    • Sorting by a joined form's field (Multiple Forms) preventing the table from loading, or leaving the rows in place
    • A blank date sorting as though it were today.
    • A Search Bar search combined with a column filter matching either one instead of both
    • Multi-word searches not requiring every word
    • Column filters on joined Name and Address fields searching the wrong form
    • A multi-select search field preventing search from working.
    • A View with "Enable Field Filters" on, but no fields chosen in "Fields With Filter", showing no filters instead of one on every eligible column
    • "Clear" leaving the column filters in place
    • A cleared date range keeping its dates on screen
    • Filters not being clickable on a table with pinned columns
    • Resizing the window discarding whatever had been typed.
    • "Percent Width" not applying in both processing modes
    • Columns left blank not sharing the width remainder evenly
    • Widths shifting once data loads. (Superseded in the next release: widths shift again by design where a column would otherwise be too narrow for its content. Choose "Keep the column at its set width" under Column Widths to hold them.)
    • "Offset entries starting from"
    • "Save Table State" on embedded Views
    • Scroller's "Row Height"
  8. 3.11.0

    7 alterações
    Alterações
    • This release tightens security around who can load a View's entries and fixes several loading and sorting issues in DataTables Views.
    • 🔒 Security
    • 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.
  9. 3.10.0

    12 alterações
    Alterações
    • This release improves rendering performance, fixes Views interfering with each other when embedded together on one page, corrects filtered search-result counts, and fixes URL-based Filter & Sort conditions returning no entries behind a full-page cache.
    • ✨ Improved
    • 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.
    • 💻 Developer Updates
    • 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.
  10. 3.9.1

    6 alterações
    Alterações
    • This update resolves single-entry links failing on Views with a large number of columns, along with multiple Search Bar Clear button issues.
    • 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+.
  11. 3.9.0

    1 correção4 alterações
    Corrigido
    • Fixes the Approval and Star per-column filters appearing as plain text inputs instead of dropdown menus.
    Alterações
    • This release exposes DataTables View settings to GravityView's REST inspector and the GravityKit Abilities API, switches DataTables search to GravityView's built-in search, and fixes the Approval and Star column filters.
    • 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]
    • ✨ Improved
    • Replaces DataTables' custom entry search with GravityView's built-in search (GravityView 2.57 and newer).
  12. 3.8.1

    2 alterações
    Alterações
    • This update fixes DataTables scripts not loading in some embed locations.
    • 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.
  13. 3.8.0

    3 alterações
    Alterações
    • This release adds per-column filtering for Gravity Forms fields with multiple sub-inputs in server-side processing mode and fixes invisible filter inputs on Hidden field columns.
    • 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.
  14. 3.7.5

    2 alterações
    Alterações
    • This release fixes DataTables pagination state persisting when search filters change.
    • DataTables pagination state persisted when switching between different search filter values, causing tables to open on the wrong page or show no results.
  15. 3.7.4

    2 alterações
    Alterações
    • This update fixes GravityEdit inline editing in client-side processing mode.
    • GravityEdit inline edit popups for radio buttons, checkboxes, and other complex fields were empty when DataTables was set to Preloaded (client-side) processing mode.

Changelog publicado pelo desenvolvedor, no idioma original.