The viewcache takes roles into account (users with the same roles share the same viewcache. It is not possible to turn this behavior off.
However, if 90% of your users are logged in, the view cache for those users should quite quickly be generated. I don't understand the need for generating the viewcache with a crawler then......
I am not sure it is a good advice, but it might be worth trying: It is also possible to use cache-blocks in view templates as well. You should then probably use the ignore_content_expiry to prevent all cacheblocks (used in view templates) from being expired whenever something new is published. URL could be used as key and maybe subtree_expiry as a mechanism for managing clearing of cache. Also the "expiry" should be used to increase the TTL of the cache file.
see http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_functions/miscellaneous/cache_block for cache-block documentation
You must be logged in to post messages in this topic!
