Not sure it should expire. You're not modifying the object that is related to your blog, but one of its children...
I am in fact more surpries about the cache getting cleared when you remove the user from teh AUTHORS folder ;-)
I suspected I would get an answer like this... :)
But, look at this logic:
when I add a user under AUTHORS I'm changing something about this user object so this triggers the cache clearing mechanism for the parents of the user
since the AUTHORS now is a parent of the user object, it's cache clearing mechanism is tiggered
and since I enabled reverse_attribute clear relation type, the cache clearing for AUTHORS should trigger the cache clearing for the Blog frontpage
It sounds logical to me...
--
Nothing is impossible. Not if you can imagine it!
But you need to take into account recursion: if you expire the cache of the parent node in a recursive manner, he will expire his own parent and so on...
I'm not really sure this is clear cut, but whenever a node (other than the currently edited one) is expired based on either standard expiry rules or smart view cache ones, eZ does not recurse cache expiration.
Principal Consultant International Business
Member of the Community Project Board
You must be logged in to post messages in this topic!