Sharepoint 2010 - master page mods not taking effect

dgmoore1
dgmoore1 used Ask the Experts™
on
I made a copy of my v4.master, changed the PermissionsString for idNavLinkViewAll to hide the "All Site Content" link, and changed the width of the Quick Links list from the default 150px to 250px. I then saved the copy, checked it back in, published it, approved the changes, and set it as the site default master.

However, when I open the site's home page none of the changes I made in the master are in effect - nothing has changed. All users can still see "All Site Content" and the width of the quick link list is still 150px.

Any suggestions would be appreciated.
Thanks
Dave
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
If the custom master page has an error in it, SharePoint will use the default custom master page to render the page rather than the custom master page.

Have you verified (by looking at the source, etc.) that your custom master page is being used? Maybe add an HTML comment you can search for in the source.

Author

Commented:
I have verified under Site Settings | Look and Feel |Master Page that the correct master is being used. When I reset it back to the original v4.master there is no change in the appearance or behavior of the pages, as if the original master and my copy are identical. But examination of both shows that the changes are present in the custom version and not in the original. I'm stumped so far. I'm pretty sure there are no errors in the custom master - I only substituted "ManageWeb" in the idNavLinkViewAll PermissionsString, and changed "150px" to "250px" in the style for the Quick Link list width.

Commented:
Can you please add an HTML comment to your new master page, republish and approve? Then visit a page using the new master page, and view the HTML source. If you do not see the HTML comment in the source, your new master page is not being used. Let's start here, and see if your new master page is even being rendered.
How to Generate Services Revenue the Easiest Way

This Tuesday! Learn key insights about modern cyber protection services & gain practical strategies to skyrocket business:

- What it takes to build a cloud service portfolio
- How to determine which services will help your unique business grow
- Various use-cases and examples

Author

Commented:
OK - I'll try that. Thanks

Author

Commented:
OK - I added an html comment to the master and verified in the source of one of the pages that the master in question is the one being used. I copied the original v4.master and made just two changes: I changed the PermissionsString for idNavLink to "ManageWeb" and I change the width of the quick launch from 155px to 255px.

Neither of these changes are taking effect - All Site Content is still visible to all, and the width of the Quick Launch remains at 155px

Commented:
OK great. Can you post the master page to EE?

Author

Commented:
OK - here's the file in question
v4-copy-1-.master

Commented:
OK - I am still looking at this. I did a visual diff between the OOTB v-4 master page, and the file you posted. See the attached report. Were you expecting to see this much difference?

I was able to quickly apply the master page and get it to render. I will look at it more.
differences.html
Commented:
Here are the changes I made to a copy of a v4.master page to accomplish what you are after...

First, for the requirement to resize the Quick Launch area, add the following CSS before the closing </head> tag in your master page:

<style type="text/css">
/* Set the width of the Quick Launch */
BODY #s4-leftpanel {
	width:250px;
}
/* Compensate for the custom width on the Quick Launch */
.s4-ca {
	margin-left:250px;
}
</style>

Open in new window


For the second requirement to hide the View All Content link except for Site Managers, you need to edit the master page in a couple of places.

Search for the following block, and make the change to the permission level as seen in line 9 of the following snippet. This will hide the like in the Site Actions menu.

<SharePoint:MenuItemTemplate runat="server" id="MenuItem_ViewAllSiteContents"
	Text="<%$Resources:wss,quiklnch_allcontent%>"
	Description="<%$Resources:wss,siteactions_allcontentdescription%>"
	ImageUrl="/_layouts/images/allcontent32.png"
	MenuGroupId="300"
	Sequence="302"
	UseShortId="true"
	ClientOnClickNavigateUrl="~site/_layouts/viewlsts.aspx"
	PermissionsString="ManageWeb"
	PermissionMode="Any" />

Open in new window


Next, find the following block, and make the permission change as seen in line 4. This will hide the link in the Quick Launch for any 2007 site collection running in compatibility mode on 2010. (Doesn't impact pure 2010 sites.)

<SharePoint:UIVersionedContent UIVersion="3" runat="server">
	<ContentTemplate>
		<h3 class="ms-standardheader"><label class="ms-hidden"><SharePoint:EncodedLiteral runat="server" text="<%$Resources:wss,quiklnch_pagetitle%>" EncodeMethod="HtmlEncode"/></label>
		<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="ManageWeb">
			<div class="ms-quicklaunchheader"><SharePoint:SPLinkButton id="idNavLinkViewAll" runat="server" NavigateUrl="~site/_layouts/viewlsts.aspx" Text="<%$Resources:wss,quiklnch_allcontent%>" accesskey="<%$Resources:wss,quiklnch_allcontent_AK%>"/></div>
		</SharePoint:SPSecurityTrimmedControl>
		</h3>
	</ContentTemplate>
</SharePoint:UIVersionedContent>

Open in new window


Finally, make the change for normal SharePoint 2010 sites, to remove the link from the Quick Launch. Note I added the SPSecurityTrimmedControl tag around the <li>. I did this to keep the list markup clean, rather than render an empty set of <li></li> tags for normal users.

<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="ManageWeb">
<li>
	<SharePoint:ClusteredSPLinkButton
		id="idNavLinkViewAllV4"
		runat="server"
		PermissionsString="ViewFormPages"
		NavigateUrl="~site/_layouts/viewlsts.aspx"
		ImageClass="s4-specialNavIcon"
		ImageUrl="/_layouts/images/fgimg.png"
		ImageWidth=16
		ImageHeight=16
		OffsetX=0
		OffsetY=0
		Text="<%$Resources:wss,quiklnch_allcontent_short%>"
		accesskey="<%$Resources:wss,quiklnch_allcontent_AK%>"/>
</li>
</Sharepoint:SPSecurityTrimmedControl>

Open in new window

Author

Commented:
This is perfect. I'm surprised at how many differences there are between your v4.master and mine. My v4.master is as provisioned to all site collections by our farm administrator - evidently it's been customized quite a bit. This is a corporate intranet site, and all site collections use similar branding and basic features.

Thanks very much - you deserve all of the points, plus a couple of gold stars. This helps me a lot.

Commented:
Glad I could help out!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial