FontAwesome icons only partially working

[fastpitchpower]

Hello, I’m experiencing an issue on my blog page http://www.fastpitchpower.com/blog

I tried to change the file icon that displays next to the post title and I’m getting an empty square in Chrome and Firefox. I noticed in the changelog and other support topics that FontAwesome has been split into 3 subsets and we now need to reference -b, -s, or -o, but I don’t understand where to put that reference in my case. I added the following CSS:

.format-standard .entry-title::before {
content: “\f433”;
}

…and it displayed the correct icon briefly in the customizer, but not on the live site. The default file icon (f15c) does work.

I cleared my cache and I am not using a caching plugin.

Thanks in advance for your assistance.

[friech]

Hi Carly,

Thank you for writing in, would you mind letting us know which icon you’re trying to use? I tested a few icons from here and they all work, please look for your icon in there and copy the CSS rule of it and replace it with what you have.

I see that you loaded the old fontAwesome 4.7 on your site, so the CSS rule provided on that site should work.

Hope it helps,
Cheers!

[fastpitchpower]

Thanks for the reply. As my CSS shows I am trying to use f433 which is listed as part of the free set here on the fontAwesome site. Am I only able to choose from the icons on the other site you sent?

I did a fresh install of the most recent release of X the other day and didn’t do anything else to the fonts, so I didn’t realize I was using an old version of fontAwesome. Is there a way to update it?

[thai]

Hi There,

Do you have any custom code or 3rd party plugins related to this file: https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0?

Please remove it, I’ve added your custom CSS to my local installation and the icon is working fine:

If you still have this issue, pease provide us with your admin account so we can take a closer look.

Thanks.

[fastpitchpower]

That was it, looks like our instagram feed plugin was the issue. Thanks!

[nabeel]

Glad we could help.

Cheers!