Advanced Settings

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.

Fonts Cache Directory

By default, OMGF uses WordPress’ uploads directory. OMGF Pro adds multisite support, and stores generated files separately for each site in the corresponding uploads-folder, e.g. /wp-content/uploads/sites/0 )

Whitelabel Stylesheets (Only available in OMGF Pro)

By default, all stylesheets generated by OMGF are minified, unless the SCRIPT_DEBUG constant is defined in wp-config.php . Enabling this option will remove all branding and comments from these stylesheets, further decreasing their size.

Developer Mode (Pro — default: off)

This option makes sure (domain) relative URLs are used in stylesheets to ease migration from one domain to another. This is especially useful in (Development) > Testing > Acceptance > Production streets, hence the name.

Modify 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 will be automatically disabled and locked if Developer Mode is enabled.

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 https://my.cdn.com/wp-content/uploads/omgf .

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 /app 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 /app/attachments/omgf .

Legacy Browser Compatibility

Enabling this option makes OMGF use an older User Agent to fetch the fonts, so they’re compatible on e.g. systems running Windows 7.

Divi/Elementor Compatibility (default: on)

Because Elementor and Divi don’t use unique identifiers for each Google Fonts stylesheet they generate, OMGF contains specific compatibility fixes for these plugins. This option is enabled by default and does no harm to websites not running Divi and/or Elementor.

With this option enabled, the length of the Google Fonts API request is used as a unique identifier to make a difference between each Google Fonts stylesheet requested by Divi/Elementor.

If at a certain point you feel OMGF (Pro) is generating too many stylesheets, then this means your site is using that many variations. This is bad for performance. To fix this, do the following:

  1. Configure your homepage to include the fonts you want to use throughout your website, 
  2. Empty OMGF’s cache directory, 
  3. Disable Divi/Elementor compatibility, 
  4. Hit Save & Optimize.

The stylesheet used on your homepage will now be used throughout your entire website, regardless of which fonts are configured on other pages.

Auto-configure Used Subsets

When this option is enabled, OMGF (Pro) will attempt to auto-detect which subsets are used on the site and match them with the subsets actually available in the detected Google Fonts. It will change the Used Subset(s) option mentioned below accordingly.

Used Subset(s) (default: Latin, Latin Extended)

Since the Google Fonts API dropped support for subset filtering, I decided to bring it back, because it brings enormous bloat to your Google Fonts stylesheets. Properly leveraging this option can reduce the size of your Google Fonts CSS stylesheets by ~80%!

This option isn’t optional and you are required to specify which subset(s) your site/language uses. The default value will suffice for America, Europe and parts of Africa. If your website is e.g. Syrian, Hebrew and Latin is required to display your fonts correctly.

Disable Quick Access Menu

When this option is enabled, the top adminbar menu will be removed. When issues are found, the menu will still appear to notify you and it will disappear again once the issues are resolved.

Debug Mode (default: off)

Only enable this option when asked by me (Daan, i.e. the developer of the plugin) or if you know what you’re doing. For more information about debugging in OMGF (Pro), click here.

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.