T4G

Thanks, @jamesosborne, I appreciate the help. Glad to see everything is implemented correctly.

If you’re not finding any in article ads that may be due to the AdSense platform determining that the other ads are sufficient for each page

I understand, that makes sense. The non-AMP version of the site applies ads more liberally, so I will see in-article ads and anchor ads. AMP, however, definitely reduces the number of ads—from what I can tell—so that’s what got my attention and I thought maybe the code was implemented wrong by Site Kit.

I am just going to leave it as is. Thanks again, I appreciate the help.

Thanks, will do. They did an update and the issue is now gone.

Hi @adamdunnage,

Just finished the troubleshooting and it is indeed a conflict with the CleanTalk plugin (Anti-Spam by CleanTalk).

Thanks!

Okay cool, I am glad it worked for someone else as well.

it’s just going to be tediously irritating to update a large number of forms for multiple sites I’m sure

Absolutely, I completely agree. I think it would be best if those people just downgrade CF7 to 5.64 while keeping hCaptcha 2.2.0 because you don’t need to add the shortcode and you get the latest security from hCaptcha to combat spam.

I read that they fixed a spam bot issue in the 2.2.0 release so that CF7 downgrade would be the best option (in my opinion).

Hi @doni3232,

Not sure who you are replying to?

It sure does work, two different ways at that. However, I cannot get it to work just as you did. I installed version 1.19.0 alongside CF7 5.7 and it will not work. In order for me to get version 1.19.0 to work with CF7 5.7, I have to add the shortcode, [cf7-hcaptcha], which you did not mention doing—you mentioned checking CF7 in hCaptcha settings. @pixel_me did mention doing this.

However, I can still submit a form without the hCaptcha shortcode on the form, which means hCaptcha is not on that page at all, not even in the background—as it is in hCaptcha version 2.2.0. So I checked the Network tab via Developer tools and hCaptcha is not loaded.

That got me curious, so I installed hCaptcha version 2.2.0 alongside CF7 5.7. I then added the [cf7-hcaptcha] shortcode to the forms and voila! It worked.

However, this bug should be addressed but this thread has no contributor support replying to it yet.

I posted the console errors only for further help and diagnosis. The console errors only apply to the broken plugin version or 2.2.0. The console errors do not exist with either the CF7 version rollback or the hCaptcha version rollback.

It seems that there is something wrong with the script as it is not populating on the forms in version 2.2.0 (just in the background), so adding the shortcode to the form(s) solves that issue.

To recap, hCaptcha 2.2.0 and CF7 5.7 works fine together so long as you add the shortcode to your form(s). Also, hCaptcha 1.19.0-2.1.0 will work with CF7 5.7 or below but the shortcode has to be in the form(s).

I am sure this will get addressed and there will be no need for the shortcode.

Best regards,
Tug

• This reply was modified 2 years, 3 months ago by T4G.

Hi,

I am getting the same issue.

We have a couple of websites. After the update to 5.7, our hCaptcha for WordPress plugin no longer displays on any of the Contact Form 7 forms.

I deactivated every plugin but the Contact Form 7 and hCaptcha plugins and still nothing. All of the caches were cleared as well.

I then decided to roll back the Contact Form 7 5.7 version to 5.64 and the hCaptcha now shows up again. So the rollback does work for me, not sure why it isn’t working for others.

I also want to note that no one can submit the contact form in 5.7 as it states, “One or more fields have an error. Please check and try again.” This only applies when the hCaptcha for WordPress plugin is activated.

I checked the Console errors and got this:

Uncaught TypeError: Cannot read properties of undefined (reading 'getElementsByTagName')
    at t.value (hcaptcha.js:1:2042)
    at t.value (hcaptcha.js:1:2155)
    at window.hCaptchaReset (hcaptcha.js:1:3559)
    at HTMLDivElement.e (hcaptcha-cf7.min.js:1:847)
    at d (contact-form-7.min.js:1:788)
    at contact-form-7.min.js:1:5898

Uncaught TypeError: Cannot read properties of undefined (reading 'getElementsByTagName')
    at t.value (hcaptcha.js:1:2042)
    at t.value (hcaptcha.js:1:2155)
    at window.hCaptchaReset (hcaptcha.js:1:3559)
    at HTMLDivElement.e (hcaptcha-cf7.min.js:1:847)
    at d (contact-form-7.min.js:1:788)
    at contact-form-7.min.js:1:5956

I contacted Contact Form 7 and they told me to come here and there was already a support ticket up.

Hope this helps!

Thanks and regards,
Tug

Awesome, so it is on their end. I wasn’t 100% sure.

Thanks!

Hi Georgi,

Oh okay, that makes sense.

Thank you for the update!

Best regards,
Tug

Hi @pdosev,

I am just checking in to see what the status is of this issue.

Thanks!

I saw that, thank you.

That’s strange it only pertains to our setup. They worked perfectly fine together for a few months and then something broke.

Thank you for the help!

I can activate the SG Security plugin if you would like? EDIT: Never Mind.

• This reply was modified 2 years, 9 months ago by T4G.

Thank you for that! Much appreciated.

I also want to note the Support UUID ampwp-9e5a78a6-787d-5fdd-beb7-d0b72b29f95d

It recommends the transitional theme for some reason but that cannot be used. It does not recommend the Standard or Reader, however.

• This reply was modified 2 years, 10 months ago by T4G. Reason: Added recommends

After a few tries, it now works as it did before. I will whitelist some IPs via Cloudflare.

Thanks for the help and information!

I have a similiar issue. I synchronized the plugin and it added the curl at the end:

2022-04-19 14:02:51: Error occurred while updating SpamFireWall local base. Error: CONNECTION_ERROR : "cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received"

EDIT: It works now.

EDIT 2: It reverted back to the same error message.

• This reply was modified 2 years, 11 months ago by T4G.
• This reply was modified 2 years, 11 months ago by T4G.