OMGF (Pro) – Troubleshooting
Running into issues with OMGF or OMGF Pro? Start here.
- (Some) pages show lines of text e.g. -html5-dom-document-internal-cdata
- cURL error 60 (http_request_failed) when clicking Save & Optimize
- Font files are loaded twice
- Frontend shows system fonts if OMGF (Pro) is active
- How can I test if OMGF (Pro) is working properly?
- I can’t find the Settings screen.
- I just deployed my testing/staging site to production and now my fonts are broken
- I still see requests to my staging/testing site after publishing it to my live/production site
- I use multisite and am getting CORS errors.
- I’m getting Mixed Content Warnings in my Console when OMGF is enabled
- OMGF (Pro) doesn’t detect/download any fonts.
- OMGF wasn’t able to Process all Google Fonts on my site
- OMGF’s API (wp-json/omgf/v1/download) returns a 406 (Handle not provided) error.
- Page source still contains a <link rel=”dns-prefetch” /> element pointing to fonts.googleapis.com.
- Refused to Apply Style because its MIME type (text/html) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
- Styling (CSS) breaks when OMGF Pro is enabled
- The stylesheet generated by OMGF (Pro) isn’t loaded.
- The wrong fonts are shown when OMGF (Pro) is active
- URL to generated stylesheet/downloaded fonts returns a 404 (Not Found) error.
- Using Debug Mode in OMGF (Pro)
- “OMGF couldn’t find [font name]”