Description
We encountered an issue where we had deployed a custom master page but not all of the sites in the site collection were recognizing the changes.
First, a little background on what we had done:
We opened the home page (a publishing site) of a SharePoint V3 site collection in SharePoint Designer. Next we copied the default.master and renamed the copy to custom.master. In custom.master we changed the logo in the header of the page to a custom image. Next, we opened the site collection in Internet Explorer and in Site Settings > Look and Feel > Master Page changed the Site Master page to custom.master. We clicked OK to save changes and reviewed the top level site. The header logo was updated. Next we reviewed another top level site, but these sites did not have the new header logo.
Solution
Site Settings > Look and Feel > Master PageSite Master Page:
* Select Specify a master page to be used by this site and all sites that inherit from it.
* Select custom.master from the drop down selection.
* Check off Reset all subsites to inherit this Site Master Page Setting
Site Settings > Look and Feel > System Master PageSite Master Page:
* Select Specify a master page to be used by this site and all sites that inherit from it.
* Select custom.master from the drop down selection.
* Check off Reset all subsites to inherit this Site Master Page Setting
The way this works is that the "Master Page" setting is used by publishing sites. The "System Master Page" is used by non-publishing sites. The terminology used in SharePoint V3 and SharePoint Designer are not intuitive, although the descriptions on the Site Settings > Look and Feel > Master Page do help a bit.
Thanks Marc Anderson for taking the time to read the small print and explain this out loud.
For further explanation, refer to Kathy's blog post, SharePoint Designer Snippets: Working with Master Pages, which helps clarify any confusion regarding this topic.
To expand on this blog post, I think of the Site Settings > Look and Feel > Master Page like this:
* Master Page = Custom Master Page = Publishing Sites
* System Master Page = Default Master Page = Non-Publishing Sites
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2007
(80)
-
▼
March
(12)
- Visual Studio 2005: Display Line Numbers Globally
- Visual Studio 2005: Error: Setup Failed
- SharePoint V2: Error: HTTP 404: File Not Found I...
- SharePoint V3: Configuring Custom NewForm.aspx, E...
- Links: SharePoint V3: High Availability
- SQL Server: Query Server Name, Edition, Product L...
- SharePoint V3: Subtle Behaviors with Custom Site ...
- SharePoint V3: Master Page Not Inherited By Non-P...
- SharePoint Designer Workflow: It's Just a Facilit...
- SharePoint V3: Error: Excel Services: Access De...
- SharePoint Intranets, Evolving Beyond Department S...
- Effective Security Model for SharePoint
-
▼
March
(12)
Events / Conferences / User Groups
- AIIM Conference
- Boston Area SharePoint User Group
- Boston Azure User Group
- Collaborate
- DevConnections
- DevIntersection
- Enterprise Search Summit
- Microsoft Build
- Microsoft SharePoint Conference
- Microsoft TechEd
- New England ASP.NET Professionals User Group
- New England Oracle Applications User Group
- Oracle Applications User Group (OAUG)
- Oracle OpenWorld
- PeopleSoft Government Contractor Special Interest Group
- PeopleSoft Southern New England Users Group
- Quest International Users Group
- SharePoint Saturday
- SPTechCon
- SQL PASS
- SQL Saturday
- Startup Weekend
1 comment:
I know this is an older article, but I'm wondering what you do if MASTER PAGE doesn't appear under "Look and Feel". I am running WSS 3.0
Post a Comment