Microsoft KB Archive/898631

= Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows SharePoint Services, in SharePoint Portal Server 2003, and in Office SharePoint Server 2007 =

Article ID: 898631

Article Last Modified on 5/4/2007

-

APPLIES TO


 * Microsoft Office SharePoint Server 2007
 * Microsoft Office SharePoint Portal Server 2003
 * Microsoft Windows SharePoint Services
 * Microsoft Windows SharePoint Services 3.0

-





INTRODUCTION
This article contains information about custom site definitions in Microsoft Windows SharePoint Services 2.0 and in Windows SharePoint Services 3.0. It also contains information about custom area definitions in Microsoft Office SharePoint Portal Server 2003 and in Microsoft Office SharePoint Server 2007. This article lists scenarios that are supported and scenarios that are not supported when you customize site definitions and area definitions.



Supported scenarios
When you work with custom site definitions or custom area definitions, the following scenarios are supported:  To create a custom site definition or a custom area definition, you copy an existing site definition or an existing area definition, and then you rename and modify the new site definition or the new area definition. For more information about this supported method, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/ms868598.aspx

 You modify the .xml files and the .aspx files in a custom site definition or in a custom area definition before you create new sites or new portal areas by using the custom site definition or the custom area definition. You deploy the custom site definition or the custom area definition. That is, you create new sites or new portal areas by using the custom site definition or the custom area definition. To modify the new sites or the new portal areas that you created, you use one or more of the following three supported methods:  You modify the site by using the user interface in SharePoint Portal Server 2003, in SharePoint Server 2007, or in Windows SharePoint Services. You programmatically modify the site or the portal area by using the SharePoint Portal Server object model or the Windows SharePoint Services object model. You modify the site or the portal area by using Microsoft Office FrontPage 2003.</ul>

Note These three methods are also supported methods to use if you want to modify the Default.aspx page in the portal site. Microsoft does not support using other methods to modify the Default.aspx page in the portal site.</li></ul>

Unsupported scenarios
When you work with custom site definitions or custom area definitions, the following scenarios are not supported: <ul> You modify one of the default site definitions or one of the default area definitions that are included in SharePoint Portal Server 2003 or in Windows SharePoint Services.

We do not support modifying the default set of site definitions or area definitions that are installed when you install Windows SharePoint Services and SharePoint Portal Server 2003. Additionally, we do not support modifying the .xml files or the .aspx files in the default site definition or in the default area definition.</li> You modify a custom site definition or a custom area definition after you deploy the custom site definition or the custom area definition.

We do not support modifying a custom site definition or a custom area definition after you create a new site or a new portal area by using that site definition or area definition. Additionally, we do not support modifying the .xml files or the .aspx files in the custom site definition or in the custom area definition after you deploy the custom site definition or the custom area definition.</li> You modify the Webtemp.xml file or the Webtempsps.xml file that is located in the following folder:



With one exception, we do not support modifying the Webtemp.xml file or the Webtempsps.xml file. The exception is the Webtemp.xml file. We support modifying the Webtemp.xml file only if you want to hide a specific template. To hide a specific template, you modify the Hidden parameter of that template in the Webtemp.xml file.</li> We do not support modifying files that reside in the _layouts folder. We reserve the right to update these files in software updates or service packs at a later date. This may cause the custom changes to be lost. You must always back up files that you have changed so that you can restore them at a later date.</li></ul>

<div class="references_section">