Conversation
supportI’m getting the error in the subject twice for two css files. Is this normal? The page I need help with: [ log in to see the link]
Hi, A few things cause that. With FVM disabled, https://slimbyapriori.global/?nocache your security policy (CSP) is not allowing some of the necessary scripts to run: https://i.imgur.com/G8WXepG.png You should fix that first. Second, you added sha384 integrity checks to some of your css (fontawesome) so what that does, is to check if the file had no changes. If there are changes, the integrity will fail and the file will not load. Minification is a change to the file, so either you must remove the integrity check (check your fontawesome settings), or you must exclude the files with integrity checks from being minified, so that it doesn’t touch them. I can add a check to remove the integrity check from minified files in the next version, but until then that is the solution. Thanks
Thank you for the detailed explanation and the tips! The CSP is a caching issue affecting Chrome and clones, but that’s for non-essential external scripts and only happens on the page where you accept the cookies first. Switch to any other page, and everything works fine. I’m trying to find a solution for that, but it’s unrelated to the minified fontawesome files. The integrity checks must be coming from some plugin or maybe from fontawesome directly. I never set that. I’m actually pulling fontawesome from the cloud. I’ll investigate where these .css files are coming from. I’ll close the issue when I get this fixed and report back.
Turns out three plugins are loading their own versions of fontawesome. Two of them have copies of the assets in their files, and another one blatantly goes for an @import in its css… Anyway, this is now solved. Thank you!
Hi, A few things cause that. With FVM disabled, https://slimbyapriori.global/?nocache your security policy (CSP) is not allowing some of the necessary scripts to run: https://i.imgur.com/G8WXepG.png You should fix that first. Second, you added sha384 integrity checks to some of your css (fontawesome) so what that does, is to check if the file had no changes. If there are changes, the integrity will fail and the file will not load. Minification is a change to the file, so either you must remove the integrity check (check your fontawesome settings), or you must exclude the files with integrity checks from being minified, so that it doesn’t touch them. I can add a check to remove the integrity check from minified files in the next version, but until then that is the solution. Thanks
Thank you for the detailed explanation and the tips! The CSP is a caching issue affecting Chrome and clones, but that’s for non-essential external scripts and only happens on the page where you accept the cookies first. Switch to any other page, and everything works fine. I’m trying to find a solution for that, but it’s unrelated to the minified fontawesome files. The integrity checks must be coming from some plugin or maybe from fontawesome directly. I never set that. I’m actually pulling fontawesome from the cloud. I’ll investigate where these .css files are coming from. I’ll close the issue when I get this fixed and report back.
Turns out three plugins are loading their own versions of fontawesome. Two of them have copies of the assets in their files, and another one blatantly goes for an @import in its css… Anyway, this is now solved. Thank you!