Samuel Aguilera

You’re welcome. I have this plugin enabled on multiple sites and I’m not getting any errors.

Are you able to replicate the issue in a clean WordPress installation, with no other plugins enabled and using a default WordPress theme? If so, please provide me step by step instructions on how to replicate the issue in this scenario.

You’re welcome @davedecc

I see that Nginx Helper doesn’t have any option to exclude pages from cache, which suggests it’s not possible to do this from WordPress. Which makes sense to me because in my experience with nginx it’s a server that tends to avoid dependencies from external sources to improve its performance.

So it wouldn’t be possible for me to add support for cache exclusion into Fresh Forms. I could look into adding support for the Purge option provided by Nginx Helper (e.g. to purge the cache after saving changes to a form), but for this I would need the staging site as I don’t have access to any nginx server currently.

Hi, you can use something like this:

add_filter( 'freshforms_post_has_gform', function ( $post_has_form ) {
	global $post;

	// Run Fresh Forms for all posts of a custom post type.
	if ( is_object( $post ) && 'product' === $post->post_type ) {
		array_push( $post_has_form, $post->ID );
	}

	return $post_has_form;
} );

In the above example Fresh Forms will run for any post of product type. Change product to your post type, and that’s all.

Hi Nathan,

Thanks for the plugin highlight, I’m glad to see you are so happy with the plugin. Don’t forget to leave your rating 😉

Regarding the LITESPEED_NO_OPTM constant, I think we have talked about it some months ago (by email).
Fresh Forms uses LITESPEED_DISABLE_ALL which disables everything (cache and optimization). So I see no benefit in adding LITESPEED_NO_OPTM .

Just in case, I did a scan of LiteSpeed Cache plugin files and found that LITESPEED_NO_OPTM is only used in the src/core.cls.php file. And LITESPEED_DISABLE_ALL is also in that file, processed before LITESPEED_NO_OPTM , confirming there’s no need to use LITESPEED_NO_OPTM when LITESPEED_DISABLE_ALL is already in use.

You’re welcome 😉

I’m not familiar with Gravity Wiz’s Cache Busting add-on internals, but according to the Overview section in the add-on page it deals with caching by loading the form via AJAX. So it’s a completely different approach.
I recommend you reach Gravity Wiz support for further clarification and help with their add-on.

Fresh Forms relies on what the supported caching plugins offer. None of them offer the ability to only exclude the form from cache, only per page exclusion is available. So Fresh Forms can’t do what you are looking for.

In other words, Fresh Forms is just a helper to automate what you could do using the caching plugin options. Eliminating the need of having to remember to configure a new exclusion each time you add a form to a page.
If the caching plugin doesn’t offer you the option to exclude the form only, Fresh Forms can’t offer you that option either.

You’re welcome 😉

Fresh Forms doesn’t include any specific support for it and it hasn’t been tested in a site using that.
The only documentation that I found for WP Egine’s Advanced Network doesn’t explain how it works internally or if it supports any kind of cache exclusion. The only mention to Cache is clearing it once manually from the panel.

But it’s supposed for that feature to just enable Cloudflare for your site, the only difference would be that you enable it from WPE’s control panel instead of going to a Cloudflare account dashboard.

The section linked in my previous reply explains that Cloudflare requires a cache-control header set for the page to exclude it from cache, and WPE doesn’t allow this. It also explains that, by default, Cloudflare doesn’t cache pages. It’s expected for this to be the case when you enable Cloudflare from WPE too, because WPE doesn’t allow other page caching solutions for their customers, therefore I bet they are just providing the Cloudflare integration to make use of the CDN and DDoS features.

In any case, it’s pretty easy to confirm if Cloudflare’s page cache is enabled for the site, just check the value for the cf-cache-status header in a page, if it says “DYNAMIC”, Cloudflare’s page cache is not enabled so you can forget about it.

@bradyjosephmills Are you adding the form shortcode directly into an Elementor widget or maybe using an ACF field for it? If so, please confirm which ACF field you use.