|
Tuesday 26 January 2010 3:26:53 am
Hi Sander, Having the left menu in the view template means the menu will be view-cached, on a per-node basis. This means that whenever you want to change the content of your menu (adding a menu entry for example), you will need to clear all nodes' view cache...which is not recommended :) Another con is that regenerating a node's view cache will take longer for it needs to compute the left menu on top of its own content. Now that the persistent_variable exists and works fine, information passing between view templates and the pagelayout is actually pretty easy. This can allow for a highly contextual menu. In terms of performance optimization, cache-blocks can be used around the menu, using the appropriate keys and options to have it expire when it is required. As to the use of menu.ini, it is no dogma. It is indeed shipped with eZ Publish, but its usage is, as most of the other solutions shipped (eZ Flow, eZ Webin), simply an example onhow to best use the features. You may decide to not use it, alleviating some ini configuration.
Hope it helps. Interested in knowing how you actually solved the issue (as your initial post dates a bit).
Cheers and thanks for triggering this discussion,
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
eZ Publish Community on twitter: http://twitter.com/ezcommunity
t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye
|
