Advanced Filtering Changelog

This release fixes the View editor not opening for some forms, keeps a new View's conditions in step with its form, and corrects conditions on multi-selection fields.

🐛 Fixed

• The View editor could not be opened when the View's form had a Name field saved without its sub-fields.
• On a new View that joins forms with Multiple Forms, conditions could not use the joined form's fields until the View was saved.
• Changing a new View's form kept its conditions on the old form's fields. Those conditions are now removed, and conditions on entry details such as Entry ID move to the new form.
• On a View saved as a draft before a form was chosen, conditions could not be added right after one was chosen.
• Issues with has ANY of, has ALL of, and has NONE of conditions:
  • On Dynamic Lookup fields with "Allow multiple selections" and without the enhanced user interface, they worked only for entries with a single selection;
  • In field conditional logic, they did not check every selection on Multi Select fields and on Dynamic Lookup fields with "Allow multiple selections";
  • On Multi Select fields that store a comma-separated list, they did not find a choice with a comma, such as "Paris, France", and a condition for "Paris" or "France" wrongly matched it.

This release speeds up filters on GP Nested Forms and similar fields, and fixes several issues with filter results, dropdowns, and date pickers.

✨ Improved

• Filter dropdowns that search users, entries, or posts now load their choices as soon as they are opened.

🐛 Fixed

• Filters using the {get} merge tag found no entries or the wrong ones when the value in the page address contained &, +, or % (such as "Research & Development"), and changed other {get} merge tags on the page.
• "Has any of", "has all of", and "has none of" filters on Dynamic Lookup fields with "Allow multiple selections" and the enhanced user interface worked only for entries with a single selection.
• "Any form field" filters, and filters on fields that store a user, post, or entry ID, did not match user names or post titles containing "&", such as "Smith & Jones".
• Filters on GP Nested Forms fields and other fields that store several users, posts, or entries (such as Dynamic Lookup and Populate Anything fields) were slow on forms with a few hundred entries.
• Merge tags with the form: modifier could cause an error when another plugin processed them without a form.
• Filters using the form: merge tag modifier could compare against the wrong value when the joined form's value looked like a merge tag.
• Filter dropdowns could open behind the WordPress admin bar, pressing Enter on a selected choice cleared it, and pressing Enter on the clear button did nothing.
• When WordPress was set to a language other than English, operators with an apostrophe showed ' (such as "n'est pas" in French).
• Issues with date filters:
  • When WordPress was set to a language other than English, month names, weekdays, and labels appeared in English;
  • Once a date was picked, the weekday names in the calendar were off by one day in time zones west of UTC (such as the US), and screen readers announced the calendar as "Event".

This release makes filters on Dynamic Lookup, Populate Anything and Nested Forms fields match the name they show, and fixes filters on product choices and on dates whose value is not a date.

✨ Improved

• The Advanced Filter section in the View settings is now announced by screen readers as a named group with its description.
• Filters on a field that stores the ID of a user, post or entry, such as a Dynamic Lookup, Populate Anything or Nested Forms field, now match the name the field shows, and only the records the visitor may see. "Is" and "is not" with a number still compare the stored ID.

🐛 Fixed

• "Is", "is not", "in" and "not in" filters on a choice of a Product, Option or Shipping field found no entries.
• A filter on Entry Date, Date Updated or Payment Date whose value is not a date, such as a merge tag for a text field, caused a fatal error on PHP 8.
• On a translated site, screen readers announced the day, month and year of a date filter in English.

This release makes conditional logic more accessible and fixes several filtering issues.

Note: Advanced Filter now requires WordPress 6.5 or newer.

✨ Improved

• Keyboard and screen reader accessibility of conditional logic: focus stays in place when adding or removing a condition, the AND/OR switch is a single control, and date fields and buttons identify the field they belong to.
• Wider Custom Value box in narrow settings panels.

🐛 Fixed

• Filters on product prices matched the wrong entries, especially with currencies that use a comma for decimals or place the symbol first (such as Pound Sterling).
• Filters on a joined form's fields (Multiple Forms) did not work with relative dates such as "yesterday".
• A form: merge tag showed a value from the main form when the target form no longer had that field.
• The page scrolled when a date picker calendar was opened or closed.

This release refines the date and choice pickers used by conditional logic, and fixes choice dropdowns on non-HTTPS sites, form: merge tags, and Number field comparisons.

✨ Improved

• Enhanced conditional logic:
  • Date filters now have a clear button, so a date can be emptied without selecting over it;
  • The date picker's calendar and clear buttons now sit inside the field and level with the value, so a date field is recognizable before reading it;
  • Dynamic Lookup filters now use the Lookup plugin's own choice API when available (Gravity Forms Lookup Field 1.8 or newer), with the previous integration kept as a fallback for older versions.

