Error downloading fonts
-
I keep getting this error in the latest version 4.2.1
OMGF encountered an error while downloading Google Fonts: http_request_failed – A valid URL was not provided.
-
Wait, I had “Hide network” checked. This is from the Console tab.
Failed to load resource: the server responded with a status of 404 ()
https://www.domain.se/pro/wp-json/omgf/v1/download/css?family=Open+Sans%3A100%2C200%2C300%2C400%2C500%2C600%2C700%2C800%2C900%2C100i%2C200i%2C300i%2C400i%2C500i%2C600i%2C700i%2C800i%2C900i&subset=latin&handle=oceanwp-google-font-open-sans&original_handle=oceanwp-google-font-open-sans&ver=5.5.1Three entries like the above.
-
This reply was modified 4 years, 5 months ago by
Argentum.
Hm, I might be on to something here. I use this setup:
The files is situated in a directory one level down, in this case /pro/
My WordPress URL: https://www.domain.se/pro
Site Address (URL): https://www.domain.se
The url of the site is rewritten with .htaccess rules.The above status 404 tries to read the url with the /pro/ in. That doesn’t work since the rewrite rule removes the pro.
The 404 url is : https://www.domain.se/pro/wp-json/omgf/v1/download/css?family=Open+Sans%3A100%2C200%2C300%2C400%2C500%2C600%2C700%2C800%2C900%2C100i%2C200i%2C300i%2C400i%2C500i%2C600i%2C700i%2C800i%2C900i&subset=latin&handle=oceanwp-google-font-open-sans&original_handle=oceanwp-google-font-open-sans&ver=5.5.@indepthphotos, I just tested with Elementor enabled and I’m getting the same error: Invalid URL provided. So the issue here definitely is Elementor. I’ll see what I can do to improve compatibility.
@argentum, thanks for debugging the issue so thoroughly. It’s a cool setup, btw. Which I’d be interested in using myself. Nonetheless, I’d have to do some testing and see if I can make OMGF compatible with this setup.
-
This reply was modified 4 years, 5 months ago by
DaanvandenBergh.
Yeah, it works well. You can create for instance a testing version of a site in a parallell directory and when it’s working just change one line of code in the root index.php file.
I don’t know how your plugin works, but with “my” setup it clearly is a difference between using the values of the two different urls in siteurl vs home in wp_options db table.
One more question, though. Which of the setups did you follow? With or withour URL change?
Method II
The wordpress files sits in https:///www.domain.se/pro/
The url of the site is https:///www.domain.se/-
This reply was modified 4 years, 5 months ago by
Argentum.
@indepthphotos, just wanted to let you know that I just released 4.2.2 which should fix the issues you were having with Elementor.
@argentum, I’ve added your subfolder issue to my to-do list. I’m marking this ticket as resolved, since the original issue is resolved. Thanks for notifying me about it, though.
Ok, I will dare an upgrade then. Thanks for trying. I will see what happens now.
I’m not getting any font errors now but still getting this error in YSlow
There is 1 static component without a far-future expiration date.
I can’t understand why OMGF isn’t recognising and replacing these fonts.
I upgraded turned of WP-Rocket and emptied the cache in OMGf.
Still the same.
Full GTMetrix scan here.
https://gtmetrix.com/reports/www.willowsanddaisies.co.uk/1KevA93F
I did have this at 100% 100% but the CDN update is now also throwing cookie domain errors ??
This style sheet is still getting called on the page.
Raleway and Montserrat fonts.
-
This reply was modified 4 years, 5 months ago by
indepthphotos.
-
This reply was modified 4 years, 5 months ago by
indepthphotos.
Ok, I see that that script is optimized by WP Rocket. I’ll do some testing to see if I can come up with something.
Btw. WP Rocket recently removed the ‘Optimize Google Fonts’ option and enabled it by default. Do you remember having this option explicitly disabled or enabled? I’d have to check it out, but this might be interfering with OMGF.
Hi Daan,
Reporting the same issue, hope I’ll be able to do some debugging for you.
Setup:
– Elementor 3.0.12 and Elementor Pro 3.0.5.
– WP Rocket 3.7
– OMGF 4.2.3.I started Troubleshooting mode with only Elementor Free and Pro, OMGF and Helo Theme.
At this time your plugin does not replace https://fonts.googleapis.com/css in Manual Mode. When I switch to Automatic, now fonts are being detected. However, fonts are showing a 403 error when loading from our BunnyCDN.I exited Troubleshooting mode, cleared OMGF cache, now the automattic detection shows error 414 for https://www.verhelst-law.be/wp-json/omgf/v1/download/css?family=Open+Sans%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic%7CLibre+Baskerville%3A100%2C100italic%2C200%2C200italic%2C300%2C300italic%2C400%2C400italic%2C500%2C500italic%2C600%2C600italic%2C700%2C700italic%2C800%2C800italic%2C900%2C900italic&handle=google-fonts-1&original_handle=google-fonts-1&ver=5.5.1
When i switch to Manual mode again, error is gone, but fonts again load from Google
I was able to reduce it to an iThemes Security compat issue, as soon as I disabled that plugin, the manual detection in your plugin started working.
-
This reply was modified 4 years, 5 months ago by
- The topic ‘Error downloading fonts’ is closed to new replies.