Is this really the version you are looking for? Kentico Xperience 8.1 Documentation is no longer updated. Use the switcher in the header to choose your product version.
You can use standard ASP.NET master pages (opens in a new tab) together with ASPX page templates. This is a powerful concept that allows you to share content across all pages without having to add it separately to every page template. For example, you can create master pages containing header and footer sections with a logo, navigation menu, search box etc.
Define master pages in files with the .master extension.
You can assign one master page to every ASPX page.
Master pages must always contain one or more ContentPlaceHolder controls:
<asp:ContentPlaceHolder ID="plcMain" runat="server"></asp:ContentPlaceHolder>The ContentPlaceHolder control specifies where child pages display their content inside the master page.
Tip: It is recommended to store master pages in the CMSTemplates folder together with your ASPX page template files. This allows the system to export master pages along with your website when you deploy it to another instance of Kentico.
The following code sample shows the markup of a basic master page.
Important
<%@ Master Language="C#" AutoEventWireup="true" CodeFile="Custom.master.cs" Inherits="CMSTemplates_CorporateSite_Custom" %>
<%=DocType%>
<html xmlns="http://www.w3.org/1999/xhtml" <%=XmlNamespace%>>
<head id="Head1" runat="server">
<title id="Title1" runat="server">My site</title>
<asp:literal runat="server" id="ltlTags" enableviewstate="false" />
</head>
<body class="<%=BodyClass%>" <%=BodyParameters%>>
<form id="form1" runat="server">
<asp:PlaceHolder runat="server" ID="plcManagers">
<ajaxToolkit:ToolkitScriptManager ID="manScript" runat="server" EnableViewState="false" ScriptMode="Release" />
<cms:CMSPortalManager ID="CMSPortalManager1" runat="server" EnableViewState="false" />
</asp:PlaceHolder>
<cms:CMSMenu ID="cmsmenu1" runat="server" Cursor="Pointer" HighlightAllItemsInPath="true" Layout="Horizontal" Padding="0" Spacing="1" />
<asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</form>
</body>
</html>All ASPX page templates require the following manager controls, so it is a good practice to add them onto your website's master page:
Control name | Description |
|---|---|
ajaxToolkit:ToolkitScriptManager | Allows pages to use AJAX components. If required, the CMSPortalManager automatically loads the ToolkitScriptManager, but adding the control directly reduces overhead. |
CMSPortalManager | Ensures the transferring of content between the database and editable regions. Also provides the management functionality needed for portal engine zones.
Note: If your master page contains the CMSPageManager control, remove it and add the CMSPortalManager instead. The CMSPageManager is an older equivalent, which is obsolete and only available for the purposes of backwards compatibility. |
The CMSMenu control is one of the options that you can use to generate a drop-down menu for website navigation.
You need to modify the code behind file of your master pages according to the following steps:
Add a reference to the CMS.UIControls namespace:
using CMS.UIControls;Change the class definition to match the following (the name of the class may be different):
public partial class CMSTemplates_CorporateSite_Custom : TemplateMasterPageMaster pages of ASPX templates must always inherit from the TemplateMasterPage class.
Add the following code into the master page's code behind class:
Adjust the value of the PageManager property according to the ID of the CMSPortalManager control placed on the master page.
protected override void CreateChildControls()
{
base.CreateChildControls();
PageManager = CMSPortalManager1;
}
protected override void OnPreRender(EventArgs e)
{
base.OnPreRender(e);
this.ltlTags.Text = this.HeaderTags;
}This code ensures that ASPX templates using the given master page support all required functionality.