• Resolved Fox Lee

    (@fox-lee)


    Hi folks,

    Lately I’m getting a console error when I use the Advanced Heading block with a custom Google Font selected:

    GET https://fonts.googleapis.com/css?family=Open+Sans+Condensed%3Anormal&ver=all
    [HTTP/2 400 Bad Request 163ms]

    I’m pretty confident it’s Getwid causing the error, as I replicated it on my sandbox site https://sandbox.gongserver.com.au/ with 2020 theme and no other plugins. (I suspect it might affect other Getwid blocks with custom Google fonts too, but I haven’t tested that.)

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Fox Lee

    (@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.

    Thread Starter Fox Lee

    (@fox-lee)

    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.
    Plugin Contributor motopress

    (@motopress)

    @fox-lee change “Font Style” option to “Inherit” while this font doesn’t have regular(400) font style https://fonts.google.com/specimen/Open+Sans+Condensed

    Thread Starter Fox Lee

    (@fox-lee)

    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.

    Plugin Support dimned

    (@dimned)

    Hi @fox-lee,
    Thanks for your reply. This will be adjusted in one of further updates.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘400 Bad request wth custom Google Fonts?’ is closed to new replies.