Hi Richard
On 01.06.2011, at 16:20, Unger, Richard wrote: > 1. Inherit differently: don't inherit all the sidebar content for all > ancestors, but instead find the closest ancestor (including self) with > sidebar content, and inherit only that. Allow definition of new sidebar > content in the current page, which then overrides any inherited content. > In this way, content is inherited, but a new sidebar definition can be > created in any page, which is then shown in all descendant pages. > By Providing an empty "dummy content" paragraph to add to sidebars, editors > can "clear" the sidebar by creating a new sidebar with only the dummy content. > This is where we are right now. We've done this before. It's pretty much the do-or-die game: either inherit everything or as soon as you add custom content nothing get's inherited anymore. However I now like the STK way much better which inherits only the paragraphs which are marked correspondingly and also allows the users to add additional paragraphs on the subpages. > 2. Provide additional "override" paragraphs. The idea is basically this: > inherit all the sidebar content from the ancestors. For each paragraph > inherited, read additional fields which are stored in the current page. The > additional fields define whether the inherited paragraph should be shown in > this page or not. Provide an additional edit-bar for each sidebar content, > with which the editor can edit the additional fields in the current page for > the given content. > I would definitely store this info in the current page, rather than with the > sidebar content. That's along the ways I'm thinking now. I think that would be feasible, but for our situation probably to much of a hassle right now. Also my thanks to Jan for your replies. Deactivating the extras area won't work for us. But one could think about configuring the extras area on a per-page basis to turn of inheritance there. That would be much easier (but also much more limited) than marking each inherited paragraph which should be hidden in some way. -will ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
