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

    (@daanvandenbergh)

    Hi @missfrosty1,

    I think there’s a bit of a misunderstanding here. When I look at your frontend, it doesn’t seem you’re using CAOS for Webfonts at all! So, obviously, something is going wrong. Perhaps it’s your settings, or something else.

    Could you give me access to your backend? That way I can check if you configured it correctly.

    Please send me an e-mail using the contact form on my site: daan.dev/contact

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi @missfrosty1,

    I’ve taken a look at the stylesheet generated by CAOS for Webfonts, and everything seems to be all right there. The fonts have been downloaded to the cache folder and the stylesheet is generated correctly.

    So, something else is going on. Because fonts.css isn’t visible anywhere in your frontend’s source code I assume something is going wrong in either your cache, or in your theme.

    So, on top of access to your backend, I’d like access to your server as well. ??

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi @missfrosty1,

    Another plugin was causing CAOS for Webfonts not to work. You’re still getting the error now in Pagespeed Insights, but that’s due to this file:

    fontawesome-webfont.woff2?v=4.4.0

    This file isn’t created by CAOS for Webfonts, but another plugin. So you should consider loading this file locally as well (and adjusting the font-display option for this file).

    Hope it helps!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Ensure text remains visible error – forever’ is closed to new replies.