Title: Did recent Autoptimize update break CSS optimization? Last modified: July 4, 2017 --- # Did recent Autoptimize update break CSS optimization? * Resolved [theomoulin](https://wordpress.org/support/users/theomoulin/) * (@theomoulin) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/) * Did anyone experience issues with Autoptimize after a recent update? All worked fine (HTML, JS, CSS optimization) up to version 2.1.x. I am actively developing a website, so I temporarily deactivated Autoptimize and WP Super Cache. Did a bunch of things, like adding Polylang, but the theme itself (Lava by Themespirit) hasn’t changed. Now I reactivated Autoptimize, updated to 2.2.2, emptied cache etc. but CSS optimization is no longer possible. It completely breaks the site layout. Masterslider is totally confused, and more plugins get completely messed up. HTML and JS optimization still work fine, it’s just the CSS part that no longer works OK. * Would anyone have a solution for this? Viewing 12 replies - 1 through 12 (of 12 total) * Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/) * (@optimizingmatters) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9287957) * Well, that could indeed be the update, but it could also be the additional plugins. * Easiest way to determine which; [download & install 2.1.2](https://downloads.wordpress.org/plugin/autoptimize.2.1.2.zip)( which is 2.1.0 + an important security fix) and see if that fixes things. * alternative; disable the new optimization logic in AO 2.2.x using this code snippet; ` add_filter('autoptimize_filter_speedupper','__return_false');` * if not the AO update, you might have to dive into the troubleshooting tips in [the FAQ](https://wordpress.org/plugins/autoptimize/#faq). * hope this helps, frank * [Michael](https://wordpress.org/support/users/grinstead/) * (@grinstead) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288118) * For me the the Autoptimize has put the cache css link in to the body and not in the head. So I’m seeing an unstyled page. * Thanks * Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/) * (@optimizingmatters) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288435) * that’s … weird. can you share your URL [@grinstead](https://wordpress.org/support/users/grinstead/), I’d love to have a look around .. * Thread Starter [theomoulin](https://wordpress.org/support/users/theomoulin/) * (@theomoulin) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288734) * Version 2.1.2 unfortunately does not solve the issue. Even with almost all other plugins deactivated, still the same issue. The FAQ talks about setting option“ Look for styles on just head?” but I don’t see that in settings. * Guess I’ll go back to most recent version, but will leave CSS optimization turned off… * Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/) * (@optimizingmatters) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288868) * > Version 2.1.2 unfortunately does not solve the issue. * good for me (no regression), not good for you obviously. * > Guess I’ll go back to most recent version, but will leave CSS optimization > turned off… * That I wouldn’t do. You could instead try (as per the troubleshooting tips in [the FAQ](https://wordpress.org/plugins/autoptimize/faq)) to exclude some of the CSS from optimization. And the “Look for styles on just head?”-option still exists, even if it’s not listed on the admin-page any more. simply execute * `update_option('autoptimize_css_justhead','on');` * and you will only be aggregating CSS from the head-section AND the option will be visible on the admin-screen (until you disable it) * happy optimizing, frank * [Michael](https://wordpress.org/support/users/grinstead/) * (@grinstead) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288891) * [@optimizingmatters](https://wordpress.org/support/users/optimizingmatters/) I would but this is on a local environment, not live. * Thread Starter [theomoulin](https://wordpress.org/support/users/theomoulin/) * (@theomoulin) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288901) * Thanks Frank. I tried the ‘hidden/deprecated’ head-only option, that indeed became visible. It also did not solve the issue. * I’ll do some deep dive somewhat later on which CSS to exclude. * kind regards, Theo * [Michael](https://wordpress.org/support/users/grinstead/) * (@grinstead) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9288918) * I’ve just noticed that it’s actually placing the style link inside a inline svg! * Code snippet: * `` * Hope that helps. * Michael * Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/) * (@optimizingmatters) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9289622) * it does help; AO uses the title-element to inject the CSS by default (and did the same the previous versions). if your SVG has a title-element (it does) and if it comes before the HTML-title, it’ll mis-inject. * what you can do; * remove the title-element from the SVG * change the place of the SVG after the title * change AO’s injection-point using the API, e.g. * ``` add_filter('autoptimize_filter_css_replacetag','css_after_svg',10,1); function css_after_svg($replacetag) { return array("","after"); } ``` * will place it after the SVG (assuming there are no earlier occurrences of `` * hope this helps, frank * [Michael](https://wordpress.org/support/users/grinstead/) * (@grinstead) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9290098) * Thanks Frank, I see, that clears that up. * Thread Starter [theomoulin](https://wordpress.org/support/users/theomoulin/) * (@theomoulin) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9290973) * Frank, Thanks for your feedback. I’ve managed to get the site to work correctly again, while optimizing CSS too. In the end I need to exclude 2 CSS files from HBook plugin and also 2 CSS files from Masterslider Pro. * Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/) * (@optimizingmatters) * [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9291630) * thanks for all the feedback guys, happy you were able to troubleshoot your problems! 🙂 Viewing 12 replies - 1 through 12 (of 12 total) The topic ‘Did recent Autoptimize update break CSS optimization?’ is closed to new replies. * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608) * [Autoptimize](https://wordpress.org/plugins/autoptimize/) * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq) * [Support Threads](https://wordpress.org/support/plugin/autoptimize/) * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/) * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/) ## Tags * [autoptimize css](https://wordpress.org/support/topic-tag/autoptimize-css/) * 12 replies * 3 participants * Last reply from: [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/) * Last activity: [8 years, 11 months ago](https://wordpress.org/support/topic/did-recent-autoptimize-update-break-css-optimization/#post-9291630) * Status: resolved