Hello @roadsider
Hope all is well!
Please exclude the file that contains google font from minification. First looks for OTH type file and deactivate compression for it, by clicking on Compression button. For example, please see this screenshot
If this will not fix the fonts, the fonts can be added in CSS files, to find in which one, please deactivate minification for all CSS files by clicking on “Compress” button and save changes. Refresh the front end page, to see if fonts are fixed.
If the fonts are fixed, start activating minification by clicking “Compress” button for one file at the time, and checking the front end. Once the font will be broken again, you will find on which file Compress option should be deactivated.
Make sure to clear site’s cache after each change.
Let us know how it went!
Kind regards
Nastia
That doesn’t seem to work. The css files that contains that font spec either says it “can’t be compressed” or that it’s “already compressed” and I can’t uncomplress it. These css files are original to the theme. I set the fonts from within the theme customization and not in the CSS file itself.
Hi @roadsider,
What error are you getting in the browser console when you enable minification and the google fonts stop working?
Best regards,
Anton
There are quite a few errors reported in the Console, but I’m not sure which one is related to this problem.
You can see a screen shot here:
https://www.dropbox.com/s/zvdl99jgmn5vdvj/Screenshot%202018-03-28%2011.27.17.png?dl=0
Hi @roadsider,
Are you, by any chance, using multiple optimization plugins?
Regarding the errors above – none of them seem HB related, although the error in index.html on line 59 seems critical. Do you have these errors when minification is turned off?
Best regards,
Anton
actually, yes, I do have most of those errors without minification. And no, there’s no other optimization plugin.
Line 59 refers to a font-awesome css file, which Hummingbird shows as “Already compressed” and can’t be uncompressed.
@roadsider,
Please try disabling compression for files that are giving you errors:
- unhandledRejection.js
- VM14423 and VM16702 – you can click on that name in the browser console and see what file the error refers to (these two files you can also try to move to footer).
In very rare cases the order of file during asset optimization can be altered which can result in an error in one of the js files, but judging from your files, none of the ones that give out errors are compressed.
If the above doesn’t help, try excluding all files from minification and see if that can help. Asset optimization can be a bit frustrating sometimes, but it’s well worth the results when you do it properly.
And if none of the above help, please contact me via this form:
https://premium.wpmudev.org/contact/#i-have-a-different-question
Use this subject, so the email is assigned to me:
Subject: “Attn: Anton”
Best regards,
Anton
