CriticalCSS maintains FontAwesome Plugin Source paths

  • We had been using the Font Awesome plugin. We locally loaded the files, changed the CSS to local references etc. Plugin is installed but deactivated. We cleared Autoptimize cache and CDN cache. (no other local cache).

    However, we are still seeing references to the paths set originally by the plugin in source code, specifically in the CriticalCSS:

    <style id=”aoatfcss” media=”all”>@font-face{font-family:”Font Awesome 5 Free”;font-style:normal;font-weight:400;font-display:auto;src:url(https://use.fontawesome.com/releases/v5.12.0/webfonts/fa-regular-400.eot);

    Am confused about how to handle this. If we purge Autoptimize cache, how does that impact CriticalCSS? When I “Edit” the page specific rule I can clearly see the above code within the file. The only option I have is to “remove” with a warning that such a removal would be permanent. This makes it sound like said page rule would never be rebuilt. Is that the case? The file in example is: ccss_70cb9bd900e6021732075c93132a8b4b.css

    How do we insure that the CriticalCSS Powerup matches the current site configuration? Do we have to manually delete the rules? Is there any other way of refreshing them?

    Thank you in advance!
    Josepf

    • This topic was modified 4 years, 9 months ago by haslamjj.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    -> might you have entered “default critical css” with the use.fontawesome.com references?
    -> removing a rule will see it regenerated, nothing permanent.

    hope this helps,
    frank

    Thread Starter haslamjj

    (@haslamjj)

    Hi Frank,

    good catch. So, with the base Autoptimize, you have to manually click off/on to refresh criticalcss? Kinda makes sense, but, should maybe be re-generated if someone deletes whole cache.

    As to PowerUp, the page rules/files all keep off of or import the base Autoptimize? And if so, how are you tailoring the crisitalcss to be page specific?

    many thanks!
    Josepf

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    with base Autoptimize the “above the fold CSS” (under “inline & defer CSS”) is entered manually, so you’ll have to edit manually yourself when things change.

    the critical CSS is generated by criticalcss.com (which receives requests to do so from the power-up), which fetches the pages from your site.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CriticalCSS maintains FontAwesome Plugin Source paths’ is closed to new replies.