2.0.6

• Fixed: Conflicts with Yoast SEO & Jetpack plugins that prevent widgets from displaying
• Fixed: Some fields display as HTML (fixes Gravity Flow Discussion field, for example)
• Fixed: Some Merge Tag modifiers not working, such as :url for List fields
• Fixed: Give Floaty a place to hang out on the GravityView Settings screen with new Gravity Forms CSS

Developer Updates

• Fixed: Backward-compatibility for using global $gravityview_view->_current_field (don't use in new code!)

2.0.5

• Fixed: Entry Link fields and [gv_entry_link] shortcode not working properly with DataTables when embedded
• Fixed: Do not output other shortcodes in single entry mode
• Fixed: Error when deleting an entry
• Fixed: When multiple Views are embedded on a page, and one or more has Advanced Filters enabled, no entries will be displayed
• Fixed: PHP warning with [gravitypdf] shortcode
• Fixed: When multiple table layout Views are embedded on a page, there are multiple column sorting links displayed
• Fixed: Error displaying message that a license is expired

2.0.4

• Fixed: Slow front-end performance, affecting all layout types
• Fixed: Search not performing properly
• Fixed: "Enable sorting by column" option for Table layouts
• GravityView will require Gravity Forms 2.3 in the future; please make sure you're using the latest version of Gravity Forms!

Developer Updates

• Fixed: GravityView_frontend::get_view_entries() search generation
• Fixed: gravityview_get_template_settings() not returning settings
• Tweak: Cache View and Field magic getters into variables for less overhead.

2.0.3

• Fixed: Compatibility with [gravitypdf] shortcode
• Fixed: When using [gravityview] shortcode, the page_size setting wasn't being respected
• Fixed: [gravityview detail="last_entry" /] not returning the correct entry
• Fixed: Widgets not being properly rendered when using oEmbed
• Fixed: Note fields not rendering properly

Developer Notes

• Fixed: GravityView_View::getInstance() not returning information about a single entry
• Added: gravityview/shortcode/detail/$key filter

2.0.2

• Fixed: Widgets not displayed when a View is embedded
• Fixed: Saving new settings can cause fatal error
• Fixed: Prevent commonly-used front end function from creating an error in the Dashboard

2.0.1

• Fixed: Hide labels if "Show Label" is not checked
• Fixed: CSS borders on List layout
• Fixed: Error when fetching GravityView Widget with DataTables Extension 2.2
• Fixed: Fail gracefully when GravityView Maps is installed on a server running PHP 5.2.4

2.0.1-prerelease

To provide customers with 2.0.1 as soon as possible.

GravityView 2.0 🚀

We are proud to share this release with you: we have been working on this release since 2016, and although most of the changes won’t be seen, GravityView has a brand-new engine that will power the plugin into the future! 🚀
- Zack with GravityView

---

Note: GravityView now requires PHP 5.3 or newer

This is a major release. Please back up your site before updating. We have tested the plugin thoroughly, but we suggest backing up your site before updating all plugins.

New functionality

• [gventry]: embed entries in a post, page or a View (learn more)
• [gvfield]: embed single field values (learn more)
• Many new Merge Tag modifiers - These enable powerful new abilities when using the Custom Content field!
• Use oEmbed with Custom Content fields - easily embed YouTube videos, Tweets (and much more) on your Custom Content field
• "Is Starred" field - display whether an entry is "Starred" in Gravity Forms or not, and star/unstar it from the front end of your site
• Added Bosnian, Iranian, and Canadian French translations, updated many others (thank you all!)

Smaller changes

• Added {gv_entry_link} Merge Tag, alias of [gv_entry_link] shortcode in {gv_entry_link:[post id]:[action]} format. This allows you to use {gv_entry_link} inside HTML tags, where you are not able to use the [gv_entry_link] shortcode.
• Default [gvlogic] comparison is now set to isnot=""; this way, you can just use [gvlogic if="{example:1}"] instead of [gvlogic if="{example:1}" isnot=""] to check if a field has a value.

Developer Updates

This release is the biggest ever for developers! Even so, we have taken great care to provide backward compatibility with GravityView 1.x. Other than increasing the minimum version of PHP to 5.3, no breaking changes were made.

• We have rewritten the plugin from the ground up. Learn all about it here.
• New REST API! Fetch GravityView details and entries using the WordPress REST API endpoint. It's disabled by default, but can be enabled or disabled globally on GravityView Settings screen, or per-View in View Settings. Learn about the endpoints.
• New gravityview() API wrapper function, now used for easy access to everything you could want
• New template structure (learn how to migrate your custom template files)
• We have gotten rid of global state; actions and filters are now passed a $context argument, a \GV\Template_Context object
• When HTML 5 is enabled in Gravity Forms, now the Search All field will use type="search"
• Countless new filters and actions! Additional documentation will be coming, both on docs.gravityview.co as well as codex.gravityview.co.

A special thanks to Gennady for your tireless pursuit of better code, insistence on backward compatibility, and your positive attitude. 👏

2.0 RC1

v2.0-rc.1

Update the translations one more time

1.22.6

• Fixed: Line breaks being added to [gvlogic] shortcode output
• Fixed: Gravity Forms 2.3 compatibility notice
• Fixed: "The ID is required." message when configuring the GravityView Search WordPress widget
• Fixed: Slashes were being added to Post Image details

Developer Updates:

• Added gravityview/edit_entry/reveal_hidden_field filter, which allows you to prevent Hidden fields from becoming Text fields in Edit Entry context
• Added gravityview/edit_entry/field_visibility filter to set field visibility on Edit Entry (default is always "visible")