Heather Wilkins

Oh, I see what it’s doing. Tested it on another site. If a core version is set in the WP downgrade settings, it only shows that version available overall. This is very confusing.

https://pasteboard.co/3YvpTaRBcflP.jpg

https://pasteboard.co/stxEBlFqeT9a.jpg

We’ve updated to the most recent version and it’s working for us. Thank you!

And we’ve seen three reports of this as well.

We’ve replicated this issue on multiple websites with version 1.24.1. The backup will complete but the plugin update seems to stall and/or fail.

Hi Adam,

Thanks for your quick reply!

Our concern isn’t specifically the ordering in the UA and GA4 code in the second portion of the code. Our concern is the first piece of the code.

When you have a UA and GA4 tag both enabled through Site Kit, the beginning of the code looks like this:

<script type='text/javascript' src='https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXXX-1' id='google_gtagjs-js' async></script>

It uses the UA ID in the gtag script.

When you disable the UA tag in the plugin and with only a GA4 tag enabled in the plugin you get this:

<script type='text/javascript' src='https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX' id='google_gtagjs-js' async></script>

We assume that the script may keep working after UA is sunset, however, it seems like using the property’s G tag/ID there may be more futureproof?

We may be saying the same thing basically and you may already be planning this as a part of the transition in the coming months but I wanted to make sure I was being as clear as possible.

So, what we’d hope to see would be this:

<script type='text/javascript' src='https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX' id='google_gtagjs-js' async></script>
<script type='text/javascript' id='google_gtagjs-js-after'>
window.dataLayer = window.dataLayer || [];function gtag(){dataLayer.push(arguments);}
gtag('set', 'linker', {"domains":["xxxxxx.com"]} );
gtag("js", new Date());
gtag("set", "developer_id.dZTNiMT", true);
gtag("config", "UA-XXXXXXXXX-1", {"anonymize_ip":true});
gtag("config", "G-XXXXXXXXXX");
</script>

Thank you for your time!

• This reply was modified 2 years, 1 month ago by Heather Wilkins.

Yes, if a user doesn’t want Google fonts on their site, since there is the custom font option, they could use that.

Or you could add some system fonts or web-safe fonts to the font options. That would be a useful alternative for users who don’t want a custom font or Google fonts.

Hi Bethany,

I’ve figured it out. I was brainstorming what might cause the fonts to load across the site when they shouldn’t be and thought the WP Rocket Google font optimization feature might be the issue and it turns out it is.

Here’s the Network panel listing all fonts loading on the above link with Web Stories and the WP Rocket Optimize Google Fonts feature enabled. You can see Roboto and Work Sans are being loaded.

-> https://pasteboard.co/DcEPnkqyDDWk.jpg

Now here’s when I use the WP Rocket “kill switch” ?nowprocket. You can see that it’s no longer loading the Roboto or Work Sans fonts. (It’s loading Sans Display but that seems to be from a different source.)

-> https://pasteboard.co/zSuuok8Va8yb.jpg

And then finally, I disabled the WP Rocket Google font optimization using a plugin they have, and we can see that Roboto is not loading and once again, only Sans Display.

-> https://pasteboard.co/uShd3fLeV4Bt.jpg

So, it appears to be an issue of the WP Rocket Optimize Google Fonts feature, so I will contact their support.

It would still be nice to have a snippet or setting in the plugin to disable Google font loading totally, even on the Web Stories themselves.

Best,
Heather

I tested disabling the Web Stories plugin only and the Roboto fonts (which are being used by the Web Stories plugin templates) stopped loading on this page. That seems fairly indicative to me.

For users concerned about Google fonts loading related to the recent German GDRP issues and Google fonts ruling, it might not be a bad option to have a snippet to disable Google font loading for users anyway as a “quick fix”. Some users of the plugin have 500 or more Web Stories. Forcing them to set a custom font in the plugin and then edit every one of the Web Stories slide-by-slide to change the font settings seems like not a great solution.

So, it would be very nice if you could provide a snippet to drop in that would disable Google fonts from the plugin site-wide. Our client doesn’t want the Google fonts on the Web Stories currently either.