Samuel Aguilera

Caching is great for scenarios where your post or page content it’s not changed frequently, but if you have a form embedded to which you do changes very often or you’re using dynamic code, that doesn’t run for a cached page, or using third-party solutions relaying in dynamic live data (e.g. reCAPTCHA), using caching in these cases is going to cause issues. The same applies to certain automatic JS optimizations done by caching plugins that are known to break JS execution easily.
An easy solution is to configure your caching plugin or proxy to exclude the page where the form is embedded, but you need also to remember this when you create a new page or embed a new form in an existing page…
This plugin will take care of the above automatically doing the following:
<ol>
<li>Flush current cache on plugin activation. This is required in order to allow the next step to run.</li>
<li>Dynamically check if there’s a Gravity Forms for any of the supported embedding methods (see below for the list).</li>
<li>If so, it will prevent post/page from being cached by any of the supported caching plugins, browsers and CDN/Proxies.</li>
</ol>
<h4>Embedding methods supported:</h4>
<ul>
<li>WordPress default editor, shortcode or Gutenberg block. Content of any post type, including pages and custom posts.</li>
<li>ACF fields of type Text, Text Area, and WYSIWYG. Disabled by default.</li>
<li>Avada. The following elements has been proven to work: Content Boxes, “Gravity Form”, Modal, Text Block. Other elements could work too, but not tested.</li>
<li>Beaver Builder. It will detect Gravity Forms shortcodes added to a Text Editor module.</li>
<li>Conversational Forms add-on. It will automatically detect any form page using the conversational_form post type (requires Conversational Forms add-on 1.3.0+).</li>
<li>Divi. It should work with any of the default modules where you can insert a GF shortcode into the content. e.g. Call To Action, Text, Tabs…</li>
<li>Elementor. The following widgets added to the post content are supported: Shortcode, Text.</li>
<li><a href="https://wordpress.org/plugins/essential-addons-for-elementor-lite/" rel="ugc">Essential Addons for Elementor</a> Gravity Forms widget.</li>
<li>GravityKit Gravity Forms Widget for Elementor.</li>
<li>PowerPack for Beaver Builder Gravity Forms Styler module.</li>
<li><a href="https://wordpress.org/plugins/ultimate-addons-for-beaver-builder-lite/" rel="ugc">Ultimate Addons for Beaver Builder</a> Gravity Forms Styler module.</li>
<li>Ultimate Addons for Elementor By Brainstorm Force.</li>
<li>WooCommerce Gravity Forms Product Add-ons by Lucas Stark.</li>
<li>WPBakery Page Builder. The following elements has been proven to work: “Gravity Form”, Text Block. Other elements could work too, but not tested.</li>
<li><a href="https://wordpress.org/plugins/wp-tools-gravity-forms-divi-module/" rel="ugc">WP Tools Gravity Forms Divi Module</a>.</li>
</ul>
If you’re not using any of the above embedding methods you can still use Fresh Forms with a filter to pass the ID number of the posts where you want to run Fresh forms. You can also make Fresh Forms to add a cookie when a form is detected to use this cookie as a way to skip caching for hosts using Varnish based caching. Please see FAQ for more details.
There’s no options page. Only the plugin version is saved to the database to be able to handle actions after an update when needed, no other data is stored.
It should work with any caching plugin with support for DONOTCACHEPAGE constant, and proxies respecting the use Cache-Control HTTP header.
Caching and Optimization plugins supported:
<ul>
<li>Autoptimize</li>
<li>Cache Enabler</li>
<li>Comet Cache</li>
<li>Hummingbird</li>
<li>Kinsta Cache</li>
<li>LiteSpeed Cache</li>
<li><a href="https://wordpress.org/plugins/page-optimize/" rel="ugc">Page Optimize</a> (Script concatenation only)</li>
<li>Perfmatters (Delay JS exclusions only)</li>
<li>Speed Optimizer (by SiteGround, the plugin with more name changes in the history of WordPress!)</li>
<li>Surge</li>
<li>W3 Total Cache</li>
<li>WP Engine System</li>
<li>WP Fastest Cache</li>
<li>WP Optimize</li>
<li>WP Rocket</li>
<li>WP Super Cache</li>
</ul>
Caching plugins NOT supported:
<ul>
<li>Breeze. It doesn’t support DONOTCACHEPAGE constant or filters to skip caching. Check FAQ for a workaround.</li>
<li>NitroPack. It doesn’t support DONOTCACHEPAGE constant or filters to skip caching. Check FAQ for a workaround.</li>
</ul>
Cloudflare and other CDN/proxies:
This plugin will add appropriate HTTP header to pages with a Gravity Forms form to exlude the page HTML from caching when the web host setup allows it.
By default Cloudflare doesn’t cache the page HTML, it does only when you have configured it to “Cache Everything”. In this case, after activating the plugin, you need to purge cache in your Cloudflare account or wait for cache expiration to let Cloudflare know the page must be excluded from caching.
Certain hosts like WP Engine and Kinsta don’t allow HTTP headers modification from WordPress side of things, therefore Cloudflare support will not work for these hosts.
Other proxy services should work in a similar way, but I don’t have access to test any other proxy service. Feel to reach me if you want to provide me access to add support for your proxy service (documentation for the proxy would be required).
Note for these cases (caching is done by an external service), Fresh Forms can just include the HTTP header when your web host allows it. Once the header is added, it’s up to the CDN/proxy being used to obey the header and skip caching for the page.
<h4>Requirements</h4>
<ul>
<li>PHP 7.0 or higher.</li>
<li>WordPress 4.9 or higher.</li>
<li>Gravity Forms 2.3 or higher.</li>
<li>Only forms embedded using classic editor shortcode or Gutenberg block are supported.</li>
</ul>
<h4>Usage</h4>
Just install and activate. No settings required except for ACF support (see FAQ).

