When are you going to fix the v5.4?

While we wait for the js to be fixed, if your only problem is the “innerText” js console error, you can hack in a workaround by adding this markup to the start of your form:

<div class=”screen-reader-response”><ul role=”status”></div>

It’s not ideal, but it at least allows the form to submit!

For quick and easy fix You can rollback to 5.32 version with https://www.ads-software.com/plugins/wp-rollback/
Install -> go to plugins -> cf7 rollback -> 5.32 -> done

same here. after update > 5.3.2 with google recaptcha activated the our forms didn’t work no more. should really be fixed. without recaptcha everything worked fine but spam dropped in immediately. thanks for the hint, @hardcorowa_jadwiga!

times ticking!
– 5.3.2 working fine
– 5.4 with google ReCaptcha activated our forms didn’t work.
(Flamingo does catch then unsent email, under spam)
– 5.4 without google ReCaptcha everything worked fine.

Yeah – this is an ongoing disaster. Been this way for months. Removing REcapcha seems to allow everything to work.

This bug still exists in 5.4.1 and when I test with/without reCaptcha there is no difference.

When I view the source of the page (opening the source in a new tab) I see:
<div class="screen-reader-response"><p role="status" aria-live="polite" aria-atomic="true"></p> <ul></ul></div>

But when I inspect the element in Chrome developer I see:
<div class="screen-reader-response"> <ul></ul></div>

So the p-tag has been removed by javascript.

Please considering it isn’t a bug. the reason is your page minifier (or something like that) that removes a target of the cf7 script so it crashes.

please check this and the author response

@codekraft In my case it was indeed the theme that had:
$('p:empty').remove();

So my apologies, and my report can be disregarded.

Hey yo,

Also running into this issue. Any chance it’s going to be fixed soon?