Upgrade web templates for SharePoint
Learn about updating customized SharePoint 2010 web templates for use in SharePoint after a self-service upgrade. SharePoint has significantly changed the underlying components it uses to render the appearance of SharePoint sites. For customizations made to default components in SharePoint 2010, these new changes include styles, page layouts, master pages and themes.
This article provides guidance for updating your web templates so that they work with the new framework.
Possible behavior after a self-service site upgrade
When you upgrade a server from SharePoint 2010 to 2013, site collection administrators are shown a link that lets them upgrade their sites gradually, or upgrade all sites in the site collection at once. Then users can upgrade and test those sites that contain customizations. Some of the problems that users might encounter after an upgrade include:
Branding applied to sites has been changed, or is missing altogether.
Custom components don't render correctly.
Pages don't render at all, and the users receive unknown errors from SharePoint.
Features that are enabled by default are disabled after upgrade.
Recommendations for upgrading sites
When you upgrade sites, we generally recommend that you use the evaluation site to install and test your components for compatibility and performance.
The following sections detail what you need to update in the web template.
Update master page references
After an upgrade to SharePoint, any custom master page references that your web template contains will be set to the default master page named seattle.master. If you customized the default master page in SharePoint 2010, you will need to change the reference to that custom page in order for your customizations to appear.
Update available features
When you upgrade a site to use SharePoint web templates, features that are attached to the template by default are removed. As a consequence, the available functionality of an upgraded web template is reduced.
To add the default functionality back to the template, you must modify the Onet.xml file for the web template that contains the feature list. To add the default features back to your web template, do the following:
To add default features back to the web template
Open the Visual Studio project that contains the web template you want to update.
In Solution Explorer, find the Onet.xml file in your project.
Open Onet.xml in an XML editor.
Make sure that each of the features in Table 1 are contained in the WebFeatures section.
Table 1. Default web template features
DisplayName | Feature ID |
---|---|
AccSvcAddAccessApp |
d2b9ec23-526b-42c5-87b6-852bd83e0364 |
AnnouncementsList |
00bfea71-d1ce-42de-9c63-a44004ce0104 |
BaseWeb |
99fe402e-89a0-45aa-9163-85342e865dc8 |
BizAppsListTemplates |
065c78be-5231-477e-a972-14177cc5b3c7 |
ContactsList |
00bfea71-7e6d-4186-9ba8-c047ac750105 |
ContactsList |
00bfea71-7e6d-4186-9ba8-c047ac750105 |
CustomList |
00bfea71-de22-43b2-a848-c05709900100 |
DataConnectionLibrary |
00bfea71-dbd7-4f72-b8cb-da7ac0440130 |
DataSourceLibrary |
00bfea71-f381-423d-b9d1-da7a54c50110 |
DiscussionsList |
00bfea71-6a49-43fa-b535-d15c05500108 |
DocumentLibrary |
00bfea71-e717-4e80-aa17-d0c71b360101 |
EventsList |
00bfea71-ec85-4903-972d-ebe475780106 |
EventsList |
00bfea71-ec85-4903-972d-ebe475780106 |
ExternalList |
00bfea71-9549-43f8-b978-e47e54a10600 |
FollowingContent |
a7a2793e-67cd-4dc1-9fd0-43f61581207a |
GanttTasksList |
00bfea71-513d-4ca0-96c2-6a47775c0119 |
GettingStarted |
4aec7207-0d02-4f4f-aa07-b370199cd0c7 |
GridList |
00bfea71-3a1d-41d3-a0ee-651d11570120 |
HierarchyTasksList |
f9ce21f8-f437-4f7e-8bc6-946378c850f0 |
IPFSWebFeatures |
f9ce21f8-f437-4f7e-8bc6-946378c850f0 |
IssuesList |
00bfea71-5932-4f9c-ad71-1557e5751100 |
LinksList |
00bfea71-5932-4f9c-ad71-1557e5751100 |
MBrowserRedirect |
d95c97f3-e528-4da2-ae9f-32b3535fbb59 |
MDSFeature |
87294c72-f260-42f3-a41b-981a2ffce37a |
MobilityRedirect |
f41cc668-37e5-4743-b4a8-74d1db3fd8a4 |
MySiteMicroBlog |
ea23650b-0340-4708-b465-441a41c37af7 |
NoCodeWorkflowLibrary |
00bfea71-f600-43f6-a895-40c0de7b0117 |
PictureLibrary |
00bfea71-52d4-45b3-b544-b1c71b620109 |
PremiumWeb |
0806d127-06e6-447a-980e-2e90b03101b8 |
PromotedLinksList |
192efa95-e50c-475e-87ab-361cede5dd7f |
ReportListTemplate |
2510d73f-7109-4ccc-8a1c-314894deeb3a |
SiteFeed |
15a572c6-e545-4d32-897a-bab6f5846e18 |
SiteFeedController |
5153156a-63af-4fac-b557-91bd8c315432 |
SurveysList |
00bfea71-eb8a-40b1-80c7-506be7590102 |
TaskListNewsFeed |
ff13819a-a9ac-46fb-8163-9d53357ef98d |
TasksList |
00bfea71-a83e-497e-9ba0-7a5c597d0107 |
TeamCollab |
00bfea71-4ea5-48d4-a4ad-7ea5c011abe5 |
WebPageLibrary |
00bfea71-c796-4402-9f2f-0eb9a6e71b18 |
WikiPageHomePage |
00bfea71-d8fe-4fec-8dad-01c19a6e4053 |
WorkflowHistoryList |
00bfea71-4ea5-48d4-a4ad-305cf7030140 |
workflowProcessList |
00bfea71-2d77-4a75-9fca-76516689e21a |
WorkflowServiceStore |
2c63df2b-ceab-42c6-aeff-b3968162d4b1 |
WorkflowTask |
57311b7a-9afd-4ff0-866e-9393ad6647b1 |
XmlFormLibrary |
00bfea71-1e1d-4562-b56a-f05371bb0115 |
- Save your changes, and deploy as you would normally.
Note
You may also need to activate these features in the Central Administration utility.
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for