🐛 Fixed

• The searchable dropdown for choice-based filters did not load on sites accessed over plain HTTP (non-HTTPS), which prevented selecting values and saving field changes.
• Numeric comparisons on Number fields using the currency format returned incorrect results when the site currency uses a dot as the thousand separator (e.g. Euro).
• A form: merge tag modifier was ignored unless it was written as the first modifier with no spaces around its colon, so filter values such as {:1:maxwords:5,form:4} and {:1: form:4} showed a value from the main form instead of the joined form.
• The condition value dropdown detached from its input when the page was scrolled while it was open.
• Switching a condition between single-value and multi-value operators could save a mismatched value for fields whose choices are loaded on demand.
• Date picker segments were skipped by keyboard navigation, and the calendar button did not indicate which field it opened. Tab now enters the field once, the arrow keys move between segments, and the button's accessible name includes its field.
• Emptying a date resized the whole date field in locales whose placeholder letters are wider than digits (e.g. jjjj).
• Screen readers announced nothing when focus moved between two adjacent choice fields. Each is now exposed as a labelled group naming its own field.

💻 Developer Updates

• Now uses the current GravityView hooks instead of ones deprecated in GravityView 2.55.

This release adds type-to-search with paginated results to choice-based filters, lets filters compare one field against another, and fixes the "has ALL of" operator on multi-value fields.

✨ Improved

• Advanced filters can now be configured directly on the new View screen, before the View is saved.
• Enhanced conditional logic:
  • Choice-based filters now offer a searchable dropdown whose results page in as you scroll, so fields with large option lists stay fast and usable instead of trying to render every choice at once. This covers the standard choice fields (Drop Down, Checkbox, Radio, Multi Select) as well as Dynamic Lookup and Populate Anything fields, which draw their options from large external data sets.
  • Now uses a fully keyboard-accessible value picker;
  • New "has NONE of" operator for multi-value filters;
  • New keyboard-accessible Date Picker.
  • Use a field merge tag (e.g. {Threshold:2}) as a filter value to compare two fields of an entry instead of a static value.
  • Compare against a field on a joined form (Multiple Forms) with a form: modifier, e.g. {Reorder threshold:1:form:123}.

🐛 Fixed

• The "has ALL of" operator on Checkbox and other multi-value fields matched every entry instead of only those containing all the selected values.

This hotfix restores the controls for adding new conditional logic rules.

🐛 Fixed

Conditional logic controls missing in the Filter & Sort tab and field settings when no rules had been configured.

This release improves conditional logic handling for empty date values, missing forms, and admin-only filters, and fixes field-level conditional logic on joined forms.

✨ Improved

• Enhanced conditional logic:
  • Empty field values are no longer treated as today's date when using is on, is not on, is before, or is after filters;
  • Filters on deleted or missing forms (e.g. when viewing feed settings for a removed form) no longer trigger errors;
  • Admin-only filters (those suffixed :disabled_admin) no longer error out when applied to multi-value fields.

🐛 Fixed

• Field-level conditional logic targeting a field on a joined form (via the Multiple Forms extension) evaluated against the main form's row instead of the joined sub-entry, causing the field to incorrectly render or hide.

This update improves Conditional Logic with better author search, numeric comparisons, and Multiple Forms compatibility.

Note: Advanced Filter now requires PHP 7.4 or newer.

✨ Improved

• Enhanced conditional logic:
  • "Created By" filter now supports searching by username, display name, email, or login;
  • Product and pricing field filters now correctly compare numeric values, ignoring currency formatting;
  • Filters for fields on joined forms (via Multiple Forms) now correctly resolve field types and merge tags;
  • Fixed "Approval Status" filter option appearing twice in the dropdown;
  • Fixed CSS scoping to prevent style collisions with other GravityKit products.

This release improves Repeater field support and SQLite compatibility, and fixes issues with dynamic field values and relative date filters.

✨ Improved

• Nested field labels now include their parent field name for easier identification.
• Compatibility with WordPress installations using SQLite.
• Support for Repeater fields.

🐛 Fixed

• Dynamically-added custom values in dropdown, checkbox, and radio fields not displaying correctly.
• Relative date filters (e.g., "Today") using the is operator not matching same-day entries.

This update fixes special character handling in conditional logic filters.

🐛 Fixed

• Conditional logic comparisons failing when choice-based field values contain special characters (e.g., >, <, &, quotes).

