SharePoint Site Collection or Sub Site?

Option	Pros	Cons
Provision a Site Collection	More scalable than Sub Sites through management of quotas and content databases. Quotas are managed at the site collection level Maximum size can be the size of the content database When sub sites grow too large, they need to be moved to or promoted to a site collection. This isn’t case if site is already a site collection. Full fidelity backups are only possible at the Site Collection level Site Collections allow security groups and permissions to be isolated from each other You can prevent access to certain Feature functionality. It’s easier to track and report on the site's lifecycle at the site collection level Content type hub removes limitation from previous version of SharePoint of not being able to share content types and site columns across site collections. Any sub sites created will inherit the site collection permissions, navigation, and branding	No permission inheritance since it is top level site. Security Management is more complex with Site Collections Difficult to see what access a user has across Site Collection No OOTB way to synchronize across Site Collections Inconsistent Navigation which would require creation of a SharePoint Feature Staple (code) Inconsistent branding would require creation of a SharePoint Feature Staple (code) Search Settings must be manually (or programmatically) synchronized across site collections Site Collections can only be provisioned via the Central Administration (CA) Site where only farm administrators have access. If you don’t want team who provisions sites should to have access to CA, this would require one of the following: Coded provisioning solution Third Party Provisioning solution Third party administration tool with security trimmed administrative interface Multi-tenancy enablement which would provide a minimal view of CA
Provision a Sub Site	Inherits security from parent site Inherits branding from parent site Inherits navigation from parent site Inherits search settings Can aggregate data throughout your site hierarchy using Web Parts like the Content Query Web Part, Data View Web Part and other data aggregation Web Parts	Do not scale well which may require a move Sub sites all exist in the same site collection container so if two sub-sites grow beyond a manageable size for a single site collection, that container cannot scale out its storage without breaking the collection apart into several site collections and facing other challenge Moving sub sites is an administratively difficult task (may require a third party tool to manage Moving sub sites with workflows attached breaks workflow history Moving sub sites breaks URLs and links

Disable Social Notification Emails in SharePoint 2010 Using PowerShell

Had client who wanted to pilot SharePoint 2010 User profiles for a select group of users.  They wanted to import all users from AD, but didn’t didn’t want non-pilot users to get e-mail notification of new colleagues as result of the notification timer job so I wrote below PowerShell script to turn this particular notification off.

Add-PSSnapin Microsoft.SharePoint.Powershell
#Set up default variables
#My Site URL

$mySiteUrl = "https://employeenetwork-dev.massmutual.com"
  
#Get site objects and connect to User Profile Manager service  
$site = Get-SPSite $mySiteUrl  
$context = Get-SPServiceContext $site  
$profileManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context)
 
$profiles = $profileManager.GetEnumerator()
 
foreach ($userProfile in $profiles) {
$userProfile["SPS-EmailOptin"].Value = 010
$userProfile.Commit()
}

Swish Affect in SharePoint 2010 Publishing PageLayout

