Installing EPiServer CMS 5 Demo Templates R1
This document describes the necessary steps to install the demo templates for EPiServer CMS 5. The demo templates are installed by using the EPiServer CMS 5 manager.
The following conditions must be met before installing the demo package.
- EPiServer CMS 5 SP2 is required.
- Templates from the public package must be installed. These templates are used by the demo templates.
NOTE If you have modified the templates from the public package, you may receive unexpected results when compiling or viewing the Web site. The demo package installation does not overwrite any files included in the public package.
Installing with EPiServer CMS Manager
- In EPiServer CMS Manager, select the existing EPiServer CMS Web site where the public template package has been installed and select Install Module from the Action menu.
- When asked to select a package to install, browse to and select DemoPackage.zip.
- EPiServer CMS Manager will now copy the templates and dependencies into your EPiServer CMS site. Once the copying is finished, a browser will be opened from where you can install demo content.
- The demo package content contains a new page structure and a new start page. The page ID of your new start page must be updated in web.config. This can be done via EPiServer CMS Manager from the Page Configuration tab when the web.config subnode of your EPiServer CMS Web site is selected. The ID of a page is shown when the mouse is hovered over a page in the page tree in EPiServer CMS Edit mode.
Opening the Demo Project in Visual Studio
- From the File menu in Visual Studio, select Open and then Project/Solution…
- Browse to the root of the site where you installed the demo templates and open DemoTemplates.csproj.
- In Solution Explorer, right-click the solution and select Add and then Existing Project... to include PublicTemplates.csproj in your solution.
You should now be set to compile the demo project.
The blog template is installed with a scheduled job, which is not activated by default. It is recommended that you activate the job to obtain full functionality. The job may take a long time to run on a large blog, so keep this is mind when you decide how often to run the job.
The job updates the values used for the tag cloud and the tag clouds will not be updated if the job is not run. The job also deletes categories and tag pages that are not used.