Releases: gravityplus/Gravity-Forms-Salesforce
Releases · gravityplus/Gravity-Forms-Salesforce
3.0.6.3
3.0.6.2
- Fixed: Issue saving Web-to-Lead settings for Gravity Forms 1.8.10 or higher. Thanks, @twiginteractive
- Fixed: An issue with the OAuth library clashing if the same library is used elsewhere. Thanks, @JasonTheAdams
- Confirmed compatibility with WordPress 4.0
3.0.6
- If you haven't read the 3.0.5 changelog notes, please do so!
- Added: Enabled Merge Tag field value support (issue #97)
- Added [API Add-on]: "Form Title" as an option for mapping form fields
- Fixed: Form details were not being properly passed (issue #94)
- Fixed: DaddyAnalytics API names were incorrect for the API integration
- Fixed: PHP warning about calling static functions
- Added: Additional Debugging
3.0.5
First release of 3.x on the WordPress.org directory.
3.0.5 (June 26, 2014)
- Added translation If you want to help translate the plugin, please submit your translation here](https://www.transifex.com/projects/p/gravity-forms-salesforce-add-on/).
3.0.4 (June 26, 2014)
- Fixed: Threw invalid API warning if settings hadn't been saved.
- Added: Localization strings
- Fixed: Both Integration Methods were showing in the Settings menu
3.0.3 (June 20, 2014)
- Fixed: Finally nailed the OAuth Refresh Token flow. It's all working nicely now.
3.0.2 Beta
Added filter to docBlock
3.0.1 Beta
3.0.1 (May 11, 2014)
- Modified: Hide Daddy Analytics custom API Name settings, unless the
gf_salesforce_custom_da_api_namesfilter returns true. - Fixed (API): Return false in
get_api()method when settings are empty.
3.0 Beta
2.6.4.1
2.6.4
- Fixed (API Version): Live Remote Field Mapping improvements
- Fixed endless spinning
- Empty options are better managed; shows "No Picklist Fields" message
- Now shows an error message if the field cannot be used for Remote Field Mapping
- Static PHP warning fixed when
WP_DEBUGenabled