rubinstein
Forum Replies Created
-
The 90s are calling, they want their colors back.
This really has to stop. We really need enforcement of the plugin guidelines or new guidelines that prevent this behavior.
Forum: Plugins
In reply to: [LiteSpeed Cache] Deleting lscache folder contentThank you very much, that answered my question. 🙂
Forum: Plugins
In reply to: [LiteSpeed Cache] Deleting lscache folder contentOh, using an API is a bit too complicated for me, I’m not a programmer.
But I’ve since managed to do a purge with WP CLI, that didn’t work before in a cron job, only in a bash shell. You have to use it like this to work in a script for a cron job:
/usr/local/bin/php /usr/local/bin/wp lscache-purge all –path=/home/user/public_html/
Deleting the lsache folder content also seems to work, I found it here in this article: https://www.a2hosting.com/kb/a2-hosting-products/turbo-web-hosting/clearing-the-litespeed-cache
So that’s why I was asking if there were any side effects in using this method. Or, in other words, what’s the advantage of using the WP CLI purge method?
Hi Ashley @aporter,
You were right: It’s my webhosting company that is deleting the directory, they confirmed it today. They said they’ll look into retaining the log files.
Thank you!
Hi @sanzeeb3,
The fix from 3.5 weeks ago seems to work, today I received the WordPress core update email, there was no error. 🙂
Thank you very much!
Hi Ashley,
I’ve deactivated UpdraftPlus and deleted the 2 corresponding WP cron entries, but the directory and 1 log file in it are still there, so we’ll see if it’ll stay that way.
Something resets the directory and the files in it daily. Yesterday it was at 1:17 am, and today it was at 7:29 am. Which is odd, as cron jobs are triggered every 5 minutes (real cron job).
Thanks!
Today I don’t have any log files at all, as you can see here:
This is a screenshot of public_html/wp-content/updraft:
Here is an image of my backups: https://i.imgur.com/PYedPWw.png
(I was mistaken, I currently have 7 backup sets.)
Hi Ashley @aporter,
Could this be a bug because I only have 1 log file but–for example today–4 backup files? If there’s a limit of 40 log files, then I should have 4 corresponding log files, right? Or maybe I don’t understand it fully…
Hi Ashley @aporter,
Thank you for your answer.
When the default is 40 days then it’s strange that I only have 1 log file (but lots of backups) with one of my installations.
How can I reset the plugin so that I have up to 40 days of log files?
Forum: Plugins
In reply to: [WP Super Cache] WP Super Cache and wp-config 600I think I might have had the same error.
cPanel error logs:
2019-10-07 04:06:03.482740 [NOTICE] [2529149] [x.x.x.x:39342] [STDERR] PHP Warning: require_once(/home/user/public_html/wp-config.php): failed to open stream: Permission denied in /home/user/public_html/wp-load.php on line 37
2019-10-07 04:06:03.482776 [NOTICE] [2529149] [x.x.x.x:39342] [STDERR] PHP Fatal error: require_once(): Failed opening required ‘/home/user/public_html/wp-config.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/user/public_html/wp-load.php on line 37
My wp-config.php has 0400 permissions, and it normally works just fine, but somehow WP Super Cache messed with it and I got an internal server error 500 as a result. I’m not 100% sure, but there’s a high probability that WP Super Cache caused this error.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache Preload doesn’t seem to stopHi @vmarko,
Thank you and sorry to ask again:
So the preload GET requests get served as HTML from the page cache directory (and it doesn’t trigger any PHP)?
Thank you and greetings from Austria to Serbia
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache Preload doesn’t seem to stopHi @vmarko,
Thank you for creating an issue on GitHub.
One more question, if I may:
After all URLs are cached: Do the preload GET requests hit the cached pages or do they trigger any PHP?
Thank you!
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache Preload doesn’t seem to stopOh, just a thought: Maybe you could add your answer (how the preload mechanism works) to the W3 Total Cache wiki page?
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache Preload doesn’t seem to stopHi Marko @vmarko,
I see, thank you for your answer.
Is there a reason why the plugin does it that way? Because the cached pages stay the same, they’re not altered in any way.
If there’s no benefit in doing it this way then yes, the possibility to stop the preload after all URLs are visited would be nice.
It’s not that it adds a huge load to the server, but I see 4% or 5% CPU spikes on shared hosting.
