Lambda theme problem

  • Resolved farisr

    (@farisr)


    4 years, 6 months ago

    Firstly, Thank you for creating what has to be the most useful, must-install plugin of them all.

    I do have a minor problem though and could do with some help please.

    I use the Oxygenna Lambda multipurpose theme on a lot of sites.
    Unfortunately, in order to disable its built-in Google font loader, I have to also install Autoptimize because the OMGF disable option doesn’t work with this theme for whatever reason.

    There’s nothing wrong with Autoptimize except that it doesn’t have as much functionality as more comprehensive caching plugins. In addition, the author seems to recommend the use of other caching plugins along with Autoptimize, while at the same time saying you should not use two caching plugins at once. Very confusing. Anyway, it doesn’t support Redis cache, and that’s a problem for me.

    As to my problems/questions:

    I noticed in the 3.6 changelog some mention of plugiins that might or might not be needed for some themes. Are we talking about stand-along plugins like Autoptimize, or custom extensions to OMGF?

    And sort of related to that, how might I go about figuring out why the Lambda theme is reluctant to allow OMGF to disable its font loading? How is it that Autoptimize manages to do so? I’m just wondering if, with some digging in the Theme files, I might be able to do away with the need for Autoptimize if I can find the right code and maybe implement a custom function?

    OR, what can I tell the Lambda developers about how OMGF disables remote loading, in case I can persuade them to change the way it is done to make it more OMGF-friendly?

    Sorry..I know this is a long post.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Are we talking about stand-along plugins like Autoptimize, or custom extensions to OMGF?

    We’re talking about add-ons to OMGF. Because not everyone benefits of OMGF being compatible with all sorts of different themes and frameworks, I chose to make OMGF extendable.

    How is it that Autoptimize manages to do so?

    An important difference between OMGF and Autoptimize is that Autoptimize manages all your CSS. That way, Autoptimize can parse the CSS and remove any mentions of @font-face resembling Google Fonts URLs, etc.

    OMGF doesn’t do that. The free version of OMGF supports themes that follow WP’s convention of enqueueing (Google Fonts’) stylesheets. It hooks into this process, removes the externally loaded stylesheet, and replaces it with its own.

    Some larger themes (usually including page builders, frameworks, etc.) can’t follow these conventions, for various reasons: e.g. previous design choices, or the conventions simply don’t meet their requirements.

    That’s why I introduced add-ons to OMGF. ??

    How might I go about figuring out why the Lambda theme is reluctant to allow OMGF to disable its font loading?

    I’ll do this for you, cause I want to extend the list of compatible themes. ?? Could you contact me, using this form? This isn’t really a support question, but more of a feature request and we can discuss it further through email. ??

    Thanks!

    Thread Starter farisr

    (@farisr)

    Will do. Thanks.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi Faris,

    I just sent you an email informing you about the release of OMGF Pro, which supports (basically) all WordPress themes. From now on the free version of OMGF will inform you about OMGF Pro, if Auto Detect couldn’t detect any fonts.

    In short, it’s faster, niftier, and awesome-er (?) than the free version of OMGF.

    You can purchase it here.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Lambda theme problem’ is closed to new replies.