Hi @rubinstein, if you want to purge the cache manually, you can use our purge API.
Hi @stanleylitespeed,
Oh, 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?
Deleting cache folder should work, WP CLI or API is just an easier and safer way to purge the cache to prevent removing wrong folder and folder permission problem. So you can keep use the folder removing method if you tested and it is working.
Hi @stanleylitespeed,
Thank you very much, that answered my question. 🙂
