Launch Log: GravityView Pro, paid featured tiers, and a “Pages with this View” menu

Lookup fields using Filter by Field show their choices again when the source form’s matching field holds several values, such as a Multi Select field or a Lookup field that allows multiple selections. The Source Field list no longer offers fields inside a Repeater, which left the Lookup field with no choices, and adding an entry through the Gravity Forms API no longer logs a PHP warning when a checkbox Lookup field’s source form has no entries yet.

Developer updates

• Added the Field::stores_list() method to check whether a field stores multiple values as a single comma-separated string.

On the Edit Entry page of Views with Prevent Direct Access turned on, for users who can't see private Views (such as Subscribers), a file added to an empty Multi-File Upload field was not saved even though "Entry Updated." appeared. A required field also showed "This field is required." and blocked the save. Multi-page forms on the same screen no longer move to the next page when a field on the current page has an error.

Since GravityView 2.29, pages loaded more slowly on sites with a permalink base such as /blog/%postname%/, Plain permalinks, Polylang showing the language code in every URL, an Entry Endpoint with capital letters, or Gravity Forms deactivated, because permalink rules were rebuilt on every page load. That no longer happens.

In Views that combine forms with Multiple Forms, entries are sorted in the right order when one form lacks the field the View sorts by and another plugin adds its own sort, and Views sorted by a Time field show their entries again.

Views built or edited by AI agents through the GravityKit MCP server keep their field settings, such as a Custom Content field's text, including when several fields or widgets change at once. Setting "Sort by field" to a form field is no longer rejected.

Other fixes:

• Single Entry and Edit Entry pages no longer show an error on sites with a View in an Elementor widget and a theme that adds custom fonts to Elementor, such as BuddyBoss Theme (since GravityView 3.8.0)
• Saving a View whose layout is inactive, such as a Map View while Maps is deactivated, no longer erases its layout, fields, and widgets
• Shortcodes in the "No Entries Message" and "No Search Results Text" settings run instead of showing as typed when the View is embedded with its shortcode, in a block theme's template part, or when results update without reloading the page
• Activating GravityView opens its page in GravityKit, then Welcome, instead of sometimes staying on the Plugins screen
• In the View editor, a field's gear button and settings window are named after the field's Label instead of the form field
• Screen readers announce the button that expands a field's settings in the View editor by name instead of "undefined"

Developer updates

• Breaking change: the gk-gravityview/view-settings-patch and gk-gravityview/view-config-apply abilities now save nothing when any setting is rejected, and list every rejected template setting under data.errors. A dotted setting for an inactive add-on (such as datatables.responsive without DataTables), an add-on name whose value is not an object (such as "maps": null), a setting name that is empty once sanitized, or an empty or nested item in a list of choices (such as "sort_direction": ["ASC", null]) returns a 400 error instead of being skipped while the rest was saved.
• An add-on setting sent to those abilities as the dotted slug the schema returns, such as maps.map_type, is now saved to that add-on's settings, and settings are validated when the abilities run from WP-CLI or cron.
• Added the GravityKit\GravityView\View\ViewPages class, whose get() method returns the published pages that show a View and whether the search stopped at its limit, and the gk-gravityview/view-pages-get ability.
• Added the gk/gravityview/view/pages/max-pages (default 500), gk/gravityview/view/pages/post-types, and gk/gravityview/view/pages/content-meta-markers filters to control how pages that show a View are found.
• Added View::shows_on(), which checks whether an embed read from a post shows the View rather than a count.
• Added the gk/gravityview/view/secure-embed-default filter; return false to start new Views with "Enable Enhanced Security" off, without affecting saved Views.
• Added the gk/gravityview/rest/template-settings/view-schema filter to modify a template setting's schema for the View being written to on the Abilities and REST write path.
• Added the gk/gravityview/features/field-types filter to change the form field types a GravityView Pro feature adds.
• Added the gk/gravityview/deactivation/warning filter to add plain text to the GravityView deactivation dialog.
• GravityView Pro: added the gk/gravityview/edit-entry/window-closed filter to reopen or close a View's Edit Window for one entry and action, without granting permission or overriding a Magic Link's expiry.
• ViewCollection::from_content() skips [gravityview] shortcodes inside HTML comments and reads the view_id attribute when id is empty. ViewCollection::from_post() no longer finds Beaver Builder modules set to never show, disabled Divi modules, or shortcodes in Elementor data on a page taken out of Elementor.
• On combined Views, the query that gravityview/view/query receives for each added form includes a GravityKit\GravityView\View\UnionMissingOrder sort for every View sort the form has no field for; keep it in place when changing the sorts.
• Re-enabling the gravityview/post_type/with_front filter after turning it off moves View URLs on the next page load instead of showing "Page not found" until Settings, then Permalinks, is saved.
• GravityView_Entry_Approval::update_approved() called without a form ID clears the View cache for the entry's form instead of form 0.
• Fixed PHP notices: "Array to string conversion" when searching Payment Amount with a Slider in the Search Bar widget; database errors from "Remove all data" on multisite sites that never used Gravity Forms; and "Trying to access array offset on null" from a View sorted by a field its form no longer has.

