Contents

Website Page

Introduction

The Website page type allows you to create rules for multiple websites existing within the same CMS instance.  This can be used for creating mobile websites, or other websites with different domains that should be given specific page branches within the CMS.

Features

The Website page uses a combination of the "Page acting as a link" option, as well as a set of properties specific to that page type.  The Online / Offline status of the page also influences behavior (turns it on / off) - this allows you to set the CMS to "launch" a website automatically if desired.

The Website pages also work in conjunction, to create rules such as a redirect and enable request.  The mobile website example following this section will explain more.

Properties

  • Host Header
    • One or more matching hosts for this Website page; separated by ";"
  • User Agent
    • One or more matching request user agents for this Website page
    • Allows a dash to create an exclusive filter. 
    • For example, -Mozilla would match for all non Mozilla browsers
  • Root Page
    • The integer Page ID of a CMS Page that will be the parent Website root node
    • Can be found by hovering over the breadcrumbs in the Page Overview screen of the CMS
    • You'll see something like ?id=N, where N is the ID you should use
  • Server Mode
    • This influences the HTTP protocol request handling; options include:
      • PC HTML - changes nothing
      • Mobile WAP - adds a Content-Type and Expires (10 minutes) HTTP Header to the response

Mobile Website Example

In this example we create a Mobile website, which uses two Website pages to redirect a mobile request, and enable mobile requests for a specific domain.  The page structure looks like this:

The top node is used as the Website page Page Root ID, and also both nodes act as a Link to that page - in this case the full path: http://m.mocpa.org/content.mobile.aspx

The first Website page node that Redirects, has these properties set:

  • Notice that the Host Header is blank - this means any host header will match.  A host header is sent in an HTTP Request as the "host:" field.  When requesting a domain such as www.google.com, the host field looks like this "host: www.google.com".
  • The User Agent field contains two match values:
    • -Mozilla (any non Mozilla browsers match)
    • iPhone (any iPhone browsers match)

The Website page rules dictate that any request with a matching User Agent, regardless of host, will be redirected to the address the page is acting as a link for.  Note: the page that is being linked to should also be within the Root Page ID, or a redirection loop will manifest.

The second Website page is acting to enable requests that the first Website page is redirecting to:

  • Notice the Host Header field contains m.mocpa.org - this means that this rule only applies to that domain.
  • The User Agent field is the same as the first example; this means that User Agents should match for this rule.

For the mobile website on MOCPA, a new Layout was created in the CMS, which is used for pages under the mobile website.  You can use the Impersonate Layout property in an Article List plugin to share content on a Mobile website, with a mobile layout, while sharing it from the same source, on the main website.

There are a few things to know about Host Headers / Domains for the non-technical user:

  • You should point the domain you want to enable in the CMS to the same web server IP that the CMS is running on.
  • You need to add a Host Header to the IIS website that the CMS is running on.

Other Thoughts

This is an advanced feature and should likely be requested via a support ticket in our tracking system.

Contact this Author: < Nicholas Bott > nick@brycegroup.com