Some issues after & before 3.0 update

  • Resolved dnplx

    (@dnplx)


    6 years, 2 months ago

    First of all, thank you for making such a great plugin. In addition to the title, I would like to give some general feedback about plugin.

    * When trying to add fonts one by one with search, it constantly deletes the previous font from list. There was no such problem before version 3.0.

    * Can’t find the fonts when you separated by commas on search.

    * So why do I use this when there is an automatic font finding function? Because the automatic font finding method does not show the versions of the fonts it finds, such as latin-ext which is very important on some languages.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    Hi!

    Thanks for the feedback.

    • Correct, I’ve changed that. Finding fonts one by one doesn’t work anymore. All the jQuery was very bug sensitive. So I decided for a more constructive solution and this was a ‘feature’ that needed to be sacrificed.
    • What’s your search query? Comma-separated search works fine on my end.
    • To be precise: The auto detect function detects the subsets your theme is using. If you insist on expanding them, sure. You should be able to do that by using search. Just know that, before you installed OMGF, your site wasn’t using other subsets than the ones that’re detected. 🙂
    Ann

    (@akg-free)

    6 years, 2 months ago

    Hi,
    similar issues here.

    BEFORE 3.0 OMGF on 2 projects:
    no external fonts embedded (1x divi deactivated, 1x removed from core).
    Everything worked.

    NOW:
    On one of the projects the were both available but not embedded, no fonts in network analysis of Firefox.

    I thought maybe clearing the OMGF cache & re-integrate them would solve it. But re-integration isn’t possible.

    With deactivated embedding in divi settings nothing works.

    With activated embedding the following happens:
    Auto detect finds 1 of 2 fonts – “Open Sans” / “Crimson Text”, but not “Open Sans Condensed” / “Hind”.

    Manual search for two fonts, “Open Sans, Open Sans Condensed” or “Hind, Crimson Text” asks if “-open-sans-condensed”/”-crimson-text” is a Google Font, finds Open Sans/Hind.

    Maybe those detailed description helps?

    • This reply was modified 6 years, 2 months ago by Ann.
    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    Hi guys, could you try search again?

    I made some improvements there.

    You might’ve typed your search query like this: font name<comma><space>font name. Previously OMGF only supported: font name<comma>font name.

    I improved the search box, amongst other things, to make it more UX friendly.

    Ann

    (@akg-free)

    6 years, 2 months ago

    Hi Daan,
    yep, search works now.

    Sadly we have other trouble now:
    We’ve published another project using your plugin. We search, download fonts, generate the stylesheet.

    Control via ftp: yup, css and fonts are loaded.
    Maybe 15 to 30 minutes later the whole folder disappears. o_o
    The GTMetrix check says they’re gone, but they’re still listed in OMGFs settings.
    This happens with and without active caching plugins.

    Sadly now we’ll change to manual local fonts. :/

    • This reply was modified 6 years, 2 months ago by Ann.
    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    Search with spaces should work as well! It doesn’t with you? That’s weird…

    I still suspect it’s either a caching or a security measure. What happens when you move the cache folder outside of the cache folder?

    Ann

    (@akg-free)

    6 years, 2 months ago

    Hi Daan, nooope, sorry! Works with and without – I’ve misread it earlier, started the answer, wrote the rest later and corrected my answer asap.

    Cache outside the cache folder is an idea – I’ll try and let you know tomorrow!

    Thank you for your support & have a nice evening! 🙂

    • This reply was modified 6 years, 2 months ago by Ann.
    • This reply was modified 6 years, 2 months ago by Ann.
    Ann

    (@akg-free)

    6 years, 2 months ago

    YEAH! Child theme instead of cache folder was successful – I don’t understand why because the 1st time this happened yesterday no caches were running.

    Thank you & sorry for the chaos!

    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    Ha! No worries. 🙂

    So moving the font storage folder to somewhere else, outside of the wp-content/cache folder worked? That’s great to hear. 🙂 Happy you managed to get it resolved.

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

The topic ‘Some issues after & before 3.0 update’ is closed to new replies.