Joshaw

Hi,

Any update on this? This plugin has stopped working for me today and I believe it’s because Google has stopped allowing the use of insecure apps.
I figured it’d be best to tag onto this chat instead of creating a new one but let me know if you’d rather a new ticket is raised.

Thanks

Perfect, thanks Josh!

@sallyruchman happy to help ??

Update: I’ve found that the reCaptcha script can actually be deferred and the form work successfully (according to another user – I haven’t personally confirmed this) so if you want to defer the script and it’s not working, try reordering your scripts. I’m just going to leave mine not being deferred for now ??

• This reply was modified 4 years, 7 months ago by Joshaw.
• This reply was modified 4 years, 7 months ago by Joshaw.

@kmzerowebmarketing thank you for letting me know, I guess that means the scripts CAN actually be deferred… It must be the order of my scripts or something.

Appreciate you letting me know what worked for you!

Thanks,

Jo

There are additional plugins you can use to add conditional formatting for CF7 fields but it doesn’t do it natively.

CF7 is a fantastic contact form plugin, I’ve used it for almost 10 years now and it’s never failed me. But whenever I’ve needed more advanced functionality I’ve used Gravity Forms, which isn’t free, which is why it can offer more advanced functionality.
I’ve also worked with sites that use free CF7 extensions, developed by other developers I think, to add conditional fields, so you have a couple of options to try.

Hope that helps ??

Contact form 7 doesn’t do this, it never has. When I need this functionality I use Gravity Forms.

I had a very similar issue.

You have this console error:

Uncaught ReferenceError: grecaptcha is not defined
    at (index):380

The reCaptcha script is being deferred

<script defer="" src="https://www.google.com/recaptcha/api.js?render=6Lco3eAUAAAAAIzgY0WSHB1I6uHF09qoc9WspXpQ#038;siteground-async=1&ver=3.0"></script>

And another is being loaded asynchronously:

<script type="text/javascript" async="" src="https://www.gstatic.com/recaptcha/releases/zItNOfzbrqVGbb4QFYpPpcrw/recaptcha__en.js"></script>

Not sure what the asynchronously loading script is but when I stopped deferring that first script it started working for me.

Hope that helps ??

• This reply was modified 4 years, 7 months ago by Joshaw.

Hi @mateuszgbiorczyk, apologies for the delay replying, I didn’t see the notification for your reply strangely.

Understand your point, it is a bit of a rare failure of the redirects as I don’t think many users flip between Chrome/Firefox and Safari, it’s probably only really us developers who do that while building & testing so hopefully it’s not something that will cause issues for users.

The big shame here is that there isn’t a standardised format yet, hopefully Safari will adopt WebP but I’m not sure where they stand with that considering it was developed by Google.

I’ve submitted a suggestion using their feedback form, anyone wanting to do the same, here’s the link:

https://www.apple.com/feedback/

@takayukister understood – I thought I was being efficient by finding someone with the same issue as me but I guess not.

I will start my own thread and await your reply.

I had the same issue, there were no console errors but when testing the error message it was the one provided when the sender is considered spam. I found that removing reCaptcha V3 integration, and using V2 instead, resolved the issue.

Please let me know if I need to start my own thread, at the moment it sounds like I am having the same issue as @techmaster360

Unfortunately I can’t share a URL of the site publicly as it’s a client site and I wouldn’t want any of their or our competitors to be aware of any issues.

Many thanks,

Jo

I’m sorry, I’d need to know a great deal more info to be able to help but I just don’t have the time to provide free support at the moment (I’m not in any way associated with this plugin or its developer).

The best thing you can do is research, test and take accurate records of this. Then share that information. The community may then be able to offer help after reading the details but with so little information it’s impossible to advise without stabbing in the dark.

You can also try the WordPress Stack Exchange forums if CF7 support take too long to reply. Or buy a contact form plugin as free ones aren’t always obliged to provide timely support.

Hopefully CF7 support will respond to this and help resolve both yours and my issues.

• This reply was modified 4 years, 7 months ago by Joshaw.

I have them same issue, but it was sending successfully in safari – were you able to test Safari?

I found the culprit to be the reCaptcha V3 integration, which has always been troublesome, shame CF7 dropped support for V2, but I’ve now installed ReCaptcha v2 for Contact Form 7 which has resolved the issue but now I have to use reCaptcha V2.

Hopefully CF7 will fix this.

@frasermcq – Mateusz suggested you contact your server admin, did you do that? If so it would help helpful to come back and share with everyone what they said in case that helps someone else solve their problem.

If the issue is different to mine you should open an new support ticket to keep support conversions clear and easy to follow, if people chip in with similar but slightly different issues it can make it harder for other people to follow and find a solution that works for them. I’m not attacking you personally just trying to keep support forum tidy and easy for people to use.

So if you are not using Cloudflare I’d suggest you start a new ticket as my issue is Cloudflare related. However if you are using Cloudflare and your issue is identical to mine, then please read on and contribute with what you have done yourself to investigate.

@mateuszgbiorczyk – I have discussed the issue further with Cloudflare and this is their explanation and suggestion:

“I believe this is due to the subsequent requests being made to Cloudflare edge requesting for the non-webp file types.
After the files were cached in our edge servers, requests for that files will be served directly from the edge server, not from your origin, thus .htaccess no longer can process it.

One suggestion I can recommend you is to consider using Cloudflare Workers to rewrite the URLs instead of using .htaccess in your origin. This can make sure the processing is done at the edge instead of at your origin, and also can reduce the origin server’s load, making the requests faster from the user’s perspective.
https://developers.cloudflare.com/workers/reference/apis/html-rewriter/”

I have had a look at Cloudflare workers but aren’t sure yet how to use it to redirect image URLs. It’s a Javascript API so I assume one just needs to detect browser support with javascript and then rewrite those mod_rewrite rules in a way javascript can use (which for me is the tricky part!)

Is this something you might include in a plugin update in the future?

Many thanks,

Jo

UPDATE

I’m afraid to say that as it turns out, turning Polish off in Cloudflare did not resolve the problem. I have contacted Cloudflare again to see if they can suggest anything else.

I’ll update this thread when I find out more.

Thanks

Jo