GravityView 2.39.1

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

• Added: Search Bar now supports displaying State and Country fields as Select, List, or Radio input types (before, only text fields)
• Fixed: Single entries not accessible when a View has filters based on Gravity Forms "Advanced" fields like Address and Name
• Added: There is now a warning when a View tab has not been configured. The question "Why aren't my entries showing up?" is often due to a lack of configuration.
• Added: Notice for future PHP requirements.
  • Reminder: GravityView will soon require PHP 5.3. 97.6% of sites are already compatible.
• Fixed: Conflict with another plugin that prevented the Field Settings from being reachable in the Edit View screen
• Fixed: GravityView widgets repeating twice for some customers