Yes, we’re pushing an update that fixes that today/tomorrow 🙂
The update is released, version 1.23 🙂
Captcha is no longer displaying on login form of my site since this update was applied yesterday.
There is a raw URL displayed instead of the Captcha.
“https://www.google.com/recaptcha/api.js?onload=wpcaptcha_captcha&render=6Lcp…..”
Same issue with the last update: the reCaptcha is no longer visible on the default WP registration form.
Hello,
After the recent update you released, it does now seem as though Google reCAPTCHA is loading on a page using wp_login_form().
Currently, the plugin has a hardcoded priority of 9999 when adding the filter into the ‘authenticate’ hook, which appears to be leaving the order of execution as late as possible.
In our case, we have other functions also hooking into the ‘authenticate’ function, and it’s vital that the reCAPTCHA feature happens before anything else (with the primary aim that our other functions won’t fire if the reCAPTCHA fails).
So, we changed the priority of our function to 99999, assuming it would then fire after the reCAPTCHA event. We then tested this by attempting to log in without checking the reCAPTCHA box. However it seemed that even by not checking the box, the captcha didn’t stop the login function, and our function still was hit.
Can you confirm that the reCAPTCHA is working correctly, in the sense that if the captcha fails, should that then stop all additional functions hooked into the ‘authenticate’ filter after it?
But also, should the priority not be ‘as early as possible?’ So that the reCAPTCHA is the first thing tested?
