Using master pages

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:
HTML
```
<asp:ContentPlaceHolder ID="plcMain" runat="server"></asp:ContentPlaceHolder>
```
The ContentPlaceHolder control specifies where child pages display their content inside the master page.

Tip: We recommend storing 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.

Creating master pages for ASPX templates

The following code sample shows the markup of a basic master page.

Important

If you installed the Kentico project as a web application, you need to rename the CodeFile attribute on the first line to Codebehind for the code example to be functional.
The CodeFile/Codebehind attribute's value must match the name of the master page's code behind file.
Set the value of the Inherits attribute according to the location and name of the master page file.

HTML

<%@ 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="plcMain" 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:

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.

The CMSPortalManager must be placed inside a standard PlaceHolder⁠ (opens in a new tab) control.

The CMSMenu control is one of the options that you can use to generate a drop-down menu for website navigation.

Writing the master page code behind

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:
C#
```
using CMS.UIControls;
```
Change the class definition to match the following (the name of the class may be different):
C#
```
public partial class CMSTemplates_CorporateSite_Custom : TemplateMasterPage
```
Master pages of ASPX templates must always inherit from the TemplateMasterPage class.
Add the following code into the master page's code behind class:

This code ensures that ASPX templates using the given master page support all required functionality.

Cookie consent

Creating master pages for ASPX templates

Writing the master page code behind

Creating master pages for ASPX templates

Writing the master page code behind