Autodetect failing

Hi Jason,

Thanks for your message.

I’ll have to do some further testing with Divi. I’m not sure why this doesn’t work.

I’ll keep you posted!

Thank you.

Hi jason,

This support ticket contains the steps to rollback.

Hi again Jason,

I just wanted to let you know that I just tested OMGF with Divi and made a small adjustment, which made it succesfully detect Divi’s Google Fonts. v4.2.1 contains the fix.

Let me know how it goes!

Looks like it’s working great!

Thanks for the update!

• This reply was modified 4 years, 1 month ago by Jason R Weed.

Great to hear! Thanks for your reply!

Hi Daan,

having a similar issue with a Divi site – OMGF is auto detecting my primary Google font used across the site (‘Hind’) along with the default ‘Open Sans’, but not ‘Monteserrat’ which is a third Google font I use for headings on some pages. Anything I can do to fix it?

Thanks

Marc

Hi @wildambience,

Could you point out to me how you’ve configured Divi to use the third font (MontSerrat)?

I’ll try to replicate the issue locally and see what we can do about it.

Sure, when using a Divi module, in the text settings, I used the dropdown menu to select the font. For example, in my case, I use Montserrat on some pages for a H1 or H2 heading, so I just go into the settings of the text module, select ‘Heading Text’ and that gives me the option of which font I want to use for H1, H2 etc

Hi again @wildambience,

I created a page on my local environment, and set a header text using the steps you provided. OMGF both Free and Pro detected the extra font successfully. Here’s a screenshot: https://imgur.com/a/k8mubj5

Have you tried setting the Optimization Mode to Automatic? Since you mention you only use this font on some pages, OMGF will automatically take care of any fonts found throughout your site. When new fonts are first encountered, pageload might take a second longer, but once the fonts are downloaded and the stylesheet is generated, it will immediately serve the stylesheet from that point on.

Hi Daan,

I rolled back the plugin to a version 3.xxx and it worked fine. Just updated to the latest version again and still had the same issue.

I deactivated WP Rocket & cleared cache in case that was an issue, and switched the Optimization mode to ‘Automatic’ and navigated to a few pages with the ‘Montserrat’ font on them eg. https://wildambience.com/wildlife-sounds/australian-boobook , as well as adding the string ?omgf_optimize=2931f to the url. But still only picking up ‘Opens Sans’ & ‘Hind’.

However, I then discovered the Autoptimize plugin had the setting ‘Remove Google Fonts’ selected (it was set like this previously for some reason and worked ok with the old version of OMGF) and once I switched this back to the default ‘Leave As Is’ setting I think this has fixed the issue. I had to refresh the OMGF setting page a few times but after about the third refresh it has picked up Montserrat font. All good to go now! Thanks for your help Daan. It might be worth noting this issue for other users who use the Autoptimize plugin.

That’s very useful info, @wildambience. Thanks!

Yes, I can imagine that recent changes make OMGF run later than Autoptimize, whereas before it would run before Autoptimize and pick up the fonts anyway.

I’ll see if and what I can do about it!