Wednesday 20 April 2011 11:46:04 pm

Yes, you should really enable ViewCaching. Usually you should disable it for some complex pages and use template cache-block on thoose pages instead.

As you can see in the docs:

• http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/View-caching

view caching is not generated per user, but rather per set of permissions/preferences:

Please note that eZ Publish creates multiple view caches for the nodes based on roles and user preferences. This means that for example different users (who are logged in, with different permissions/preferences) will be served different caches while anonymous users and users with the same type of permissions/preferences will be served the same file. In other words, when view caching is on, the "view" view of the "content" module will only be run if the system is unable to locate a view-cached version of the result - otherwise a cached version will be inserted in the pagelayout. Please note that the pagelayout itself is not cached by default.

As for your problem, there can be several reason for it so you should investigate it a little bit further and give us some more info.

For example, the cache dir of your frontend siteaccess should be the same as the cache dir for the admin siteacces. Also, view cache for a node is regenerated only when the node is changed and published. Furthermore, the parts of the page that are in pagelayout.tpl do not use view cache. And so on...

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Thursday 21 April 2011 6:47:05 am

Sorry Marko but Franck is right: if you enable the ViewCacheTweak pr_user, ViewCaching will be generated per user. Franck, you can indeed try enabling it, and see how it performs. But it will indeed generate lots of cache files, as a combinatory of user + preferences if you have any. Cache clearing can then be quite heavy. But it is worth a try.

Yes, sorry I didn't notice that part. But this proves that ViewCacheTweak should be documented in the official docs (and not only in Serwatka's hidden gems).

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Thursday 21 April 2011 8:22:32 am

Yes, sorry I didn't notice that part. But this proves that ViewCacheTweak should be documented in the official docs (and not only in Serwatka's hidden gems).

True, true... maybe you could file a documentation issue ? Our doc manager is quite responsive, we keep him well fed !

And don't mind eZ Publish ! You are well documented.

Thanks ! But you're being overly kind here ;-)

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier