• @takayukister, thank you for the update. We are reviewing the code now. How did you address SPAM bots and individuals have have Javascript disabled? Will those attempts now be blocked?

    Thanks in advance

Viewing 3 replies - 1 through 3 (of 3 total)
  • On line 111 of /modules/recaptcha.php, he removed the problematic lines for empty tokens:

    
    if ( ! $token ) {
    	return $spam;
    }
    

    He also added an informational post about the upgrade.

    This is great because it will help with the spam problem without requiring editing of the code, but I’m hoping that since this doesn’t address the speed/resource problems with reCAPTCHA v3, 5.2 will add the option to continue with v2 of Google reCAPTCHA. : )

    Thread Starter Andy LoCascio

    (@locascioa)

    We have completed our testing and are actually quite happy with V3. We were able to trigger the SPAM block by using autofill for all the fields. That is much better than V2. We feel the speed/resource issue is relatively minor. Hiding the annoying bug is more important (just an additional bit of styling for that). All-in-all we are happy with this version.

    Andy LoCascio – Sound Strategies

    @locascioa: Thanks for the update!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Question Regarding 5.1 – URGENT’ is closed to new replies.