Playing with jQuery and SharePoint 2010 and created an IPad like swish/slider affect with following single pagelayout and CSS – Take a look at the pagelayout for CSS and jQuey file locations where you can add to the hive or change references and store files in a folder on the site (you can download latest jquery.easing files from the jQuery plugin site http://gsgd.co.uk/sandbox/jquery/easing/ and see the strict jquery demo site which gave me the idea here http://tympanus.net/codrops/2010/06/02/smooth-vertical-or-horizontal-page-scrolling-with-jquery/).  What’s happening -- CSS stretches 1 page to give affect that you’re scrolling 3 pages.  I added 3 web part zones and wrapped with Classes to show only that portion.  In edit mode, all three web part zones are displayed in a single page view which required a separate CSS reference for edit mode.  This is fun but think about performance on home page before loading it up with web parts.

PAGE LAYOUT:

<%@ Page language="C#"   Inherits="Microsoft.SharePoint.Publishing.PublishingLayoutPage,Microsoft.SharePoint.Publishing,Version=14.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePointWebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 
<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<asp:Content ID="Content1" ContentPlaceholderID="PlaceHolderAdditionalPageHead" runat="server">
        <ContentTemplate>
            <style type="text/css">
                    .ms-pagetitleareaframe table, .ms-titleareaframe
                    {
                        background: none;
                        height: 10px;
                        overflow:hidden;
                    }
                    .ms-pagetitle, .ms-titlearea
                    {
                        display:none;
                    }
            </style>
            <SharePointWebControls:CssRegistration ID="CssRegistration1" name="<% $SPUrl:~sitecollection/Style Library/~language/Core Styles/pageLayouts.css %>" runat="server"/>
            <SharePointWebControls:CssRegistration ID="CssRegistrationScroll" name="<% $SPUrl:~sitecollection/_layouts/1033/styles/mmbranding/mmscroll.css %>" runat="server" />
            <PublishingWebControls:editmodepanel ID="Editmodepanel1" runat="server">
                <!-- Styles for edit mode only-->
                <SharePointWebControls:CssRegistration ID="CssRegistration2" name="<% $SPUrl:~sitecollection/Style Library/~language/Core Styles/zz2_editMode.css %>" runat="server"/>
            </PublishingWebControls:editmodepanel>
        </ContentTemplate>
    <SharePointWebControls:UIVersionedContent ID="UIVersionedContent1" UIVersion="4" runat="server">
        </SharePointWebControls:UIVersionedContent>
        <ContentTemplate>
            <style type="text/css">
                .v4master #s4-leftpanel { display: none; }
                .v4master .s4-ca { margin-left: 0px; }
            </style>
            <SharePointWebControls:CssRegistration ID="CssRegistration3" name="<% $SPUrl:~sitecollection/Style Library/~language/Core Styles/page-layouts-21.css %>" runat="server"/>
            <PublishingWebControls:EditModePanel ID="EditModePanel3" runat="server">
                <!-- Styles for edit mode only-->
                <SharePointWebControls:CssRegistration ID="CssRegistration4" name="<% $SPUrl:~sitecollection/Style Library/~language/Core Styles/edit-mode-21.css %>"
                    After="<% $SPUrl:~sitecollection/Style Library/~language/Core Styles/page-layouts-21.css %>" runat="server"/>
                <SharePointWebControls:CssRegistration ID="CssRegistrationScrollEdit" name="<% $SPUrl:~sitecollection/_layouts/1033/styles/xyzbranding/xyzscrolledit.css %>" 
                    After="<% $SPUrl:~sitecollection/_layouts/1033/styles/xyzbranding/xyzscroll.css %>" runat="server"/>
            </PublishingWebControls:EditModePanel>

        </ContentTemplate>
    </asp:Content>
<asp:Content ContentPlaceholderID="PlaceHolderPageTitle" runat="server">
    <SharePointWebControls:FieldValue id="PageTitle" FieldName="Title" runat="server"/>
</asp:Content>
<asp:Content ContentPlaceholderID="PlaceHolderPageTitleInTitleArea" runat="server">
    <SharePointWebControls:TextField ID="TextField2" runat="server" FieldName="Title"/>
</asp:Content>
<asp:Content ContentPlaceHolderId="PlaceHolderTitleBreadcrumb" runat="server"> 
    <SharePointWebControls:VersionedPlaceHolder ID="VersionedPlaceHolder1" UIVersion="3" runat="server"> 
    </SharePointWebControls:VersionedPlaceHolder>
    <SharePointWebControls:UIVersionedContent ID="UIVersionedContent2" UIVersion="4" runat="server"> 
    </SharePointWebControls:UIVersionedContent>
    <ContentTemplate> 
    <SharePointWebControls:ListSiteMapPath ID="ListSiteMapPath1" runat="server" SiteMapProviders="CurrentNavigation" RenderCurrentNodeAsLink="false" PathSeparator="" CssClass="s4-breadcrumb" NodeStyle-CssClass="s4-breadcrumbNode" CurrentNodeStyle-CssClass="s4-breadcrumbCurrentNode" RootNodeStyle-CssClass="s4-breadcrumbRootNode" NodeImageOffsetX=0 NodeImageOffsetY=353 NodeImageWidth=16 NodeImageHeight=16 NodeImageUrl="/_layouts/images/fgimg.png" HideInteriorRootNodes="true" SkipLinkText=""/> </ContentTemplate> </asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">

    <SharePointWebControls:UIVersionedContent ID="UIVersionedContent7" UIVersion="4" runat="server">
        <ContentTemplate>
                <PublishingWebControls:EditModePanel ID="EditModePanel2" runat="server" CssClass="edit-mode-panel">
                    <SharePointWebControls:TextField ID="TextField1" runat="server" FieldName="Title" />
                </PublishingWebControls:EditModePanel>
        </ContentTemplate>
    </SharePointWebControls:UIVersionedContent>
        <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>        
        <script type="text/javascript" src="/_layouts/xyzbranding/jquery.easing.1.3.js"></script>
    <script type="text/javascript">
        $(function () {
            $('ul.nav a').bind('click', function (event) {
                var $anchor = $(this);
                /*
                if you want to use one of the easing effects:
                $('html, body').stop().animate({
                scrollLeft: $($anchor.attr('href')).offset().left
                }, 1500,'easeInOutExpo');
                */
                $('html, body').stop().animate({
                    scrollLeft: $($anchor.attr('href')).offset().left
                }, 1000);
                event.preventDefault();
            });
        });
</script>
    <div class="section home" id="section1">
    <table>
        <tr>
            <td >
                <table>                            
                    <tr>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="<%$Resources:cms,WebPartZoneTitle_CenterLeft%>" ID="CenterLeftColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="<%$Resources:cms,WebPartZoneTitle_Center%>" ID="CenterColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="<%$Resources:cms,WebPartZoneTitle_CenterRight%>" ID="CenterRightColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                    </tr>
                </table>
            </td>
            </tr>
        <script language="javascript">            if (typeof (MSOLayout_MakeInvisibleIfEmpty) == "function") { MSOLayout_MakeInvisibleIfEmpty(); }</script>
    </table>
                <ul class="nav">
                <li>1</li>
                <li><a href="#section2">2</a></li>
                <li><a href="#section3">3</a></li>
            </ul>
    </div>
    <div class="section my" id="section2">
    <table>
        <tr>
            <td>
                <table>                            
                    <tr>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="CenterLeftMy" ID="CenterLeftMyColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="CenterMy" ID="CenterMyColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="CenterRightMy" ID="CenterRightMyColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                    </tr>
                </table>
            </td>
            </tr>
        <script language="javascript">            if (typeof (MSOLayout_MakeInvisibleIfEmpty) == "function") { MSOLayout_MakeInvisibleIfEmpty(); }</script>
    </table>
                  <ul class="nav">
                <li><a href="#section1">1</a></li>
                <li>2</li>
                <li><a href="#section3">3</a></li>
            </ul>
    </div>
    <div class="section home" id="section3">
    <table>
        <tr>
            <td>
                <table>                            
                    <tr>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="CenterLeftNews" ID="CenterLeftNewsColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="CenterNews" ID="CenterNewsColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                        <td id="_invisibleIfEmpty" name="_invisibleIfEmpty" valign="top" height="100%"> 
                        <WebPartPages:WebPartZone runat="server" Title="CenterRightNews" ID="CenterRightNewsColumn"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone> </td>
                    </tr>
                </table>
            </td>
            </tr>
        <script language="javascript">            if (typeof (MSOLayout_MakeInvisibleIfEmpty) == "function") { MSOLayout_MakeInvisibleIfEmpty(); }</script>
    </table>
                 <ul class="nav">
                <li><a href="#section1">1</a></li>
                <li><a href="#section2">2</a></li>
                <li>3</li>
            </ul>
    </div>
</asp:Content>

CSS:  You’ll need to come up with your own images for the background or can get the black/white images from http://tympanus.net/codrops/2010/06/02/smooth-vertical-or-horizontal-page-scrolling-with-jquery/

XYZScroll.CSS:

*{
    margin:0;
    padding:0;
}

body{
    background-color:transparent;
    width:12000px !important;
    position:absolute;
    top:0px;
    left:0px;
    bottom:0px;
    height:100%
}
BODY #s4-ribbonrow
{
    position:fixed;
    z-index:99;
    overflow:visible !important;
}
BODY #s4-titlerow
{
    position:fixed;
    z-index:98;
    margin-top:43px;
}
.section
{
    padding-top:134px;
    bottom:0px;
    width:4000px;
    float:left;
    height:900px;
}
.section h2{
    margin:50px 0px 30px 50px;
}
.section table{
    margin:0px 0px 0px 0px;
}
.home{
    background:url(/_layouts/images/xyzbranding/black.jpg) no-repeat top left;
}
.my{
    background:url(/_layouts/images/xyzbranding/white.jpg) no-repeat top left;
}

.news{
    background:url(/_layouts/images/xyzbranding/black.jpg) no-repeat top left;
}

.section ul{
    list-style:none;
    margin:20px 0px 0px 550px;
    font-weight:bold;
    font-size:14pt;
}
.home ul li{
    float:left;
    padding:5px;
    margin:5px;
    color:#aaa;
}
.home ul li a{
    display:block;
    color:#f0f0f0;
}
.home ul li a:hover{
    text-decoration:none;
    color:#fff;
}
.my ul li{
    float:left;
    padding:5px;
    margin:5px;
    color:#aaa;
}
.my ul li a{
    display:block;
    color:#222;
}
.my ul li a:hover{
    text-decoration:none;
    color:#000;
}
.news ul li{
    float:left;
    padding:5px;
    margin:5px;
    color:#aaa;
}
.news ul li a{
    display:block;
    color:#222;
}
.news ul li a:hover{
    text-decoration:none;
    color:#000;
}

XYZScrollEdit.CSS (for edit mode):

*{
    margin:0;
    padding:0;
}
body{
    background:#000;
    width:1400px !important;
    top:0px;
    left:0px;
    bottom:0px;
    overflow:visible !important;
}
.section{
    margin:0px;
    bottom:0px;
    width:1400px;
    height:100%;
}
.section table{
    margin:0px 0px 0px 0px;
    height:100%;
}

Breaking Up SharePoint 2010 Social Tags

If you ever need to break up the “Tags and  Notes” and “Like It” links on a SharePoint 2010 Master Page rendered by the GlobalSiteLink3 usercontrol, you could replace the reference on your master page with the following JavaScript and HTML.  I reflected the dll which renders these global links to find that it was simply rendering the JavaScript

<asp:Content ContentPlaceholderID="PlaceHolderMain" runat="server">

<script type="text/javascript">

function SendTag() {

SafeRunFunction(function () { TagDialogOpener.Open(encodeURI(window.location), document.title, '0'); }, 'SocialData.js', 'TagDialogOpener');

}

function GetQuickTag() {

SafeRunFunction(function () { var o = new SocialQuickTag('<%# this.ClientID %>'); o.url = encodeURI(window.location); o.title = document.title; o.tagged_text = 'Tagged this page with \u0027I Like It.\u0027'; o.failure_text = 'Failed tagging this page.'; o.replaceImg_style = 'border:0; left:-0px !important;top:-332px !important;position:absolute;'; o.AddQuickTag(0); }, 'SocialData.js', 'SocialQuickTag');

}

<script>

<td class="s4-socialdata-notif">

<div class="ms-socialNotif-Container">

<span class="ms-socialNotif-groupSeparator"></span>

<a class="ms-socialNotif" id="GetQuickTag" href="javascript:;" onclick="GetQuickTag();" title="Tags this page with &#39;I Like It.&#39; Tags make it easy to remember links and post items to your news feed." >

<span>

<span style="height:32px;width:32px;position:relative;display:inline-block;overflow:hidden;">

<img style="border:0; left:-0px !important;top:-132px !important;position:absolute;" id="GetQuickTagImg" alt="Tags this page with &#39;I Like It.&#39; Tags make it easy to remember links and post items to your news feed." src="/_layouts/images/mossfgimg.png"/>

</span>

<span class="ms-socialNotif-text">I Like It</span>

</span>

</a>

<a class="ms-socialNotif" id="TagsAndNotes" href="javascript:;" onclick="SendTag();" onmouseover="GetSocialNotification();" title="Tags help you remember links and classify the page. Notes are public comments. Tags and notes post to your news feed and work across different sites." >

<span>

<span style="height:32px;width:32px;position:relative;display:inline-block;overflow:hidden;">

<img style="border:0; left:-0px !important;top:-300px !important;position:absolute;" id="TagsAndNotesImg" alt="Tags help you remember links and classify the page. Notes are public comments. Tags and notes post to your news feed and work across different sites." src="/_layouts/images/mossfgimg.png"/>

</span>

<span class="ms-socialNotif-text">Tags</span>

</span>

</a>

</div>

</td>

Master Page Feature Receiver

If you have a visual studio 2010 project to deploy a master page and you want it applied during feature activation and unapplied when the feature is deactivated, use a feature receiver.  Visual Studio templates for SharePoint 2010 give you the ability to add a “Feature Receiver” which allows you to add some custom code to act on a feature at various phases of activation (for the master page, we only care about the “FeatureActivated” event and the “FeatureDeactivating” event).

To add the feature receiver, from your Visual Studio Project’s Solution Explorer, right click on your feature name and click Add Event Receiver. This automatically opens the receiver in the code window to edit. Replace the “FeatureActivated” and the “FeatureDeactivating” events with code in the following format (this code is for deploying to the web scope – you need to use the SPSite object if deploying to the Site scope instead of the SPWeb object).

        // Uncomment the method below to handle the event raised after a feature has been activated.
        public override void FeatureActivated(SPFeatureReceiverProperties properties)
        {
            SPWeb currentWeb = properties.Feature.Parent as SPWeb;
            Uri masterURI = new Uri(currentWeb.Url + "/_catalogs/masterpage/custom_v4.master");
            currentWeb.MasterUrl = masterURI.AbsolutePath;
            currentWeb.CustomMasterUrl = masterURI.AbsolutePath;
            currentWeb.Update();
        }

    // Uncomment the method below to handle the event raised before a feature is deactivated.
        public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
        {
            SPWeb currentWeb = properties.Feature.Parent as SPWeb;
            Uri masterURI = new Uri(currentWeb.Url + "/_catalogs/masterpage/v4.master");
            currentWeb.MasterUrl = masterURI.AbsolutePath;
            currentWeb.CustomMasterUrl = masterURI.AbsolutePath;
            currentWeb.Update();
        }

The above code sets the Master Page to your custom master page when the feature is activated and sets it back to the default master page when it is deactivated.

You should now have all that you need for deploying your custom brand files to your portal sites.