1.20 on February 24, 2017
- Added: Product Fields are now editable
- Quantity,
- Product fields are hidden if the entry contains external transaction data
- Support for Coupon Addon
- Fixed: Single Entry not accessible when filtering by a Checkbox field in the Advanced Filters Extension
- Fixed: WPML links to Single Entry not working if using directory or sub-domain URL formats
- Fixed: Product field prices not always formatted as a currency
- Fixed: Product fields sometimes appeared twice in the Add Field field picker
- Fixed: PHP warning when updating entries. Thanks for reporting, Werner!
- Modified: Don't show CAPTCHA fields in Edit Entry
- Fixed: "Trying to get property of non-object" bug when updating an entry connected to Gravity Forms User Registration
- Fixed: Yoast SEO scripts and styles not loading properly on Edit View screen
- Updated: Minimum version of Gravity Forms User Registration updated to 3.2
1.19.4 on January 19, 2017
- GravityView requirements will soon be updated: Gravity Forms Version 2.0+, PHP 5.3+
- Updated: GravityView now requires WordPress 4.0 or newer
- Fixed: Search Bar search not working for states in the United States
- Fixed: WPML conflict where Single Entry or Edit Entry screens are inaccessible
- Fixed: Prevent PHP error when displaying GravityView using get_gravityview()
- Updated translations:
- Danish 100% translated
- Norwegian 100% translated
- Swedish translation updated
* Fixed: List field inputs not loading in Edit Entry when values were empty or the field was hidden initially because of Conditional Logic
* Fixed: Prevent Approve Entry and Delete Entry fields from being added to Edit Entry field configuration
* Fixed: Don't render Views outside "the loop", prevents conflicts with other plugins that run `the_content` filter outside normal places
* Fixed: Only display "You have attempted to view an entry that is not visible or may not exist." warning once when multiple Views are embedded on a page
* Fixed: The `[gravityview]` shortcode would not be parsed properly due to HTML encoding when using certain page builders, including OptimizePress
* Fixed: Potential errors when non-standard form fields are added to Edit Entry configurations ("Creating default object from empty value" and "Cannot use object of type stdClass as array")
* Updated translations:
- Chinese *100% translated* (thank you, Michael Edi!)
- French *100% translated*
- Brazilian Portuguese *100% translated* (thanks, Rafael!)
- Dutch translation updated (thank you, Erik van Beek!)
- Swedish translation updated
- Updated Spanish (Spain + Mexican) and German (`de` + `de_DE`) with each other