Skip to main content

Message to multiple site collections


Before some months I start following the TechNet forums about SharePoint. I read every week many questions, bookmark the interesting once, answer and research the others. I find it very useful and many new things are learn in a very fast way. Of course, the price of this is a time but let’s say I have a lot of it now J

I notice one issue in tree similar questions so I decide to write a post about it.

The scenario: how to add a message on a multiple site collections.
This might be necessary when some farm maintenance is planned and the users must be notified.

The solution: Site collection feature which use the JavaScript API to display the notification. The script is injected on the page with a delegate control AdditionalPageHead.

Code Sample:   download from here 

Explanation:


SharePoint 2010 JavaScript client API has the function SP.UI.Status.addStatus which adds astatus message on a page. The code is simple:

SP.UI.Status.addStatus('the mayans:','The world will not end on 22.12.2012!',true);


This function is a part for the client site API so the sp.js javascript must be loaded on the page.

The big question here is how such javascript can be loaded on each page. One possible opinion is with changes in the master page of each site collection. But this is a heavy task. And may cause some issues.

The better approach here is the use of the delegate control AdditionalPageHead.

First, what is a delegate control – this is a region in the page that allows the content to be replaced with custom one. All master pages have the following markup which define a delegete control with ID AdditionalPageHead :
<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead">
</SharePoint:DelegateControl>
Second, how we add our logic using this AdditionalPageHead control – with a element file that contains the following markup:

 <xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <Control Id="AdditionalPageHead" ControlSrc="~/_controltemplates/SPNotification/PageHead.ascx" Sequence="1001" />
</Elements>

here PageHead.ascx control is our custom control which contains the csutom javascript logic:

<script type="text/javascript">
    function AddNotification() {
   var sid = SP.UI.Status.addStatus('the mayans:', 'The world will not end on 22.12.2012! ', true);
    }
    ExecuteOrDelayUntilScriptLoaded(AddNotification, 'sp.js')
</script>

The final step is to use a powershell for deploying the solution and activating the feature in each site collection. Here is an example of search script. Feel free to modify it so it serve your needs:
------------------------------------------------------------------------
$snapin = Get-PSSnapin Microsoft.SharePoint.Powershell
if ($snapin -eq $null)
{
    Write-Host "Loading SharePoint Powershell Snapin"
    Add-PSSnapin "Microsoft.SharePoint.Powershell"
}

$solutionPackage = "SPNotification.wsp"
$path ="C:\something\"

# add solution
Add-SPSolution -LiteralPath ($path + $solutionPackage) -Confirm:$false
Write-Host "Adding solution" $solutionPackage
while ((Get-SPSolution | where-object {$_.Name -eq $solutionPackage}) -eq $null)
{
Start-Sleep -Seconds 3
}

#deploy solution
$solution = Get-SPSolution | where-object {$_.Name -eq $solutionPackage}
Install-SPSolution -Identity $solutionPackage -GACDeployment -Force
Write-Host -NoNewLine "Solution " $solution.Name "is deploying "
while ((Get-SPSolution | where-object {$_.Name -eq $solutionPackage}).Deployed -eq $false)
{
Start-Sleep -Seconds 3
}

#iteratio through all site collection and activate the feature
$farm = Get-SPFarm
$websvcs = $farm.Services | where -FilterScript
        {$_.GetType() -eq [Microsoft.SharePoint.Administration.SPWebService]}
foreach ($websvc in $websvcs) {
    foreach ($webapp in $websvc.WebApplications) {
        Write-Host "web app: " $webapp.Name
        foreach ($site in $webapp.Sites) {
           Write-Host "Activate feature in " $site.uRL
           Enable-SPFeature –Identity 'b6bcf98b-8f73-4c08-b4fe-32f052a8c971' –url $site.uRL
        }
    }
}
------------------------------------------------------------------------


Comments

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration       < wssawc : ClientPeoplePicker          Required ="true"          ValidationEnabled ="true"          ID ="peoplePicker"          runat ="server"   ...

SharePoint and List Joins with CAML

This came to me as an issue when I started migrating one project from SharePoint 2010 to SharePoint 2013. The code uses LINQ to SharePoint and it was not written in a clever way. We decide to use CAML queries and optimize the code. The scenario: Create gridview that gathers information from three(or more) lists. The problem: How to create the CAML query joins and projected fields correctly. Explanation : Option 1: Get generated CAML query from LINQ to SharePoint code This doesn’t work. I wrote the LINQ to SharePoint code connected the three lists. When I executed the code the following error was thrown – “ The query uses unsupported elements, such as references to more than one list, or the projection of a complete entity by using EntityRef/EntitySet. ” Here is some explanation about it and why this can’t be used. Option 2: Write the query yourself I found this article in MSDN . Read it ! The second part in it is exactly my scenario. But it takes me a lot of time to un...

SharePoint 2016: High Availability Farm Topology

MinRole concept was introduced in SharePoint 2016 and it aims to simplify the process of designing the farms. However, I still find ambiguous information about the count of servers in SharePoint 2016 farm. Let's ask ourselves the question - What is the minimum number of servers which allow High Availability MinRole farm? According to technet   we have the following options: Small High Availability (HA) MinRole farm 4 Four servers with two shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 6 Six servers with both dedicated and shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application servers ·    ...