Gravity View v3.7.0

This release makes "Search Everything" and sorting use what fields display rather than what they store, fixes several security issues around entry visibility and exports (we recommend updating), and resolves many issues with embedded Views, search, multi-page Edit Entry, and combined forms. #### ✨ Improved * Broader "Search Everything" matching that covers what fields display, not just what they store: - Names of users, posts, entries, and database table rows that Dynamic Lookup, GP Populate Anything, and GP Nested Forms fields store by ID; - Labels of choice fields, such as Drop Down and Checkboxes; - Fields inside Repeater fields. * Sorting by fields that store the ID of a user, post, entry, or database table row, which now orders entries by the displayed name, including in Views that combine forms with the [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension. #### 🔒 Security * Views embedded with a `{user:...}` merge tag in their search (such as `search_value="{user:ID}"`) showed every entry to logged-out visitors instead of none. * The Entry and Entry Field blocks, the `[gventry]` and `[gvfield]` shortcodes, entry embeds (oEmbed), and the REST API's single entry route could display entries that the View's filters exclude, such as entries hidden by Advanced Filtering conditions or by the "Show only entries created by the currently logged-in user" setting. * Entries not listed on a page could be opened in its lightbox when the page also contained an escaped `[[gravityview]]` shortcode or a secured View embedded without its secret. * The Single Entry page heading of a View embedded in a reusable block could show the title of an entry the visitor wasn't allowed to view. * Search Bar fields restricted to logged-in users could still filter results for logged-out visitors. * A GravityView Search widget left in the WordPress Inactive Widgets area still allowed visitors to search by its fields. * Some values in CSV and TSV exports, including bulk action exports and the attachments manifest, could run as spreadsheet formulas when the file was opened in a spreadsheet application. #### 🐛 Fixed * Pages with a Search Bar widget loaded more slowly after the GravityView 3.5.0 update, increasingly so with each search field, form field, and user on the site. * Custom CSS that arranged List or Layout Builder entries into columns with the Legacy theme, such as the grid CSS from our documentation, displayed every entry in a single column after the GravityView 3.5.0 update. * Entry links set to open in a lightbox, such as `[gv_entry_link lightbox="true"]`, opened a full page instead in [DataTables](https://www.gravitykit.com/products/datatables/) 3.14.0 and later and in Views that refresh results without reloading the page. * Single Entry Title issues: - Single Entry pages and the entry lightbox had an empty title, and the Breadcrumbs block showed "(no title)", when the Single Entry Title setting was empty (the default) or its merge tags had no value for the entry — Single Entry pages now fall back to the page's title; - Single Entry pages of an embedded View with a Single Entry Slug showed the page's title instead of the Single Entry Title, and GravityView Social Sharing & SEO gave them the page's SEO title and the wrong canonical URL; - Views embedded with a merge tag in their search (such as `search_value="{user:ID}"`) showed the page's title instead of the Single Entry Title and couldn't open entries in a lightbox. * Issues on pages that display more than one View or entry embed: - When the same View was embedded more than once, an embed could show another embed's search, page size, or other shortcode settings, lose its widgets, or refuse to open its own entries in a lightbox; - When the same View was embedded more than once, its Single Entry pages displayed the entry once per embed; - A View lost its Search Bar widget, pagination, and other widgets when it followed an Entry block or `[gventry]` shortcode showing a Map View entry, or an entry displayed through a theme's legacy single entry template; - A View embedded in another View's field, such as a Custom Content field, pushed the parent View's remaining entries outside the View. * Issues in Views that combine forms using the Multiple Forms extension: - With entry caching enabled, Views combining many forms through joins or unions could show another View's entries and ignore searches; - With entry caching disabled, a page showing two Views of the same form, one of which combined other forms, could display the first View's entries in the second View; - Sorting by a field that one of the combined forms lacks ordered that form's entries by entry ID and applied the second sort field as the first; - The Entry and Entry Field blocks and the `[gventry]` and `[gvfield]` shortcodes showed nothing for entries from a form combined through a union. * Issues with the First and Last entry options: - The Entry Link block and `[gv_entry_link]` shortcode set to First or Last could link to an entry from a different View on the same page, an