Table of Contents
OMGF (Pro) generates and caches a stylesheet containing static URLs pointing to font files located on your server. E.g.
https://your-site-url.com/wp-content/uploads/omgf/name-of-stylesheet/name-of-font-latin.woff2
If you generated the stylesheet on your development, testing, acceptance or staging environment, and deploy it to your live (or production) environment, this stylesheet is copied along with the rest of your files.
If your staging site doesn’t allow requests from your production environment (like a good environment would) your fonts will break.
There are two ways to work around this:
Refresh the Cache
Since the stylesheets are cached, refreshing them is the most obvious solution.
Simply navigate to OMGF’s settings screen, and under the Local Fonts tab, inside the Task Manager section, click the Refresh Cache button.
Enable (D)TAP Optimization
If you deploy changes from testing/acceptance to production often, continuously having to think about refreshing OMGF’s cache will become a tiresome job. Instead, you can enable the Optimize for (D)TAP option (available in OMGF Pro) to take care of this for you each time you deploy a new version of your website.