Topic Resolution: Resolved
  • Closed
  • steven wilson
    Spectator
    June 10, 2015 at 6:50 pm #18164

    I just installed the new version of evolve and none of the fontawesome icons are showing. see this screen grab:

    the url of the site is http://harmonybible.coop/

    steven wilson
    Spectator
    Posts: 22
    June 10, 2015 at 6:51 pm #18165

    screen grab doesn’t seem to have worked. it’s here

    https://www.dropbox.com/s/6epjke7v2e5ui55/Screenshot%202015-06-10%2014.49.36.jpg?dl=0

    steven wilson
    Spectator
    Posts: 22
    June 10, 2015 at 9:54 pm #18168

    FIXED:

    my site is hosted in a subdirectory on my server (which is then pointed to the domain by my domain registrar) and as such, Firefox will not display the font awesome icons since the font files are hosted in a different directory.

    ADD THIS TO .htaccess

    <IfModule mod_headers.c>
    <FilesMatch “\.(eot|font.css|otf|ttc|ttf|woff)$”>
    Header set Access-Control-Allow-Origin “*”
    </FilesMatch>
    </IfModule>

    before the ‘end wordpress’ statement. problem solved.

    steven wilson
    Spectator
    Posts: 22
    June 10, 2015 at 10:10 pm #18170

    further update: in trying to figure out why the icons were now working in Firefox and Safari but not in Chrome, I found that the font files are actually included in the theme files but they do not need to be (unless there’s something I missed). In fact, their inclusion in the theme leads to trouble if your site files are installed somewhere other than the url of the site itself.

    If you don’t have access to (or don’t know how to use) the .htaccess file, the solution is simple. You must add

    <link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">

    to the header.php file after the <head> statement. You can find this file by going to Appearance > Editor and then scrolling down to Header in the list on the right. After clicking on Header, look down a little bit in the file and add that statement after <head> and you should be ok. I’ve since returned my .htaccess file to its initial state and all seems fine.