Venkat Raj

@thrdlickova Could you please share what kind of error messages are you getting? Any browser console errors?

@vladimirvuch We don’t have a fixed time frame for this feature. But I can say, you can expect it in the first week of June

@aethon Disabling and enabling cache should fix the problem. If not, you need to check file permissions for the mentioned folder.

Rolling back to 3.2.3 won’t solve the issue. WordPress 6.2 has major changes and to be compatible with it you need to use 3.2.14

That said you can go to plugin page and click advanced From that page, you can download any of the previous versions
https://prnt.sc/V02CBBzaaK-G

@sahadatuk21

Do you have webp conversion tools installed on your server? See details here…
https://getwpo.com/faqs/#How-can-I-get-WebP-conversion-tools-to-work-

We are using resmush.it API service to compression image. Their server may be overloaded with traffic. We are working on our own image compression service.

Could you please share contents of uploads/smush-xxxx.log file using https://pastebin.com/ ? thanks

@hadis89
1. Since this is privileged task, only logged in users can run preload.
2. This is long running task for huge sites. So, it creates sub tasks for each URL and schedule it to run via cron job (WP Cron). At max_execution_time it is possible that it loaded ~25 pages and stops (but creates cron job to run later, to avoid max. load on server at one stretch)
3. process_tasks_queue method will run on wpo_page_cache_preload_continue hook

@ttrrrmax2 Those files are used to detect .htaccess capability of your server. That said, we are working on an alternative way to do this without using those files.

@japonicus Add this line define('WPO_USE_WEBP_CONVERSION', false); in your wp-config.php file