OMGF (Pro)’s advanced settings offer ways to fine-tune its behavior and make it work with your specific configuration, e.g. when you’re using a CDN.
Do not change these settings, if you don’t know what you’re doing!
AMP handling (Only available in OMGF Pro — default: Fallback)
Decide how OMGF Pro should behave on AMP pages. Fallback makes sure that Google Fonts are loaded per AMP’s specifications, by loading them from Google’s own servers. Disable will remove the Google Fonts from Accelerated Mobile Pages altogher.
Excluded Post/Page IDs (Only available in OMGF Pro — default: empty)
In some situations you might decide to not run OMGF Pro on certain pages. Using this option, you can specify the post and page IDs of pages where OMGF Pro shouldn’t run.
Fonts Cache Directory
The folder where OMGF (Pro) stores its font files and stylesheets. In most cases this doesn’t have to be changed.
Fonts Source URL (Only available in OMGF Pro)
Use this option to modify the
src attribute of each defined
@font-face element in the generated stylesheet. When modifying this option, make sure you enter the full path to where the downloaded font files are served from.
This option makes OMGF Pro flexible enough to work with the most exotic configurations out there. Some examples:
Configure OMGF Pro to use your CDN URL
If your CDN’s URL is https://my.cdn.com and OMGF Pro’s font files are stored in /wp-content/uploads/omgf, then the value to enter here is
Configure OMGF Pro to only use the Relative Path in the stylesheet
When you’re developing a website on another server, using a different URL, it’s best to make OMGF Pro generate the stylesheet using Relative URLs. This will save you a headache when migrating the website to its production environment.
A relative path is the path defined after the domain. If your site’s staging URL is https://staging.mycooldevcompany.com and OMGF Pro’s font files are stored in /wp-content/uploads/omgf then you can configure OMGF Pro to only use relative paths while generating the stylesheet by entering the following value:
Configure OMGF Pro to serve font files from alternate paths (using e.g. Nginx/Apache rewrites, etc.)
Some security plugins (e.g. WP Hide) use obscurity to secure your WP install. This basically means making the WordPress’ folder names (e.g. wp-content, uploads, themes, etc.) unrecognizable to visitors. You can use the flexibility of the Fonts Source URL option to make OMGF Pro work with these configurations.
Let’s say your security plugin rewrites requests to
/wp-content and requests to
attachments are rewritten to
uploads and OMGF Pro stores its fonts in
/wp-content/uploads/omgf. This would mean that the path OMGF should use in the stylesheet is
Remove Settings/Files At Uninstall (default: off)
If you want to uninstall the plugin and all of it’s files and settings, check this setting and save changes, before removing the plugin.