Consider the following scenario: you setup a new Sitecore template (or branch) which you want to add anywhere in the tree without setting any sitecore insert options
The reason you may want to do this is you have several templates in place throughout the tree, if the insert options can’t be inherited then you would need to update a lot of standard values!
If you dont use the rule engine for this (see this post) you can still achieve the same solution.
In the following example, we want the user to be able to add a Generic Form anywhere under the home node of the site.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
using System; using System.Linq; using ###.DataSource.Cms; using Sitecore.Data; using Sitecore.Pipelines.GetMasters; namespace ###.Domain.Cms.Specialization.Processors.GetMasters { /// <summary> /// Allow content editor to add a generic form anywhere under the home node /// </summary> public class GetGenericForm { public void Process(GetMastersArgs args) { if (args.Item.ID.Guid == ItemKeys.Home || args.Item.Axes.GetAncestors().Any(a => a.ID.Guid == ItemKeys.Home)) { args.Masters.Add(Sitecore.Context.ContentDatabase.GetItem(new ID(TemplateKeys.GenericForm))); } } } } |
Which then needs patching into the uiGetMasters pipeline (/App_Config/Include):
|
1 2 3 4 5 6 7 8 9 10 11 |
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <processors> <uiGetMasters> <processor patch:after="processor[@type='Sitecore.Pipelines.GetMasters.RunRules, Sitecore.Kernel']" type="###.Domain.Cms.Specialization.Processors.GetMasters.GetGenericForm, ###.Domain.Cms" /> </uiGetMasters> </processors> </sitecore> </configuration> |
After the talk at the Bristol Sitecore User Group yesterday, Raul demonstrated the rule engine for this kind of thing – the exact same problem can be solved without any code 🙂
You need to set yourself up a rule eg:
Note, one step remains – you need to select the root item.