morning @cembtw;
I’d like to see the test-page with and without autoptimize and can normally do so by adding ?ao_noptimize=1 to the URL, but it seems you have W3TC configured to ignore the querystring, could you temporarily change that so I can compare the CSS on the exact same page?
thanks,
frank
Thread Starter
CEMBTW
(@cembtw)
I’ve now turned off caching on that page entirely (and there is no old cached version being served), but I had to remove the my_ao_noptimize filter call from my functions.php to get the ao_noptimize querystring to work.
can you completely purge your autoptimize (and page) cache @cembtw?
Thread Starter
CEMBTW
(@cembtw)
I’ve now purged both and verified by checking the cache folders themselves.
I can confirm that indeed some CSS seems to be missing from the Autoptimized file.
Next I installed https://wordpress.org/plugins/wpdatatables/ (the Lite version) on my development laptop and it’s CSS is optimized without any problems, so this does not seem to be a generic problem with that specific plugin.
So I have no clue -yet- of what might be happening @cembtw ..
Some things to try that might help us understand:
* selectively disable other plugins (except for wp datables & AO) to see if the problem disappears (confirming a plugin conflict)
* add wpdatatables/assets/css/ to the CSS optimization exclusion-list to see if that fixes all layout issues
* go back to AO 2.2.2 (download here) to confirm if it indeed works with that version
frank
Thread Starter
CEMBTW
(@cembtw)
– I didn’t disable everything, but disabling plugins recently changed, or that seemed like likely culprits (W3TC, Plugin Organizer) didn’t seem to fix anything.
– Exclusions resulted in the excluded CSS loading correctly, as expected.
– The problem still existed after reverting to 2.2.2, so I was wrong to associate this with an update.
But maybe only somewhat wrong, as I was able to resolve the issue by removing the temporary add_filter('autoptimize_filter_speedupper', '__return_false'); fix from my functions.php.
I though this was a fluke, but I am able to recreate/resolve the issue just by adding/removing that filter, uploading, and refreshing the page.
Any idea why? Does that make any sense?
-
This reply was modified 8 years, 5 months ago by
CEMBTW.
I am able to recreate/resolve the issue just by adding/removing that filter
ohhh, that makes some sense indeed; speedupper functionality, while also including the cache warming that cause some servers to “overheat”, is mainly a totally different way of optimizing the JS/ CSS. with the speedupper, AO minifies and caches each file separately and aggregates the already minified files (thus preventing the minifier to have to handle too big a files). by disabling the speedupper with that function, AO goes back to pre-2.2 behavior, and I guess the minifier chokes on the … significant amount of CSS somehow.
as 2.3.2 fixes the problem with the server load, I would suggest you to keep speedupper active (so removing the filter) and all will be fine.
have a nice weekend!
frank
going to close this as it works as it’s supposed when speedupper is active (the default behavior) @cembtw. don’t hesitate to follow up if you have any more questions or remarks!
frank
Thread Starter
CEMBTW
(@cembtw)
Yes, this is resolved. Thanks for the help!
