tailieunhanh - Thủ thuật Sharepoint 2010 part 95

Tùy biến và giải pháp trọn gói Một phổ biến pitfall khi giao dịch với SharePoint xây dựng thương hiệu là chủ đề của khách hàng. Trong SharePoint 2003, tuỳ biến được gọi là unghosting và các trang uncustomized được gọi là ghosted, nhưng những điều khoản đã được phản đối từ SharePoint 2007. | 716 CHAPTER 23 BRANDING SHAREPOINT 2010 Customization and Solution Packages One common pitfall when dealing with SharePoint branding is the topic of customization. In SharePoint 2003 customization was known as unghosting and uncustomized pages were referred to as ghosted but those terms have been deprecated since SharePoint 2007. Because branding in SharePoint frequently involves changing out-of-the-box files customization can happen easily and sometimes happens unexpectedly when someone who is inexperienced is working with SharePoint Designer . The following sections describe how these files work in SharePoint. Uncustomized Files When a SharePoint site is created its files are actually instances of files from the SharePoint server s file system that are provisioned into the content database. When a browser visits one of these pages SharePoint looks in the content database and sees that the page is based on a file that resides in the file system retrieving it from the file system and presenting it to the user. These types of files are known as uncustomized files and they represent many out-of-the-box files such as master pages page layouts and content pages. Different SharePoint sites on the same farm can point to the same files on the file system as long as all of them are uncustomized. Customized Files Any time one of these uncustomized files is changed via the SharePoint web user interface or through SharePoint Designer the changed version is stored in the content database and the file becomes customized. When a browser visits a customized page SharePoint looks in the content database sees that the file is customized and simply displays the contents of the file as it was stored in the content database. On the face of things this doesn t seem too bad but from an administrative perspective there can be maintenance issues with customized files. For example if a master page is installed via a SharePoint solution package WSP and activated on a site collection as a .