Waqas Sarwar's profilewaqas's spaceBlogListsGuestbookMore ![]() | Help |
|
|
How To: Hide/Remove the View All Site Content link in SharePointArticle: http://www.crsw.com/mark/Lists/Posts/Post.aspx?ID=36
Summary Important: This solution is not an answer for security. The user will still have access to the View All Site Content page. The View All Site Content link is simply removed or hidden from the page. Applies To
- Windows SharePoint Services 3.0 Downloads Hide View All Site Content - Solution Package Installation and Activation For those interested in how to install this solution, it is very easy and does not require any coding, compiling, or editing. Basic Install Steps:
Using (Activating) the new feature:
Your View All Site Content link should now be hidden and the View All Site Content link should now appear in the Site Actions menu. For those only interested in using this solution, you do not need to read any further. However, for those who are interested in how this is accomplished, the rest of this article discusses just that.
So, How'd You Do That?
Update
This solution can also be used to hide the Recycle Bin. Simply add the following code to the custom core.css file in the sample solution project and your Recycle Bin will also be hidden.
#ctl00_PlaceHolderLeftNavBar_idNavLinkRecycleBin Overview The result of this article is to hide View All Site Content link from the users. An additional View All Site Content menu item is added to the Site Action menu and is accessible only to users having the AddAndCustomizePages right. Here is a picture of the typical View All Site Content link as it appears on a SharePoint web site and how it looks after it is hidden.
Additionally I add a new custom menu item to the Site Action menu. Here is the result of the new link. This link will only appear for users having the AddAndCustomizePages right such as designers and administrators.
And finally, this functionality is wrapped up into feature allowing it to be activated or deactivated for each site as needed. Here is the new feature that will appear in the list of Site Features for a web site.
All of this is wrapped in to a single SharePoint solution package (.wsp) file and can easily be installed on a SharePoint farm by a server administrator. Note: From this point forward in the document, any reference to the View All Site Content link will be abbreviated to VASC. Consideration There are a couple ways to in which to accomplish this. The first and most obvious method is to modify the master page that contains this link. This involves a fairly simple process of modifying the master page and removing the VASC link, then redeploying the new master page. The drawback from this is that you do have to modify the master page which is sometime not desirable, plus the master page is likely to have more than one site based on it, and it may be desirable to have this View All Site Content link remain on those sites. However, if you are willing to modify the master page, there is another posting you may find of value. Keep in mind the security you define in the master page will be the same for all sites on your SharePoint farm. If that is desirable, you may find this post on SPSecurityTrimmedControl: Conditionally display contents by security of use. My Approach I had a couple goals I wanted to my solution to meet. They were: 1. To be able to selectively choose the sites where the VASC link is hidden. 2. Avoid having to modify the master page if possible. 3. Provide a simple way for users to hide/remove the VASC link. After a little investigation, a few things about SharePoint (3.0/2007) surfaced that allowed me to achieve all of my goals and provide a solution that can easily be implemented. Hidden by Style The approach I have decided to use is to simply hide the VASC link using a style sheet modification. The VASC link for most, if not all of the sites assigns an ID (ctl00_PlaceHolderLeftNavBar_idNavLinkViewAll) to the anchor tag containing the VASC link. This makes it easy pretty darn easy hide this link by simply adding a bit of style code to the page. In fact, just for giggles, you can copy the following style sheet code into a Content Editor Web Part. This web part can even be strategically placed at the bottom of the page; optionally hide the title bar and nobody would even know it was there. Here is the sample style to try it just for fun. This will hide the View All Site Content link on your page. #ctl00_PlaceHolderLeftNavBar_idNavLinkViewAll But this is not really good enough. At least, not alone this isn’t. I needed a way to do this for every page on a given site. And copying this code to each and every page on a site is not only extremely tedious; it is almost guaranteed to be incomplete and error prone. Microsoft Office SharePoint Server (MOSS) 2007 does provide an easy way to do this, but Windows SharePoint Services (WSS) 3.0 does not. Using MOSS 2007, you can apply a custom style sheet to a web site and optionally apply it to every sub site. For SharePoint servers where this is desired, and if you are using MOSS 2007, this will work for you. Also keep in mind; you just removed the VASC link for every user – including your site designers and administrators. Although this is not the worst of all problems, it is probably not the absolute desired solution either. I still like the idea of using the custom style code to hide my VASC link. But I also need to place a link on the page for users who will need easy access to the VASC link such as designers and administrators. I know I can easily accomplish this by adding an access controlled link to the Site Actions menu, but I will come back to this in a moment. I still need to address how to easily apply a customized style to every page on a given site. CustomizeCss So how can I apply a custom style to every page on a given site? SharePoint provides a way to do this using the SharePoint object model. With a bit of custom C# code I use the SPWeb.CustomizeCss method to specify a custom style sheet to be used on every page of my site. The CustomizeCss method on the SPWeb class provides way to specify the style sheet file name of an existing style sheet used by SharePoint. SharePoint utilizes a number of different style sheet files. The one we are interested in is the style sheet file that is applied to each and every page on the site. One such style file is the core.css file, and this will do just for our needs. The standard default core.css file is located in …\12\TEMPLATE\LAYOUTS\1033\STYLES. This STYLES folder is a virtually mapped via the /_layouts virtual directory that is mapped to each and every site in SharePoint. So, the core.css file is accessible to every site by simply using the URL of “[site-root-url]/_layouts/1033/styles/core.css”. For every page that SharePoint renders, it renders a link to the core.css using this path. However, for any site that has been configured to use a custom core.css style sheet via the CustomizeCss method on the SPWeb class, the URL rendered in each page references a core.css file located in a different location. This is accomplished in C# by the following code where web is an instance of the SPWeb class for the web site of your choice.
The CustomizeCss(“core.css”) statement tells SharePoint to use a custom copy of the SharePoint core.css file. Once this CustomizeCss method is executed, a copy of the core.css file found in the …\12\TEMPLATE\LAYOUTS\1033\STYLES folder is copied to the folder (not a document library) named _styles on the applied site. The resulting URL to this new core.css file can be found at Reverting this site back to using the original global (un-customized) copy of the core.css file can be accomplished just a easy using the following code.
Executing the RevertCss method does not remove the custom core.css file on the web site’s “/_styles” folder. It simply tells the site to no longer use it and to use the original core.css found in the C:\…\12\TEMPLATE\LAYOUTS\1033\STYLES folder; which is the same folder as the as the “[site-root-url]/_layouts/1033/styles” folder. So we now know how to use the CustomizeCss and the RevertCss methods on the SPWeb class provide an easy way to point the site to a new custom style sheet file. Now that we have an easy way to point our site to a custom core.css file, all we need to do is copy our custom core.css file that contains all the original core.css contents plus the extra style code to hide the VASC link and copy it into the _styles folder of the site. All of this can easily be implemented using a SharePoint feature. Using a feature provides a standard way to enable or disable functionality with a site in a safe and secure manner. I won’t cover all the details on how to create the feature here, but the source code provides all the code you need. Now that we know how to hide the View All Site Content link easily using a feature and the CustomizeCss and RevertCss methods, we need to provide an easy way to allow site designers and administrators to quickly and easily use the View All Site Content link. Site Action Link To provide web managers such as designers and administrators with a convenient link equal to the View All Site Content link, we will add a new custom action menu item. I won’t go into the details of the code and how to create the feature here, but I will briefly cover the expected functionality. Again, the source code is available for those interested in the technical details. The Site Action is usually located in the upper right corner of the web site and contains links used by site administrators such as the Site Settings link. The nice thing about the Site Actions menu is that it is collapse and consumes a minimal amount of screen real estate. So, adding an additional menu option to the Site Actions menu will not only be convenient for site administrators, it’s pretty easy to implement in a SharePoint feature. This new View All Site Content link on the Site Action can be secured in a manner that best suits your needs. In the solution sample I provide, this new View All Site Content link on the Site Actions menu is only visible to users who have the “AddAndCustomizePages” right which allows designers and administrators to see it, but is not visible to typical users of a site. There are plenty of examples on how to add a custom item to the Site Action menu so I will not cover that in any detail here, but the solution sample I provide does include all the code – and the nice thing is, it isn’t much code. Installation and Activation Basic Install Steps: Activating the new feature: Your View All Site Content link should now be hidden and the View All Site Content link should now appear in the Site Actions menu. Conclusion The result is a single feature that a site administrator can activate and deactivate on any web site to hide and show the standard View All Site Content link in the quick launch navigation. Additionally, it adds a useful new View All Site Content to the Site Actions menu that is visible only to users having the AddAndCustomizePages right on that site. References:
Enjoy! Customizing the WSS 3.0/MOSS 2007 Menu Control -- MossMenu source code releasedThe AspMenu class that ships with WSS 3.0 (and by extension MOSS 2007) is nearly identical in behavior to ASP.NET 2.0’s Menu class (as the name implies). AspMenu derives from Menu and adds tweaks to work around a few reasonably well known annoyances and provides improved highlighting support.
Unfortunately, this class was marked sealed and is therefore not eligible to be used as the base class for derived types. Effectively, this means that customers cannot inherit the additional functionality of the AspMenu class when trying to provide further customization of the menu.
We realized this problem too late in the release process and were unable to remove the sealed marker from the AspMenu class that ships with WSS. However, we are instead providing the source code for that class here (as an attachment to this blog entry) under the name MossMenu.
Note: MossMenu is provided as is and will only work on sites built with WSS 3.0 or MOSS 2007. MossMenu relies on some JavaScript which has been included along with the C# source. This is really just for completeness’ sake [aside: some trival about the use of the apostrophe for the possessive forms of nouns] as this script is automatically included on most pages through the core.js script include reference.
Issues with the ASP.NET 2.0 menu, which have been worked around: 1) If the mouse pointer happens to be hovering over a menu item that exposes a fly-out as the page is loading, it is possible that an error dialog will appear stating: "Internet Explorer cannot open the Internet site, Operation aborted" and a blank page will be shown upon clicking OK. It seems that the problem arises from attempting to append to the DOM before it is properly initialized. 2) If SSL termination is employed on a site with a menu, users will be greeted with “This page contains both secure and nonsecure items. Do you want to display the nonsecure items?” when hovering over a menu item which exposes fly-outs. (http://support.microsoft.com/?id=910444) 3) In right-to-left locales, the fly-out indicator arrow still points from left-to-right.
Improvements to default highlighting behavior of ASP.NET 2.0 menu: · When hooking the menu up to a SiteMapProvider through a SiteMapDataSource, the menu automatically highlights the node that matches that returned by the provider’s CurrentNode property. However, if the particular node returned by CurrentNode is not shown by the menu nothing will be highlighted at all. The improved behavior determines if there is an ancestor of the current node which is displayed in the menu and highlights this node instead.
Hope this helps.
Back to Basics: Connecting to Project Server (video)If you are a project manager who wants to create a project using Project Server 2007, you have two ways of connecting to it. You can connect directly using a Web browser and a URL given to you by an administrator, or you can connect through Project Professional 2007 on your desktop, which is explained explain in this video. http://office.microsoft.com/en-us/project/HA102910371033.aspx?pid=CH100948801033 Thanks Posted by Heather O'Cull at Friday, November 07, 2008 11:09 PM TechNet Security Resource Center for SharePoint Products and TechnologiesHey Guys! This page provides IT pros with security resources for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007.
Thanks Special thanks to chrisfie for this entry at Christophe Fiessinger’s Blog on November 13, 2008, 8:35pm PM Boot Camp: Up to speed with Project 2007Hi Guys!
If you're new to Project 2007, or even new to project management in general, the Up to speed with Project 2007 video series might be the basic training you're looking for. This six-part series covers the basic elements of project management and the Project 2007 interface, as well as how to start a new project, create relationships between tasks, use calendars, build a team, identify project costs, check project progress, and generate reports. The entire series can be viewed in less than an hour, providing a quick way to ramp up and get started managing your projects using Project 2007.
Thanks
Waqas
Special thanks to Heather O’Cull this entry at Microsoft Office Project 2007 on November 12, 2008, 6:55pm See whats new at Michael Jordan's Series of PresentationsHey Guys!
Michael Jordan, a Lead Architect at Microsoft, has been delivering a great series on Project Server 2007. In the series, he presents on the aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007. You can register for the upcoming webcasts and catch up on the ones you have missed at the Microsoft Project Webcasts page.
Thanks
Waqas
Special thanks to Do More Than Manage for this entry, released on November 12, 2008, 12:00am How to deploy cumulative updates for Project Server 2007The TechNet team has just published this key article Deploy cumulative updates (Project Server 2007) Please read this article prior to deploying any Project Server Cumulative Update. As a reminder the last cumulative update was released on October 28th: Announcing the release of the October Cumulative Update for Project and Project Server 2007 Special Thanks to Christophe Fiessinger for this Blog, released on November 13, 2008, 8:41pm Configure PDF IFilter in WSS 3.0There are various posts around on setting up MOSS 2007 to use the PDF IFilter, and some stuff on Windows SharePoint Services 3.0 as well. I’ve found a method which works for me, so I wanted to put this together in one place - not least of all so I can find it when out on site with a client. Out of the box neither WSS 3 nor MOSS 2007 will index content located in Acrobat PDF files, so you need to set up the IFilter. I’ve also found that that PDF files loaded prior to the installation of the filter won’t be re-crawled automatically, so to be on the safe side you might want to kick off a full crawl. Here is what I’ve found works for WSS 3.0:
Thanks Special Thanks to Worker Thread
Microsoft Ramp Up Program: Just Launched SharePoint for Developers TrackThe Ramp Up program (www.MyRampUp.com) has just launched a brand-new learning track: SharePoint for Developers, Part I today. This includes:
Ramp Up is a free, online, community-based program that can help users save time in learning Microsoft technology. The easy-to-access content (provided by subject-matter gurus) is specifically tailored to the Ramp Up program, and offered in a variety of forms (whitepaper, v-lab, codecast and slidecast). This SharePoint track, along with the other currently offered tracks (eg, Visual Studio 2008), teaches the important skills in a guided path, making the learning process easier and more efficient. Currently, there are no assessments in the program, so it’s quicker than ever to graduate and receive the reward (25% off on certification and 50% off on e-Learning - only for graduates of Ramp Up).
Thanks Originally by chrisfie from Christophe Fiessinger’s Blog on November 6, 2008, 3:58am Announcing the Microsoft patterns and practices: SharePoint GuidanceThis is a great assets for all SharePoint and Project Server developers: http://microsoft.com/spg Overview This guidance helps architects and developers build SharePoint intranet applications. A reference implementation (RI) demonstrates solutions to common architectural, development and lifecycle management challenges.
Regards Originally by chrisfie from Christophe Fiessinger’s Blog on November 6, 2008, 3:58am Enforcing MS Project Settings using Group PoliciesMicrosoft have released new contents regarding using Active Directory GPO to enforce settings. The process can be used for Microsoft Project 2007 deployment to standardize the usage of the tool. In a MS Project Server 2007 EPM environment, there are settings your should check or uncheck based on how you are planning to use the system. Standardizing those settings make it easier from the user experience of the tool & make things easier for later issues. Review the following links for details. Best Regards
Waqas Sarwar
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">div> Originally from MS Project Server on November 3, 2008, 5:34pm 10 Signs You Don't Really Know Microsoft ProjectYou manually create a Project Summary Task Wrong: 2. You "hard code" dates Wrong: 3. You don't input the teams estimated Duration on all tasks Wrong: 4. Your tasks don't start with a verb 5. You assign Predecessors to Summary Tasks Wrong: 6. You assign Resources to Summary Tasks Wrong: 7. You never inspect the critical path tasks 8. You never search for (or eliminate) Resource Over-Allocations 9. You never Baseline your schedule 10. You never update your schedule to align with reality
Best regards
Waqas Sarwar
Special thanks to http://www.pmconnection.com/modules.php?name=News&file=article&sid=32 for this outstanding post. 25 Microsoft Project Tips and Tricks25 Microsoft Project Tips and Tricks
|
|
|