Gravity Forms Cache Buster 0.6.14

Gravity Forms Cache Buster bypasses WordPress caching plugins so every form submission validates correctly. Enable it per form by shortcode or Gravity Forms block, or apply it globally with exclusions. Works with WPML and Nested Forms.

VERSION:
0.6.14
UPDATED:
2026-11-20
DEVELOPER:
Gravity Wiz
LICENSE:
GPLv2 or greater
AUTO UPDATE:
Yes

Description

Ever submitted a form on a cached page and watched it fail with a validation error that makes no sense? Gravity Forms Cache Buster exists for that exact moment. Page caching stores a static copy of your page, and that copy includes the hidden tokens and nonce values Gravity Forms generated for whoever happened to load the page first. The next visitor fills out the form, hits submit, and the server rejects it because the stored values are stale. This plugin steps around that problem so each visitor gets a form that validates.

The Challenge

Caching plugins do their job well. They cut server load, shorten page response times, and keep a busy site from buckling. The trouble is that they treat every page as the same page for every visitor. A form is not like a blog post. It carries per-session data that has to be fresh when the entry arrives, and a cached copy can’t supply that.

The symptoms are irritating because they are inconsistent. A form works when you test it while logged in, since many caching setups skip logged-in users. It fails for anonymous visitors. Some submissions go through and others bounce. A visitor who sees an error rarely tries twice, so the lost leads, orders, and enquiries don’t announce themselves. You only find out when someone mentions it, or when the inbox goes quiet.

The usual workaround is to exclude the whole page from the cache. That fixes the form and punishes everything else on the page: the hero images, the long copy, the scripts. On a high-traffic landing page, that is a heavy price for one contact form.

How Gravity Forms Cache Buster Helps

The Gravity Forms Cache Buster WordPress plugin lets the page stay cached while the form itself is handled separately. Rather than relying on whatever the cached HTML contains, the form is fetched fresh when the page loads in the visitor’s browser. The surrounding page keeps the speed benefits of your caching plugin, and the form gets valid, current values for each person.

You choose how broadly to apply it. If only one or two forms cause trouble, you can switch it on for those forms individually. If your site has many forms and you would rather not touch each one, you can apply it to all forms and then list the ones that should be left alone. That second approach suits sites where caching is aggressive across the board and forms appear in many places.

Because the form loads after the page, there is a brief moment before it appears. The plugin includes a loading animation so visitors see a clear indicator instead of an empty gap where the form should be. It’s a small detail, but it stops people from assuming the page is broken.

Per-form control by shortcode

If you place forms with the standard Gravity Forms shortcode, you add a cache-busting option to the shortcode attributes. The form you embed this way gets the treatment, and others on the site are untouched. Other shortcode attributes you already use are passed along to the form as usual, so your existing setup keeps its behavior.

Per-form control in the block editor

Forms inserted with the Gravity Forms block in Gutenberg can be cache-busted too. You enable the option in the block’s settings instead of editing shortcode text. For editors who build pages visually and never touch shortcodes, this keeps the workflow where they already work.

Core Features

  • Per-form activation by shortcode. Add the cache-busting option to a specific embedded form and leave the rest alone.
  • Gravity Forms block support. Turn it on from the block settings for forms placed in the block editor.
  • Global mode with exclusions. Apply cache busting to every form on the site, then exempt specific forms that don’t need it.
  • Loading animation. Visitors see a visual cue while the form is retrieved, rather than blank space.
  • WPML support. Multilingual forms work with cache busting on sites translated through WPML.
  • Nested Forms support. Forms that contain child forms are handled correctly.
  • Works alongside your existing caching plugin. You keep page caching in place instead of excluding pages from it.
  • Script event handling. Gravity Forms’ standard script events continue to fire, including on forms where Cache Buster is not enabled, so your custom JavaScript hooks keep working.

Why the multilingual and nested support matters

Two kinds of forms tend to break generic fixes. Multilingual sites serve different content per language, and a cache workaround that ignores that can show the wrong form or fail to load one. Nested Forms adds another layer, since a parent form embeds child forms that need their own proper handling. Gravity Forms Cache Buster accounts for both, which saves you from testing every language and every nested structure by hand to find out what broke.

Open and adjustable

The plugin is released under the GPL, so you are free to read the code, modify it for an unusual hosting or caching arrangement, and keep a customized copy running on as many of your own sites as you need. Developers who maintain client sites will appreciate being able to adapt behavior without waiting on anyone.

Practical Applications

Lead generation landing pages

A campaign page that is heavily cached to handle traffic spikes still needs its enquiry form to work every time. With cache busting enabled on that one form, the page stays fast and each submission validates. Nobody has to choose between speed and conversions.

Agencies managing many client sites

Agencies often inherit sites with a caching plugin configured by someone else and a handful of Gravity Forms scattered across pages. Switching on the global option and excluding a few simple forms is quicker than auditing every page. It also makes the fix consistent when new forms get added later.

Multilingual business sites

A company running its site in several languages through WPML can offer a contact or quote form on each translated page. Cache busting lets those forms submit properly in every language without custom per-language exclusions in the caching plugin.

Complex multi-part forms

Registration or application workflows built with Nested Forms, such as an event signup where one parent entry collects several attendee records, depend on every piece loading correctly. Cache busting keeps those structures intact on cached pages.

Content sites with embedded forms in posts

Publishers who drop newsletter or survey forms into articles with the Gravity Forms block can enable cache busting from the editor itself. Articles remain cached for fast reading, and the embedded form still accepts responses.

Known Limitations

Because the form is loaded after the page itself, it appears a moment later than the surrounding content. The loading animation covers that gap, but it is a real trade-off compared with a form that is baked into the page. It’s worth testing on your own setup, particularly where scripts are deferred or combined by an optimization plugin.

Frequently Asked Questions

Do I have to exclude my pages from the cache to use this?

No, that is the point of the plugin. The page stays cached and only the form is fetched fresh for each visitor. You keep the performance gains from your caching plugin while getting submissions that validate properly.

Can I enable it for some forms and not others?

Yes. You can switch it on form by form through the shortcode or the Gravity Forms block settings. Alternatively, apply it to every form on the site and then list the forms you want excluded, which is handy when most of your forms sit on cached pages.

Will it work with forms in other languages or with child forms?

Yes on both counts. The plugin supports sites translated with WPML, and it handles forms built with Nested Forms. You don’t need a separate workaround for either setup.

What will visitors see while the form loads?

A loading animation appears where the form will be, so the page doesn’t look empty or broken. Once the form is retrieved, it replaces the animation and works like any other Gravity Forms form. If you use an optimization plugin that delays or combines scripts, check the form on a live page to confirm the timing feels right.

Category: