Date: 09/01/07 (IT Professionals)    Keywords: programming, html, technology, asp, java, web, microsoft

Hi all,

I've been battling with creating (rather modifying a custom page someone else before me has created) a custom master page for my company for a while now; it looks great-ish, but there's a major flaw in there, behind the scenes it's full of errors; I have to link the master page to just about every file such as newForm.aspx and etc. further the most major issue is that a non admin user can't see the custom content; but farm admins can see the custom content just fine.

I suspect there's a whole lot missing in the master page (as I've tried the same thing with a default page, and it worked fine, so my permission settings are fine, even though for non Admins it says "error: access denied", the issue is the master sheet for sure, since the error dissapears  when i switch back to one of MOSS default masters) thing is i don't have enough knowledge of master pages (I am relatively new to SharePoint 2007; having worked with 2003 years ago. I've never done any major customizations like this one)  to fix it on my own, even though i've spent the past few weeks trying to do so.

The project I'm working on (an intranet for a media company) is due to go live Sept 9th, thing is, without proper user permissions it'll be tricky to make it work properly, and I've been battling with the master page for about two weeks now trying to make it work, I fix one issue, but keep finding more.

I appreciate any and all the help i can get on this one as all the code's starting to look the same to me now, and maybe a fresh set of eyes will help.

Master page code and screenshot of what it looks like and what it should look like for all users below the cuts, if you need any extra info please contact me, and I'll provide for you; I really really appreciate it if someone can help me out on this one.








<%-- Identifies this page as a .master page written in C# and registers tag prefixes, namespaces, assemblies, and controls. --%><%@ Master language="C#" %><%@ Import Namespace="Microsoft.SharePoint" %><%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %><%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %><%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %><%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %><%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %><%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %><%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %><%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %><%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %><%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %><%-- Uses the Microsoft Office namespace and schema. --%><%-- The head section includes a content placeholder for the page title and links to CSS and ECMAScript (JScript, JavaScript) files that run on the server. --%>









<%-- When loading the body of the .master page, SharePoint Server 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. --%>

Source: http://community.livejournal.com/itprofessionals/63910.html