Conflict with Amp plugin

  • Resolved universalmovies

    (@universalmovies)


    3 years, 6 months ago

    Hello, I have a premium account and I find myself having a conflict problem between Fastest Cache and the Amp plugin.

    basically they tell me that Fastest tends to remove the type = “module” attribute.

    how can i solve?

    thank you

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

  • Yes, as of v2.1 the AMP plugin will serve module scripts to supporting browsers. So what was previously:

    <script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>

    Is now:

    <script src="https://cdn.ampproject.org/v0/amp-analytics-0.1.mjs" async="" custom-element="amp-analytics" type="module" crossorigin="anonymous"></script>
<script async nomodule src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js" crossorigin="anonymous" custom-element="amp-analytics"></script>

    The script[type=module] is served to modern browsers while the script[nomodule] is served to old browsers (especially IE 11).

    The problem is that WP Fastest Cache is stripping out the type="module" attribute which is required. On the non-module scripts, the nomodule attribute must be retained.

    Learn more about JavaScript modules on MDN.

    We have the same problem Emre bey! Iyi bayramlar btw ??

    Plugin Author Emre Vona

    (@emrevona)

    the problem is caused by the premium plugin. To create threads about the premium version on www.remarpro.com forum is forbidden so please contact us via email about the problem which is related to the premium version.

    Please contact us via email for the solution: https://www.wpfastestcache.com/contact-us/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with Amp plugin’ is closed to new replies.

Tags