Changing the location of custom fonts

I’m posting this in case anyone else has this problem, as it has caught me out a few times now.

If you ever want to change the location of your custom font files, for example, if you’ve moved your site to a new domain, you would begin by changing the URL of the font file as described here: https://forum.tagdiv.com/using-custom-fonts/

…however, you MUST then come back to the Theme Fonts panel and click Save Settings. You MUST do this even if you haven’t changed the font on any part of the theme. Otherwise the new location will not be used.

It would be great if the developers could add a fix so that this extra step is not necessary.

Actually, it sometimes doesn’t work.

I change the “Custom font files” on this page: http://wow-staging.nucreativetesting.co.uk/wp/wp-admin/admin.php?page=td_theme_panel&td_page=td_view_custom_fonts

…and then “SAVE SETTINGS” on this page: http://wow-staging.nucreativetesting.co.uk/wp/wp-admin/admin.php?page=td_theme_panel

…and then empty the cache, and reload the page. But the theme still tries to load the fonts from the old location.

I think the theme is caching the old values. How can I fix this?

Hi Bogdan,

We don’t have a caching plugin or a CDN. We do have Jetpack, but we don’t have Photon switched on.

And besides, the CSS for the fonts gets output in the html file itself as a <style> tag – this is just below a comment: <!– Header style compiled by theme –>

So it’s not an external CSS file, and it shouldn’t be cached.

I have also cleared my browser cache, but that hasn’t fixed it.

Hi Bogdan. We have been through this before on the same site: https://forum.tagdiv.com/topic/cant-remove-myfonts-com-preview-bar-from-top-of-window/

I can give you login information to fix the problem yourselves again, but I would prefer to have a solution I can implement myself, in case it happens again.

The last time we went through this by email, the solution was apparently to “clear the font buffer” – although I don’t think there is an option to do this through the UI, so it might just be something that the devs do whenever this happens. Do you know what this means, and can we do it ourselves?

Ok, after much fiddling around, I have managed to get it to work on my own. The solution seems to be:

When you come back to wp-admin/admin.php?page=td_theme_panel, you have to open the Theme Fonts section, then also open one of the sub-sections (Header, Modules and Blocks General, etc), then click the ‘SAVE SETTINGS’ button.

I can’t verify this to be the actual cause of the fix (I don’t have time to faff about with it any longer) but it seems to have worked on this occasion.