--- title: "GravityView 3.0 beta is here: what’s changing and how to try it" date: 2026-04-29 author: "Casey Burridge" link: "https://www.gravitykit.com/gravityview-3-0-beta/" --- # GravityView 3.0 beta is here: what’s changing and how to try it We're excited to announce the launch of the GravityView 3.0 beta! This is a structural upgrade (the biggest in years). We've rebuilt the plugin's internal plumbing to a modern layout so we can ship features and fixes faster going forward. The beta is open now, and we need your help testing it before it goes live! For most sites the changes will be invisible: your Views keep working, your templates keep rendering, and your entries show the same data in the same places. But because 3.0 touches the foundations of the plugin, we want real-world testing across as many configurations as possible before we call it shipped. Three things you should know up front: 1. This is a beta release—please only install it on staging or test sites 2. If you run custom code that talks to GravityView, there's a [developer guide](https://www.gravitykit.dev/migrating-to-3-0-dev-guide/) with more technical details that you should consider reading 3. Having GravityView 2.59 installed is required to access the 3.0 beta release ## How to try the beta The beta isn't pushed through the standard plugin updater. To try it, you need to opt in: 1. In your WordPress admin, go to **GravityKit → Settings** **→** **General**. 2. Toggle on the **Become a Beta Tester** option. 3. Head to **Plugins → Updates**. The 3.0 beta will appear as an available update under "Beta". 4. Click **Try Beta** to install it like any other GravityView update. ![The GravityKit Manage Your Kit screen showing the GravityView 3.0.0-beta.1 release with a button that reads 'Try Beta'.](https://www.gravitykit.com/wp-content/uploads/2026/04/CleanShot-2026-04-23-at-10.52.57@2x-1024x683.png) If you later want to switch back to the last stable release, click **Use Stable Version**. The last stable release version will then be installed **Please only install the beta on a staging site.** It's in beta for a reason, and betas can be buggy! ## What's actually new GravityView 3.0 is mostly a behind-the-scenes rewrite. We moved the plugin's class library to a single, modern layout (PSR-4 namespaces). This sounds dry, but it matters because it lets us ship features and fixes faster without fighting the limits of the old structure! What you should see (and what we want you to verify): - **Nothing visual changes.** Views, entries, search, filters, and the View editor should look and work the same. - **Your templates keep working.** Any custom template files you've copied into your theme (`list-body.php`, `single-entry.php`, and so on) should continue to render without edits. - **Your saved Views keep working.** No re-saving or re-configuring required. - **Add-ons are compatible in our testing.** GravityEdit, Advanced Filtering, DataTables, Maps, and the rest of the GravityKit add-ons pass our internal tests against 3.0, but this is exactly the kind of thing beta testing exists to verify. Please report anything odd. What's changing under the hood: - **A cleaner internal structure.** Future features ship faster. - **Legacy code paths are being retired** on a long schedule: old hook names still work, with deprecation notices only shown when you enable `WP_DEBUG`. - **Some files no longer need to physically exist** for GravityView to work. This is mostly a detail for developers, but if you've ever copied an obscure file into your plugin folder as a workaround, that kind of trick may no longer be needed. The dev guide covers what to watch for. ## The WordPress version requirement GravityView 3.0 requires **WordPress 5.5 or later**. If your site runs an older WordPress, update WordPress first, then install the 3.0 beta. Why the bump? WordPress 5.5 (released in 2020) added the internal features we now rely on—better REST and cron handling, stronger security primitives, and the site health tools you see in your WordPress dashboard. Supporting anything older forced us to keep workarounds in place for a WordPress version no modern site should still be running. How to check your WordPress version: 1. Log in to your WordPress admin. 2. Go to **Dashboard → Updates**, or look at the bottom-right corner of any admin screen. 3. If you see `5.5` or higher, you're good. If you're below 5.5, update WordPress first. Most modern hosts auto-update, so many sites are already on 6.x without any action needed. ## Before you install the beta: a checklist This is beta software. Do not install it on a production site. Run through this checklist on staging. 1. **Set up a staging environment** if you don't have one. Most hosts offer one-click staging. Otherwise, use [Local](https://localwp.com) or [WordPress Playground](https://playground.wordpress.net). 2. **Back up your site.** Any reputable host provides one-click backups. Run one before installing the beta. 3. **Confirm WordPress is 5.5 or newer.** Upgrade WordPress first if it isn't. 4. **Confirm Gravity Forms is 2.6 or newer.** (Recommended: 2.7+.) 5. **Install the beta on staging** using the opt-in path above. 6. **Click through your most-used Views, search them, filter them, edit an entry.** The more real-world scenarios you test, the more useful your feedback. 7. **Test your other GravityKit add-ons at the same time.** All GravityKit products get aligned 3.0 releases—test them together on staging, not piecemeal. 8. **If you have custom code** (site-specific plugins, theme-level GravityView templates, or hand-written hooks), read the dev guide linked below, or point your developer to it. ## If something breaks If you hit an issue: 1. **Deactivate the 3.0 beta** on your staging site. 2. **Reinstall the 2.x version** from "Manage Your Kit", or your GravityKit account page. Alternatively, restore your site from the pre-update backup. 3. **Tell us what happened** (see next section for how to report issues). ## How to report issues We need feedback to ship a solid 3.0. If you hit a bug, a regression, or something that just looks wrong, please reach out to our support team. You can do this either through the [support portal](https://www.gravitykit.com/support/) or by emailing . Mention you're on the 3.0 beta so we can route it appropriately. Include in your report: - What you did (steps to reproduce). - What you expected to happen. - What actually happened. - Your WordPress version, Gravity Forms version, and any active GravityKit add-ons or extensions. - A screenshot if it's a visual issue, or browser console output if it's a JavaScript error. Small reports are better than no reports. If something feels off but you can't articulate it, send that too! ## Timeline We don't have a target release date for GravityView 3.0. We're working toward late May 2026, but 3.0 ships when the beta tells us it's ready. We'll keep you posted as that picture clarifies. Subscribing to our [newsletter](/newsletter/) is the best way to stay up to date with all our product developments. ## For developers If you've written custom code against GravityView (custom field types, template overrides in PHP, hook callbacks, or your own GravityKit-adjacent add-on), our in-depth [developer guide](https://www.gravitykit.dev/migrating-to-3-0-dev-guide/) is the place to go. It covers: - The PSR-4 namespace refactor and how legacy class names keep working. - The change that removes the physical-file assumption, and the errors you might hit during the beta window. - The Query Filters search pipeline. - Every deprecated hook and its replacement. - A before-you-upgrade checklist aimed at plugin authors. ## Have questions? If you're not sure whether a plugin, theme, or custom integration needs attention, email with the details and we'll take a look.