Navigation
Archive / Font Awesome's Cross-Origin Resource Sharing issue
This is archived content. Visit our new forum.
  • Author
    Posts
  • February 22, 2016 at 8:06 am #806782

    japsteven23
    Participant

    Hi there,

    After the recent update, my font awesome icons disappear on the front end pages, but works fine while editing in Cornerstone. When I load my page http://www.stevenjap.com/, the log shows these errors: (as seen in attached)

    Font from origin 'http://fonts.googleapis.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.stevenjap.com' is therefore not allowed access. The response had HTTP status code 404.
Failed to load resource: the server responded with a status of 404 (Not Found)

    And when I checked the link associated with the error, it returns with 404 error.

    I’ve followed the instructions to edit the .htaccess from
    https://community.theme.co/kb/solutions-to-potential-setup-issues-font-awesome/ and
    https://community.theme.co/forums/topic/fontawesome-icons-no-longer-displaying/
    Also cleared all the caches (W3 Total Cache and Cloudflare), but no result.

    Please let me know if I miss out anything. Thanks!

    February 22, 2016 at 9:07 am #806863

    Thai
    Moderator

    Hi There,

    In this case, would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

    – Link login to your site
    – WordPress Admin username / Password
    – FTP Account

    Don’t forget to select Set as a private reply. This ensures your information is only visible to our staff.

    Thanks.

    February 22, 2016 at 10:20 am #806994

    japsteven23
    Participant
    This reply has been marked as private.
    February 22, 2016 at 11:06 am #807060

    japsteven23
    Participant

    Hi there,

    I followed the guide here: http://www.bloggingspell.com/w3-total-cache-cloudflare/ and somehow managed to fix the issue by disabling minify on my W3 Total Cache.

    I suspect it clashed with Cloudflare’s minify and causes the error in connecting with Font Awesome. Do you think that would be the case?

    February 22, 2016 at 12:20 pm #807185

    Rupok
    Member

    Hi there,

    Thanks for updating. Sometimes Cloudflare and other CDN and caching plugin minify the resources too much (depends on the settings) that might create the issue.

    Cheers!

  • Author
    Posts