GravityView v3.12.0 WordPress Plugin

GravityView is a WordPress plugin that allows users to easily display entries from Gravity Forms on their website. The plugin provides a variety of features, including the ability to create unlimited views, approve and reject entries, edit entries from the front end, and support for all official Gravity Forms add-ons. GravityView is also multilingual, with support for several languages, and allows users to import CSVs for use in Gravity Forms.

The plugin is great for paid directories, as it works with payment add-ons for Gravity Forms, allowing users to easily create paid directories. Users can also edit entries on the front end of their site, and GravityView integrates with DataTables for browsing, filtering, and sorting entries with live updates.

One of the best things about GravityView is the support offered by the team behind the plugin. They are responsive, helpful, and actively working to improve the plugin. With an average of over 60 improvements in the past month alone, users can be confident that GravityView will continue to be a reliable and useful tool for displaying Gravity Forms entries on their website.

NameGravityView
TypeWordPress Plugin
Version3.12.0
LicenseGPL v2
Last Updated
Live DemoView Demo

Core Features of GravityView WordPress Plugin

  • Unlimited Views: You can create as many views as you like to display your Gravity Forms entries on your website.
  • Approve & Reject Entries: You have full control over which entries go live on your website. You can either approve or reject entries as you see fit.
  • Edit Entries From the Front End: You can edit your entries directly from the original Gravity Forms form on the front end of your website, without having to go to the admin dashboard.
  • Gravity Forms Add-Ons Compatible: GravityView works seamlessly with all official Gravity Forms Add-Ons, allowing you to extend the functionality of your forms.
  • Multilingual: GravityView is available in multiple languages, including English, Turkish, Bengali, German, French, Italian, Dutch, Hungarian, Portuguese, and Romanian.
  • Import CSVs: You can easily import data from a CSV file to use in your Gravity Forms.
  • Featured Entries: You can star specific entries to always show them first in your views.
  • Awesome Support: The GravityView team is dedicated to providing great support, and they’re available to help you with any questions or issues you may have.
  • Great for Paid Directories: You can use a payment Add-On for Gravity Forms to create a paid directory.
  • Front End Edit Entries: Your users can also edit their own entries from the front end of your website, and you can choose who can edit and which fields they can edit.
  • DataTables Integration: GravityView integrates with DataTables, which allows you to browse, filter, and sort your entries with live updates.
  • Gravity Flow & Gravity PDF & GFChart: GravityView works seamlessly with GravityFlow, Gravity PDF, and GFChart to extend the functionality of your forms.
  • Constantly Improving: The GravityView team is constantly making improvements to the plugin, with an average of 13.85 changes per week in the past year.

What’s New (Changelog) in GravityView v3.12.0

= 3.12.0 on November 12, 2026 =

This release adds a "Pages with this View" menu, a Welcome page, and guided tours of the View editor, turns on Enhanced Security for new Views, and fixes issues with Edit Entry file uploads and combined Views. It also includes a privacy fix for Views in page builders, so we recommend updating.

