Old Version Was Flawless, New Version Won’t Detect Fonts.

  • Looking through the support threads I can’t help but feel I’m not alone in thinking that the complete overhaul of the new OMGF has ruined a great thing.

    I support the developer, they clearly put a lot of thought and work into their revamp, but the simplicity of the user experience is gone and… the new version doesn’t even detect fonts anymore.

    My Project Stats:
    WordPress 5.7
    Oxygen Page Builder 3.7
    OMGF Free 4.3.2
    Caching Off

    Manual Detection: No detection of fonts.
    Automatic Detection: No detection of fonts.

    What am I doing? What can be done?

    Note: I could downgrade to a very old version of OMGF, but how long is that really a viable option?

    Help please.

    ADDENDUM:
    I downgraded to OMGF 3.7.0, ran a search for my font families, downloaded them and generated my stylesheet in no-time flat. I would like to enjoy the same efficiency with the newer version so as to have future-proofing peace of mind.

    Any suggestions will be great. Thank you.

Viewing 4 replies - 1 through 4 (of 4 total)

  • In the same boat.
    However, it did detect 1 time. Then not after that.
    Have turned off Full page caching too.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    @clickingclients,

    If it did detect 1 time, what changed afterwards?

    @xizor,

    Thanks for writing such a detailed support ticket.

    Yes, the OMGF v4 upgrade was a big change, and it works very different compared to v3.

    Lucky for you, v4 has been around for a while now and I’ve managed to work out most of the issues.

    I’ve learned that in most cases, it’s a security issue:
    – If your server runs on Apache, mod_security might be blocking the call to OMGF’s built-in API — and sometimes even falsely flags it as a SQL injection attack.
    – Some WordPress firewall plugins block the API call, because they add a X-Content-Type-Options: nosniff header. Sometimes switching to Automatic mode and visiting your frontend resolves this issue.

    To gain more insights into your specific situation, you can do the following:

    – Switch Optimization Mode to Automatic,
    – Open a new browser tab and press F12, to open Developer Tools,
    – Make sure the Console is visible,
    – Visit your site’s frontend.

    See if any error messages related to OMGF appear — the address of the API might be in there: yourdomain.com/wp-json/omgf/v1/

    You can also try the following:

    – Switch Optimization Mode to Manual,
    – Enter a URL of a page different of your homepage,
    – Click Save & Optimize,
    – Check if any error messages appear at the top of the screen,
    – And if not, check your PHP logs to see if any error messages related to OMGF might’ve appeared there.

    Looking forward to your response!

    Thread Starter MindCreatesMeaning

    (@xizor)

    Hello @daanvandenbergh ,

    Thank you for providing me with two methods for testing for errors.

    Neither method produced any errors that presented themselves visually in console or at the top of OMGF v4 settings page.

    I’m open to further guidance.

    Currently I have resorted to using the ‘Block Specific Plugin Updates’ Plugin to protect OMGF v3.7 from updating. I do hope to get past this though as I would much prefer to employ the latest versions of your software releases.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Ah, I just noticed you’re using Oxygen Builder. OMGF v4 isn’t compatible with OB. The fact that v3 was, is nothing more than a happy coincidence unfortunately.

    However, others have found ways to make it work combined with the Additional Fonts add-on.

    You can read more here.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Old Version Was Flawless, New Version Won’t Detect Fonts.’ is closed to new replies.