Afraid I see nothing special in 5.6.1 release notes that could cause issues amberpitcher.
What I would propose; let’s first and foremost try to identify what is breaking things by just disabling CSS or JS or HTML or Image optimization (incl. lazyload). Based on that we can see what the next steps need to be 🙂
frank
With the release of WordPress 5.6.1, Autoptimize is now causing JS errors in the console. PRIOR it was working fine. I’ve tested by reverting everything back and forth. It breaks many elements.
Here’s a breakdown of what’s being seen in the console.
Uncaught SyntaxError: Unexpected end of input : autoptimize_0293c44e3fb4653e741312e354e788fe.js:76
Looks like if all 3 options are on it breaks the page and some elements. If one of them is off it breaks some elements from loading.
I’ve tried all combination of JS, CSS and HTML optimization on and off.
@optimizingmatters let me know if I can assist any other way.
The error in the console implies a problem with JS optimization. Are you also using Elementor? Do you have a staging site where you could leave things broken for me to look into?
@optimizingmatters I don’t have a staging site, unfortunately.
However, I can revert back to the previous config where it’s broken for a period of time, now that I know how to fix it for the time being. (Disabling the plugin)
Worth to note, I do make use of W3 Total Cache. But that shouldn’t matter as if was working in the previous version of the plugin with critical CSS.
Did you have W3TC doing CSS/ JS optimization as well while having AO active @guaym2 ? And when on 5.6.1 with AO but with W3TC disabled, do the problems continue?
@optimizingmatters The problem does exist with W3 Total Cache deactivated while having AO activated.
While W3 Total Cache is turned off and AO is active. AO generates additional errors
autoptimize_0293c44e3fb4653e741312e354e788fe.js:2 Uncaught SyntaxError: Unexpected token ‘<‘
I’m also not using elementor like OP.
any (additional, host-level or 3rd party) page cache that need purging? the < implies the file being served is HTML, likely a 404-page?
@optimizingmatters nothing else on my end.
Oh and you have things broken now anyway, feel free to share the URL 🙂