Fresh Forms for Gravity


You have to love a plugin that just works, and this one does. Install, activate, and all the caching and optimization problems related to Gravity Forms go away. THANK YOU!


Excellent Plugin that Solves a Real Problem

Prevent supported caching and JS optimization plugins breaking Gravity Forms.

manojtd

Once you use a Content Delivery Network (CDN) such as Amazon Cloudfront to speed up your blog, you will come across instances when you update a static file (a style or image file, for instance), but your readers keep getting the stale file from the CDN. No amount of cache clearing on your blog server is going to help refresh the cached file because it is on the CDN. The only way would be to “invalidate” the file, which will signal the CDN to pull a fresh copy from the origin location. But this necessitates you to log on to the CDN server, locate the file, generate a proper invalidation request, and wait for it to percolate to all the mirrors. And it often costs money.
CDN Buster offers a much easier alternative. You enter a Version String in the plugin admin page, and append the same string where you define the CDN address in your caching plugins, such as WP Super Cache or W3 Total Cache. This way, when your reader loads a page, he is looking for a different file, and your CDN server will query your blog server for it, where this plugin will intercept the query and serve the modified file from the original location. Thus, the modified file will get loaded on your CDN and all will be well.
<h4>Pro Version</h4>
In addition to the fully functional Lite version, CDN Buster also has a <a href="http://buy.thulasidas.com/cdn-buster" title="CDN Buster -- easy invalidation of your CDN cache, $5.95" rel="nofollow ugc">Pro version</a> with many more features.
<ol>
<li>Automatically update the CDN settings in your WP Super Cache or W3 Total Cache plugin.</li>
<li>Change the origin pull location on your CDN server to a generic string (e.g. <code>cdn-bustor-*</code> where <code>*</code> can be anything) without touching your blog settings to invalidate the cache.</li>
<li>Invalidate by file type, so that only certain types of files are invalidated.</li>
<li>Invalidate single files from a list that you specify.</li>
</ol>
<h4>Why use a CDN</h4>
Content Delivery Network (CDN) is a collection of geographically distributed servers that mirror and serve you static contents (images, JavaScrip/CSS files, movies etc.) to your readers much faster than your own blog server can. It speeds up your blog tremendously:
<ol>
<li>It serves a large part of your website payload from servers that are close to the readers. CDN servers are specifically optimized for such contents.</li>
<li>Since your resources on the CDN have different address (URL), the reader’s browser loads the statc content and the dynamic content (from your blog server) in parallel, enhancing the user experience.</li>
<li>The load on your blog server goes down becuase it is no longer serving a large part of the page content, which improves its performance.</li>
</ol>
In short, if you are not using a CDN yet, you should. It is very easy to set it up if you use any popular cacching plugins (such as WP Super Cache or W3 Total Cache). Most CNDs are of the so-called Origin Pull kind, where the CDN server automatically pulls a file from a location (typically your blog itself) whenever it is asked to serve a file it doesn’t have in its cache. This is usually a one-time operation, which is slow. The CDN then proceeds to mirror the file on its servers all over the world. Thereafter, whenever the file is requested, the file is served instantly from a server closest to the reader.

CDN Buster

Wrote this plugin because I could not find anything similar in the directory. Hope you find it useful.



Author Review

CDN Buster is a tool to invalidate the files cached on your CDN server en masse. It helps you update the stale files on your CDN server easily.

Fresh Forms for Gravity vs CDN Buster