Launch Log: AI-built boards, inline Entry Tags editing, and Views kept on uninstall

A View that searches a Lookup field for one ID, such as a View embedded in an entry with an {entry_id} search value, now includes entries with several selections in a multi-select Lookup field, and is not searches leave them out. In the Search Bar’s “Search Everything” field, _ and % in a Lookup search match only themselves.

Developer updates

• Added the Field::gk_get_search_target() method, which tells GravityView where to search and sort by a stored ID’s label.

A search for “Bug” no longer matches longer tags such as “Bugfix” in Views (requires GravityView 2.57 or newer) and the Gravity Forms entries list, and tag links work for tags containing & or +.

Other fixes:

• Tags saved as comma-separated text, such as by an import, appear in Views and the entries list, and stay separate tags when the entry is edited
• Using the tag box in a GravityEdit editor no longer stops other clicks on the page from working
• Default tags with accented letters or quotation marks are saved correctly
• Fields shown by an is conditional logic rule on an Entry Tags field are saved
• Gravity Forms entry exports and View CSV and TSV exports show tag names instead of code
• Uninstalling Entry Tags from Gravity Forms’ Uninstall settings screen works

Developer updates

• Replaced GravityView hooks deprecated in GravityView 2.55 with their current equivalents.
• Tag output in GravityView is now built on the gravityview/template/field/output filter at priority 4, before GravityView’s entry link (priority 5) and GravityEdit (priority 6).
• Breaking change: the gravityview/template/field/entry_tags/output filter now receives the finished field HTML, including the tags, any entry link, and GravityEdit’s wrapper.

When a card’s Label uses the same field as the lanes, changing the Label now moves the card to the matching lane, and dragging the card to another lane updates the Label without a reload. Conditional logic on fields that store a user, post, or entry ID, such as Dynamic Lookup, GP Populate Anything (Gravity Wiz), or Nested Forms fields, now matches the name the field shows. Rules using is and is not with a number still compare the ID. @ mention emails offer their own merge tags, such as {notifier_name}, and attachments, mention emails, voting, and rich text in cards and notes get security improvements.

Other fixes:

• Conditions on Entry Date, Date Updated, or Payment Date with a non-date value no longer cause a fatal error on PHP 8
• Conditions using is, is not, in, or not in on Product, Option, or Shipping choices find entries
• Screen readers on translated sites announce the day, month, and year of date conditions in the site’s language
• Cards moved or added by two people at the same time keep the right order
• Permanently deleting a card removes its votes on boards with “Trigger Form Notifications” turned off

Developer updates

• Added board, lane, and card abilities to the WordPress Abilities API under gk-gravityboard/*, runnable at /wp-json/wp-abilities/v1/abilities/gk-gravityboard/<name>/run.
• Added the gk/gravityboard/card/lock_timeout and gk/gravityboard/lane/lock_timeout filters to set how many seconds a card or lane change waits for another change on the same form to finish before it is refused (default: 5).
• Added the gk/gravityboard/attachments/blocked-extensions filter to modify which file extensions are refused on boards that allow all file types.
• Added the gk/gravityboard/merge-tags/assignee-properties filter to modify which user fields the {gravityboard_assignee:<property>} merge tag can output.
• Breaking change: board users and card assignees in the board data no longer include email, and a note’s user_email is empty unless the current user can edit forms.
• The gk/gravityboard/card/sorted hook now skips drags within a lane on boards sorted by votes, since nothing is saved.
• Feed::get_feed() now returns false for feeds that belong to another add-on.
• Deprecated Ajax::can_add_attachment() and Ajax::can_delete_attachment() in favor of Attachments::can_upload_attachment() and Attachments::can_delete_attachment(), and Helpers::has_entries_in_lane() in favor of Helpers::get_lane_entry_ids().

All calendar text can now be translated or reworded with a translation plugin such as Loco Translate. Timed events from external calendar feeds, such as Google Calendar, Outlook, or iCloud, now convert to the site’s time zone like the calendar’s own events.

All-day events in calendar subscription links now end on the right day. One-day events used to end on the day they started, and events without an end date ran until the subscription last updated. Resizing an event across several days on a calendar without an End Date field now undoes the resize, where it used to change the event’s start date.

Developer updates

• The calendar’s language downloads respect the gk/foundation/translations/disable-download filter, so a site that turns off translation downloads gets none.
• Deprecated the gravityview/calendar/scripts/fullcalendar/locales_dir_url filter, which no longer has an effect. Change the calendar’s text with a translation or the gravityview/calendar/options filter, whose values still take priority.

Inline editing of Entry Tags fields gets a set of fixes. Saving on the Gravity Forms entries list now finishes, the editor no longer shows the first entry’s tags alongside the entry’s own, and a tag containing a quotation mark or < no longer erases every tag. Tags saved as comma-separated text open in the tag picker, and an entry with damaged tag data no longer stops inline editing for the fields below it.

Dynamic Lookup fields whose selected record is no longer one of their choices, such as an entry moved to the trash, keep their selection when edited inline. Dynamic Lookup checkboxes show the right boxes ticked after their choices change, and editing another field inline no longer removes those selections.

Saving a field inline no longer removes backslashes from its value. With Inline Edit Mode set to “In-Place,” or when editing a whole column, opening another field while an editor is open now takes one click instead of two.

Views built with the GravityKit MCP now behave like Views built in the View editor. New Views use the site’s default theme instead of Legacy (as do Views created with the REST API), Edit Entry fields show for users editing their own entries, and unsaved settings show their default values. Settings turned on or off with text such as “yes” or “off” are applied correctly, and cloned Views keep their Multiple Forms joins and unions, Layout Builder row settings, and backslashes.

Restoring a View revision now brings back Advanced Filter conditions, Multiple Forms joins and unions, and Layout Builder row settings. Restoring a revision saved before GravityView 3.0.0 no longer removes the View’s form, layouts, fields, and widgets, and the Revisions screen shows the right changes after a restore. In the View editor, Advanced Custom Fields (ACF) fields no longer keep a draft View from publishing or saving, and saving with Enter or during an autosave no longer asks you to confirm leaving the page.

Custom CSS can now override the layout’s styles, such as table cell padding, along with the Vantage theme’s styles and DataTables features such as Buttons. On the Vantage theme, a Google Fonts @import no longer wipes out the rest of the Custom CSS. Views shown inside another View, such as through a Custom Content widget or the [gventry] shortcode, keep their Custom CSS, Custom JavaScript, layout styles, and Style settings.

Views that join or union forms with Multiple Forms get a set of fixes. In joined Views, the Entry Field block and [gvfield] set to First or Last show a value, the Entry block and [gventry] show the joined form’s values, and links such as /entry/12,34/ work. Edit Entry shows and saves the right fields, where a field added from another form could change the entry’s own field with the same ID. In unioned Views, entries from the added form follow the field mapping in CSV and TSV exports and the REST API, and respect field settings such as “Link phone number” and “Encrypt email address.”

Other fixes:

• A search value of 0 in the [gravityview] shortcode or an embedded View is no longer ignored
• In DataTables Views, clearing the Search Bar and searching again shows every entry, and the browser Back button steps back through earlier searches and pages
• “Embed only” DataTables Views placed with Beaver Builder load for visitors and users below the Editor role
• Edit Entry no longer erases GP Populate Anything (Gravity Wiz) Drop Down values that depend on a field placed later in the form
• Edit Entry shows the right fields when the same form is embedded on the page, and a field added to the Edit Entry tab twice saves correctly
• :urlencode no longer encodes Dynamic Lookup values twice, and merge tag modifiers print { instead of { when a value contains a curly brace
• On block themes such as Twenty Twenty-Five, images and entry links open in the lightbox even when the page’s first View has “Enable lightbox for images” turned off
• CSV and TSV exports keep trailing empty values
• Cloning a View from the Views list keeps backslashes in its title and settings
• Sites with a View embed missing its secret no longer create a separate admin notice for every nonexistent address visited

Developer updates

• Added the gk/gravityview/search/empty-value/default filter to set what embeds without a search_value_empty value show when their search value is empty (return none to show no entries).
• Added the gk/gravityview/edit-entry/page-title filter to change the page title on the Edit Entry screen (return an empty string to keep the page’s own title). It and gk/gravityview/edit-entry/document-title default to an empty string when “Use as Page Title” is unchecked.
• Added GV\Entry::is_active() and GV\Entry::is_trashed() methods, which compare the entry’s status case-insensitively.
• Breaking change: gravityview()->plugin->uninstall() now removes only temporary data and keeps Views, entry approval statuses, GravityView entry notes, capabilities, and options. Use GravityKit\GravityView\View\ViewRemover::remove_all() to delete Views.
• Breaking change: GV\View::get_entry() now returns the joined row (a GV\Multi_Entry) on Views that join forms and accepts joined entry slugs such as 12,34. On that row, $entry['id'] and $entry['form_id'] are null, so use $entry->ID or $entry->entries instead.
• Deletes granted by the gk/gravityview/delete-entry/can-delete filter are now checked against the View’s forms and the entry’s status.
• Each View’s Custom CSS and Style settings now print from their own gravityview_view_css_{View ID} stylesheet handle, after GravityView’s stylesheets.
• A View’s id setting now stays an integer when a shortcode embeds the View, so strict (===) comparisons with the View ID match correctly.
• gk-gravityview/view-clone now copies every _gravityview_ meta key of the source View, and View revisions also track _gravityview_filters, _gravityview_form_joins, _gravityview_form_unions, and _gravityview_row_settings.
• gk-gravityview/view-config-get and gk-gravityview/view-settings-patch now return the default value of each core View setting that is not saved, and refuse to turn on show_only_entries_by_current_user when Advanced Filtering is not active or conflicts with the View’s filters.
• The entry lightbox page now includes a doctype, so browsers no longer render it in quirks mode.

On sites with permalinks set to “Plain,” Single Entry, Edit Entry, and Delete Entry links in the table now open the right page instead of raw data. The Calendar widget shows events again in DataTables Views on sites running GravityCalendar 2.23.1 or older. DataTables Views embedded outside the page content, such as by the theme, now honor Search Operators like Not Equal and Not In (requires GravityView 3.8.0 or newer).

On Views that union forms with Multiple Forms, the table now follows the field mapping for entries from the added form, including in Copy, CSV, and Print exports and in Preloaded (Client-side) search. A PHP deprecation notice on PHP 8.4 or newer is also gone.