Optimizing Matters

in that case Autoptimize is creating too many cached files @adheena, I would suggest to disable “also aggregate inline JS” and “also aggregate inline CSS”.

hope this helps,
frank

you can create lyteCache-config.php in the wordpress root directory and in there define the constant LYTE_CACHE_EXPIRE_TIME to the value of your choice, that way you don’t have to change lyteCache.php? ??

server response time remains very high indeed, even though it *looks* like WPSC is working as it should. you might have to discuss this with your hosting provider Vlad.. :-/

given the long server response time, the first thing to do would be installing a free page caching plugin, e.g. KeyCDN Cache Enabler (the free version of Autoptimize doesn’t do page caching).

First and foremost try to identify what is breaking Modula 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

yes, skip-lazy, which is supported by almost all lazyloading plugins by the way ??

Autoptimize’s lazyload allows you to exclude images using the filename or any attribute/ value in the <img tag (e.g. class name), so excluding should help to keep lazyload active except for the maintenance image? ??

frank (ao dev)

OK, just fixed the issue with the “doing it wrong” in the upgrade routine as well, thanks for the assistance! ??

enjoy the weekend!
frank

OK, so just pushed a fix to the Beta version on Github, would be great if you could download the zipfile and test as well Paul? ??

changing the language to a non-default one, that’s what I was missing! thanks for that! ??

have been trying to get that deprecation warning to show up, but can’t find it anywhere strangely enough. nothing of that sort in php errorlog, nothing via query monitor, nothing showing on pages even with WP_DEBUG and WP_DEBUG_DISPLAY set to true. any tips on how to get this to show are more than welcome! ??

those PHP-files contain the logic to serve the CSS/ JS, the none-files contain the CSS/ JS. if you want to avoid this, you can re-enable the “serve as static files” option near the bottom of the main settings page if you prefer not to have those .php and .none files;

thanks for the heads up Paul, I’ll look into that! ??

ah, that sounds like a problem with a stale persistant object cache (e.g. memcached or redis), ask you host to try flushing that maybe?

it says I didn’t check something

OK, can you copy/ paste the exact error message?