Robert Peake

Note that this plugin won’t stop page visits from automated scripts from showing up in your logs. Bots may still attempt brute force attacks against your login page — they will just be unlikely to be successful due to the Google captcha protecting that page. Hope that makes sense.

This plugin stores a maximum of nine (9) variables in the wp_options table. All of them have option names starting with login_nocaptcha*. They are updated, but should not be added as duplicates. So, it is likely something else is filling up your options table, or that there is a problem with the unique keys constraint on the table such that it allows numerous duplicates.

The error about xml-rpc tells you that people are logging in in ways that no captcha plugin can help protect you about–using the xml-rpc protocol directly. If you are not expecting this, you may wish to consider disabling this option: https://www.wpbeginner.com/plugins/how-to-disable-xml-rpc-in-wordpress/

Yes, it works with the latest version of WordPress (6.1.1) and I have updated it to show this. Thanks!

Unfortunately, no. WordPress core “reuses” the code for logging in to the admin for logging in everywhere else. It is in that code that the recaptcha “hooks” itself in, so because they are the same there is no way to “hook” it one place and not the other.

yes, caching is a common problem. Glad to hear it works!

Hi–looks like it’s working again? Could you post the solution in case it can help others?

Thanks for the idea. Currently no plans to add Turnstile support. Hopefully another plugin will do this soon, and do it well.

Glad to hear you have some good support there. It’s a very strange issue (i.e. hasn’t come up yet as we’re approaching nearly 100k installations!) so would be curious to hear the resolution.

Sorry for the long silence, Linda. Curious to hear if you found a solution…

Linda it looks like the hook login_enqueue_scripts is not firing properly to add the <script src="https://www.google.com/recaptcha/api.js?onload=submitDisable"></script> code into the footer

Linda, if the captcha is displaying in the settings page but not on the login form, almost certainly some other plugin is interfering with the rendering of the captcha. I had a look at your main site, and in the place where this plugin should be summoning Google to display the captcha, there is code for WP Rocket. Is it possible this is enabled on your live site but not on the staging site? Have you cleared the WP Rocket cache recently? Those are my best guesses at this point.

You can certainly try uninstalling and reinstalling. But in these kinds of situations, almost always it is another plugin that isn’t “playing nicely” with the login form, so I’d start with triple-checking that the plugins that are installed and enabled are 100% the same between your stage and live site.

Those two URLs would be considered in the same domain, so that may not be the issue.

You’ll want to check that the plugin is both installed and activated, and check the plugin configuration page to see if there are any error messages.

As the plugin is not displaying at all, it may not be active on the main site or may not be configured correctly.

Your stage and live sites probably have different domains. Check your settings with Google to make sure the keys you are using in the plugin settings allow for all the domains they are being used on.

Dan, I am actively using this on a site running WP 6.0.2 and not seeing any errors or problems with either the embedded gallery or link through to the Flickr page.

The 403 error on the gallery page itself comes from Flickr, and says “you need to be signed in to see this”:

https://www.flickr.com/photos/photomatt/sets/72157692025663315/

I don’t see this on the slideshows I am hosting, so I can only assume there must be some setting on the album itself making it private.

Good luck!

Check the site options table for keys beginning with “brr_”, and delete them all. This will reset all settings. WP does not delete your settings when you deactivate the plugin, unfortunately, so you have to do this manually.