Typekit fonts not being applied

Hi all.

Fresh install of Pro, with typekit font added through header/footer builder (not the typekit extension.) Filson Soft (the font i’m trying to use) shows up in the Templates/Fonts section, but doesn’t get applied anywhere on the site. Font-family is being applied, but it’s ignoring filson-soft:

Dev site is: http://provenperformance.223.165.76.42.sth.nz/

Font that is meant to be applied for reference: https://typekit.com/fonts/filson-soft

Any ideas why this might be?

Have you tried turning off the Fonts Manager in theme options then back on? Usually that is what fixes it for a lot of people in the group :slight_smile:

2 Likes

Yeah, multiple times. With it disabled my fonts are all default Lato.
With it enabled, it says it’s applying the “Heading” template, but the font is acutally just a default system sans-serif.

Hello There,

Thanks for updating in! Are you sure that you have added the KIT ID you have assigned to this url: http://provenperformance.223.165.76.42.sth.nz/

Please kindly edit your KIT settings and make sure that the domain is assigned to that ID.

Please let us know how it goes.

Yeah, thats all fine, otherwise it wouldn’t be telling me that Filson Soft is an option. Here are some screenshots of the typekit settings to prove that it is set up correctly:

(Note: I had to strip image tags as apparently i’m only allowed to add one image per post.)

tco-forum-uploads.s3.amazonaws.com/original/2X/d/d8547166a98dedb6e6990ff1a9af1bffd410d75a.png

tco-forum-uploads.s3.amazonaws.com/original/2X/5/585c9dc6394508ed5a06f03731a55f487139d6cc.png

tco-forum-uploads.s3.amazonaws.com/original/2X/3/3bbd03ba9e245a5c888aa8ede3301aad60764cea.png

You’ll note that the font appears correctly in the header builder:

tco-forum-uploads.s3.amazonaws.com/original/2X/a/a16f3a38be90f4510965a74baa58b5aee9a2448e.jpg

But not when viewing the live page:

tco-forum-uploads.s3.amazonaws.com/original/2X/2/263d186521c70f0386125741a7f362abe6da701a.jpg

Hey there,

Sorry for the confusion. You will actually need to use the X Typekit extension. I’ve enabled it and it works now. Not sure if this is intentional or is a bug. I’ll forward this to our development team.

Thanks.

Hey @liquidedge,

I’ve installed a release candidate on your site for the maintenance release we plan on pushing out today. Take a look at the site and let me know if you see anything outstanding. You can now remove the Typekit extension as that functionality is built into Pro.

Great, thanks @alexander and @christianynion. All appears to be working finenow.

You’re welcome.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.