This release adds conditional filtering on joined forms with the Multiple Forms extension and enhances conditional logic for Views and fields, along with related bug fixes.

🚀 Added

• Conditional filtering on joined forms (requires Multiple Forms 0.6.0 or newer).
• Support for using merge tags in text inputs.
• Automatic "Currently Logged-in User" options for Populate Anything fields using WordPress users as a source.

🐛 Fixed

• Errors when using Consent field sub-inputs in conditional logic.
• Filters using {user:} and {created_by:} merge tags are now treated as no-match when the user is logged out.

This update improves View and field conditional logic.

🚀 Added

• Ability to search fields by "does not contain".
• Predefined options (e.g., Today, Tomorrow, etc.) for Date fields.

✨ Improved

• Created By field now support is empty and is not empty operators.

🐛 Fixed

• Filtering not working with radio button fields and Survey field Likert scales.

This update resolves a potential issue affecting View filters and field conditional logic.

🐛 Fixed

• A potential JavaScript conflict that could prevent configuring View filters and field conditional logic.

This release adds support for custom filter values and merge tags in multi-value filters, and fixes several issues, including a deprecation notice in Gravity Forms 2.9.1+.

🚀 Added

• Ability to define custom filter values when using the has ANY of or has ALL of operators.
• Support for merge tag processing in filters with multiple values.

🐛 Fixed

• Deprecation notice in Gravity Forms 2.9.1 or newer caused by the use of the GFFormsModel::matches_operation() method.
• An issue where a missing filter value, when combined with the has ANY of or has ALL of operators, caused the user interface to break.

This update adds new filter operators for fields with predefined choices, and resolves various filtering and logic issues.

🚀 Added

• is empty and is not empty operators for fields with predefined choices.
• Option to specify a custom value for the contains operator when fields have predefined choices.

🐛 Fixed

• Incorrect results returned when a Current User Role filter option was combined with another condition using an OR statement.
• PHP warning when filter condition value is left empty.
• Field conditional logic on a field from a joined form (via Multiple Forms extension) did not work.

This update resolves an issue where it was not possible to completely remove filters from a View.

🐛 Fixed

• Removing all filters or the last one caused them to reappear after saving the View.

This release fixes an issue with field comparisons involving merge tags and addresses a PHP 8.2 deprecation notice.

🐛 Fixed

• Incorrect results returned when comparing two fields, with the second field's value provided by a merge tag (e.g., "Field A is greater than {Field B:2}").
• PHP 8.2 deprecation notice due to passing a null value to json_decode().

This release resolves the issue where the "Add Condition" button would disappear when configuring View filters or field conditional logic.

🐛 Fixed

• "Add Condition" button disappearing when configuring View filters or field conditional logic.

This major update introduces nested groups of conditions with selectable AND/OR logic, role-based filtering, and a new View setting for displaying entries by the logged-in user. Read the announcement for more details.

🚀 Added

• Ability to create nested condition groups.
• Option to toggle the logical operator (AND/OR) for conditions and condition groups.
• Filtering based on the current user role(s).
• View setting to display entries created by the currently logged-in user, serving as a shortcut for the "Created By" filter.

Developer Updates:

• Added the gk/advanced-filters/max-nesting-level filter to modify the maximum nesting depth for condition groups, with a default setting allowing for nesting up to 3 levels deep.

This release fixes a critical error in the View editor and resolves a problem where the Duplicate Page plugin was causing the Advanced Filter's functionality to break.

🐛 Fixed

• JavaScript errors in the View editor caused by the Duplicate Page plugin.
• Fatal error when opening a previously saved View with no data source configured.

This update resolves an issue with the Merge Tag picker disappearing in the View editor, as well as several issues related to filter conditions.

🐛 Fixed

• The Merge Tag picker in the View editor's field settings no longer disappears in the Edit Entry layout.
• Filtering by progress now accurately interprets entry's '100%' completion rate as 'complete'.
• Processing filters for non-date fields no longer results in errors.

This release introduces support for the Gravity PDF shortcode in the field conditional logic, and addresses a PHP 8.1+ deprecation notice.

🚀 Added

• Added support for the Gravity PDF shortcode ([gravitypdf]) in the Empty Field Content area under field conditional Logic.

🐛 Fixed

• A PHP 8.1+ deprecation notice.

This release includes fixes for the View and field conditional logic.

🐛 Fixed
* "Form field ID #X is no longer available" error when adding conditional logic, despite the field existing.
* "Created by Currently Logged-in User (Disabled for Administrators)" filter not functioning correctly with field conditional logic.
* Incorrect results when filtering checkbox fields using the "is not" condition.

