Title: Plugin conflict Last modified: June 5, 2018 --- # Plugin conflict * [andywall9](https://wordpress.org/support/users/andywall9/) * (@andywall9) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/) * Hi guys * I found that the Contact Form 7 forms had stopped submitting on some of our websites with the following error in the console: * TypeError: data is null * After investigating, I found that it was a conflict with the Password Protected plugin. This was with the current versions of both plugins – v5.0.2 for CF7 and v2.2.1 for Password Protected. Deactivating the Password Protected plugin allowed the forms to submit properly again. * Note – even with the PP plugin activated, but not having the password protection turned on still stopped the forms submitting. * I’m not sure which plugin will need updating to fix this, so I’ll put it on both support pages so everyone is aware and provide a link to the other thread. * Thanks * Edit – here’s the link to the CF7 support page: [https://wordpress.org/support/topic/plugin-conflict-198/](https://wordpress.org/support/topic/plugin-conflict-198/) - This topic was modified 8 years ago by [andywall9](https://wordpress.org/support/users/andywall9/). Viewing 6 replies - 1 through 6 (of 6 total) * [sojournerweb](https://wordpress.org/support/users/sojournerweb/) * (@sojournerweb) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10364942) * I have found this issue too in my own testing. * [zigsp8](https://wordpress.org/support/users/zigsp8/) * (@zigsp8) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10365596) * I also have the same result. Error in console ————— Uncaught TypeError: Cannot read property ‘into’ of null at ajaxSuccess (scripts.js?ver=5.0.2:238) at Object. (scripts.js?ver=5.0.2:355) at i (jquery.js?ver=1.12.4:2) at Object. fireWith [as resolveWith] (jquery.js?ver=1.12.4:2) at y (jquery.js?ver=1.12.4: 4) at XMLHttpRequest.c (jquery.js?ver=1.12.4:4) * /wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.0.2 * Deactivating password protect allows email to go through. * [Ben Huson](https://wordpress.org/support/users/husobj/) * (@husobj) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10367741) * Please try the recent 2.2.2 version * If this still does not work, please try checking the Password Protected setting to allow REST access. * Please let me know if this works (or not). * Thanks * Ben * [zigsp8](https://wordpress.org/support/users/zigsp8/) * (@zigsp8) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10369918) * Thanks Ben, * Updating to 2.2.2 and using the ‘Allow REST API Access’ seemed to do the trick for me. * FYI: without the ‘Allow REST API Access’ still got error in console, this time it was… * `/wp-json/contact-form-7/v1/contact-forms/43/feedback:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)` * zig * Thread Starter [andywall9](https://wordpress.org/support/users/andywall9/) * (@andywall9) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10394303) * This now appears to be working fine for me – here are the versions I’m now on: - Password Protected – 2.2.2 - Contact Form 7 – 5.0.2 - WordPress – 4.9.6 * I didn’t need to check the Allow REST API Access option, and have tested this both with Password Protection enabled and disabled. * Thanks guys * Thread Starter [andywall9](https://wordpress.org/support/users/andywall9/) * (@andywall9) * [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10402788) * It turns out this isn’t resolved – the above for me was tested in Firefox, but we’ve just found that in Chrome we get the error stated by zigsp8: * [http://###.co.uk/wp-json/contact-form-7/v1/contact-forms/34/feedback](https://wordpress.org/support/topic/plugin-conflict-197/?output_format=md) 401 (Unauthorized) * This occurs when the Allow REST API Access option is not ticked – having the Password Protected Status as enabled or disabled makes no difference. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Plugin conflict’ is closed to new replies. * ![](https://ps.w.org/password-protected/assets/icon-128x128.gif?rev=2824217) * [Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content](https://wordpress.org/plugins/password-protected/) * [Frequently Asked Questions](https://wordpress.org/plugins/password-protected/#faq) * [Support Threads](https://wordpress.org/support/plugin/password-protected/) * [Active Topics](https://wordpress.org/support/plugin/password-protected/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/password-protected/unresolved/) * [Reviews](https://wordpress.org/support/plugin/password-protected/reviews/) ## Tags * [plugin conflict](https://wordpress.org/support/topic-tag/plugin-conflict/) * 6 replies * 4 participants * Last reply from: [andywall9](https://wordpress.org/support/users/andywall9/) * Last activity: [8 years ago](https://wordpress.org/support/topic/plugin-conflict-197/#post-10402788) * Status: not resolved