Hi Will! I have been looking for a solution for the same problem.
We don't use the STK, but the situation is analogous: "right-sidebar" content is inherited by subpages from their ancestors. In this way different branches can have different sidebar configurations, but it is not normally possible to suppress or remove anything at a deeper level in the tree. We are looking at different ideas for solving this: 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. 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. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Will Scheidegger Gesendet: Dienstag, 31. Mai 2011 17:12 An: Magnolia User-List Betreff: [magnolia-user] STK: Stop paragraph inheritance in extras Dear Magnolians We really like the "show in subpages" feature of extras and promo paragraphs. But now we have received the request to banish some inherited paragraphs from some areas of the site. Of course one could now say: Easy - simply add the paragraphs to each branch where they should be inherited and don't add them where they should not be inherited. Depending on the complexity of the tree this will not be practical however. Can anyone think of an easy way to stop the paragraph inheritance in certain branches? From the usability point of view one should be able to get a limited edit dialog on inherited paragraphs which only contains a "show in page and subpages" checkbox. That should be rather easy... but technically? Where would you store that info that inherited paragraph X should not be displayed on page Y? Any ideas warmly appreciated. Thanks! -will ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
