.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Locking down application.master related pages to end-users.

Posted By:      Posted Date: October 12, 2010    Points: 0   Category :SharePoint

I see that end users can access ASPX pages (such as  "_layouts/settings.aspx" etc) that are related to application.master.

My goal is that when end users try to navigate any of these pages (either directly or through OOB links), I want to return them to an error page (or home page). The end users may still need to modify "my settings" page which also has "_layouts" in it. So I have to consider this as an exception.

I did search a bit and not getting right solution yet.

Please suggest.

View Complete Post

More Related Resource Links

Locking down Themes and Master Pages



We have a requirement to lock down the themes and the master pages to all the sites and site collection in a Farm. Meaning, when we give a site collection to a user, we will apply the corporate branding. Hence, when we give a site collection to the business users, they should not modify that. Since, we are dedicating "Site Owners"previleges they can modify the same. We want to restrict this. Another constraint is that the "Site Owners" should have all the permissions, hence, we cannot modify the permissions for this group alone. So, we need to have another strategey by which they will not be able to modify the thmes or the master pages.

I tried these options:

1. At the Central Administration, I created a Permissoin Policy and given Deny access to Apply Themes, but, in this case even the Site Collection Administrator cannot modify the themes, also, when we change the language settings, it gives error.

2. Modified the themeweb.aspx in the layouts folder, to have:

protected override bool RequireSiteAdministrator

SharePoint Application and Site Pages - Part 1 of 2

In this first part of the two part series, Steven covers the differences between Site and Application pages in SharePoint 2007, why each may be used in various circumstances, and prepares for the construction of a menu located application page. After a brief introduction he examines the concept of Site Pages and Application Pages separately in detail with supported screenshots.

SharePoint Application and Site Pages - Part 2 of 2

As the second article in a two part series, Steven examines the attributes and details of a SharePoint 2007 application page, including the construction and feature deployment of the same page based project. Since this is a WSS level objective, as opposed to MOSS, you will not need MOSS to work with the code included in this project. Windows Server 2003, WSS, and Visual Studio 2005 are all that is needed, with no additional add-ons. He provides a detailed analysis of each step involved in the creation and deployment of the project.

Application Vs. Content Pages in SharePoint

SharePoint has two types of ASPX pages. One type is the application page, also known as a _layout page. The other type of ASPX page is a content page, also known as a site page. Each of these page types is stored in a different location in SharePoint. When developers create custom ASPX pages, they must decide on the page type.

Master Pages in MOSS 2007

'MasterPages' feature in sharepoint 2007 makes the entire customization job easy.In 2003 we used to face lot of issues to get the same look and feel and the standard behaviour for overall site. In 2007, customizing the look and feel for the entire site can be done in a simple way by using 'MasterPage' feature.

Master Pages: Master Your Site Design with Visual Inheritance and Page Templates


Master pages in ASP.NET 2.0 solve a problem many Web developers have been solving on their own with a variety of techniques for years - providing a single master template for an entire site. This article covers the details of master pages, discussing their usage and implementation and how they are a natural evolution of custom techniques developers are using today.

Fritz Onion

MSDN Magazine June 2004

Button click in master page use in other pages I have to click twice. Why?


In my masterpage I have a menu with buttons. I want the buttons to do something after click. It works but I have to click twice on the button, why? What do I have to do to just to click once?

how to change default menu tab in master pages?



i have 5 tabs in my master page application. how can i make 2nd tab as default?

any ideas?


Ajax and master pages


I have a site that uses master pages.  Some of my pages use ajax, so they have the scriptmanager on them.  I now have to add some ajax to one of the master pages.  When I try to display a page that already has a script manager on it, I get an error that I can only have one script manager.  Is there a way to deal with this other then searching for every page that uses the master page and ajax and removing the scriptmanager tag? 

I'm hoping to start using Ajax more and more, so I'm really more concerned with best practices then I am about having to find and remove tags.  What is the right way to use Ajax on master pages and some, but not all content pages?

Why do the aks master pages not get applied if the feature is not activated on the top site collecti


I installed AKS 2.0 and activated AKS feature. The problem I found was the aks master pages do not get applied if the feature is not activated on the top site collection. why is so?

example: If i activate the feature on http://<servername>/sites/<sitename> and apply the master page, I dont see any changes.

              But if i activate the same aks feature on http://<servername/ then everything started working on all sites.

              The reason i found is the CSS reference in the aks master pages.

              It reference should be given as follows:

                 for http://<servername>/sites/<sitename> ->  <link rel="stylesheet" type="text/css" href="../../Style%20Library/AKS/Aks_Band_Blueband.css"/>

                 for http://<servername>/ -><link rel="stylesheet" type="text/css" href="/Style%20Library/AKS/Aks_Band_Blueband.css"/>

