Gravity View history.

This release adds display options to the Entry Notes field, improves drag-and-drop in the View editor, resolves an HTML escaping issue in the View editor, and fixes issues with search, multi-form Views, and the View block. #### 🚀 Added * The Entry Notes field can now display the number of notes, a simple Yes/No, or custom text (merge tags supported) instead of the notes themselves — useful for flagging entries that have been commented on, including in exports. #### ✨ Improved * Dragging a field in the View editor now follows the pointer, so the zone under the mouse receives the field — narrow and empty zones are easier to target. #### 🐛 Fixed * HTML in a form field's label was output without escaping in the View editor. * The Entry Notes field exported an empty column to CSV. * Searching by Entry Date returned the wrong entries on sites with a non-UTC timezone — results were shifted by the timezone offset, so entries from the searched date were missing while entries from a neighboring day appeared. * Table layouts using a theme other than Legacy displayed a solid white background behind the table, so rounded corners looked square on colored or dark pages. * Issues in Views that combine entries from multiple forms using the [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension: - Pagination and entry totals counted only the primary form's entries on Gravity Forms 3.0, so pages of results could be missing and reported counts were too low; - Single entry pages could open the wrong entry, or none at all, on sites that use custom entry slugs. * Dragging fields in the View editor: the Move and Duplicate buttons wrapped onto a second line in narrow columns, and a field could not be picked up when the drag started on those buttons. * View block issues in the block editor: - Enabling Preview loaded the site's front-end styles into the editor and changed its appearance — preview styles now load only inside the editor canvas; - The block's controls (View selector, Preview toggle) appeared unstyled; - A preview that failed once kept showing the error after a later preview succeeded. * An "Entry meta already set" error was repeatedly logged when another plugin (e.g., GravityBoard) had already registered the same entry meta key. * PHP warnings ("Undefined array key 10") appeared above Views on sites with custom code attached to the deprecated `gravityview_after` action at a non-default priority. * URLs registered by other plugins (such as Uncanny Toolkit Pro's group sign-up pages) redirected to the home page on sites that use a static front page. * GravityView's notification events (entry approved, updated, deleted, duplicated) were not sent — with no error — on sites where another plugin modified the form through the `gform_pre_render` filter. #### 💻 Developer Updates * Views that combine entries from multiple forms now pass an extra `union` key in the SQL fragments array filtered by `gform_gf_query_sql`, holding the `UNION ALL` statements and the subquery's closing alias. Code that rebuilds that array from a fixed list of keys needs to carry it through, or the query loses its unioned forms. #### 🔧 Updated * [Foundation](https://www.gravitykit.com/foundation/) to version 1.28.0.

This update resolves a lightbox error in Views with page-dependent Advanced Filtering conditions and clears a stuck dashboard warning about the extension being inactive. #### 🐛 Fixed * Opening an entry in a lightbox showed "The requested entry could not be found." when the View's [Advanced Filtering](https://www.gravitykit.com/products/advanced-filter/) conditions depended on the page the View was embedded on (e.g., using `{custom_field:...}` or `{embed_post:...}` merge tags). * A dashboard warning that the [Advanced Filtering](https://www.gravitykit.com/products/advanced-filter/) extension was inactive could remain stuck and non-dismissible after the extension was reactivated; it is now cleared automatically. #### 🔧 Updated * [Foundation](https://www.gravitykit.com/foundation/) to version 1.26.0.

