I'll try to change that. The problem is as I can't find a predictable way of having the two parts out of sync, I can only try to login/out with a different user until something happend. If it doesn't, it won't mean it won't happend later.
Anyway, the ttl=0 isn't going to be very good for the perf ;)
X+
P.S. Is there a way to debug the cache ? I would like to display informations about what is in the cache (file name?) and what isn't. How do you do that ?
Found one of the problems: the TTL of the cache isn't set, so that's two hours per default. After two hours, the cache isn't cleared, but the variable isn't calculated when the cache is recalculated.
I'll try to play with expiry=expiry ignore_content_expiry or subtree_expiry=subtree_expiry
1) I don't know what's the key to put to have the same one that the standard content.
It looks like it's somehow dependent on the user (eg an admin on the forum here and a regular user aren't going to have the same thing), but it isn't recalculated for every user (can be proven wrong, but I think that would explain the bug of the misterious edit button on the wrong posts in the forum on ez);.
2) The cache is going to be cleared on any item published under it, no matter how deep it is. The standard behaviour is to limit that to the node and its children (deep=1).
Am I wrong ? I never found any definitive descriptions on the rules of the content cache (what are the rules to decide if the cache is used or if it's recalculated) and it behaves differently when the template is compiled or isn't.