Changelog do GravityView

Melhoria

• "Delete all Views" button under GravityKit > Settings > GravityView > Delete Views that permanently deletes every View, including trashed ones, without affecting forms, entries, or settings.
• "Use as Page Title" setting on the Edit Entry tab to choose whether the Edit Entry Title also replaces the page and browser tab titles (on by default, so existing Views keep their titles).
• Settings to choose what an embedded View shows when its search value is empty, such as when a {get:customer} merge tag has no value: "When the search value is empty" on the View field, which now shows no entries by default ("is not" searches still show every entry);; search_value_empty="none" in the [gravityview] shortcode;; "Show no entries" in the View block and the Elementor, Divi, and Beaver Builder modules, selected by default for new block, Elementor, and Beaver Builder embeds (new Divi…
• Improved checks when deleting, approving, or rejecting entries from the front end.
• Improved how embedded Views apply their Search Field and Search Value, so they show only the entries they are set to show (sites using the GravityView Widget for Elementor plugin also need its next update).
• Views built or cloned with the GravityKit MCP could show entries their settings were meant to restrict, or allow REST access that was turned off.
• Page and browser tab titles on Views with an Edit Entry Title could show entry values to visitors not allowed to edit the entry.
• Search Operators other than "Is", "Is Not", and "Contains" in the View block, the View field, the Elementor, Divi, and Beaver Builder modules, and the [gravityview] shortcode matched any entry containing the Search Value, so "Not Equal" and "Not In" listed the entries they should have excluded.
• A search value of 0 in the [gravityview] shortcode or an embedded View was ignored, so the View listed every entry instead of those matching 0.
• Issues with Views built with the GravityKit MCP: New Views used the Legacy theme instead of the Default theme setting (GravityKit > Settings > GravityView > Appearance), as did Views created with the REST API;; Edit Entry fields were hidden from users editing their own entries;; Unsaved View settings, such as "Show only approved entries", showed as empty instead of their default values;; Every value of the "No Entries Behavior" setting was refused;; View and field settings turned on or off…
• Cloning a View from the Views list removed backslashes from its title and settings, such as field labels.
• Issues with restoring View revisions: Advanced Filtering conditions, Multiple Forms joins and unions, and Layout Builder row settings were not restored;; Restoring a revision saved before GravityView 3.0.0 removed the View's form, layouts, fields, and widgets;; On sites that limit revisions, restoring the oldest kept revision did not restore View settings, and the notice showed no date;; The revision saved by a restore held the View settings from before it, so the Revisions screen showed the…
• Issues saving Views in the View editor: Publishing a draft View left it as a draft when the View editor showed Advanced Custom Fields (ACF) fields;; Saving a draft was blocked until every required ACF field in the View editor was filled in;; Saving by pressing Enter, or by clicking a save button while WordPress was autosaving, asked to confirm leaving the page and saved only after confirming.
• Issues with Custom CSS and styles: Custom CSS could not override the layout's styles, such as table cell padding;; On Views using the Vantage theme, Custom CSS could not override many of the theme's styles, and rules starting with the layout's class, such as .gv-table-view td, had no effect on the Single Entry page or in the entry lightbox;; On Views using the Vantage theme, Custom CSS containing a Google Fonts @import lost all of its rules, and a