Middag Lennard;
Had a quick look at your site, but it seems you’re (also/ now) running wp fastest cache CSS minification. this;
* could be the reason for the breakeage if run concurrently with AO
* makes it harder for me to find out what might be going on (I tend to disable stylesheets one by one until I see which one should be excluded)
so, can you disable wpfc minify options (at least for now)?
frank
Thread Starter
lwkooy
(@lwkooy)
Ha Frank,
I am. A bit of the ‘more is more’ philosophy :).
Of course! I disabled all the minify and combining funcitons of wpfc (only ones left checked are ‘Cache System, Preload, Gzip and Browser Caching).
thanks!!
ok, for starters let’s try adding this to the CSS optimization exclusion field;
mrtailor/css/app.css, mrtailor/css/default.css, mrtailor/css/styles.css, font-awesome.min.css
frank
Thread Starter
lwkooy
(@lwkooy)
weird; icons work for me?
View post on imgur.com
would be surprising actually, because fontawesome (of which 2 versions are loaded by the way) which is responsible for the icons is excluded from CSS optimization.
Thread Starter
lwkooy
(@lwkooy)
Yeah. But I tried excluding those quite sometimes already. No luck.
I’m in chrome, incognito to make sure I don’t hit the cache. The cions need to be in the header as well (now they are a bit half in the slider, half in the header).
No clue why he loads them twice as well. i think one set is in the theme and another one gets called from the visual composer plugin.
ah, had a look in chrome and see this one (and more like it) on the console;
Access to Font at ‘https://wordpress-ohiobear.netdna-ssl.com/wp-content/plugins/js_composer/assets/lib/bower/font-awesome/fonts/fontawesome-webfont.woff2?v=4.6.3’ from origin ‘https://wordpress-ohiobear.netdna-ssl.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘https://ohiobear.com’ is therefore not allowed access.
This is not related to AO really, this can be fixed (I think) with a settting at maxcdn/ netdna’s or by excluding fontawesome & co from being served by the CDN.
frank
in Firefox (with AO CSS optimization off, apparently) I now also get
10:06:19.332 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wordpress-ohiobear.netdna-ssl.com/wp-content/themes/mrtailor/inc/fonts/font-awesome/fonts/fontawesome-webfont.ttf?v=4.4.0. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).1(unknown)
this maxcdn-article explains how to fix this.
succes 🙂
frank
Thread Starter
lwkooy
(@lwkooy)
Hi Frank,
Thanks for all the help. I’ll let you know if I solved it.
cheers,
Lennard
Thread Starter
lwkooy
(@lwkooy)
Hi Frank,
That solved it. For everyone that might end up reading this post: make sure you purge the cdn cache i you edit the .htaccess file
cheers
