wamwebdev

Hi Marko,

Thanks for that information. My setup has just 2 URLs in the prime sitemap currently (it’s a staging site). I’m only interested in priming the cache for a particular set of URLs, as most of the site is fairly static content-wise. My Cron job calls wp-cron every minute, and the 2 URLs are generated in about 4 or 5 seconds.

I understand that this is in effect imitating users visiting pages and generating cached versions. But what I want to achieve is that the cache priming happens, without fail, every 15 minutes, irrespective of cache page lifetime or when a user last visited a one of the sitemap pages. Is this possible with W3TC?

Regards

Hi Marko,

Thanks for the quick response. I will try to explain my query with an example:

If I have the cache object lifetime set at e.g. 3600s and the prime update interval set at e.g. 900s, the pages in the prime sitemap won’t be regenerated until they expire (after 3600s). What I’m asking is whether there’s a way to override this rule, such that primed pages are always regenerated at the update interval.

Obviously you could set the update interval and the cache lifetime to “match”, but due to the finite time it takes to prime a series of pages, and the fact that the pages won’t be regenerated unless they have completely expired, there’s too much room for user requests to potentially affect the update timing.

The reason I’m asking this is because we have content that is displayed differently depending on the time of day. This content is (typically) already published, and can change on the hour or half-hour. So the purge policy for published posts won’t work in this case.

I hope you now understand my query!

Regards

Hello,

Would it be possible to provide a %notes% replacement code? I’m looking for a way to provide a message that’s already conditional on %if_special_today%, and could be a string or null. So something like:

%if_open_today%My message here %if_special_today%%notes%%end%, the rest of the message.%end%

Thanks for building this plugin, by the way. Very useful and works well.

Regards

Hi,

Thanks for that update. I have just updated to 4.6.4 and now the group accordions are working correctly on the front end (contrary to my post above, they weren’t working after the 4.6.3 update, though the separate accordions were OK). There are still a couple of issues:

• Selecting multiple separate accordion blocks in the editor list view causes an unresponsive page.
• Existing group accordions are displaying a block error in the editor – “This block contains unexpected or invalid content.”. This is resolved if you “attempt block recovery” but I thought I’d just report it.

I’m using WordPress 6.5.2

Regards

• This reply was modified 7 months, 1 week ago by wamwebdev.

Thanks, Mark, for the quick response and useful info.