Hi,
I’m using the Gravity Forms reCAPTCHA Add-On to prevent my form from spam. When ever I’m activating the add-on and try to submit my form, the message “There was a problem with your submission. Please review the fields below” appears.
I’ve already excluded the page from WP Rocket and also disabled the plugin for testing, but the message is the same.
I’ve replied to your support ticket about this issue.
For anyone else finding this topic, if the theme or another plugin includes a conflicting script, that could be preventing the reCAPTCHA script from adding the score to the submission, which can result in a validation error without any field-specific errors.
Caching and script optimization are the most common cause of this issue, so we do recommend excluding pages that include forms from those features:
When clearing the cache and excluding the page from caching and optimization doesn’t resolve the issue, the next troubleshooting step is to perform a conflict test, following the steps described here: Testing Theme/Plugin Conflict
Note that for a valid conflict test, a test must be done with only Gravity Forms & reCAPTCHA enabled. All other plugins, including third-party add-ons for Gravity Forms, should be disabled, and a default WordPress theme without custom code should be used (e.g. Twenty Twenty-Four).
If you don’t feel comfortable doing this on the live site, try creating a staging clone or sandbox setup for testing.
In our case, we figured it was the custom Gform button that was the problem.
In order to resolve the issue, we either rollback to the previous version or add the onClick event to the button.
The problem is that we have a lot of websites to cover with this fix and will take some time. Is there an official solution coming in the next update?
The issue with custom buttons that do not include the onlick that triggers the form submission scripts will not be resolved via an update, that is something you need to fix in your own custom code that is changing the button.
The recommended approaches to modifying the button, whilst retaining the attributes from the original button, can be found on the following page of the documentation: