Venkat Raj
Forum Replies Created
-
@lordsnake Could you please share your php
error_logfile? Thanks You happen to use any CDN?@jidwictut9 Do you mean
.htaccessfile in the root? If so, I couldn’t reproduce the issue. WP-Optimize only removes the rules added by it such as browser caching, gzip compression, etc It does that based on comments such as# BEGIN WP-Optimize Gzip compression. If you happen to add your rules between the #BEGIN and #ENDcomments, then this can happen@formularon Could you please provide more information about your server? Do you use clourflare?
If you would like to discuss this in private, please send email support.wpo@updraftplus.com@roow Please follow this article. https://getwpo.com/faqs/how-can-i-get-these-tools/
@jakebb Those files are not useless files, those are used to determine the redirection capability of your server. That said, we are working on a fix to remove the usage of those file.
@formularon I assume, your hosting provider added PHP’s built in function
escapeshellargtodisable_functionsdirective for security purposes.
You can adddefine('WPO_USE_WEBP_CONVERSION', false);to yourwp-config.phpfile to prevent this.@goldcrest As said earlier, there is no such feature at this moment. I can think of only one solution for this. Reduce the cache life span to your desired duration
@libergm WP-Optimize is not fully compatible with AMP
@glezsak Please add
define('WPO_USE_WEBP_CONVERSION', false);to yourwp-config.phpfile. That should fix the web server log issue.
Regarding minify, what do you see ascurrent cacheandtotal cachesizes? Does it grow too frequently? Doe sthelast minify cache updatetime changes too often?
https://prnt.sc/xRUnZA2f9Ytx@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 receivedHowever, 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 inunexpected response receivedHowever, large preloads will run in batches and as cron job. That is the reason you see continued preloading.
May be you could try theTurn off Broken Connection Abortingsection 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.14There 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?