Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Thanks @htrex, always good to see somebody helping out the wider WordPress/Wordfence community. As topics are searchable this should appear for anybody looking it up in future.

    The topic you cited seemed to have been solved with turning off the checkbox Front-end Website under Monitor background requests from an administrator’s web browser for false positives at the bottom of the Wordfence > Firewall > All Firewall Options page, but I will certainly pass your link on to the development team should considerations for AMP compatibility be part of our ongoing plugin update cycle.

    Thanks,

    Peter.

    Thread Starter htrex

    (@htrex)

    Hi @wfpeter,
    as far as I can understand from your reply here https://www.ads-software.com/support/topic/amp-error-message-jquery-min-js/#post-14057380 the wordfence script enqueued for logged in only users is usefull to warn and eventualy whitelist false positives which could happen for admin ajax requests to the backend.

    Disabling this Wordfence feature doesn’t seem optimal and I hope the next Wordfence version could have a better AMP compatibility.
    If I understand correctly, enabling AMP compatibility should be as easy as adding “data-ampdevmode” attribute to scripts and styles added for logged in users only, please remark it to plugin devs.

    Thanks

    Alessandro

    • This reply was modified 2 years, 9 months ago by htrex.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Official AMP plugin compatibility’ is closed to new replies.