Pods Gravity Forms Add-On 1.4

• Support: Added support for Gravity Forms 2.3 database tables changes (You may see a warning on the Edit Pod screen but this is a false positive because we cache a list of all tables to transients and it triggers the warning solved by removing those old "rg" tables)
• Changed: Backwards compatibility issue -- You can now more easily set custom override values, however the old style was not able to be brought over -- you'll want to update your feeds when possible, the old values will not show up and you'll have to select the custom override value option once more, then fill it in
• Changed: Backwards compatibility issue -- Now requiring WordPress 4.6+
• Feature: When editing entries in the admin area, changes now sync to the associated Pod item (except trash/deletes)
• Feature: New Bulk Entry Syncing to Pods WP-CLI command wp pods-gf sync --form=123 or you can specify which feed (even if it is not active) with wp pods-gf sync --form=123 --feed=2
• Feature: Support for List field mapping to a Pod field which ends up serializing the value, but can be prepopulated back into the Gravity Form
• Feature: List field mapping to relationship fields related to another Pod (list columns map to individual fields in the related Pod) with new filters pods_gf_field_columns_mapping and pods_gf_field_column_row
• Feature: Support for Chained Select field mapping to a Pod field
• Feature: New Custom fields section added for Pods that support meta (Posts, Terms, Users, Media, and Comments), you can set additional custom fields including ability to set custom values there too
• Feature: Ability to set conditional processing per feed, based on specific values submitted
• Added: Whenever you create a new feed, mapping will automatically be associated between a Gravity Form field and a Pod field if the labels match
• Added: Custom override values now support GF merge tags by default (no insert UI yet) like {form_id} and any other merge tag
• Added: Required WP Object Fields in mapping are no longer required if you choose to 'Enable editing with this form using ____' option for Post/Media or User pod types
• Added: Support for E-mail field mappings with 'Confirm E-mail' enabled
• Added: Support for Date fields with multiple inputs (date dropdown / text fields)
• Added: Smarter requirement handling for WP object fields based on object type (only require what the WP insert API requires)
• Added: New mapping fields are now available for more Entry and Payment fields
• Added: New merge tags {pods.id} and {pods.permalink} are available for usage and in the merge tag selection dropdowns
• Improved: Added headings to each group of feed options so they are easier to work with
• Improved: Address field mapping for Country, State, and CA Provinces now convert properly to their Pods counterparts
• Updated: PHP Markdown library updated to 1.0.2
• Fixed: Issues with using 'bypass' as a save action
• Fixed: Dynamic select options should set the current value (as posted in form) properly
• Fixed: Date/time fields shouldn't auto populate with empty dates such as 0000-00-00 anymore
• Fixed: Additional attachment processing fixes
• Fixed: Lots of Pods GF UI issues resolved
• Fixed: Removed Autocomplete limit (was 30) that was being enforced, now all data from related field will show
• Fixed: Dynamic mapping value checking to support arrays of values
• Fixed: Lots of Prepopulating fixes
• Fixed: Now supports multi page form validation and prepopulating