• Resolved Brian

    (@bwold)


    After switching to v3, multiple users are now reporting that they cannot submit the form. They get the yellow box with “Failed to send your message. Please try later or contact the administrator by another method.” Other users are able to send forms, and in testing on both desktop and mobile, I’ve had both success and failure — sometimes with the same or similar submission data.

    1) I really wish the error message was more clear, or there was a reporting feature on the back end to let an admin see exactly what failed. For now, I’m assuming that RECAPTCHA v3 is the issue.

    2) I use CF7DB to store entries in a table for troubleshooting. But that appears to only record successful submissions. So I have no way of knowing how many legit people have tried to submit the form and failed due to RECAPTCHA issues?

    3) Google’s RECAPTCHA admin and docs reference an Actions option, which is set in the CF7 JS. Right now, all forms are set to “homepage”, which is confusing. In a future update of CF7, I’d love to see either the name or ID of the form there, so I can use the reporting in RECAPTCHA admin to see which forms are getting abused.

    <script>
      grecaptcha.ready(function() {
          grecaptcha.execute('reCAPTCHA_site_key', {action: 'homepage'});
      });
      </script>

    4) As of now, it’s all or nothing with RECAPTCHA. A way to bypass RECAPTCHA on a particular form could be useful for troubleshooting.

    5) RECAPTCHA documentation says it scores from 0.0 (bad) to 1.0 (good), and apparently defaults to 0.5 as sendable. In the future, an option to tune that threshold (per form) might be helpful.

    Any additional info on how this new system works would be much appreciated. For now, I think I may have to deactivate the keys and just absorb the junk as it comes in.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    1) I really wish the error message was more clear

    You can edit the messages. See Editing Messages.

    2) I use CF7DB to store entries in a table for troubleshooting. But that appears to only record successful submissions.

    Try Flamingo. Flamingo also records spam and mail-failed submissions.

    3) Google’s RECAPTCHA admin and docs reference an Actions option, which is set in the CF7 JS. Right now, all forms are set to “homepage”, which is confusing. In a future update of CF7, I’d love to see either the name or ID of the form there

    reCAPTCHA’s front-end verification isn’t connected to a specific form. It monitors the access pattern on the whole “homepage”s. So it would be inappropriate to set the name or ID of a form as the Action.

    4) As of now, it’s all or nothing with RECAPTCHA. A way to bypass RECAPTCHA on a particular form could be useful for troubleshooting.

    You can do it with Contact Form 7’s filter & action hooks. The wpcf7_spam filter or wpcf7_recaptcha_verify_response filter would be helpful for the purpose.

    5) RECAPTCHA documentation says it scores from 0.0 (bad) to 1.0 (good), and apparently defaults to 0.5 as sendable. In the future, an option to tune that threshold (per form) might be helpful.

    You can do it with the wpcf7_recaptcha_verify_response filter. See this thread for details: https://www.ads-software.com/support/topic/failed-to-send-your-message-since-recaptcha-v3/

    Thread Starter Brian

    (@bwold)

    Thanks for the extra info. Re #1 (messages): I was trying to say that I wish the error message included details specific to that form submission, like “rejected by RECAPTCHA” or “recipient mail server error.” I believe there are at least several cases that generate the yellow box error, but whenever it happens, there’s no easy way to determine what caused it.

    I’ll look again at Flamingo; if it records the errors with any specific details, that might do it for me.

    Again, thanks!

    • This reply was modified 5 years, 10 months ago by Brian.
    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Unfortunately the reason of spam isn’t recorded anywhere for now. I’ll consider implementing it in a future release.

    Hello,
    I am having this same issue. I noticed that two of the rejection messages are the some, one for a failed send and another for when it identifies spam. So, I changed the message for spam, and I got my message rejected and it was the message for “Submission was referred to as spam”

    So it seems that reCaptcha3 is being a little too strong. also, I noted that this happened in the Chrome browser, but not the Safari or Firefox browser. The Chrome browser was just updated recently (which it does automatically BTW), and it broke a browser extension I use. I had not had this problem previously.

    Here was the explanation in that case:
    “The concern was in fact related to the signature of the Chrome browser thus preventing the application from working properly.” Apparently, the extension did a check of the browser signature, which changed in the recent update.

    Could this part of the issue?

    This happens with some of my forms too. Often you can eventually submit the form if you keep resubmitting it, but it takes 3 or 4 resubmissions before it will get through.

    Recaptcha v3 is a bit too picky. I know there are other plugins you can use to stay with recaptcha v2, but you ought to build a way into CF7 for users to stick with v2.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Recaptcha v3 Problems’ is closed to new replies.