hi @chieleman
the issue is related to a minifier that removes the empty p
TypeError: Cannot set properties of null (setting ‘innerText’)
there are many possibile solution read here:
https://ww.wp.xz.cn/support/topic/typeerror-cannot-set-property-innertext-of-null/
Hi Erik,
Thanks for your message. You mention an error. I don’t get an error. Nothing happens. Just checking if it could still be the same thing…
I looked at your link and a couple more links. I see a solution, but don’t know how to implement it.
It mentions I should remove jQuery(‘p:empty’).remove(); from a js file or replace it with jQuery(‘p:empty’).not(‘[role=”status”]’).remove();
Which js file are we talking about? There are so many .js files…
TIA
chieleman
you could see the error in console after submit.
The jquery code you reported was used because that guy had a function (in functions.php) that reads all the page content and removes the empty p.
In fact, you should also find out why in wordpress installation the empty p was removed, it could be an html minifier (try checking if the html code is minified correctly by w3 total cache / change the minification method) or it could also be your website host or a template function etc
hope it helps!
Contact Form7 is not working on WordPress site
It was working fine two days earlier. Since yesterday, Whenever we submit contact information, nothing happens. Neither any error message nor any successful message displayed. I am using Flatsome theme.
Can you tell me any solution,
Regards
SK Rathore
Hi Erik,
Thanks for your time and effort. Unfortunately your second reply is more confusing to me than the first one. 🙂 I am by no means an expert. So many options and each one of them would take me a long time to figure out. For now I installed plugin WP Rollback, I rolled back to 5.3.2 and it is working like a charm again. For now I will use the older version and hopefully it won’t be to unsafe…
Thanks again.
chieleman
Sorry! In this case, try to get help from an expert who can guide you in the correct configuration of your website’s optimisation plugins, because therein lies the problem.
Okay, thanks for pointing me in the right direction!
I’m not sure if the error lies in the optimisation plugin. I don’t have any optimisation plugin, all plugins deactivated and the error still occurs. I guess it’s an bug in the 5.4 version, because the trick with the rollback to 5.3.2 works. Any tips?
ciao @helloit
so in console after submit you find a message like “TypeError: Cannot set properties of null (setting ‘innerText’)”? if not please start a new post, we are here to help you, but I don’t think your problem is exactly the same
yeah i guess you are right, i have shown nothing in console. Sorry for the wrong post.
I am confused Erik.
You mention that this post is about getting a “inconsole after submit you find a message like “TypeError: Cannot set properties of null (setting ‘innerText’)”? ”
However, don’t get an error like that. At least not on the front side. Perhaps in the backside, but I never looked in the backside.
Michiel
you need to update to >5.4.0 to see that error in console, it will appear after you try to send and email with the contact form
you can test if you have (o will have) this issue, typing this in your console:
var form = document.querySelector('.wpcf7');
form.querySelector('.screen-reader-response ul').innerText = 'ok';
if it returns ‘ok’ is ok otherwise it will return “Uncaught TypeError etc” (and isn’t ok)
-
This reply was modified 4 years, 9 months ago by
Erik.
Thanks Erik for your support. While submitting the contact form, I am getting “Uncaught SyntaxError: missing name after . operator”. I have deactivated the cache/optimization plugins, Can you please help me to resolve this issue.?
https://chargingshop.eu/elements/pages/contact/
-
This reply was modified 4 years, 9 months ago by
skrathore86.
@skrathore86
in your case the issue seems caused by “Google Analytics by MonsterInsights” script that interrupts the js execution.
it is also necessary to update “flatsome” template because old versions are causing issues with wpcf7 >5.4.0
.
