Fox Lee

Felix, the solution given above (turn off “Generate Critical CSS in the Background”) worked for me. It doesn’t change the weird character generation, but it does stop the erroneously generated html from ever being visible, so in practical terms it’s a fine solution.

Ah, I see, I’ve read the pinned 4.1 announcement and I understand what’s going on there now. Nevermind! In any case, it seems that disabling the background generation prevents the issue due to preventing the flash in general, so that’s good enough for practical purposes. Thanks!

Thanks for your help. I wonder why I have an outdated version when I have auto-update turned on, and why WordPress isn’t offering me the update either? I’d hope that would prevent exactly this kind of issue :\

Could you link me to that newer version? (Or just for the project’s GitHub page I guess, I’m sure I can find it myself from there).

Apologies for not replying sooner, I missed the notification for your message. On the bright side, I think you got it! I’m now seeing the correct font render on all of the available settings.

Thanks again for your work. Your support for this plugin is always first rate.

Installed, but I’m afraid I’m not seeing any difference on my sandbox site.

It’s active on the example page https://sandbox2.gongserver.com.au/test-post-5/ if you want to check it out.

I appreciate your prompt reply. Do let me know if there’s any further info I can provide that might be useful ??

Can’t you edit this to avoid generating a faulty request though? I can use a workaround just fine, but that’s hard to communicate to a client when I hand the site off. If the option is there they will expect it to work.

Upon further inspection, the cache clearing did not help, it was simply that I had turned Autoptimize back on and its Google Font handling was changing the requests into something valid. If I turn it off, the error returns.

(Apologies for the new reply—I attempted to edit my previous post, but apparently I can’t make edits right now.)

EDIT: I’ve now discovered that I can work around it by specifying the font weight, rather than letting it default. So, it may be an issue with calling all versions of the font, rather than specific weights?

• This reply was modified 4 years, 6 months ago by Fox Lee.

Problem… possibly?… solved? I encountered this discussion of the same error unrelated to Getwid:

https://docs.layerswp.com/forums/question/getting-400-errors-for-google-fonts/

Upon clearing my caching through cPanel (I had no caching active within WordPress) I’m not getting the error any more. The fonts still appear to not be loading on some pages, but since I’m no longer getting the error I suspect this may also be caching-related somehow.

Nevermind, it was my fault! I had some code that was messing with it, but I didn’t realise it because that code was supposed to be disabled. Ugh, I hate when that happens -_-;

Thanks for your help, and sorry for wasting your time there!

Hi @qtwrk , I was just trying to suggest an avenue for investigating this problem, not asking for help myself.

A client came to me with this same issue today, and after some trial and error I found it that the site was generating mixed-content requests. (So the browser was blocking the lazy load script, among others.)

As to why LSC would request these files over http, and why it would only happen for logged-in users, I’m still trying to work out. The site URL and address are set correctly to https, so there’s clearly something else at work.

Thanks @dimned, I really appreciate the quick responses and active support yall provide. It lets me feel much more confident about using this plugin and recommending it to clients!

You’re very welcome @spression! I’m glad it wasn’t too late to be of use. How interesting that the problem would mirror itself between our sites. Hopefully this will help the team pin down exactly what’s going on between those two blocks ??

Quite a late reply, but in case it’s still useful: when I got this error with section blocks, it appeared to be connected to disabling the Image Hotspot block. (I’ve shared this with the team in another thread.)

Of course your problem might be something different! But, if you have also disabled some blocks, that might be a worth looking into at least.