tag:blogger.com,1999:blog-14718171.post5756424462599563674..comments2024-02-18T09:32:27.373+01:00Comments on Robin's Sharepoint Blog: Security trimmed SiteSettings pageRobin Meuréhttp://www.blogger.com/profile/06878262430984779866noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-14718171.post-46945770571096208882009-07-21T21:44:15.622+02:002009-07-21T21:44:15.622+02:00Hi Zimberg,
this is a very old post.. I won't...Hi Zimberg,<br /><br />this is a very old post.. I won't recommend doing it again to be honest. Since it's not supported to modify out-of-the-box files. <br /><br />I think at this time I would recommend to write a feature that hides the links in the SiteSettings by using the HideCustomAction elements http://msdn.microsoft.com/en-us/library/ms465980.aspxRobin Meuréhttps://www.blogger.com/profile/06878262430984779866noreply@blogger.comtag:blogger.com,1999:blog-14718171.post-27635470636614022952009-07-21T17:05:26.018+02:002009-07-21T17:05:26.018+02:00Sam, that article doesn't have anything to do ...Sam, that article doesn't have anything to do with this article. <br /><br />Yeah, you could hack the SiteSettings.xml file in the SiteSettings feature, and you could edit all of the application pages you don't want your users to go to by adding a security trimming control, but both the SiteSettings feature and those application pages are central to the whole farm. So you'd have to make these changes to each WFE server, they aren't deployable or retractable, and they will affect all web applications on the farm. <br /><br />Out of the box SharePoint has really left me disappointed with the default infrastructure. Trying to do simple things is a lot more difficult than it should be because of things like centralized application pages pointed to by a virtual directory instead of ghosting them or even copying them for each web app.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-41295036977841280882007-12-06T09:50:00.000+01:002007-12-06T09:50:00.000+01:00try this http://msdn2.microsoft.com/en-us/library/...try this http://msdn2.microsoft.com/en-us/library/ms948916.aspx<BR/><BR/>sam from chicagoAnonymousnoreply@blogger.com