Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 8 down vote favorite
3

The "Recently Modified" section in the quick launch is not something I want my users to see. How can I eliminate or hide it in a SharePoint 2010 installation?

share|improve this question

1 Answer

up vote 3 down vote accepted

I accomplished this by using the steps outlined here.

  1. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\DocumentTemplates\
  2. Open wkpstd.aspx in a text editor.
  3. Find <SharePoint:RecentChangesMenu runat="server" id="RecentChanges"/> and replace with <SharePoint:RecentChangesMenu runat="server" id="RecentChanges" visible="false"/>.

If you ever need to reverse this process simply remove the visible="false" from the same tag.

Edit: As David pointed out in the comments this is not considered a "best practice" as updates from Microsoft can effectively undo the changes made to files in the 14 hive. In theory, however, should an update reset your wkpstd.aspx file you could simply take these steps again to re-hide the Recently Modified section so long as the update didn't fundamentally change the tag that needs to be altered.

share|improve this answer
1  
Can you do this with the Navigation option in Site Settings or is this not modifiable through there? I've used that for our page navigation but haven't implemented wiki's yet, it'd be good to know if I'll need a different method to manipulate nav settings. – MichaelF Apr 8 '11 at 19:23
I'm really new to SharePoint, but if I'm understanding your question correctly I think this solution should work for every quick launch or quick launch-esque structure throughout your site collection. I haven't implimented wikis in my SP2010 install yet (and probably never will) so I haven't tested that, but I believe this worked for wikis when I demoed SP2007 a few months ago. Your results may vary. – JonnyP Apr 8 '11 at 19:30
1  
Directly modifying Microsoft files in the 14 hive is 'bad' for a number of reasons. The most significant is that Microsoft can and will replace them in a future patch/update. – Dave Wise Apr 8 '11 at 20:10
@David - I did not know that. I'll edit my answer to reflect that this isn't considered a "best practice". – JonnyP Apr 8 '11 at 20:24
1  
I was thinking along the lines of what David said, typically we avoid doing anything in the 14 hive except updated web.config's that we need changed for our customizations. – MichaelF Apr 10 '11 at 18:22
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.