SharePoint By Gaurav Goyal

If you want to remove "I like It" , "Tags & Notes " Then just follow these steps : Open Central Administration Click on System Settings Click on Manage Farm Features (_admin/ManageFarmFeatures.aspx) Deactivate the Social Tags and Note Board Ribbon Controls OR You can deactivate this feature by Power shell command : SharePoint 2010 Management Shell Disable-SPFeature –Identity SocialRibbonControl

First, increase the Maximum Upload Size for a specific web application. Go to the Central Administration > Application Management > Web Application General Settings Specify the new maximum upload size for your webapplication. For now, we are setting it to 256MB. It could be even set upto 2GB. Your second step should be to try increasing your default chunk size of large files by trying this STSADM command: Stsadm.exe –o setproperty –pn large–file–chunk–size –pv        This basically denotes the chunk of data that can be read from SQL Server at one time.     The -pv which determines the property value stands for the upload size in bytes (B).     It could be set to a maximum of 2GB i.e. (2,147,483,648 B).     Do an IISRESET Next, in web.config file of your particular web application, under the httpRuntime tag in system.web section, increase the upload limit to match the value that you set earlier in central administration. You also need to add the execution timeout to allow mo

Let’s say you have a control on your page that you want only a certain group of users to see. Fortunately, SharePoint has a built-in control that lets you hide controls to which users do not have the necessary permissions.  This control is the SPSecurityTrimmedControl. <Sharepoint:SPSecurityTrimmedControl runat=”server” Permissions=”ManageLists”> Place your control(s) here </SharePoint:SPSecurityTrimmedControl> All you have to do is wrap your control with this security control and set the correct permissions in the Permissions attribute. The Permissions attribute, when used in Visual Studio or Designer, will have intellisense and will be filled with the following properties obtained from http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx .  Whatever permissions you specify will be required by the user in order to view the control(s) inside of the SPSecurityTrimmedControl:   Member name  Description EmptyMask

Enabling a Button on the Ribbon Based on Selection A lot of people have asked me how to create a button which enables if and only if a single item is selected. This isn’t something we have out of the box, but the code to get this functionality is pretty simple. I’m going to assume that you’re generally familiar with SharePoint, CustomActions, and customizing the Ribbon – if that’s not the case, you’d probably be better off researching those things before delving into this. Basically, the enabling behavior all boils down to the following few lines of code: EnabledScript = " javascript:function singleEnable() {   var items =     SP.ListOperation.Selection.getSelectedItems();   var ci = CountDictionary(items);   return (ci == 1); } singleEnable(); " What this does is query to get the dictionary of selected items, and if the size of the dictionary is 1 it returns true (enable), otherwise it will return false (disable). Technically,

 A way to remove or hide the ribbon area from user with lease privilege, and here is how: 1)       Open your SharePoint master page 2)       Locate this line: < div id ="s4-ribbonrow" class ="s4-pr s4-ribbonrowhidetitle"> 3)       Change it to: < div id ="s4-ribbonrow" class ="s4-pr s4-ribbonrowhidetitle" style =" display :none" > 4)       Now find the end of the “ s4-ribbonrow ” tag and add following block right after it: < Sharepoint : SPSecurityTrimmedControl ID ="SPSecurityTrimmedControl2" runat ="server" PermissionsString ="AddAndCustomizePages">     < script type ="text/javascript">         document.getElementById( "s4-ribbonrow" ).style.display = "block" ;     </ script > </ Sharepoint : SPSecurityTrimmedControl > 5)       Save the new master page and publish it. Learn more about SPSecurityTrimmedControl

  SP2 had a number of enhancements designed around making it easier to upgrade to SharePoint 2010.  One such new feature that wasn’t popularized is your ability to find and remove corrupted, broken sites known as orphans. As I’ve mentioned in the past, with SharePoint being split across multiple databases, it is quite possible that a site could be in either the content database OR the config database. With service pack 2 there’s a new way to find orphaned sites.  In addition to running STSADM –o PreUpgradeCheck , one of my favorite tools along with TEST-SPContentDatabase with SharePoint 2010 you can identify these messed up corrupted sites. You’ll run enumallwebs (STSADM reference on TechNet) to identify the orphaned sites, and use deletesite (STSADM reference on TechNet) to remove them.  Note this command is available in SP2, and was enhanced in the post SP2 October Cumulative update.  You really should consider that October update as the most significant release with

      <DIV id="ListPlaceholder"><IMG src="/_layouts/images/GEARS_AN.GIF"></DIV>       <!-- Paste the URL of the source list below: -->     <iframe id="SourceList" style="display:none;" src="/site/Lists/Calendar/Current%20Month%20Events.aspx" onload="DisplayThisList()"></iframe>       <script type="text/javascript">     function DisplayThisList()     {         var placeholder = document.getElementById("ListPlaceholder");         var displaylist = null;         var sourcelist = document.getElementById("SourceList");         try {                if(sourcelist.contentDocument)                   // Firefox, Opera                   {                 displaylist = sourcelist.contentDocument.getElementById("WebPartWPQ2") ;             }                else if(sourcelist.contentWindow)                   // Internet Explorer                   {            

This SharePoint 2010 solution allow site administrator to define who can or cannot see the SharePoint ribbon. In few words With this solution you can on each site define if the ribbon is display or not for :     * Everyone     * Anonymous user     * for one or many specific SharePoint groups This solution can be found on codeplex.com

If you’re using custom JavaScripts with SharePoint 2010 some global JavaScript variables may come in handy. These variables work if you’re using SharePoint’s default or any other custom master page.  L_Menu_BaseUrl – the base URL of the site / subsite. Very useful when you need to determine the absolute path of the site in JavaScript. Example: document.location = L_Menu_BaseUrl + ‘lists/calendar/allitems.aspx’ //redirects to Calendar list  L_Menu_LCID – the LCID of the site you’re in. Useful if you need to determine the language of the site. The list of Locale IDs can be found here .   _spUserId – the ID of the logged in user.

Hide Recently Modified Items In SharePoint 2010 we all are familiar with the following annoying quicklaunch menu:   Follow these steps :  Go to  " Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\DocumentTemplates" . Open "wkpstd.aspx" file . Search for tag " SharePoint:RecentChangesMenu". Add visible="false"  at the end of this tag. Save this file & refresh SharePoint site .