saens

Also, regarding 2)

I’ve been looking at my server logs and you’re saying “2. It starts caching the page again.”
But this is simply not true. Also supported by what you’re saying here: https://wordpress.org/support/topic/page-cache-preload-doesnt-seem-to-stop/#post-11981646

I’m seeing pages being served that are hours old and have been visited by w3tc warm-up many times in between.
I’m seeing pages expiring (going cold) only to be warmed when the w3tc warm-up visits them. And with a low visit interval as you propose many pages go cold waiting to be hit by the w3tc warm-up and actually get refreshed.

Thanks for your responses.

Regarding 3). I always test in clean private windows. So I’d expect to always have a page served with a time-stamp < 1 hour. This is not the case.
Local/browser cache shouldn’t be an issue because of the private window. Unless you mean something else with what you’re saying in 3.

For clarity: I’m referring to the timestamp in the bottom HTML:

<!–
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Paginacaching met redis

Served from: testest.nl @ 2021-01-26 12:25:00 by W3 Total Cache
–>

• This reply was modified 5 years, 6 months ago by saens.

Thanks for your reply.
I’m trying to understand what actually happens with what I am seeing.
I’ve not changed my settings yet.

1. w3tc just starts over when it has cached all pages, yes?
2. what does w3tc do when it reaches the first page after starting over?
overwrite or generate and throw away if TTL is not reached?

I’m seeing a page which is more than 1 hour* old. And if what you’re saying is correct, then I should never see a page this old (with my current aggresive settings)

*Served from: testest.nl @ 2021-01-25 00:16:19 by W3 Total Cache

Thank you.

I can assume parallel running jobs (from both wp-cron.php and /?action=wpfastestcache&type=preload) won’t interfere with eachother?

Thanks for your reply.

It won’t tell us anything. I’ve had this error once in my logs, and have been on current version for months. So it’d be an unsufficient sample size.

I’ll keep an eye on my logs if it happens more frequently, and then I’ll think about changing code on my live-server.

Seems to work yea. Will you integrate this into the plugin itself?

The gist is:
Fil array with the comments

		$comments = get_comments( array( 
			'post_id' => $product->get_id(),
			'number' => $count_reviews,
			'type' => 'review'
			) );

then run through the loop and output the comment how you wish.
I put it together based off examples at stackexchange.com

My code won’t help you since it’s tailored to my specific demands. The basic is the same as the examples that you can find.