Title: Uncaught TypeError: e.wpcf7.parent.querySelector(…) is null Last modified: March 9, 2021 --- # Uncaught TypeError: e.wpcf7.parent.querySelector(…) is null * Resolved [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/) * (@aarontgrogg) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/) * Having a new issue on an existing site: * ``` Uncaught TypeError: e.wpcf7.parent.querySelector(...) is null l https://capitolmotors.com/wp-content/plugins/contact-form-7/includes/js/index.js:1 https://capitolmotors.com/wp-content/plugins/contact-form-7/includes/js/index.js:1 X https://capitolmotors.com/wp-includes/js/dist/api-fetch.min.js:2 X https://capitolmotors.com/wp-includes/js/dist/api-fetch.min.js:2 p https://capitolmotors.com/wp-content/plugins/contact-form-7/includes/js/index.js:1 b https://capitolmotors.com/wp-content/plugins/contact-form-7/includes/js/index.js:1 b https://capitolmotors.com/wp-content/plugins/contact-form-7/includes/js/index.js:1 ``` * This is reported in dev console as coming from `index.js:1:4356` and is preventing** all** CF7 forms from submitting, the page just sits there when the Submit button is clicked… * Current setup: – WP: 5.6.2 – CF7: 5.4 * Anyone else seeing this? * Appreciate any help or direction. - This topic was modified 5 years, 3 months ago by [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/). * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Funcaught-typeerror-e-wpcf7-parent-queryselector-is-null%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 15 replies - 1 through 15 (of 15 total) * Plugin Author [Takayuki Miyoshi](https://wordpress.org/support/users/takayukister/) * (@takayukister) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14155501) * What other plugins and theme do you use on the site? * Thread Starter [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/) * (@aarontgrogg) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14155907) * Thanks for the reply. * Theme: Automotive By Theme Suite, Version: 11.9.8 Plugins: Numerous * Per standard practice… 1. Deactivated all plugins and reverted to Twenty Twenty-One theme, and error message disappeared. 2. Gradually restored all plugins, still no error. 3. Restored Automotive theme, still no error. 4. Reactivated page caching (via WP-Optimize), error returned. 5. Deactivated page caching, no error. 6. Reactivated page caching again, error returned. * Error occurs in: `/wp-content/plugins/contact-form-7/includes/js/index.js` On line 230 (via Pretty Print): `e.wpcf7.parent.querySelector('.screen-reader-response[ role="status"]').innerText = '',` * The `querySelector` returns `null`, so `innerText` throws an error. * For some reason, when page caching is turned off, this line is never called ( breakpoint never reached)… * Any guess??? - This reply was modified 5 years, 3 months ago by [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/). * Thread Starter [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/) * (@aarontgrogg) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14157081) * FYI, I have also tested the same installation, Automotive theme activated, all plugins activated, but using CF7 v.5.3.2, with page caching activated, and I do NOT get this error message: [https://dev.capitolmotors.com/contact/](https://dev.capitolmotors.com/contact/) * Plugin Author [Takayuki Miyoshi](https://wordpress.org/support/users/takayukister/) * (@takayukister) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14159074) * Doesn’t the result mean just that WP-Optimize is causing the error? * Thread Starter [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/) * (@aarontgrogg) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14159323) * Strictly speaking, yes, but also, why would a cached page break the plugin’s JS? * Also, same error when using WP Super Cache, which is another pretty common page caching plugin. * So far, WP Fastest Cache seems to be error free, will continue with that one for now. Correction: WP Fastest Cache also throws the error, just not on page load as the other two do, but it does throw the same error once the “SUBMIT” button is clicked… * This is an issue, and I realize it is a conflict between plugins, but when one plugin starts conflicting with multiple plugins, the first plugin has to re-examined… * I hope I have provided enough debugging information to be helpful, but if not, happy to help some more. * Thanks. - This reply was modified 5 years, 3 months ago by [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/). Reason: Turns out WP Fastest Cache also breaks * Plugin Author [Takayuki Miyoshi](https://wordpress.org/support/users/takayukister/) * (@takayukister) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14159738) * The most direct cause of this TypeError is known that someone removes `

` that should normally exist under `
`. I don’t know who does that and why, but from the result of your testing, it is likely to be the WP-Optimize plugin, in the case of your site. * Thread Starter [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/) * (@aarontgrogg) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14159774) * Okay, apologies, this is NOT related to any caching plugin, but apparently the theme, and I was not seeing it earlier because, without a caching plugin, the error only appears after clicking `Submit`… * The difference appears to be the change from v5.3.2’s: `$( '[role="status"]', $response ).html( data.message );` to v5.4’s: `e.wpcf7.parent.querySelector('. screen-reader-response [role="status"]').innerText` * As 5.3.2 uses a comma in the selector, it allows for `[role="status"]` to be missing, whereas 5.4 **requires** `[role="status"]` to be _within_ `.screen-reader- response`. * And for some reason, when using our theme, the `

` element is missing in the markup. * If you have any idea what might cause _this_, I would love to hear it, but if not, I will begin _that_ investigation, and again, my apologies for wasting your time… * Thread Starter [Aaron T. Grogg](https://wordpress.org/support/users/aarontgrogg/) * (@aarontgrogg) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14159935) * On the outside chance anyone else encounters this, it took a fair bit of tracking to find the culprit, but it boils down to the theme, maybe justifiably, removing empty paragraph tags, I guess trying to keep things clean? Theme file: `/wp- content/themes/automotive/js/main.js` Line 7: `$('p:empty').remove();` * I will try contacting the theme developer to ask if they can remove this in the future (though unlikely), but in the short-term, I have added a script to my template that adds a ` ` inside `

` so it is no longer empty, so the theme script no longer deletes it… * Plugin Author [Takayuki Miyoshi](https://wordpress.org/support/users/takayukister/) * (@takayukister) * [5 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14160912) * Oh, really? I was almost blaming the wrong person. I have to apologize to the WP-Optimize devs. * [pezflash](https://wordpress.org/support/users/pezflash/) * (@pezflash) * [4 years, 11 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14595120) * Finally! Thanks a bunch, Aaron. I was getting this error (ajax not working) on latests releases of CF7 en several sites, and now i see what is was causing the issue… The point is that the $(‘p:empty’).remove(); was on my own JS files( yeah, to keep things clean and avoid extra spacing on some wrong formatted -by client- texts). * Thanks again, and thanks Takayuki for such an incredible plugin. Best regards from Madrid Jesús * [Kevin Batdorf](https://wordpress.org/support/users/kbat82/) * (@kbat82) * [4 years, 10 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14742461) * Anyone looking to keep removing empty p tags but need an exception, you can update to this: * `$('p:empty:not([role])').remove()` * [@takayukister](https://wordpress.org/support/users/takayukister/) Because you know it’s a common issue, maybe you could just add a check before you attempt to access a property or method on a null type? * This will completely break everything if it’s null: `e.wpcf7.parent.querySelector('. screen-reader-response [role="status"]').innerText = ""` * Having empty paragraph tags lingering in the markup is another issue. The reason people remove empty these tags is because they show margins, which throw off content. * A better solution would be to use a div and inject a paragragh, or just inject text into the div. That’s fine too. * [Webprom Design](https://wordpress.org/support/users/webprom/) * (@webprom) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14961852) * Having this issue after everything got updated 🙁 * [jenUnderscore_](https://wordpress.org/support/users/jenunderscore_/) * (@jenunderscore_) * [4 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14967606) * We had the following built into our template. It’s a bit of a relic from days of yore when WordPress would add empty P tags in certain cases. * Removing it solved the issue. * $(‘p:empty’).remove() * [Webprom Design](https://wordpress.org/support/users/webprom/) * (@webprom) * [4 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-14968903) * Unfortunately, it’s impossible to find it in the crazy theme I’m editing 🙁 Does anyone know any other solution? * [Micemade](https://wordpress.org/support/users/anydog/) * (@anydog) * [4 years, 6 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-15096245) * I can confirm that the removal of empty `

` tags causes this issue. [@takayukister](https://wordpress.org/support/users/takayukister/)– I’m curious, why is that empty tag needed for? Thanks. Viewing 15 replies - 1 through 15 (of 15 total) The topic ‘Uncaught TypeError: e.wpcf7.parent.querySelector(…) is null’ is closed to new replies. * ![](https://ps.w.org/contact-form-7/assets/icon.svg?rev=2339255) * [Contact Form 7](https://wordpress.org/plugins/contact-form-7/) * [Frequently Asked Questions](https://wordpress.org/plugins/contact-form-7/#faq) * [Support Threads](https://wordpress.org/support/plugin/contact-form-7/) * [Active Topics](https://wordpress.org/support/plugin/contact-form-7/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/contact-form-7/unresolved/) * [Reviews](https://wordpress.org/support/plugin/contact-form-7/reviews/) ## Tags * [.js errors](https://wordpress.org/support/topic-tag/js-errors/) * 15 replies * 7 participants * Last reply from: [Micemade](https://wordpress.org/support/users/anydog/) * Last activity: [4 years, 6 months ago](https://wordpress.org/support/topic/uncaught-typeerror-e-wpcf7-parent-queryselector-is-null/#post-15096245) * Status: resolved