[ad_1]
Morning Jörg;
Can you try adding wp-content/plugins/Ultimate_VC_Addons/ to the comma-separated CSS optimization exclusion list?
frank
Hi Frank,
Thanx for the response!
That is exactly what I meant with “excluding the affected plugins from CSS Autoptimize”. That’s what I did and what solved the issue with the errors. However, as a result a major part of CSS is therefor excluded from optimization. I am looking for a solution, to fix caching. Autoptimize is listed as WPML compatible, which should include a working caching for multi-domain setups. Or maybe there is a way to solve the issue in the affected CSS (relative paths)?
Best regards,
Jörg
Well it’s not really a WPML + AO issue but rather a multidomain + VC addons + AO one 🙂
What you could do/ try;
1. disable “aggregate CSS” and enable “remove render-blocking CSS” (making sure either “above the fold CSS” is provided or that you have rules on the “critical CSS” tab
2. OR try to make the exclusion more specific (there likely just one CSS-file inside wp-content/plugins/Ultimate_VC_Addons/ that is defining the fonts)
3. OR change webserver config to send the Access-Control-Allow-Origin: * header in the response for fonts
hope this helps,
frank
Hi Frank,
Thanx! Yes, it does help! I went for option 2. 🙂
What is involved in the issue is a philosophical question. 😉
Ultimate VC AddOns is just one affected Plug-In. Quform is another one.
Though there might be other options for multidomain, WPML does offer this mode of operation. So, sorry to insist, I would expect it to work when “WPML compatibility” is stated. However, to be fair, various “WPML compatible” PlugIns do not work properly in a multidomain setup (e.g. Yoast). So I am used to sorrow 😉
Best regards,
Jörg