[flexnettsParticipant]

Hi,

I seem to have issues with just Google Chrome rendering the quicksand font (www.flexnet-ts.com) in particular the menu and headings.

All fine in IE and Firefox, just Chrome, has anyone else had these issues?

Thanks in advance!

Carl.

[ChristopherModerator]

Hi there,

Would you please follow the troubleshoot guide for font embedding HERE.

Specially see if adding proper types into HTACCESS file will do the trick for you.

Thank you.

[kristenowlParticipant]

I am having the same exact problem as flexnetts. The really strange thing is that quicksand WAS displaying just fine until a couple days ago. I also noticed a body font not working right (lato), and I corrected that issue by selecting a different font and then going back to lato. This isn’t fixing it for quicksand. Any ideas?

[ChristopherModerator]

Hi there,

Because this requires a template change, I’d advise that you setup a child theme. This allows you to make code changes that won’t be overwritten when an X update is released. After your child theme is setup, please review how we recommend making template changes in Customization Best Practices.

Please add this in child theme’s style.css file :

@import url(https://fonts.googleapis.com/css?family=Quicksand);
body{
font-family: 'Quicksand', sans-serif;
}

Hope that helps.

[Author]

Posts