Hi there,
Thanks, I’ll investigate this.
Regards,
Marc.
When you say not compatible. What happens then?
And why do you need to stop using it?
Are you saying the page with CF7 and recaptcha is not cached or does it do something else?
Thread Starter
Exo
(@richardshea)
Hi, it’s very random too I’m finding – if I clear cache the forms can then be submitted.
Until then, the form won’t submit and a generic error shows… which according to CF7 forums is a recaptcha error.
What is interesting is, when I cache the page manually (visit it myself) for the first time it works, but via a cron/rebuild of cache the next day it causes the forms problems.
I’ve switched off the cache on all my sites as it turns out it’s happening on a form maker called DHVC Form (Visual Composer) too.
But I did some tests on WP-Forms and Caldera with recaptcha and they seemed fine, so I’m none the wiser to be honest which doesn’t help you, and I can’t replicate the fault unless I clone to a staging copy which I’ll try and do ASAP for you as I’d like to use your cache as it’s so wonderfully simple!
From what I understand of how Google reCAPTCHA works, it’s your reCAPTCHA plugin that needs to be coded for cache-compatibility, not the other way round (the cache plugin can’t do anything to help). If a unique-per-user token is embedded in the page HTML, then that is always incompatible with page cacheing – i.e. not something the page cache plugin can fix. But if that unique-per-user token is fetched by your reCAPTCHA component over AJAX, then it can work together with page cacheing. So, what this boils down to is, you need to deploy a reCAPTCHA plugin that does it in a page-cache-compatible way.
