Pro 4.0.0 Beta 8: Appears Google Fonts API Changed Recently?

Beta
#1

Reposting this here due to accidentally posting in the wrong forum (new user, sorry!).

I enabled Roboto and Lato for the Headings and Body Copy fonts, respectively. Both of these come from Google Fonts. When viewing the pages live, the fonts do not display. Inspect Element reveals a GET 400 error for the Google Fonts API.

I am not a developer, however, I have run into this issue on another platform I use for work. I’m wondering if Google revised the structure of the font API URLs, hence causing an issue between the theme and the Google Fonts servers.

When I switched from Google Fonts to Adobe Fonts/Typekit as the source, I no longer had the issue :slight_smile:

#2

Thanks for bringing this up! I’ve checked with both Roboto and Lato and they’re working ok for me. Would you mind sharing a link to the site where it’s failing? I can take a look and see if I can discern why the 404 is happening for that request. Thanks!

#3

Hey @alexander, it’s that same DEV site I sent in the other topic. As I said, I resolved it by using Adobe Fonts in place of Google Fonts. If you go to the site now the 4xx error doesn’t appear.

When I tested, it worked just fine on my one computer—presumably because I have Adobe CC and those two fonts installed via Typekit—and did not work on my other, which lacks Adobe CC.

#4

Ok thanks, I think the best I can do in that case is just keep an eye out for the error. If you happen to see it again, let me know when I can check the page. I’ve not been able to find a way to get the system to create one that is malformed or doesn’t resolve to the Google Fonts API properly.

#5

Will do, @alexander! Thanks!

#6

:+1: Appreciate it!