Adobe Typekit Font Not Displaying

Support
#1

Hi,

I’ve got a problem with Century Gothic font not loading on the frontend via Adobe Typekit. I can see someone has reported this already and you have issued a bugfix in the latest version but the problem still persists.

The Cornerstone preview seems to load the font but only in the document that you’re currently editing. For example, Home page will render the font but Headers and Footers won’t. Then switch to a Header and it loads the font but the Home page doesn’t.

The font is not loading on the front end at all.

Staging site and login in the secure note for you.

Pro 6.7.5
WP 6.8.2

#2

Hi @boomfly,

Thanks for reaching out.

The reported issue with the specific font has already been resolved, so there might be another reason for the problem you’re experiencing. I’ve applied the Century Gothic font to the Address section, and it is rendering correctly on my end.

If you’re still facing the same issue, please first verify that the correct font is selected. If the font is already selected and the issue persists, kindly share a screenshot of the section where the font is set but not rendering properly.

Thanks,

#3

Hi @tristup,

Thanks for your response. The font should be Century Gothic throughout the entire site so all text and headings, everything should be Century Gothic.

All elements are using the Body/Headings palette preset and selecting this is showing correctly in Cornerstone but incorrectly on the frontend. If you switch an element to the Century Gothic font directly i.e. not a palette preset, it then displays incorrectly in Cornerstone but correctly on the frontend.

#4

Hi @boomfly,

I have created a new Global Font and changed it to a different font family, and it worked except for the Century Gothic as you described here. I will inform our development team of this for further investigation.

Thanks

#6

We’ll release a fix for the scenarios you brought up. Have a great day.

1 Like
#7

Thanks Charlie, have a great day.

#8

You are most welcome, @boomfly.