Fontawesome icons

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter cswilsn2k

    (@cswilsn2k)

    I did notice some errors in my apache error log as well

    [Tue Sep 12 02:32:05.370113 2017] [core:error] [pid 3976:tid 140686611363584] [client 107.77.199.78:26152] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace., referer: https://static.netexconsult.com/cache/abtf/proxy/29/0f/06/290f061df289ebc0a8c5c0598e288dfb.css

    Plugin Author optimalisatie

    (@optimalisatie)

    Hi cswilsn2k,

    The proxy URL in the error log is a static file URL. If it redirects then the cause is likely to be found in the web server configuration or potentially a (security) plugin that modifies .htaccess (Mod Rewrite).

    Regarding Font Awesome, when a CSS file contains relative links (to fonts or images) then they would break when the CSS is loaded from the proxy location. To solve the issue it would be possible to place the Font Awesome CSS locally and convert the relative paths to absolute paths within the WordPress installation or on a custom CDN.

    We usually place Font Awesome in a conditional Critical CSS entry with the option “Prepend to any” with just the specific fonts that are used. You could save up to 80% of the CSS that way.

    The option Prepend to any causes the font CSS to be included before other Critical CSS on a page so that rendering of the critical CSS that uses the fonts is smooth.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fontawesome icons’ is closed to new replies.