🚀 Added
* New in [GravityView Pro](https://www.gravitykit.com/products/gravityview-pro/):
- Live Filters, a sidebar of filters (checkboxes, radio buttons, dropdowns, ranges, dates, date ranges, and star ratings) that updates a View's results and counts without reloading the page, either with each choice or when the visitor clicks Apply;
- Edit Window, which locks editing (and, optionally, deleting) an entry after a deadline: when the form's schedule ends, a set time after submission, on a fixed date, on the date in an entry's Date field, including GravityBoard Due Dates (with an offset in calendar days and a rule for blank dates), or under AND/OR conditions that combine these deadlines with entry field values;
- Connected Views, which link Views so visitors can move from an entry in one View to its related entries in another, and back;
- Dynamic Lookup, Entry Tags, and Event Field built in, taking over from a separately installed copy, with the same settings and data, once you deactivate it.
* "Pages with this View" submenu in the GravityKit toolbar menu, which links users who can edit a View to every published page that shows it, including page builder pages, from the View editor or any of those pages (requires WordPress 6.9 or newer).
* A GravityView page in GravityKit > Welcome, which replaces the Getting Started page and opens after activation, with an overview of what you can build, a "Get set up" checklist, courses and guides, and a one-click sample View for sites with no Views yet.
* Two guided tours in the View editor: "Build your first View", offered on the New View screen, and "See how it works", a tour of a finished View with a short clip for each step.

✨ Improved
* "Enable Enhanced Security" turned on by default for new Views, so they display only through a block or shortcode that includes the View's secret (the block picker and the shortcode in the Publish box add it automatically), without changing existing Views.

🔒 Security
* Saving a page with a GravityView widget in Elementor or Beaver Builder stored a copy of the View, as the person saving the page saw it, with the page, so save those pages again in the builder after updating to replace the stored copy.
* [gvlogic logged_in="…"] without an if showed its [else] content to everyone, logged in or not, when Entry Tags 1.5.1 or GravityCharts 1.2 to 1.23.1 was active.

🐛 Fixed
* Issues on the Edit Entry page since GravityView 3.11.0, on Views with "Prevent Direct Access" turned on and for users who cannot see private Views, such as Subscribers:
- A file added to an empty File Upload field with Multi-File Upload turned on was not saved even though "Entry Updated." appeared, and if the field was required, "This field is required." appeared and the entry could not be saved;
- Multi-page forms moved to the next page when a field on the current page had an error, hiding the error.
* Since GravityView 3.8.0, Single Entry and Edit Entry pages showed an error on sites with a View in an Elementor widget and a theme that adds custom fonts to Elementor, such as BuddyBoss Theme.
* Saving a View whose layout was inactive, such as a Map View while Maps was deactivated, erased its layout, fields, and widgets, so the View had to be built again.
* Since GravityView 2.29, pages loaded more slowly on sites with a permalink base such as /blog/%postname%/, Plain permalinks, Polylang showing the language code in every URL, an Entry Endpoint with capital letters, or Gravity Forms deactivated, because permalink rules were rebuilt on every page load.
* Issues in Views that combine forms with [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/):
- Entries were sorted in the wrong order when one form lacked the field the View sorts by and another plugin added its own sort;
- No entries appeared when the View was sorted by a Time field.
* Shortcodes in the "No Entries Message" and "No Search Results Text" settings showed as typed, brackets included, when the View was embedded with its shortcode or in a block theme's template part, or when results updated without reloading the page.
* Issues with Views built or edited by AI agents:
- Fields were added empty, without their settings, such as a Custom Content field's text;
- Adding or changing several fields or widgets at once removed the HTML from Custom Content;
- Setting "Sort by field" to a form field through the GravityKit MCP server was rejected.
* Activating GravityView sometimes stayed on the Plugins screen instead of opening GravityView's page in GravityKit > Welcome.
* In the View editor, a field's gear button and settings window were named after the form field instead of the field's Label.
* The button that expands a field's settings in the View editor was announced as "undefined" to screen readers.

💻 Developer Updates
* Added the GravityKitGravityViewViewViewPages class, whose get() method returns the published pages that show a View and whether the search stopped at its limit.
* Added the gk-gravityview/view-pages-get ability, which returns the pages that show a View, or every embedded View the user can edit.
* Added the gk/gravityview/view/pages/max-pages filter to change the maximum number of pages read when finding which pages show each View (default: 500).
* Added the gk/gravityview/view/pages/post-types filter to change the post types searched for pages that show a View.
* Added the gk/gravityview/view/pages/content-meta-markers filter to set the post meta an integration stores its layouts in, so saving that meta clears the cached list of pages that show a View.
* Added the gk/gravityview/view/secure-embed-default filter to control whether new Views start with "Enable Enhanced Security" turned on (return false to start them with it off, without affecting saved Views).
* Added View::shows_on(), which checks whether an embed read from a post shows the View rather than a count.
* Added the gk/gravityview/rest/template-settings/view-schema filter to modify a template setting's schema for the View being written to on the Abilities and REST write path, so extensions that add per-View choices (such as joined-form sort fields) can expand options.
* Added the gk/gravityview/features/field-types filter to change the form field types a GravityView Pro feature adds, which GravityView uses to count the forms whose fields stop working when that feature is off.
* Added the gk/gravityview/deactivation/warning filter to add plain text to the warning in the GravityView deactivation dialog.
* GravityView Pro: Added the gk/gravityview/edit-entry/window-closed filter to reopen or close a View's Edit Window for one entry and action, without granting permission or overriding a Magic Link's expiry.
* ViewCollection::from_content() now skips [gravityview] shortcodes inside HTML comments, since they never run, and reads the view_id attribute when id is empty.
* ViewCollection::from_post() no longer finds Beaver Builder modules set to never show, disabled Divi modules, or shortcodes in Elementor data on a page taken out of Elementor.
* On combined Views, the query that gravityview/view/query receives for each added form now includes a GravityKitGravityViewViewUnionMissingOrder sort for every View sort the form has no field for, which should be kept in place when changing the sorts.
* Changes to the gk-gravityview/view-settings-patch and gk-gravityview/view-config-apply abilities:
- Every rejected template setting is now listed under data.errors, and nothing is written when any setting is rejected;
- An add-on setting sent as the dotted slug the schema returns, such as maps.map_type, is now saved to that add-on's settings instead of under an invalid name that had no effect;
- A dotted setting for an inactive add-on (such as datatables.responsive without DataTables), an add-on name with a value that is not an object (such as "maps": null), a setting name that is empty once sanitized, or an empty or nested item in a list of choices (such as "sort_direction": ["ASC", null]) now returns a 400 error and saves nothing, instead of being skipped while the rest was saved;
- Settings are now validated when the abilities run from WP-CLI or cron.
* Re-enabling the gravityview/post_type/with_front filter after it was turned off made Views show "Page not found" until Settings > Permalinks was saved, instead of moving View URLs on the next page load.
* GravityView_Entry_Approval::update_approved() called without a form ID cleared the View cache for form 0 instead of the entry's form, so Views kept showing old results after custom code approved an entry.
* Searching Payment Amount with a Slider in the Search Bar widget logged an "Array to string conversion" PHP warning on every search.
* On multisite networks, "Remove all data" in GravityView's Remove Data settings logged database errors for each site that had never used Gravity Forms.
* A View sorted by a field its form no longer has logged a "Trying to access array offset on null" PHP warning from Gravity Forms each time it was shown.

🔧 Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.40.0.

Download GravityView Latest Version

Join to Download
You can download this product for free by joining our membership.
Instant access to all files with unlimited downloads for unlimited sites.
Share This Article!

Leave a Reply

Your email address will not be published. Required fields are marked *

Verify you're human
6 + 5 =