• Resolved oscarmondo

    (@oscarmondo)


    The plugin has worked fine for a long time but as of 6/5/17 I’m getting console 404 errors and FontAwesome is no longer loading correctly. This is a pretty big issue as we have multiple client sites now showing broken icons. Screenshot below:

    console errors

    EDIT: The screenshot is tiny so here’s the text.

    (index):1 GET https://www.lakebomoseenlodge.com/wp-content/uploads/2017/fonts/fontawesome-webfont.woff?v=4.7.0 
    (index):1 GET https://www.lakebomoseenlodge.com/wp-content/uploads/2017/fonts/fontawesome-webfont.ttf?v=4.7.0 404 (Not Found)
    • This topic was modified 7 years, 9 months ago by oscarmondo.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mickey Kay

    (@mcguive7)

    I’m unclear on where this URL is even coming from. Better Font Awesome does not interact with your uploads folder at all, so I think this URL is being generated elsewhere. Are you somehow customizing and/or hooking into this plugin? The only place that fonts/fontawesome-webfont.* appears is in the Font Awesome default CSS file: https://cdn.jsdelivr.net/fontawesome/4.7.0/css/font-awesome.css?ver=4.7.0

    All I can think of is that maybe you are using a plugin that concatenates/modifies CSS. For the above URL to be generated, I’d think you would need to be serving your HTML from within uploads/2017, and inlining your CSS. Can you please confirm a URL where I can see this? Also, are there other plugins you have enabled that modify CSS in these ways? I’ve verified that this version is working just fine for me locally, so I’d love to get to the bottom of what’s different on your setup. Thanks for your patience, and apologies for the trouble. Let’s get this resolved!

    Thread Starter oscarmondo

    (@oscarmondo)

    I am using a minification plugin, that’s probably it. So the CSS file is looking for a particular file path, but that path is being changed by the minification, is that the idea?

    Plugin Author Mickey Kay

    (@mcguive7)

    Exactly. This is a common issue with minification plugins. Basically, the CSS specifies a path like the following for fonts:

    url('../fonts/font-awesome.ttf')

    This says basically, go up one directory and look for the fonts directory. Unfortunately this will fail with minification, as you’re seeing, but fortunately this is why most minification plugins allow you to exclude specific resources. Thanks for confirming this is the issue!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Console 404 errors, FontAwesome not loading’ is closed to new replies.