Conditions on an Event field's dates, or on a date field from a joined form, offered only a calendar. They now accept a custom value and relative dates such as Today and Tomorrow.

Filters on the value 0, such as "Amount is 0", treated 0 as empty, so is 0 also matched entries where the field is empty and is not 0 left them out. Filters using greater than or less than no longer match entries where the field is empty.

The View editor no longer shows a critical error when the View's form has a Dynamic Lookup field on Dynamic Lookup older than 1.2.0, or a Drop Down, Radio, Checkboxes, or Multi Select field with no choices, such as a Populate Anything (Gravity Wiz) field while Populate Anything is inactive.

Preloaded (Client-side) tables without Field Filters sort encrypted email addresses in the right order.

Tables with no entries or search results also work as expected again:

• Preloaded (Client-side) tables with no entries show the No Entries Message instead of the No Search Results Text, and display the form or redirect when No Entries Behavior is set to "Display a Form" or "Redirect to URL"
• HTML in the No Entries Message and No Search Results Text displays as HTML instead of tags
• Shortcodes in these messages run on pages that embed the View with its shortcode, and run in full on the View's own page and in a View block

Developer updates

• Breaking change: the zeroRecords and emptyTable texts in the gravityview/datatables/config/language filter are now rendered as HTML, so a filter that returns plain text containing < or & must escape it (for example, with esc_html()).

Views combining several forms show their entries again when "Move Featured Entries to Top" is on. How Move Featured Entries to Top works explains the setting.

The {featured_tier} merge tag takes these modifiers:

• :badge for the badge
• :until for the date a paid spot ends
• :rank for the tier's rank (1 for the top tier)
• :color for the badge color
• :class for the tier's CSS class
• :id for the tier ID

Developer updates

• Each featured entry gets a gv-featured-tier-{tier ID} CSS class, which stays the same when the tier is renamed.
• Added the gk/featured-entries/tiers filter to change a View's tiers.
• Added the gk/featured-entries/order/paid-statuses and gk/featured-entries/order/subscription-statuses filters to change which payment statuses count as paid.

With GravityView 3.10.0 and later, the Single Entry page of an embedded View with "Prevent Direct Access" turned on shows its reviews and review form again.

Commenting on reviews works in more cases. "Comment on this review" no longer opens a "Page not found" page for a user who already reviewed the entry, on Views with the "Rate" field hidden, or when the link opens in a new tab, and "Log in to comment" returns to the entry after login. Users limited to one review can now comment on reviews. Comments are no longer refused when "Require ratings" is on, and the comment form has a text box when "Hide 'Title' and 'Review' fields from the form" is on. The first link in the "Please moderate" email now opens the entry page.

Rating fixes:

• Clicking new stars when editing a review changes the rating, without clearing it with the trash icon first (since 2.4)
• The review form no longer starts with the stars of the user's existing review picked, which let a review without stars past "Require ratings" (since 2.4)
• A user who rated an entry and then commented on a review sees their stars in the "Rate" field (since 2.4)
• In DataTables Views, paging, sorting, or searching no longer makes the next click in the "Rate" field save the rating again, and the "Rate" field works on the first page of Preloaded tables
• On phones and tablets, one tap saves a rating once, and scrolling with a finger that starts on a star or vote no longer saves a rating
• In Views that join forms, clicking a star or vote in the "Rate" field saves the rating