There is already implementation in trunk http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-core/src/main/java/info/magnolia/cms/util/ExtendingContentWrapper.java ... the main concern for this implementation was the fact that it might introduce conflict if you want to extend the node on the same level that is called "override" so the final implementation might use different keyword (e.g. mgnl:override)
I thought we planned to deliver that feature already with 4.4, but perhaps I was wrong. Philipp? related jira issue is: http://jira.magnolia-cms.com/browse/MAGNOLIA-3259 ... 0 votes, 0 watches ... perhaps it is not so interesting :D Jan On Nov 5, 2010, at 4:51 PM, Unger, Richard wrote: > > Hi! > > Ok, I found a solution on this issue: > > Simply not to configure any templates under availability on the master site, > and only configure the needed templates on each site variant. > > However, a solution using extends would be cleaner for us. Are there any > plans to develop the "extends" functionality of content2bean with respect to > allowing overrides at some locations? > > Regards from Vienna, > > Richard Unger > > > > -----Ursprüngliche Nachricht----- > Von: Unger, Richard > Gesendet: Freitag, 05. November 2010 16:17 > An: Magnolia User-List > Betreff: AW: [magnolia-user] Template availability > > Hi! > > Follow-On Question about template availability: > > Generally I understand the template availability mechanism as explained by > Antti. > Class TemplateAvailability determines which of the set of templates are > available to the user, based on: > - the template category > - the configured availability under site definition -> > mysite/templates/availability/templates > > My Question is about the availability and Site Definitions. We are trying to > create a master site definition, with "site variants" based on this master > definition, using the "extends" feature. > > If we configure the availability on the master site, and then configure a > different availability on a site variant, magnolia always offers all > templates for selection: those from the master site, plus the additional ones > from the site variant. If we remove a template availability entry in the site > variant, the template is still available if configured in the master site. > > In other words, the extends features seems to work only in an "additive" way > - the available templates can only be increased, not reduced. > > Is this analysis correct? > > Is there any way you could suggest that will achieve site variants extending > the master definition, but that have their own template availability > definitions? > > Thanks! > > Regards from Vienna, > > Richard > > > -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[email protected]] Im Auftrag von Antti Hietala > Gesendet: Mittwoch, 03. November 2010 16:44 > An: Magnolia User-List > Betreff: Re: [magnolia-user] Template availability > > > Template availability in STK is controlled at two levels: > > 1) Site definition controls site-wide template availability. The "default" > site definition makes templates available to all sites. See Templating Kit > > Site Definitions > /default/templates/availability. Your site definition can > extend the default. Here you can also restrict template access to certain > roles, see stkGlossary for example. > > 2) Categories determine which template may be assigned to a page. Your > question about news pertains to this level of control. STK has five > out-of-the-box template categories (examples in parentheses): > - home (stkHome) > - functional (stkRedirect) > - section (stkSection) > - feature (stkNewsOverview) > - content (stkArticle, stkNews) > > Availability plays out like this: > - Categories allowed at root level: home, functional > - Categories allowed at root + 1 level: functional, section, feature > - Categories allowed at root + 2 level and below: functional, section, > feature, content > > The dependencies between categories are not configurable (yet) but you may be > able to override the behavior. See classes > info.magnolia.module.templating.Template and > info.magnolia.module.templatingkit.templates.STKTemplate. > > Search also the user list archives, e.g. > http://old.nabble.com/STK%3A-hierarchy-of-templates-defined-where--td25508007.html#a25508007. > > > --Antti > > > On Nov 3, 2010, at 1:32 PM, Jon RINGWOOD PSE 55500 wrote: > >> Can anyone tell me how template types are restricted in the Website? For >> example, in the news-overview folder you can only select certain template >> types for new pages. Similarly the about page can only be set to a >> predetermined list of templates. How is this done? >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> -- >> This email and any other accompanying document (s) contain information from >> Kent Police, which is confidential or privileged. The information is >> intended to be for the exclusive use of the individual(s) or bodies to whom >> it is addressed. The content including any subsequent replies could be >> disclosable if relating to a criminal investigation or civil proceedings. If >> you are not the intended recipient, be aware that any disclosure, copying, >> distribution or use of the contents of this information is prohibited. If >> you have received this email in error, please notify us immediately by >> contacting the sender or telephoning 01622 690690. >> > > > > ---------------------------------------------------------------- > 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]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
