Crawler and Scheduled Purge

Hello,

I have recently setup the Crawler on one of my sites to improve cache freshness but I have three issues.

1:
I have setup the crawler to run using a cpanel cron job and turned off WP cron. I have the cpanel cron job hitting wp-cron.php at 00:10:00 and 00:40:00 so it crawls twice 30 minutes apart between 12am and 1am.
I have another cpanel cron task setup that runs a custom script that just fires \LiteSpeed\Purge::purge_all();. this happens at 00:01:00.
The purpose of this is to purge the whole cache, then crawl the site to re-create it.

The problem I am having is that the first crawler pass after a Purge All always just crawls one page and stops with end_reset response. This happens if I run it manually or via cron job. The second crawl works fine and crawls all 14 pages.
Why does a purge all prevent the crawler from crawling ALL pages?

2:
I have tried using the built in Scheduled Purge but at first it appeared to not work. i.e. the cache was never purged. However while looking through the crawler logs this morning, I noted the following amongst the log Cache_control TTL is limited to 2567 due to scheduled purge rule…. it has now occured to me that the Scheduled Purge actually doest purge the cache, but simply sets TTL so that next time it is crawled after that time the cache is expired so it is refreshed for that page.. is this correct? If so the documentation should really be updated to reflect this as it is not in anyway clear.

3:
Scheduled Purge appears to use un-localised server time (UTC), rather than the local timezone. This causes problems when combining it with cPanel cron tasks which do use local time…. It is not reasonable to expect users to update the Scheduled Purge time twice per year when Daylight Savings begins and ends. It should use local time.

• This topic was modified 3 years ago by miketemby.