This release adds a Table layout row-header setting for better screen reader support and a View editor warning when the Edit Entries bulk action can't run on the frontend, restores the LifterLMS integration, scopes a front-end search to the View it was performed on, includes security hardening for embedded Views, and fixes an issue that could prevent activation on some configurations, along with several lightbox, access, accessibility, and Vantage-style layout issues. #### 🚀 Added * Table layout: a new "Use this field as a row header" field setting renders that column's cells as ` ` instead of ` `, so screen readers announce the identifying cell (like a name or title) as context for the other cells in the row. #### ✨ Improved * Hardened the "Enhanced Security" embed secret. Existing embeds keep working; if one ever stops rendering, re-copy its embed code from the View editor. Developers can require the new secret on specific Views (see Developer Updates). * The View editor now warns when the Edit Entries bulk action can't run on the frontend because the View's form uses conditional logic, instead of allowing the action to be configured and silently do nothing. * Phone field compatibility with Gravity Forms 3.0+. #### 🐛 Fixed * An entry opened in a lightbox showed "The requested entry could not be found." when the View's filtering depended on a value from the page request (e.g., [Advanced Filtering](https://www.gravitykit.com/products/advanced-filter/) configured to read a URL parameter). * An entry opened in a lightbox could show a raw error (`{"code":"rest_cookie_invalid_nonce",...}`) instead of the entry when the visitor had logged out or their session expired (for example, a tab left open past the daily security-token refresh). The lightbox now falls back to the normal access-controlled response: a public entry displays, and a restricted one shows the friendly "could not be found" message. * The confirmation message did not display after duplicating or deleting an entry from the front end. * On the List layout, placing heading markup (such as an ` ` in a Custom Content field) in the Listing Title or Subtitle zones left an empty heading in the page that accessibility checkers like WAVE flagged as an "Empty heading" error. The layout's heading wrapper now becomes a ` ` when the field's content is itself a heading, and is omitted entirely when there is nothing to display. * Entries appeared in the Multiple Entries layout but showed "You are not allowed to view this content." when opened or edited, even by administrators. This affected entries whose status was saved with different capitalization (e.g., `Active` instead of `active`), which can happen when entries are imported. * A Search Bar Date Range field overflowed its column in both "Separate Fields" and "Combined" modes, running off-screen or overlapping the adjacent field; the pickers now shrink to the available width and stack when the column is narrow. * The Search Bar's Search button rendered at the horizontal center of the form instead of below the search fields, and on browsers without `:has()` support it aligned with a neighboring field's label instead of its input. * The Search Bar's Clear/Reset button was missing on pages without an active search, so changing inputs no longer revealed the Reset button; it is now always part of the form again and appears when there is something to reset or clear. * Removing the last widget from a widget-area row and updating the View removed the row itself from the editor with no way to add it back; the default full-width and half-width rows now always stay available as drop targets. * Activating GravityView could prevent a site from loading when its theme or another plugin already included the same email-obfuscation library. * A deprecation warning ("The gravityview_template_..._options hook is deprecated") was logged blaming an add-on such as [Gravity Flow](https://gravityflow.io/) when the add-on registered a custom field or widget type, even though GravityView itself attaches that hook on the add-on's behalf. * The GravityView integration was missing from the [LifterLMS](https://lifterlms.com/) Settings → Integrations screen (and the "My Forms" student dashboard tab with it) since the 3.0 update. * The `[gv_entry_link]` shortcode with `lightbox="true"` opened a full page instead of the lightbox when the View's entries were loaded over AJAX, such as on the [DataTables](https://www.gravitykit.com/products/datatables/) layout. * A [DataTables](https://www.gravitykit.com/products/datatables/) View using the Vantage theme rendered a narrow table pushed to one side of the View, with empty space beside it, when FixedHeader or FixedColumns was enabled. * A "translation loading triggered too early" (`_load_textdomain_just_in_time`) notice appeared on WordPress 6.7 and newer because some widgets and field types loaded translations too early. * Single entry pages could fail to load when custom entry slugs were enabled and an entry link was built for an entry that could not be resolved, such as by the [WPML]

This release hardens lightbox entry access, fixes opening and editing entries in a lightbox, and fixes an issue with the Bulk Edit action's field picker. #### 🔒 Security * Hardens access control for entries opened in a lightbox. We recommend updating to the latest version. #### 🐛 Fixed * Fixes an entry showing "The requested entry could not be found." when opened or edited in a lightbox (a regression introduced in 3.0.1), even though the same entry opened correctly as a full page. This affected Views set to "Embed Only" and Views using a custom entry slug. * When using the Bulk Actions "Edit Entries" action with "Pick specific fields", a selected form field was not shown the next time the View editor settings were opened, causing the selection to be lost when the View was saved again. #### 🔧 Updated * [Foundation](https://www.gravitykit.com/foundation/) to version 1.24.2.