I just uploaded a new video showing how to host Google fonts locally on a WordPress site using two different methods. First, I demonstrate how to do it manually using a custom WordPress theme. Then, I show off a new plugin called Yabe Webfont (thanks @suabahasa!), which greatly simplifies the process regardless of whether you are using a Page Builder or coding your theme by hand.
One quick question. Do you know the difference between the free Yabe plugin and the pro version? It looks like there is no difference but it’s a way for people to support the development of it voluntarily.
In trying to diagnose some slow loading local fonts on a client site (you have to refresh the site after it initially loads sometimes to get the fonts to show), I noticed that the design panel is writing an absolute path to my fonts.css file into the theme.css rather than a relative path.
I went through @adamslowe’s YouTube tutorail in the process of troubleshooting the loading issue and ran across this. Maybe I’m missing something in the prefrences in PG somewhere.
Anyone have any ideas? Thanks!
**Also, a quick note. Changing this to a relative path up on the live site doesn’t seem to make a difference so I’m starting to think that the slow font loading it’s experiencing has something to do with the Azure cloud hosting and the caching the client has.
Hi @matjaz! Thanks for the reply, I really appreicate it.
Unforunately it’s the same behaivor with the latest version (7.72). Since this site is already live, and has been for the last 10 months, I’ve just been editing the import link in the theme.css file to a relative link after Pinegrow. It’s not the end of the world, but something I have to remember when I do any edits to the site via PG.