• Fixed: Issue with setting relative dates (e.g., "today", "yesterday") in the date input field

• Improved: The extension was refactored to facilitate future development and maintenance

• Fixed: Regression introduced in 2.4 where the "is empty" and "is not empty" conditions would return incorrect results

• Fixed: Incorrect results could be returned when the form has an upload field with the multiple files option enabled
• Fixed: Filtering numeric fields (e.g., Number) with empty values using the "is empty" condition would return all entries

• Added: Filters containing Merge Tags suffixed with :disabled_admin are ignored when the current user is an Admin. e.g. {user:id:disabled_admin} (learn more about this modifier)
• Improved: Choices filled by GP Populate Anything can now be selected

Developer Updates:

• Added: gk/advanced-filter/disabled-filters WordPress filter to modify Advanced Filtering filter groups and filters

• Added: Shortcode processing in the content that's displayed when the field value does not meet conditional logic
• Improved: Advanced Filter is now loaded only in the View editor
• Fixed: "Greater than" and "Less than" comparisons not working with the "Total" field

• Fixed: Setting entry's creator to "No User" would bypass the "Currently Logged-in User" filter

• Fixed: PHP notice when using "Any form field" with field conditional logic
• Fixed: Fatal PHP error when a filter is added and its operator is not modified

• Improved: It is now possible to filter only those entries that have been updated since creation
• Updated: German translation (thanks, Michael Eppers!)

• Fixed: MySQL error on certain hosts when "Date Updated", "Date Created" or "Payment Date" entry meta are filtered using the "is empty" condition
• Fixed: JavaScript error when a filter is configured for a multi-input form field that no longer exists

• Fixed: Incorrect results returned when filtering by empty/nonempty multi-file upload fields

• Fixed: "Created by Currently Logged-in User (Disabled for Administrators)" filter did not work with field conditional logic
• Fixed: Relative date comparison did not respect WordPress's timezone offset

• Fixed: Field conditional logic did not work with multiple-input field types (e.g. Address, Name, etc.)

• Fixed: Comparison of dates in field conditional logical results in a PHP notice
• Fixed: Checkbox field not working with field conditional logic
• Fixed: JavaScript error when opening field settings with conditional logic configured for a nonexistent field ID

• Fixed: Filter values containing certain characters (e.g., "+") would fail to be processed
• Fixed: Comparison of dates in field conditional logical results in a PHP notice

• Fixed: Relative date comparison (e.g., "Entry Date" > "tomorrow") not working for field conditional logic
• Fixed: Decoding of URL-encoded special characters in filter values (e.g., "%26" was not being converted to "&")

• Fixed: Allow using relative dates (e.g., "now", "today") in the date input field

• Improved: Merge Tags can be now be processed in field conditional logic filters
• Modified: Field conditional logic can only be configured for Multiple and Single Entry contexts

• Fixed: Properly replace Merge Tags in certain "Created By", "Date Created/Updated" and certain other filters
• Updated: Russian translation (thank you, Irina F!) and Polish translation

• Fixed: "is empty" and "is not empty" filters not working for Date fields

• Added: Conditionally display configured fields based on logic rules
  • Define content that is displayed when the field is not shown
• Added: Specify custom value when "is" operator is used in combination with predefined select values
• Added: Support for filtering by a multiple-choice field option that has no label
• Fixed: Advanced Filter not initializing when a View is created from within the form editor
• Fixed: PHP warning

• Added: "Is Empty" and "Is Not Empty" filter condition operators
• Fixed: Entries with empty field values showing up in results despite having the proper filter condition in place

• Fixed: Filters not properly saving when using the initial value of a filter drop-down choice
  • This also resulted in the possibility of only entries with empty field values being shown
  • To fix, please edit your View, re-configure your filters, and update your View

• Added: Date Updated to the available filters
• Fixed: Pre-existing filters created using Version 1.x and using the "All" mode were not able to be deleted

• Updated: Brand new interface!
• Added: Create seriously powerful filters using "AND" and "OR" together with nested conditions
• Added: Use relative dates with "Date Updated" and "Payment Date" entry details
• Fixed: The combination of search modes (Search Bar "All" mode in combination with Advanced Filter "Any" mode)
• Fixed: "Show only approved entries" forces uses "All" search mode, even when Search Bar is set to "Any"
• Fixed: When editing a View using Quick Edit, configured Advanced Filters are deleted
• Translations: Added Polish translation. Thank you, Dariusz Z!
• Updated: Now requires GravityView 2.0 and WordPress 4.4
• No longer works with the Internet Explorer browser
• Developers: Read what changed from 1.3 to 2.0

