jave.web

@iontulburedev Doesn’t CF7 also support the v2? docs – https://contactform7.com/recaptcha-v2/ + use this plugin for login?

Google tells you how to hide it and what you have to do if you do that:
https://developers.google.com/recaptcha/docs/faq#id-like-to-hide-the-recaptcha-badge.-what-is-allowed

Ok so I’ve managed to move the badge in a relatively nice way, based on the script handle name:

add_filter( 'script_loader_src', function ( $src, $handle ) {
    if ($handle === 'google-recaptcha') {
        return add_query_arg( 'badge', 'bottomleft', $src );
    }

    return $src;
}, 10, 2 );

In reality it adds “&badge=bottomleft” to the https://www.google.com/recaptcha/api.js safely – in case there are more params (and there are more params).

All that would be enough would be a built-in option to move it to another side and/or having the ability to choose if one wants the badge or just the text with links below the form.

@iontulburedev no need, Contact Form 7 itself supports integration to recaptcha v3 ??

Are there any plans to do so?

CF7 is one of the 2 most used form plugins, historically the most used one.

Every client I have ever worked with on a WP site required a contact form. This means I can’t install this plugin for clients, because I would have to install another one for contact form.

I suggest one-time fee (let’s say $5 per site) to be able to put it there.

Maybe genereally it would be good if one could skip to some specific media page, so one doesn’t have to run the regeneration again and also to pause/resume could also work like continuing from the last known state in case of any unhandled errors.

Also putting this to **Improvements** is misleading, it should be in a section like “Breaking changes” or something of that sort. thanks.

We’ve also updated some sites relatively recently, and the shortcode is appearing instead of working [anr-captcha].

Your anwser does not really answer the OP’s core question, so I will ask more directly:

Did you remove [anr-captcha] shortcode from the free features? If you did break backwards compatibility in this nasty way – can you please provide an upgrade code? People were adding this shortcodes to custom registration forms from member plugins etc. Thanks!

HOTFIX:
Note that the plugin seems to support PHP5.6 in itself so on your own risk you can try in /wp-content/plugins/svg-support/vendor/composer/platform_check.php replace
if (!(PHP_VERSION_ID >= 70000)) {
with
if (!(PHP_VERSION_ID >= 50600)) { – this will allow it to run on PHP5.6.0+

@webtoffee yes I said that myself, however that is NOT the case for the text in the pop-up window which is different from the text in the cookie bar.

Also the point was to have translated default texts on install ?? Having ability to edit them later is fine, but unnecessary.

A little correction – I can’t find translation of the texts in the pop up nowhere. (Unless a translation plugin is used, which is NOT always the case ?? )

@robert681 it’s @javeweb , but thank you for mentioning and agreeing ??

Hi,
that is not because of this plugin but just because how Google’s verification works, if Google recognizes too many attempts from a certain IP, network or a region they don’t expect to visit the site,
they switch from “just” a checkbox to a picture verification, that you’re not a robot ??

Happens to me too both on WP and non-wp sites with Google’s recaptcha if I login more times in a row.

Well …
I can’t test a pre-release version on a web with a lot of users.
However,
I did check the code and I see you’ve added empty($post) check to the problematic function get_post_privacy_settings.
Even though this may resolve this specific issue in particular, it’s not a proper check.
The proper check should be
is_numeric($post) || (is_object($post) && ($post instanceof WP_Post))

Optionally you can also drop the is_object and just test the instanceof only – according to PHP docs: “instanceof does not throw any error if the variable being tested is not an object, it simply returns false. Constants, however, were not allowed prior to PHP 7.3.0.”

But this is the only sure way to determinate you’re really accessing a WP_Post.