Critical errors in latest version

1. It’s correct that the ‘Generate Stylesheet’ page has been removed in favor of Auto Detect running fully automatic now. A list to give more control over the detected fonts will be re-introduced soon.
2. Interesting. Since the detection mechanism hasn’t changed. Could you do something for me?
– Empty OMGF’s cache directory,
– Open a new browser tab, press F12 and open the network tab,
– Then visit your website’s frontend in that same browser tab,
– You’ll see a list of requests being generated. In there should be a request to /omgf/v1/download/css. Please copy and paste that request here.

That’ll give me the info I need to debug this issue.

Hello,

my optimization notice still lies there and seems to do nothing.
https://imgur.com/a/58nO0vJ
Moreover, I only see basic and advanced setting but do not see the main configuration page. Is there something wrong that I’m doing?

I tried clearing all the cache to no avail.
I am using Extra theme and Sg Optimizer as well as Cloudflare

Thank you!

Hi @cyberpunk627,

What do you mean ‘it seems to do nothing’? When you click the link, nothing happens at all? No loading screen, nothing?

It’s correct that the ‘Generate Stylesheet’ page has been removed in favor of Auto Detect running fully automatic now. A list to give more control over the detected fonts will be re-introduced soon.

I found out that using the new API will break the thing:

wp_register_style( ‘google-fonts’, ‘https://fonts.googleapis.com/css2?family=Gothic+A1:wght@100;400&display=swap’, false );

If you use the old one, it works:

wp_register_style( ‘google-fonts’, ‘https://fonts.googleapis.com/css?family=Gothic+A1:100,400&display=swap’, false );

@daanvandenbergh

It’s correct that the ‘Generate Stylesheet’ page has been removed in favor of Auto Detect running fully automatic now. A list to give more control over the detected fonts will be re-introduced soon.

Please, the auto deteciton never worked. So we need the manual one back. No font files is generated and nor any stylesheet.

I failed to mention (although it’s mentioned in the changelog): the Install Custom Fonts feature will be re-introduced soon as a separate add-on. It was the least popular feature of OMGF, that’s why I’m going to offer it separately to those that use it. Which apparently is you, @alriksson ??

@slowhandasg, CSS2 support will be added soon.

I was having errors due to “use relative paths” option resulting in “nested” paths, thus giving a 404 error of course.
A lot of tinkering with the cache, omgf empty cache and optimise again, seemed to do the trick somehow: I got the usual fonts back and it seems to be working since no calls to Google are being made.
Probably something very specific with my setup.
It would be nice now to understand how comes that so many fonts are being used by my website, and to reduce them to the minimum possible to further optimise…I always sticked to the default font but it seems that a real lot are being intercepted by your plugin.
Thank you for your great work!

It would be nice now to understand how comes that so many fonts are being used by my website, and to reduce them to the minimum possible to further optimise…I always sticked to the default font but it seems that a real lot are being intercepted by your plugin.

If you like you can contact me, so I can take a closer look at your site to see what we can do to tweak OMGF further.

It’s nice to know that you managed to make it work. Granted that the auto detect running in the background could use some UX improvements. I’ll see what I can do to clarify the process to the user.

I reverted OMGF plugin to version 3.8.2 and now all problems with newer version of the plugin is fully resolved.

I plan to stay at this version level until the author can produce a stable and error-free version to install.

With all due respect I would think that these releases would be tested better before pushing them out to users.

I failed to mention (although it’s mentioned in the changelog): the Install Custom Fonts feature will be re-introduced soon as a separate add-on. It was the least popular feature of OMGF, that’s why I’m going to offer it separately to those that use it. Which apparently is you.

Ok meaning that I need these two plugins to make ti work or just the new plugin?
Why not keep it in the main plugin with a settings of toggle on and off features? And then have it disabled by default? Just suggesting an easier UI from a user prospective.

I reverted to version 3.8.2 to fix it, the autodetect on the new version doesn’t do anything.

Keeping my downgraded version on the production site. Just tested on staging to see if the v4 stil works but it don’t if you need to use manua font detection or generate stylesheet.

Sorry, but feels like. => What the plugin do right now without forcing to purchase pro is to disable google fonts. Not really any use for that if you don’t want to use system fonts. But the whole idea with the plugin is to host google fonts locally.

Similar issue to cyberpunks627: when using relative paths, part of the path is duplicated: …/wp-content/uploads/omgf/hyd-google-fonts/wp-content/uploads/omgf/hyd-google-fonts/font.woff2
when not using relative path it works.

Hi @lhotc,

Thanks for the input. I’ll look into it.

@ the others,

I’m looking into the auto detect failure, which a lot of you seem to be experiencing. v4 passed all my automated and manual tests before release. Meanwhile, please stay on v3, if that serves your purpose better.