You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug or issue you're experiencing
Front end form protected by reCaptcha keep displaying an error message to the visitors:
Please verify that you are not a robot.
in the console: /cpresources/freeform-scripts-front-end-captchas-recaptcha/v3.js net::ERR_ABORTED 404 (Not Found)
Steps to reproduce
Expected behavior
Craft & Plugin Info (please complete the following information):
Craft Version: 4 latest
Freeform Version: 5 latest
Freeform Edition: PRO
Fresh Install or Upgrade:
Additional context
The text was updated successfully, but these errors were encountered:
Can you try switching the Freeform Script Insert Type setting (Craft CP → Freeform → Settings → Form Behavior) to As Files instead and see if that resolves it? 🙂
I can't reproduce this issue happening on my test site, and I haven't heard of anyone reporting this issue yet.
Can you confirm the exact versions of Freeform and Craft you're using? If not the latest available, please try updating.
I guess switch it back to Encrypted Payload. Can you screenshot me what your reCAPTCHA settings look like in the form builder for the affected form? 🙂
Further to this... we recommend not using the Display Error behavior for reCAPTCHA v3 since the user cannot make any changes on their side of things. Instead, you should use Send to Spam Folder. It would also then include the score the user was given by reCAPTCHA when viewing the submission in the Spam Folder. 🙂
Describe the bug or issue you're experiencing
Front end form protected by reCaptcha keep displaying an error message to the visitors:
Please verify that you are not a robot.
in the console: /cpresources/freeform-scripts-front-end-captchas-recaptcha/v3.js net::ERR_ABORTED 404 (Not Found)
Steps to reproduce
Expected behavior
Craft & Plugin Info (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: