Title: Plugin Compatibility Last modified: March 28, 2019 --- # Plugin Compatibility * [drnick2](https://wordpress.org/support/users/drnick2/) * (@drnick2) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/) * With the last update I am getting plugin incompatibility warnings shown below: * **Warning: The following plugins may be incompatible with AMP: wp-copy-protect- with-color-design, wordfence, weaver-xtreme-plus, amp** * Why would the Amp plugin be incompatible with itself? Also why would Wordfence be incompatible? * Thanks in advance. Viewing 15 replies - 1 through 15 (of 15 total) * Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11368678) * Any plugin that adds custom scripts would be incompatible. Any plugin that adds markup which is not valid AMP would be incompatible. As for why it is saying AMP is incompatible, it may be due to CSS for your theme and plugins pushing out the CSS added by the AMP plugin. * Are you using the Native or Paired modes? If so, please try rechecking the AMP validity of the most recently-published post (via the revalidate link in the admin bar). * Otherwise, if you are using Classic mode, then that warning is somewhat misleading as I believe it doesn’t apply for you, at least in regards to AMP. * Thread Starter [drnick2](https://wordpress.org/support/users/drnick2/) * (@drnick2) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11370699) * [@westonruter](https://wordpress.org/support/users/westonruter/) Thanks for the prompt reply, I am using the paired mode and I needed to accept the errors generated by Amp due to the plugins I mentioned. From what I can see and I might be wrong, once the errors are accepted then any other errors (same)generated from those plugins will not be shown in subsequent pages or posts. * Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11370946) * [@drnick2](https://wordpress.org/support/users/drnick2/) That is correct. Once you accept the sanitization (removal) of invalid markup that causes a validation error, you won’t get warnings about that same validation error anymore. (If the invalid markup has variable content you’ll have to do a bit more to make sure that happens.) * Would you please share a screenshot of the validation errors for a URL (e.g. the validated URL screen for the homepage)? I want to see why AMP is being flagged as not being compatible. - This reply was modified 7 years, 2 months ago by [Weston Ruter](https://wordpress.org/support/users/westonruter/). * Thread Starter [drnick2](https://wordpress.org/support/users/drnick2/) * (@drnick2) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11371644) * Below is a link for a couple of screenshots. [https://photos.app.goo.gl/94rFApUsQgZsF9X59](https://photos.app.goo.gl/94rFApUsQgZsF9X59) The top screenshot is when I activate a plugin and the second screenshot shows the accepted errors with the plugins listed that are causing the warning. Please edit out the link after you view the screenshots, thanks. * Thread Starter [drnick2](https://wordpress.org/support/users/drnick2/) * (@drnick2) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11371904) * [@westonruter](https://wordpress.org/support/users/westonruter/) Sorry did not direct the message to you. Below is a link for a couple of screenshots. [https://photos.app.goo.gl/94rFApUsQgZsF9X59](https://photos.app.goo.gl/94rFApUsQgZsF9X59) The top screenshot is when I activate a plugin and the second screenshot shows the accepted errors with the plugins listed that are causing the warning. Please edit out the link and delete the previous message if possible after you view the screenshots, thanks. * Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11371967) * [@drnick2](https://wordpress.org/support/users/drnick2/) thanks, but I need you to navigate into the validation URLs for that one specific URL (manuka-honey). That will then detail what the specific errors are for each plugin. * Note also that I cannot edit the forum posts to remove content. * Thread Starter [drnick2](https://wordpress.org/support/users/drnick2/) * (@drnick2) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11372032) * [@westonruter](https://wordpress.org/support/users/westonruter/) Thanks for explaining further what you needed. I had to split it into two photos, below is the link. * [https://photos.app.goo.gl/7jtRFpptz5xxRJEaA](https://photos.app.goo.gl/7jtRFpptz5xxRJEaA) * Thanks again:) * Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11372157) * [@drnick2](https://wordpress.org/support/users/drnick2/) thanks. Ok, it is not expected that “Invalid element: script” happens in the AMP plugin. Please expand the details for one of those validation errors to reveal what the attributes are which are causing it to be invalid. * If you have a plugin that is replacing “[https://”](https://”); with“//” then that could be the problem. AMP requires the full URL to be present. * Thread Starter [drnick2](https://wordpress.org/support/users/drnick2/) * (@drnick2) * [7 years, 2 months ago](https://wordpress.org/support/topic/plugin-compatibility-39/#post-11372267) * [@westonruter](https://wordpress.org/support/users/westonruter/) No plugins used like that. Since it would take a lot of screenshots and there are essentially** three errors** related to Amp, I will list them below, if you need something more let me know. * **Invalid_Element :Script** * Invalid markup: