Viewing 6 posts - 31 through 36 (of 36 total)
  • Author
    Posts
  • #1480979

    @Ismael Yes, but I don’t have the time for creating staging environments for this unfortunately, but you’re welcome to on your side. I said you can test on the live site, but made an assumption that people would test quickly and briefly.
    We’ve already provided cpanel access so you can edit files from the File Manager or use the same credentials for FTP if needed.
    As mentioned, we are the hosting provider too. All our sites are on PHP-FPM so we’re not going to change this. We have other sites running Enfold without a problem, so I doubt PHP-FPM (or the redis and memcached extensions) is the problem here.
    In a few hours, we’ll need to implement a workaround and change the Enfold contact form to a different one… so please create a staging site or do whatever last tests you would like to.
    Thank you for your assistance everyone!

    #1481058

    Hi,

    We cloned your site to our local installation, and the contact form with reCAPTCHA worked correctly. This is definitely an issue related to the server configuration.

    Best regards,
    Ismael

    #1481069

    Hi all,

    We’ve tried disabling PHP-FPM as directed, but that hasn’t resolved the issue either.

    Thanks for your help. We’ve had to go with a workaround unfortunately (removing the contact form altogether), in the absence of any solution.

    It must be related to server config in some way, and the way the Enfold contact form and Google Captcha work – as we don’t have the issue if we remove either of these variables.

    Moderators: Kindly remove the brand identifying screenshot in the previous post and the mention of the company name in your post on March 17, 2025 at 10:52 am.

    Thank you!

    #1481110

    Hi,

    We removed any mention of the site from this thread and relocated the screenshot into the private field.

    Best regards,
    Ismael

    #1481381

    Hi
    My research has revealed the following:

    @engage24
    and we (mediaformers) both seem to be using the caching plugin W3 Total Cache. I have done various tests. If I delete the caching plugin completely (not just deactivate it), sending the contact form with Recatcha v3 works again. However, it is important that the wp-content/object-cache.php file is also deleted!

    Further insight: With the W3 Total Cache plugin activated, I receive the following recommended improvement in the WP backend under “Website status”: “A scheduled event has failed” (ava_cron_admin_notices_clean_up). Without the plugin, this recommendation is no longer there.

    Perhaps this information will help with further analysis. If necessary, W3 Total Cache should be informed.

    Best regards
    Mike

    #1481418

    Hi,

    Thank you for the info @mediaformers!

    Best regards,
    Ismael

Viewing 6 posts - 31 through 36 (of 36 total)
  • The topic ‘After adding Captcha V3, we get “Token to validate form already expired.”’ is closed to new replies.