Hello,

This is a great module!

However, I have some problems with node cache - the boost module works with my other pages, such as views and taxonomy.

My cron runs every 3 minutes (I use FeedAPI for my news sites).

I set the default maximum cache lifetime to 10 minutes. So for views and taxonomy pages, the cache will be 10 minutes.

But for nodes, I want the cache to be longer - 3 hours. So, in page configuration block of node, I set maximum cache lifetime (Scope - Content Container: node) to 3 hours. Everything is fine; the Boost hidden comment at the end of node page is fine.

Therefore, I expected my nodes would be flushed every 3 hours. Surprisingly, the nodes are still flushed every 3 minutes, exactly when the cron runs.

To debug this problem, I set maximum cache lifetime for nodes back to default, which is 10 minutes.

One would expect the nodes to be flushed every 10 minutes. No, the nodes are expired even before they are cached! Below is the boost comment at the end of one node:

In case you want to know, here are my other Boost settings:

Enabled (my site has many subdomains sharing one db)
[x] Do not store the cache file path in the database
[x] Flush all sites caches in this database (singe db, multi-site)
Disabled
[ ] Only allow ASCII characters in path

To Use the Cron Crawler
Enabled
[x] Overwrite the cached file if it already exits
[x] Expire content in DB, do not flush file.
[x] Enable the cron crawler

Thanks for your help!