Samuel Aguilera

It’s not running late, it’s just not running, because stopping feed processing is not a feature of this plugin.

For most feeds, which need the entry to be saved first in order to be able to process the feed, preventing the entry from saving will also prevent the feed processing. But this is not the case for feeds which run before saving the entry, like Authorize.net feeds.

I’ll look into this as a feature request.

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.

I don’t have any relation with the Gravity Wiz team. Gravity Wiz is a third-party developer.

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.

Adding a custom header to the page is a pretty common action done by most caching plugins to confirm the caching is active for the page.

In the same way Fresh Forms adds its custom header to confirm it was able to exclude the page from cache.

There’s no way to remove this. I’ll consider adding a filter in a future version of the plugin. In the meantime, the plugin is open source and available at GitHub, feel free to fork it.

• This reply was modified 8 months, 3 weeks ago by Samuel Aguilera. Reason: typo

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.

@pttony It is not the same problem that was reported by the previous users, but the main change from 1.4.12 to 1.4.15 was enabling ACF support by default. So the above should be some content that you added to an ACF field and Fresh Forms is scanning it looking for a form.

I see no reason for the above content to require 2GB of RAM, but in any case I have reverted ACF support back to disabled by default, as it was in 1.4.12. Just update to 1.4.17 and everything should be fine.

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.

I don’t have access to the pro version of Essential Addons for Elementor, but I tried the Gravity Forms widget provided by the Lite version and there’s no issue.

It sounds to me like some kind of conflict because in the end the problem is that the post content that Fresh Forms is receiving to check if there’s a GF shortcode is an array when it should be a string. I’m unable to replicate this scenario, but in any case I have deployed a new version of Fresh Forms (1.4.16), that should prevent the fatal error in that scenario.

Thanks for your cooperation guys, I really appreciate 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.

@lamordnt Thanks for the error message, I’m unable to replicate it in my test sites. I have been using the latest version for a few days before the release.

Can you please confirm the following details?
PHP version.
WordPress version.
Embedding method used to embed the form.

Please check the “Cloudflare and other CDN/proxies:” section of the plugin description.

Please provide more details. What’s the error you are getting exactly? Depending on your host settings you would see it displayed or saved to the PHP error file.

Also please confirm the embedding method that you are using.

Hi @fizzpopmedia, I’m glad to know that you are so happy using Fresh Forms, don’t forget to leave your rating ??

Thanks for the idea, it’s a great one, but being Fresh Forms a Gravity Forms add-on, it wouldn’t make sense to cover other scenarios where no Gravity forms are used. And unfortunately I have no time to approach a new project like that.

That said, Fresh Forms has a filter that was originally intended to deal with embedding methods not supported by Fresh Forms, but in practice you can use the filter to force its caching exclusion feature to work even on post/pages where there’s no Gravity form embedded. So, for example, if you use the filter to force Fresh Forms to run for page id 10, it doesn’t matter what you have added to the page, Fresh Forms will run the cache exclusion in the same way that it does when a Gravity form is detected.

You can find some examples in the plugin FAQ. Note that after adding/updating the snippet to include the post/page id you will need to empty Litespeed’s cache in order for Fresh Forms to be able to run on those pages.

@nathaningram I’m not sure if you received my reply to your email (I sent it just a few hours after receiving your email).

In any case, Fresh Forms 1.4.12 has been released including support for PowerPack for Beaver Builder by IdeaBox Creations Gravity Forms Styler module.