Multiple Forms Changelog

This release adds support for using conditional filtering on joined forms through the Advanced Filter extension.

🚀 Added

• Conditional filtering on joined forms (requires Advanced Filter 4.3.0 or newer), enabling advanced conditional logic across multiple form data.

This update fixes sorting issues affecting joined data in Views.

🐛 Fixed

• Sorting Views by fields from joined forms, including the field used to create the join, was not working.

This release introduces an option to control the visibility of unapproved joined entries, refactors join logic for better filtering, and resolves issues with missing or incorrectly displayed joined entries.

🚀 Added

• New 'Show only approved joined entries' setting in the View editor to control the display of unapproved or disapproved joined entries.

✨ Improved

• Reworked join logic for more flexible filtering.
• Multiple join conditions on the same form are now processed within a single join, ensuring all conditions apply together.

🐛 Fixed

• Some related joined entries were missing from the View.
• Unapproved joined entries were incorrectly displayed in the View.

💻 Developer Updates

• Added: gk/multiple-forms/query/handler/join/conditions filter to modify conditions for a joined form query.

This release adds support for different View types in the View editor and fixes issues with sorting and missing parent form entries.

🚀 Added

• Support for using different View types in the Multiple Entries and Single Entry layouts (requires GravityView 2.26.1 or newer).
• Compatibility with the upcoming Layout Builder View type in GravityView.

🐛 Fixed

• Trashed entries in a joined form prevented related entries from the parent form from displaying in the View.
• Sorting on joined fields did not work properly.
• Sorting by one field (column) would instead sort by another.

• Fixed: Fatal error when editing fields with GravityEdit if the View uses joined forms

• Fixed: Missing option to add fields from joined forms in the View editor when using GravityView 2.19.4 or newer

• Fixed: Performance issue caused by Multiple Forms modifying database queries, even when not needed
• Fixed: Linking to the Single Entry from a View with joins now works as expected (with joined entry IDs separated by commas)

• Fixed: Fatal error that prevents the ability to create a new View

• Fixed: Fatal error when running less than PHP 8.0

• Improved: Display an admin notice when GravityView or Gravity Forms are not installed and activated
• Fixed: 'GravityKitMultipleFormsGF_Query_JSON_Literal' not found fatal error when performing a search on a View
• Fixed: Joining two Views using "any form field" joins can cause fatal errors

• Fixed: Fatal error when GravityView is not activated (introduced in Version 0.3)

• Fixed: PHP warning

• Fixed: Fatal error related to namespacing

• Fixed: Fatal error when activating the extension

• Added: You can now sort Views by joined form fields
• Modified: Minimum version of PHP bumped to 7.2 to match all other GravityKit plugins
• Fixed: When field ids across joined forms were the same, values could be pulled from the wrong form
• Fixed: View editor became unusable when a joined form was trashed or deleted
• Fixed: When "Show only approved entries" was enabled for a View, it was behaving as if "Strict Entry Match" were also enabled

• Fixed: Conflict preventing Yoast SEO scripts from running on Views

• Added: Allow joining forms on field meta and properties
  • Adds support for Nested Forms by GravityWiz!
• Added: Allow joining multiple forms on entry meta (non-field data)
• Added: gravityview_multiple_forms/allow_join_on filter for developers to modify the list of permissible meta and properties
• Added: Italian and Persian translations (Thanks, Farhad P.!)
• Improved: Do not require a published View to display join conditions
• Modified: Now requires GravityView 2.6 or newer
• Fixed: Fatal error when using Gravity Forms 2.2 or older
• Fixed: "Cannot read property 'title' of undefined" JavaScript error

• Fixed: PHP Warning: Declaration of GF_Patched_Query::_prime_joins() should be compatible with GF_Query::_prime_joins()

• Liftoff!