Venkat Raj

@sbdermaceuticals At this moment, yes, you’ll get warning if you try to compress 1000s of images at once. But with batch process, you’ll be fine.

That said, I’ll make this a priority in our development process.

Hi @kingofrocknroll

There is also a cache related log file in uploads/wpo/logs/cache-xxxx.log though it mainly logs when the caches are purged. May be you look into that file, to see if caches are purging for some reason.

You should also see wpo_page_cache_preload_continue cron event when preload is running.

WP_Optimize_Preloader which is extended by WP_Optimize_Page_Cache_Preloader are the classes responsible for Preloading .

Hi @sbdermaceuticals

I understand that compressing thousands of images at once is best done as background process. We will try to add this feature in future release

Currently in premium version, you can bulk compress images from Media Library itself, and can use batch process as Media Library already has pagination. Also, you can filter by compressed/uncompressed images from that screen

Hi John

I understand that executing smaller jobs in the queue first gives an illusion of progress rather than waiting for a big task to complete (such as table optimization). I’ll see what I can do

• This reply was modified 9 months ago by Venkat Raj. Reason: typo

Apologies for the inconvenience caused. It happened after making it compatible with jQuery 4. Issue will be fixed in next week’s release. Thanks for your patience.

@dtrembath There has been some compatibility issues with 4.2.0 release which is now fixed in 4.2.1 Please update to latest version and it should fix the issues.

@bheching Please update to 4.2.1 It should fix the issue

Hi @grnews1

I confirm that this is a bug (absence of that option), and we will fix this in the next release.