Venkat Raj

@glezsak Please add define('WPO_USE_WEBP_CONVERSION', false); to your wp-config.php file. That should fix the web server log issue.

Regarding minify, what do you see as current cache and total cache sizes? Does it grow too frequently? Doe sthe last minify cache update time changes too often?
https://prnt.sc/xRUnZA2f9Ytx

@raval104 How do you conclude that WP-Optimize is causing the problem? How do you conclude that other plugins aren’t causing the issue?

When I visited your site, WP-O seems to be active and yet the links are not clickable. See the screenshot https://prnt.sc/HmOWBhY6Skql

Here is the browser console screenshot we talked about earlier.
https://prnt.sc/6FQSjIj_UPFT

It seems you have some AMP related plugins installed and it is causing the issue. Once you deactivate WP-O, it won’t do anything with HTML response your server send to browser.

Deactivate all plugins and activate plugins one by one to find out which one is causing the issue.

@mikealan Preload is a long running task. So WP-O increases timeout limit and close browser connection to continue preloading in the background. Some server configurations prevents the attempt to close browser connection and some kill long running php processes automatically which will result in unexpected response received However, large preloads will run in batches and as cron job. So, the preload will continue to work regardless of the alert message. We are working on a better user experience on this issue.

As you said yourself the error log entries are unrelated to WP Optimize. When you run preload every page of your site will be visited programmatically. The theme and plugins used in those pages throws those notices.

Though most of it are deprecated notices, you should contact Custom Facebook Feed Pro plugin authors since it is the one that throws a fatal error.

@ms100

Since preload is a long running task, WP-Optimize attempts to close browser connection and run in the background. However some litespeed server configurations prevents the attempt to close browser connection which will result in unexpected response received However, large preloads will run in batches and as cron job. That is the reason you see continued preloading.

May be you could try the Turn off Broken Connection Aborting section in the link you have mentioned.

https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/#turn-off-broken-connection-aborting

@seanconklin There was a compatibility issue with WordPress 6.2 which is fixed. Please update to WP Optimize version 3.2.14

@ms100
> What is the best server cronjob interval for the WP-Optimize plugin?
I think my choice of words are bad in my previous reply. It doesn’t matter how frequent your server cron run, it only executes WP cron jobs as per its schedule. If You scheduled your preload the same time as your cache expires, i.e. 10 hours as per your comment, then it will run once in 10 hours, even though you scheduled server cron to run once in every 30 minutes.

So what you need to check is how large is your site and long does it take to complete preload.

2. Do your server has restrictions on number of files (even though it has space). I have seen such restrictions

3. There is a compatibility issue with WP 6.2 which is fixed. Please update to 3.2.14

There was a compatibility issue with WordPress 6.2 which is fixed. Please update to WP Optimize version 3.2.14

@ms100 Preloading a large site is batch process. It will process a batch of URLs in 10 minutes interval. So, if you run cronjob at every 30 minutes, you’ll likely see it is processing whenever you visit site.

Your server cronjob should run whenever the cache expires.

Regarding the error log statements, do you have enough disk space?

@alanaubert Make sure you have webp conversion tools available on your server.

https://prnt.sc/pM5j1TfNv8C9

Compress (and also create WebP format)
https://prnt.sc/Uh8efGrimIPd

Already compressed, but webp format is not created yet
https://prnt.sc/1vLIPtOFzA5I

@ms100 I understand that we already asked this, but make sure wp-content/cache folder is writable.

If your site traffic is low and you set cache life span to 24 hours and cache preload schedule is same as cache life span, visiting your dashboard can trigger the preload process.

Change Minify > Advanced options > Lifetime old cache > to 1 days.

What OS/Server are you using?

@makol which plugin shows this message?
There is no file named class-wpo-cache-preloader.php? in WP-Optimize plugin. Which you can downloaded plugin zip, extract and check it.

It seems the site has been hacked and file has been uploaded

@lordsnake

Please fix the JS errors https://prnt.sc/Zy1wL1yHjaz8

Inspect the headers and see the difference between status ‘cached’ or ‘saving to cache’ or ‘not cached’
https://prnt.sc/9m-lQmcoC5Kn

Also try to disable Redis cache and see if that fixes the problem.

If you could send us wp-content/cache/wpo-cache/www.elkmountaintents.com/canvas-tents-for-sale/index.html files when it is displaying correctly and not displaying products, we can check what is going wrong.

@netzzjd Please make sure none of your plugins uses development mode. For example, Mobile menu plugin has such an option
https://www.ads-software.com/plugins/mobile-menu/

Which uses timestamp as version for the static assets that will invalidate existing minify cache.

If this fails, could you please submit a support request here to discuss site specific details. Even though it is pre sales form, it will reach our support channel.

https://getwpo.com/ask-pre-sales-question/

@alanaubert You should compress your image in order to create a webp version of it. If you already compressed your images and has been using it in your content, then you can only convert those images to webp format from media library itself.

This option is available in the latest version 3.2.13

@netzzjd Do you happen to use Divi theme?