学步园

The documentation for creating site definitions and provisioning for MOSS 2007 Publishing sites is almost non-existing on MSDN.

My first suggestion is to look at the out of the box publishing site definition “BLANKINTERNET”.
This site definition is located in the 12 hive: C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/TEMPLATE/SiteTemplates/BLANKINTERNET
The template configuration for this site definition can be found in the file: C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/TEMPLATE/1033/XML/webtempsps.xml. Note that only the part in the element <Template Name="BLANKINTERNET" ID="53">... is applicable.

I will post a more complete article on how to create your own publishing site definition with custom page layouts, master pages and content types later when I have more time... For now I’ll just go over the elements on which I had most work getting them to work. It’s actually not quite hard as long as you know how to do it.

1. Make sure the required onet.xml and webtemp*.xml files are copied to the right directories

Your onet.xml file should go into the folder C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/TEMPLATE/SiteTemplates/[YOURSITEDEF]/XML
Provisioned files may go one level higher: C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/TEMPLATE/SiteTemplates/[YOURSITEDEF]

webtemp*.xml file should go into: C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/TEMPLATE/1033/XML

2. onet.xml: referencing the correct site features

In order to get the publishing site features activated when you create a site based on your custom site template, make sure all required publishing site and web features are activated. Features at site level are defined and activated at the site collection level. Web features will be activated for every new web you create using this configuration.

Configuration>

3. The right syntax for AvailablePageLayouts and AvailableWebTemplates

The Publishing Web Feature (ID 22A9EF51-737B-4ff2-9346-694633FE4416) contains some properties that allow us to specify master pages, page layouts and available web templates.

The syntax for specifying the values in the onet.xml file is not documented (as far as I could find).

AvailablePageLayouts

Your custom page layout should be deployed to the site collection by activating a page layout provision feature for example.

For a single page layout, the syntax is available in the BLANKINTERNET site definition:

Property Key="AvailablePageLayouts" Value="~SiteCollection/_catalogs/masterpage/mypagelayout.aspx"/>

For defining multiple AvailablePageLayouts I found that the separator is : (colon) by looking at the Search site definition (SRCHCEN):

Property Key="AvailablePageLayouts" Value="~SiteCollection/_catalogs/masterpage/
mypagelayout.aspx:~SiteCollection/_catalogs/masterpage/mypagelayout2.aspx"/>

AvailableWebTemplates

If you want to restrict the list of available web templates you can do this with the AvailableWebTemplates property.

Property Key="AvailableWebTemplates" Value="*-MYSITEDEF#1"/>

For specifying multiple web templates, I found the syntax thanks to a post in a forum: http://www.eggheadcafe.com/software/aspnet/29217247/availablewebtemplates-key.aspx

Someone found the syntax by looking at the Microsoft.SharePoint.Publishing.PublishingWeb class using reflector. Snippet from the solution mentioned in the forum:

AvailableWebTemplates Key Format is:
LCID-[sitetemplatename][#sitetemplatenumber];LCID-[sitetemplatename]
[#sitetemplatenumber];LCID-[sitetemplatename][#sitetemplatenumber]

1033-BLANKINTERNET#1;1049- BLANKINTERNET #1;*- BLANKINTERNET #2

*-BLANKINTERNET#2 - ALL Languages
(Thanks Sorgi?)

So if we know the separator is ; (semi-colon) the element should look like:

Property Key="AvailableWebTemplates" Value="*-MYSITEDEF#1;*-MYSITEDEF#3"/>

Please see the Microsoft.SharePoint.Publishing.PublishingWeb class reference on MSDN: http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.publishing.publishingweb.aspx. Looking at the class properties will also give you more insight into how to use the properties in the onet.xml file.

4. Using multiple configuration and hiding them in the UI

The webtemp*.xml file may contain multiple template configurations. You may make some of these hidden for example if you want to create those specific sites via code only. Use for Hidden="TRUE" this.

webtemp*.xml snippet:

... snippet:-->

Template Name="MYSITEDEF" ID="10020">

Configuration ID="0" Title="My site template" Hidden="FALSE" ImageUrl="/_layouts/1033/images/img.gif" Description="This is a publishing site template" SubWebOnly="FALSE" DisplayCategory="My own category">

Configuration>

Configuration ID="1" Title="My site template – Autocreated contact section" Hidden="TRUE" ImageUrl="/_layouts/1033/images/img.gif" Description="This template is used by code to generate the contact site." SubWebOnly="TRUE" DisplayCategory=" My own category" VisibilityFeatureDependency="97B7C2D9-51E6-4add-844E-D133D25B7B15">

Configuration>

... snippet end-->

5. Making your own content types available

When you use custom page layouts chances are you are also using custom content types. By using the AvailablePageLayouts properties your custom page layouts become available but there is still a problem. By default the Pages library only contains the MOSS publishing content types, as you can see in this screenshot:

Users will be available to create new pages using your page layout but all the custom properties you use in their related content types are missing. The page layout may not show any property in edit mode. If you go the Site Settings > Site content types, you will see your custom content types and their site columns.
You may manually add the content types to the Pages library by going to Site Actions > Site Settings > Modify Pages Library Settings. Choose “Add from existing site content types” and choose the content types. Once this is done your custom page layouts should start working normally.
Doing the manual setting is one possibility but having to do this manually for every new web is not really an option.
I ended up creating a web feature that is automatically activated by the site template definition. My feature contains a ReceiverAssembly and class in which I add the desired content types to the Pages library.

Code snippet:

pageLib = Microsoft.SharePoint.Publishing.PublishingWeb.GetPagesListName(web);

SPContentTypeCollection allContentTypes = web.Site.RootWeb.AvailableContentTypes;

SPContentTypeCollection usedContentTypes = web.Lists[pageLib].ContentTypes;

(SPContentType contentType in allContentTypes)

{

if (contentType.Hidden==false && contentType.Group.ToLower().StartsWith("Mygroupname ") == true)

//if the content type does not yet exist in the library add it:

{

if (usedContentTypes[contentType.Name] == null)

{

web.Lists[pageLib].ContentTypes.Add(contentType);

}

}

}

That’s it for me!