Google Fonts not showing correctly on Pro

[Omwoods]

Hi! Using latest Pro theme and Wordpress. Adding a secure note with login details. In short, I’ve switched on and off between Font Manager (as I’ve seen adviced here) but nothing helps. I can see the website body fonts as Fira Sans on my computer because I have that font installed on my computer. But on my phone, the Google font simply won’t work no matter what I try.

I’ve added a WOFF custom font for the script in some headings and that does work on my computer and web too. Just the Google font won’t work. Can you please help? Also, I’m making a shift from working only with X to using Pro now, so maybe there’s something I’m missing that’s different between them, for the fonts to work?

Thank you!

[tristup]

Hi @Omwoods,

Thanks for reaching out.
It seems that the Fira font is not added yet through the Font Manager, please go through how a custom font can be added from the Custom Font section of this article: https://theme.co/docs/font-manager#enabling-font-manager-in-the-theme-options
Please find the video which may help you with this:

Getting Started With Custom Fonts

Hope that helps.
Thanks

[Omwoods]

Thank you! That works, but I need to now individually choose the body font for each text element. That’s ok though. The only issue remaining is updating the body/heading fonts to Fira Sans on the footer widgets and topbar text, in a way that works elsewhere than on just my computer (because I have Fira Sans installed).

I tried adding CSS to topbar, footer… to use font-family Fira Sans (you’ll see that if you login) but it still doesn’t work.

How to accomplish a custom font for footers, widgets, topbar, blog posts, etc?

Thank you!

[ruenel]

Hello @Omwoods,

You need to assign the uploaded custom fonts to your site globally. Go to Pro > Typography > Body and Content and Pro > Typography > Headings where you must select the font.

I went ahead and select your fonts. Please double check it.

[Omwoods]

Thank you! The fonts are working well now

[matt]

Glad to hear that, @Omwoods!