GWW 320: Eighty Proof
Gravity Forms 3.0 is here, and all 80 of our plugins are ready. 🎉 Plus, smarter entry exports and conditional logic that knows who’s filling out your form.
Greetings, wizards!
Dani and I were brainstorming some product plans the other day when we realized that Entry Archive was our 80th Gravity Forms plugin. That’s eighty Gravity Forms plugins — all available via Spellbook — and nearly 20% of them are free! 🤯
That also explains why the last month has been so busy for us, as we’ve been getting that full collection ready for Gravity Forms 3.0. 😆
And guess what just arrived?
Gravity Forms 3.0 Has Landed
After a beta, a release candidate, and a whole lot of compatibility testing on our end, Gravity Forms 3.0 is officially here. It’s a major release, so there may be a few breaking changes to be aware of. Give the changelog a quick read before hitting update.
Today, we’re covering two of the biggest changes—both of which affect Gravity Wiz products. You’ll also want to check out this week’s full Product Updates for even more Gravity Forms 3.0 compatibility improvements.
Heads up: Gravity Forms is rolling out the release in stages. If it hasn’t appeared in your dashboard yet, it’s on the way.
International Phone Formats
The Phone field can finally handle the rest of the world. Set a default country, let your users pick their own country and dialing code, and let built-in validation catch numbers that don’t match the format.
If that sounds familiar, there’s a good reason: GP Advanced Phone Field has offered international phone support since 2022. It builds on those essentials with regularly updated validation powered by Google’s libphonenumber, compatibility across phone field formats, GeoIP country detection, preferred and filtered country lists, and phone metadata—such as type, carrier, and location—that you can use in conditional logic and merge tags.
We put together a quick FAQ explaining where the two solutions overlap, what sets them apart, and how to choose the right one for your form.
Accessibility by Default
Every new form you create now starts with accessible settings already switched on, which makes WCAG 2.1 AA a much shorter walk than it used to be. The datepicker got the biggest upgrade: it’s been rebuilt on the WhatSock library instead of jQuery UI, so date selection is fully accessible and we can almost bid farewell to that very dated library. 🥁
What this means for GP Limit Dates: we’ve already added compatibility for the WhatSock datepicker, so your date restrictions keep working exactly as before. One caveat — WhatSock doesn’t support native inline datepickers yet. We’re working on a solution so we can ditch jQuery UI entirely. 🪦
Entry Archive: Exportiarmus!
We just launched this free plugin last week and we’re already back with a little upgrade.
Archived entries no longer go missing when you export. GF Entry Archive now includes them in your Export Entries results by default.
And if you don’t want them in your exports, we added Entry Status as an export condition, so you can pull just your active entries, just your archived ones, or everything at once. 🗃️
How To: Conditional Logic by User
GP Advanced Conditional Logic gives you the easiest and most secure way to configure conditional logic based not only on whether a user is logged in, but on nearly any other factor about that user — their role, or a user meta value like their membership level or registered location.
Dan walks through all three flavors: Is Logged In for gating a field behind a login, Role for staff-only fields on public forms, and Meta for reading whatever your membership plugin already stores about someone.
Video: Automatically Advance Multi-page Forms
Fewer clicks = better completion rates. And this week’s video shows you how easy it is to make that happen with any form (not just conversational ones).
Product Updates
Gravity Perks
GP Advanced Phone Field (v1.1.11)
- Fixed a Gravity Forms 3.0 compatibility issue that could trigger a fatal error when an Advanced Phone Field failed validation.
GP Blocklist (v1.3.11)
- Fixed a compatibility issue with Gravity Forms 3.0 where enabling Blocklist honeypot could allow blocked submissions to be created as normal entries instead of being sent to spam.
GP Bookings (1.0-beta-2.13)
- Fixed issue where GP Bookings data could not be included when exporting or importing forms in Gravity Forms 3.0.
GP eCommerce Fields (v1.2.38)
- Fixed Gravity Forms 3.0 compatibility issues with eCommerce fields.
- Fixed compatibility issue with Gravity Forms 3.0 where activating the plugin would throw a fatal error caused by the Subtotal field.
GP Entry Blocks (1.0-beta-2.34)
- Added line break before Sorting Input field in Summary column options.
- Fixed HTML-entity-escaped field labels showing in the merge tag selector.
GP Limit Dates (v1.1.37)
- Added compatibility for Gravity Forms’ migration to WhatSock datepicker library.
GP Notification Scheduler (v1.3.21)
- Fixed issue where the Reschedule meta box displayed an empty error notice after notifications were rescheduled successfully.
- Fixed issue where batch rescheduling removed inactive scheduled notifications.
GP Page Transitions (v1.0.47)
- Fixed issue where Auto Progression did not work with input mask, Phone (US format), and Date Picker fields in Gravity Forms 3.0.
Free Plugins
GF Entry Archive (v1.0.2)
- Added archived entries to Export Entries results by default
GF Feed-specific Submit Button (v1.4.1)
- Fixed an issue where Feed Specific Submit Button labels were not applied when using Gravity Forms 3.0.
GF Rounding (v1.14.2)
- Fixed a JS console error happening with Gravity Forms 3.0.