So my question is, am i missing anything? am i supposed to activate the AKS feature on top level site collection at any cost? if yes, why is so? 

And after applying aks master pages, i see differnece in font sizes. Why the font size is getting changed?


Sharepoint 2007 - Wiki site - New Pages Not Inheriting Custom Master Page


I am working on a SP site (MOSS not WSS) which is heavily customised away from the OOTB layout. I need to create a Wiki site, which was going well - I've created a master page which displays the miniconsole (this was not visible with our customised layout), and made it the default master page for the site. This has been applied to the two standard pages that come with the Wiki site, however when a new page is created, it seems to inherit the default.master, rather than my custom master page - thus not showing the miniconsole.

When I have created a new page, I am able to use SharePoint Designer to attach my custom master page to it, which works perfectly, however this will not be a viable option going forward as end-users create their new wiki pages.

How can I get the new pages to inherit my master page when they are created?


Inherit from multiple master pages


How does one inherit from multiple master pages?


I.e.  I have a base master page that contains several ContentPlaceHolders.









I want to have separate master page files (one for each ContentPlaceHolder) so that I have 4 separate files: 3 ContentPlaceHolders (each adding specific content) and 1 base master page.

The ASPX files will then inherit from the base master page.



Programmatically Hide Master Pages from Site Master Page Settings page?



I know there is a field you can check when you edit the properties of a Master Page in the Master Page Gallery to set a Master Page to hidden but ... can anyone think of a way to programmatically hide specific Master Pages from the Site Master Page Settings page?

Maybe this should be two questions:

  1. How do I programmatically access a Master Page in a Master Page Gallery?
  2. Is there a property that can be set that will hide the page from the Site Master Page Settings page?

Developing common content pages that can be hosted at the Web application or TLS level and can be sh

We are working on a Publishing site and planning to provision each client as a sub-site under the top level site (TLS). All of these sub-sites will almost have the same web pages and based on the client specific requirement they can customize these pages if needed. To meet the above requirement: I want to develop common content pages or application pages with the publishing capabilities and host them at the TLS, making these common pages available for all sub-sites under the TLS with the following requirements. ·        Sub-sites will not have any of these pages on their own and there would be only one central copy of this common page at TLS. ·        The sub-sites should be able to access these common pages in their context that means using the sub-site specific Master page & Themes. ·        When there is a specific customization is required such as adding a different web part, or updating the HTML data on the page, the common page will be edited in the sub-site and eventually making its own copy of the common page and resulting breaking apart from the common page for any future changes. ·        When the user edits the page he should be alerted that customizing this common page will make a local copy an

How to develop Common Content or Application pages in Sharepoint 2010, with respect to the customiz

  I have a top level site and subsites (which might be around 10). Where as the top level site represents a common landing page and each sub site represents a client site to which user will be directed upon login. This is a PUBLISHING web site. I need to design to start with common pages across all clients and if there is a need let the client to customize the common page accroding to their need. This is a PUBLISHING site so all these common pages should have Web parts zones with authoring capabilities. What is the best way of achieving this?    

No results for users that are members of a 'Deny All' policy for web application

I have a SharePoint Farm with search working happily.  This farm also has a remote access component that I have configured on a separate extended web application.  The business has some accounts that it does not want to allow access to the Intranet remotely, and has added these accounts to a 'Non Remote Intranet Users' security group.  I then set up a rule on the Extranet zone to Deny All access for this group.  The Default zone still allows them to browse however, which is working great. The only problem is that members of this group do not get any search results whatsoever.  From the logs it appears that all results get security trimmed.  :( Can I disable security trimming somehow?  Is this a bug?  Any suggestions would be appreciated.  :)

Deploying master pages in sharepoint 2007

Present situation:   Client has dev environment and they have customized the default page which comes ootb and is in Page Library. Also Created Master page using Sharepoint designer, and made that master page as the default master page for the site. The proposed solution: For promoting to different environments we will have to move packages WSP's across environments.   The present situation: All the environments were restored by using site collection backup and restore option (stsadm -o restore ...)   The Problem: Can we overwrite the master pages, page templates which are presently in master page gallery and page library by using feature   Or is there a better way of doing this.   Can somebody specify a better option for promoting.  
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend