• Resolved firstfestivefooties

    (@firstfestivefooties)


    I am using the AMP plugin to help my online store/website run faster but it shows Complianz as having compatibility issues. Any ideas on how to fix this? I asked AMP and they didn’t have any suggestions other than using a different plugin instead or requesting/suggesting the plugin be made to be compatible with AMP

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Aert Hulsebos

    (@aahulsebos)

    Hi @firstfestivefooties,

    What do you mean by compatible? Complianz works fine with AMP, as is our AMP consent banner.

    It is correct there may be inline scripts or tags used in the page source that are not compatible with AMP, but these are specific to consent management if there’s no AMP enabled.

    I think “suppressing” Complianz in the AMP plugin might even work.

    regards Aert

    Thread Starter firstfestivefooties

    (@firstfestivefooties)

    Fair question. When I refer to “compatible”, what I mean is:

    When I run an AMP “site scan” Complianz shows up on the list of “Plugins with AMP incompatibility”. Also, after using a Health Check plugin, I discovered the Neve theme (which is also supposed to be AMP compatible) only shows up as having compatibility issues when I activate the Complianz plugin.

    I am fairly new to this, so I’m not really familiar with coding, inline scripts, etc. What would “suppressing” the Complianz plugin (from AMP) do? Also, other than “suppressing” Complianz is there anything I can/should do to address the compatibility issue?

    Plugin Contributor Aert Hulsebos

    (@aahulsebos)

    Hi @firstfestivefooties,

    I just had another look, the main issue seems to be the control of javascript of third parties.

    I ran a test and both a Matomo <script> tag, and a Facebook element from Elementor were assigned to us. Both are not allowed, either inline scripts (that’s why you need to configure Analytics for AMP) and attributes incompatible for AMP.

    This however is not the case if you’re looking at an https://designcmplz.us.instawp.xyz/index.php/2022/03/04/hello-world/?amp=1 where Complianz works. In this case, AMP has suppressed the incompatibilities and Complianz enabled the AMP integration.

    This should be fine, as the AMP integration from us should replace the incompatible, and suppressed files loaded on a ‘normal’ page. However, AMP seems to look either at the pre-cached page-source or if the plugin has been submitted to their Ecosystem; https://amp-wp.org/ecosystem/

    I’ll have a look at the latter, but I don’t see any issues other than a probable false positive due to our configuration.

    regards Aert

    Thread Starter firstfestivefooties

    (@firstfestivefooties)

    Thanks for the response. I want to double check, if I’m understanding correctly, AMP is falsely flagging Complianz as having incompatibility issues. If I “suppress” Complianz plugin within AMP, then everything should work correctly?

    Plugin Contributor Aert Hulsebos

    (@aahulsebos)

    Hi @firstfestivefooties,

    Yes!

    regards Aert

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘AMP incomplatible with Complianz’ is closed to new replies.