EPiServer web controls: MenuList and PageTree
Both the MenuList and PageTree control are controls that you’ll come across when building the navigation for your EPiServer site. Usually you’ll start out with the MenuList for the main navigation, and use the PageTree for the sub navigation.
MenuList
Templates
A few of its public properties.
- EnableVisibleInMenu – show pages that have visible in menu unchecked
- EvaluateHasChildren
- ExpandAll
- ExpandNodeIfStartPage
- NumberOfLevels
- PageLink
- PageLinkProperty
- RequiredAccess
- ShowRootPage
- SortBy
- SortDirection
- SortOrder
Examples
By default the MenuList will filter out pages that are not published or that the user has no access to. It will also filter out pages where the property visible in menu is unchecked.
<EPiServer:MenuList runat="server" ID="MainMenu"> <HeaderTemplate><ul id="MainMenu"></HeaderTemplate> <ItemTemplate><li><EPiServer:Property runat="server" PropertyName="PageLink" /></li></ItemTemplate> <SelectedTemplate><li><EPiServer:Property runat="server" CssClass="active" PropertyName="PageLink" /></li></SelectedTemplate> <FooterTemplate></ul></FooterTemplate> </EPiServer:MenuList>
protected override void OnLoad(EventArgs e) { base.OnLoad(e); MainMenu.PageLink = PageReference.StartPage; MainMenu.DataBind(); }
Markup rendered
<ul id="MainMenu"> <li><a href="/en/News/">News</a></li> <li><a href="/en/Events/">Events</a></li> <li><a href="/en/Documents/">Documents</a></li> <li><a class="active" href="/en/Examples/">Examples</a></li> </ul>
Separator template
I don’t use the separator template often. However, sometimes I need to add a class to distinguish the first li element.
<ul id="MainMenu"> <li class="first"><a href="/en/News/">News</a></li> <li><a href="/en/Events/">Events</a></li> <li><a href="/en/Documents/">Documents</a></li> <li><a class="active" href="/en/Examples/">Examples</a></li> </ul>
To do this I use a combination of the header and separator template.
<EPiServer:MenuList runat="server" ID="MainMenu"> <HeaderTemplate><ul id="MainMenu"><li class="first"></HeaderTemplate> <ItemTemplate><EPiServer:Property runat="server" PropertyName="PageLink" /></li></ItemTemplate> <SelectedTemplate><EPiServer:Property runat="server" CssClass="active" PropertyName="PageLink" /></li></SelectedTemplate> <SeparatorTemplate><li></SeparatorTemplate> <FooterTemplate></ul></FooterTemplate> </EPiServer:MenuList>
Sometimes you need to add a few span tags inside the anchors. Mostly just for adding more background images. When this happens you cannot use the EPiServer:Property control for this. Instead you use a combination of regular HTML and data binding syntax.
<ItemTemplate> <li> <a href="<%# Container.CurrentPage.LinkURL %>"> <span class="l"></span><span class="c"><%# Container.CurrentPage.Property["PageName"].ToWebString() %></span><span class="r"></span> </a> </li> </ItemTemplate>
PageTree
The PageTree control is the one I use when I need a more complex navigation than a simple list. It has a lot of templates that help with most things I come a cross. However it can be a little hard at first to know which of the templates to use.
- HeaderTemplate
- FooterTemplate
- ItemTemplate
- ExpandedItemTemplate
- ExpandedTopTemplate
- IndentTemplate
- SelectedExpandedItemTemplate
- SelectedExpandedTopTemplate
- SelectedItemTemplate
- SelectedTopTemplate
- TopTemplate
- UnindentTemplate
Both MenuList and PageTree inherit from PageTreeData, which means they have almost identical public properties. They also share the same default filtering settings.
I think the easiest way to show you what the different templates do is with an example.
<EPiServer:PageTree ShowRootPage="false" runat="server" id="SubMenu"> <HeaderTemplate> <div id="SubMenu"><!-- HeaderTemplate --> </HeaderTemplate> <IndentTemplate> <ul> <!-- IndentTemplate --> </IndentTemplate> <ItemHeaderTemplate> <li> <!-- ItemHeaderTemplate --> </ItemHeaderTemplate> <ItemTemplate> <EPiServer:Property PropertyName="PageLink" runat="server" /> <!-- ItemTemplate --> </ItemTemplate> <ExpandedItemTemplate> <EPiServer:Property runat="server" PropertyName="PageLink" CssClass="ExpandedItemTemplate" /> <!-- ExpandedItemTemplate --> </ExpandedItemTemplate> <ExpandedTopTemplate> <EPiServer:Property runat="server" PropertyName="PageLink" CssClass="ExpandedTopTemplate" /> <!-- ExpandedTopTemplate --> </ExpandedTopTemplate> <SelectedItemTemplate> <EPiServer:Property CssClass="SelectedItemTemplate" PropertyName="PageName" runat="server" /> <!-- SelectedItemTemplate --> </SelectedItemTemplate> <SelectedExpandedItemTemplate> <EPiServer:Property runat="server" PropertyName="PageLink" CssClass="SelectedExpandedItemTemplate" /> <!-- SelectedExpandedItemTemplate --> </SelectedExpandedItemTemplate> <SelectedExpandedTopTemplate> <EPiServer:Property runat="server" PropertyName="PageLink" CssClass="SelectedExpandedTopTemplate" /> <!-- SelectedExpandedTopTemplate --> </SelectedExpandedTopTemplate> <ItemFooterTemplate> </li> <!-- ItemFooterTemplate --> </ItemFooterTemplate> <UnindentTemplate> </ul> <!-- UnindentTemplate --> </UnindentTemplate> <FooterTemplate> </div> <!-- FooterTemplate --> </FooterTemplate> </EPiServer:PageTree>
To connect our MainMenu (MenuList) with our newly created SubMenu (PageTree), we’ll use MenuLists OpenTopPage property (returns a PageReference to the open top page).
public MenuList MenuList { get { return _menuList; } set { _menuList = value; } } protected override void OnLoad(EventArgs e) { base.OnLoad(e); SubMenu.PageLink = MenuList.OpenTopPage; SubMenu.DataBind(); }
We need to connect the main menu with the sub menu. Set the MenuList property in your master page.
// The registered user controls for the main and sub menu ... <public:MainMenu runat="server" ID="MainMenu" /> ... <public:SubMenu runat="server" ID="SubMenu" />
protected override void OnLoad(System.EventArgs e) { base.OnLoad(e); if (SubMenu != null && MainMenu != null) { SubMenu.MenuList = MainMenu.MenuList; } ... }
The markup rendered should look something like this.
<div id="SubMenu"><!-- HeaderTemplate --> <ul> <!-- IndentTemplate --> <li> <!-- ItemHeaderTemplate --> <a href="/en/Examples/File-explorer/">File Explorer</a> <!-- ItemTemplate --> </li> <!-- ItemFooterTemplate --> <li> <!-- ItemHeaderTemplate --> <a href="/en/Examples/Registration/">Registration</a> <!-- ItemTemplate --> </li> <!-- ItemFooterTemplate --> <li> <!-- ItemHeaderTemplate --> <a href="/en/Examples/Subscribe/">Subscribe</a> <!-- ItemTemplate --> </li> <!-- ItemFooterTemplate --> <li> <!-- ItemHeaderTemplate --> <a href="/en/Examples/Demo/">Demo</a> <!-- ItemTemplate --> </li> <!-- ItemFooterTemplate --> <li> <!-- ItemHeaderTemplate --> <a href="/en/Examples/Search/">Search</a> <!-- ItemTemplate --> <li> <!-- ItemHeaderTemplate --> <a class="ExpandedTopTemplate" href="/en/Examples/Contact/">Contact</a> <!-- ExpandedTopTemplate --> <ul> <!-- IndentTemplate --> <li> <!-- ItemHeaderTemplate --> <a class="ExpandedItemTemplate" href="/en/Examples/Contact/Test/">Test</a> <!-- ExpandedItemTemplate --> <ul> <!-- IndentTemplate --> <li> <!-- ItemHeaderTemplate --> <a class="SelectedExpandedItemTemplate" href="/en/Examples/Contact/Test/Test2/">Test2</a> <!-- SelectedExpandedItemTemplate --> </li> <!-- ItemFooterTemplate --> </ul> <!-- UnindentTemplate --> </li> <!-- ItemFooterTemplate --> </ul> <!-- UnindentTemplate --> </li> <!-- ItemFooterTemplate --> </ul> <!-- UnindentTemplate --> </div> <!-- FooterTemplate -->
I recommend clicking around a little to see when the different selected templates kick in.
[...] EPiServer web controls: MenuList and PageTree [...]
[...] used in this code, I recommend checking out my blog posts: EPiServer web controls: Property and EPiServer web controls: MenuList and PageTree. <%@ Control Language="C#" AutoEventWireup="true" [...]
[...] in a previous blog post written about the PageTree control. That post describes it pretty well, so I’m not going to repeat it here. Instead I’ll [...]
[...] EPiServer web controls: MenuList and PageTree [...]
[...] EPiServer web controls: MenuList and PageTree [...]
Hi Frederik
Love your articles – better than the official EPiServer documentation by a long way!
In the above example, when you get to the PageList control you refer to the MenuList object as ‘MenuList’ when I think it would probably be correct to refer to it as ‘MainMenu’ as that is the instance that you created with the MenuList object in the first MenuList example?
As you can see we’re learning very very slowly here
Alex
Hi Alex
Thanks for the feedback! I’ve updated the post now (was some code missing).
Frederik
Hi Frederik
That makes much more sense
I was assuming that in order for the PageTree object to know the ‘OpenTopPage’ of the MenuList it would use the MenuList object we created for the Primary Navigation (called ‘MainMenu’)…
However the code you’ve added makes total sense as you simply create a new MenuList object, a tad confusingly also called ‘MenuList’ [nb: EPiServer do the same in their example so it must be standard confusing practice!] and then ask that to tell us it’s ‘OpenTopPage’ instead.
Let me know if I’m reading the code wrong here!
Thanks again
Alex
We’re using the MenuList controller you created for your main navigation by making it available through a publich property (MenuList), which we then use to set SubMenu’s public MenuList property. We then set SubMenu’s PageLink property to the main navigations OpenTopPage (which holds a PageReference to the “top” page that the user is on).
Hope this helps.
Frederik