• Added: Filter entries by the role of the entry creator - big thanks to Naomi C. Bush from gravity+!
• Added: Filter by the roles of the currently logged-in user
• Added: Filter by entry Approval Status without needing the Approval form field - Learn how to filter by approval status

Important update - please update as soon as possible.

Fixed: With Gravity Forms 2.3, when using "Created By" filters, the search mode was allowed to be "Any". For Views with the "Any" setting, searches were able to be performed without filters applied.

• Fixed: Filtering by Entry ID not working in Gravity Forms 2.3
• Fixed: Filtering by relative date today was showing yesterday's entries on GMT websites
• Changed option names:
  • From "Logged-in User" to "Currently Logged-in User"
  • From "Logged-in User" to "Currently Logged-in User (Disabled for Administrators)"
• Updated Dutch translations—thank you, Erik van Beek!

• Fixed: Filtering by "Entry ID" not saving
• Fixed: Filtering by a checkbox or multiselect field can prevent viewing a single entry
• Updated translations: Danish, Spanish (Mexico), French, Norwegian, Portuguese (Brazil)

• Fixed: Fatal error in the Dashboard if GravityView_View is not set
• Fixed: Prevent accessing plugin file directly

• Fixed: Issue with "Any form field" filters preventing access to single entries
• New translations: Spanish translation by Joaquin Rodriguez, German translation by Hubert Test. Thank you!

• Important update: Fixed security issue introduced in 1.0.16 where logged-in users can see all entries.
• Changed "Created by (or admin)" filter to use gravityview_edit_others_entries capability instead of gravityview_view_others_entries

• Fixed: If a View has an empty "Any field has" filter, it prevents accessing single entries
• Updated: "Created by (or admin)" filter now also allows users with the gravityview_view_others_entries capability to see entries
• Now requires GravityView 1.15 or newer
• Added additional logging

• Fixed: Allow comparing against empty field values
• Fixed: Properly replace Merge Tags when using using "Any form field" filter
• Added: Chinese translation (Thanks, Edi Weigh!)

• Fixed: When saving a filter condition using a product field the operator "is" disappears
• Fixed: When searching by an option field there were no results

• Fixed: Post Category filters
  • Dropdown not populated with categories
  • Added "Is Not" option
• Fixed: Date Created filter not working properly
• Tweak: Increase the number of users displayed in the Advanced Filter "Created By" dropdown
• Updated: Translation textdomain from gravity-view-advanced-filter to gravityview-advanced-filter
  • Included updater library in translation strings

• New: Add "is not" option to GravityView Approval fields. Now you can show only unapproved entries.
• Tweak: Make it clearer in the logs when the extension is preventing displaying results for security
• Updated: Extension updater script

• Fixed: Not able to enter relative dates (like now or two weeks ago) in date field filters
• Updated: Extension updater script

• Added: New filter to disable the entries' filter "created by the current logged-in user" when user is administrator
• Updated: French translation

• Fixed: Error on WordPress Dashboard preventing Gravity Forms widget from displaying

• Fixed: Filtering by date fields when using PHP strtotime() values like -3 days or +3 weeks
• Added: Prevent showing anything if the View ID isn't set when filtering results
• Updated: Hungarian translation by dbalage and Dutch translation by @erikvanbeek

• Fixed: Entries were being shown for users who were not logged in

• Fixed: not filtering if only one filter is defined.

• Fixed: Do not show entries for non logged users when the 'Created By' field value is 'Logged-in user'
• Tweak: Added gravityview/adv_filter/view_filters filter to allow modifying the filters generated by the Extension
• Fixed: Auto-upgrade for Multisite sites
• Added: Dutch translation (thanks, @erikvanbeek!)

• Added: Support for relative dates ("now" or "-3 days") for date type fields
• Added: Support Gravity Forms Merge Tags. Example: "{user:display_name} IS Ellen Ripley"
• Fixed: Conflicts with non-Latin UTF-8 characters like "ß"
• Added: Romanian translation (thanks, @ArianServ!) and Dutch translation (thanks, @erikvanbeek!)
• Updated: Bengali, Turkish, and Spanish translations (thanks, @tareqhi, @suhakaralar, and @jorgepelaez)

• Fixed: Conflict with other GravityView search parameters
• Updated: Bengali, Turkish, and Spanish translations (thanks, @tareqhi, @suhakaralar, and @jorgepelaez)
• Fixes fatal error on Views screen when deleting a View

• Fixed: Scripts not being added in No-Conflict mode
• Added: Romanian translation - thanks, ArianServ!

• Liftoff!