Comments on: SharePoint Branding Part 6 – A "solution" to all issues?

By: MrJasper

MrJasper — Fri, 28 Aug 2009 19:09:06 +0000

Ah if only it was quite so simple. A good series of articles, though a long way to say solutions is the answer. Anyway I happen to work for one of those big corporates and we have dozens of site collections covering multiple divisions etc, you get the picture. So my requirement is that I dont actually care what master page your site uses as long as it inherits the masterpage from the site collection. Note Inherit not copy. So your solution helps but because it requires a filename I cant really use it.

However you and anyone else in the same ballgame might want to check out this posting

http://msdn.microsoft.com/en-us/magazine/cc700347.aspx

This cracked it for me. Basically whats interesting from my part is this code in the receiver that gets activated everytime a site gets created

// fired whenever a new site is created
public override void FeatureActivated(SPFeatureReceiverProperties properties) {
SPWeb ChildSite = (SPWeb)properties.Feature.Parent;
SPWeb TopLevelSite = ChildSite.Site.RootWeb;
ChildSite.MasterUrl = TopLevelSite.MasterUrl;
ChildSite.CustomMasterUrl = TopLevelSite.CustomMasterUrl;
ChildSite.AlternateCssUrl = TopLevelSite.AlternateCssUrl;
ChildSite.SiteLogoUrl = TopLevelSite.SiteLogoUrl;
ChildSite.Update();
}

So basically it makes a team site or non publishing site refer to the top level masterpage and css if you wish. Read the whole article as there is a solution for replacing the application master too so you dont need to use up your space for the custom css file to apply your look and feel to all pages.

So i can deploy any masterpage into a site collection and a new site will pick it up. An exsiting site can have it cascaded.

By: thelastdon

thelastdon — Thu, 30 Oct 2008 18:35:54 +0000

Thanks for the articles dude. Article 6 close the deal for me, dude this was priceless training. I’m the
brand master on my job. Sharepoint Rocks!

By: jojo

jojo — Wed, 01 Oct 2008 22:48:33 +0000

to Brijesh H Patil —

try putting your spweb object into a using scope

here is a good article to explain
http://www.krokhmal.com/2006/10/05/MemoryLeaksUsingSPSObjectModel.aspx

By: CleverWorkarounds » SharePoint Branding - How CSS works with master pages - Part 1

Sun, 31 Aug 2008 09:54:02 +0000

[...] Links: [Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part [...]

By: max

max — Tue, 24 Jun 2008 07:31:04 +0000

the code doesn´t work for me :/

//CleverWorkarounds.nov.dll
using System;
using System.Collections.Generic;
using Microsoft.SharePoint;

namespace CleverWorkarounds.nov
{
public class SetDefaultMasterPage : Microsoft.SharePoint.SPFeatureReceiver //line 7
{
public override void FeatureActivated (SPFeatureReceiverProperties properties)
{
SPWeb MyCurrentWeb = properties.Feature.Parent as SPWeb;
MyCurrentWeb.MasterUrl = “/_catalogs/masterpage/nov.master”;
MyCurrentWeb.CustomMasterUrl = “/_catalogs/masterpage/nov.master”;
MyCurrentWeb.AlternateCSSURL = “/Style Library/nov.css”;
MyCurrentWeb.Update();
}
}
}

i get the error code CS0534 in line 7

can somebody help me, plz?

By: paisley

paisley — Tue, 17 Jun 2008 23:57:03 +0000

this is hands down the best one stop shopping place for learning how to use features/solutions for branding I have EVER seen. Most of this I experinced myself before reading it – very nice to see I am not the only one who had to stumble through it pice by piece. Nice job documenting it for future reference! This is definitely a bookmarker for those times you need to refresh your memory on the details. Lots of little clarifications that I needed as well. Your writing style is very entertaining.

thanks!

By: SharePoint Branding - SharePoint por Hector Insua

SharePoint Branding - SharePoint por Hector Insua — Wed, 04 Jun 2008 22:23:38 +0000

[...] Links: [Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7] Published Jun 04 2008, 11:23 PM by [...]

By: Brijesh H Patil

Brijesh H Patil — Mon, 05 May 2008 10:43:58 +0000

Hope you people are very excited in using the recursive function and
forgetting to close the SPWeb and SPSite objects. As per your recursive there
is a huge memory leakage… ha ha there comes the point… how would you handle
that Mister… well I am facing the problem with the memory leaks and sharepoint logs
is filling up … check that and let me know with the appropriate solution…

Many Thanks,
Brijesh.

By: Manfred

Manfred — Wed, 16 Apr 2008 15:15:00 +0000

Hi again!

Another small update:

When deploying the solution I posted earlier, everything went fine until I checked
the subwebs… I forgot that the folder “Style Library” is located in the root site
of the SPSite and is not virtual for the subwebs. So here’s a better solution:
public override void FeatureActivated(SPFeatureReceiverProperties properties) { SPSite MySite = (SPSite)properties.Feature.Parent; SPWebCollection MyWebSites = MySite.AllWebs;


            foreach (SPWeb MyCurrentWeb in MyWebSites)

            {

                SetMaster(MyCurrentWeb, MySite);

            }
        }
        private void SetMaster(SPWeb MyWeb, SPSite MySite)

        {

            MyWeb.MasterUrl = "/_catalogs/masterpage/YourMaster.master";

            MyWeb.CustomMasterUrl = "/_catalogs/masterpage/YourMaster.master";

            MyWeb.AlternateCssUrl = MySite.Url+"/Style Library/YourCSS.css";

            MyWeb.Update();

if (MyWeb.Webs.Count > 0) { foreach (SPWeb SubWeb in MyWeb.Webs) SetMaster(SubWeb, MySite); } }

Have fun!

By: Manfred

Manfred — Wed, 16 Apr 2008 11:04:42 +0000

Hi there!

Great Page, great articles. I truly enjoy your way of writing.
Just a small “upgrade” to your solution:
If you want to set the new Master for all Webs in your site (including the subwebs
of the subwebs and so on) you may need this method:

public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPSite MySite = (SPSite)properties.Feature.Parent;
SPWebCollection MyWebSites = MySite.AllWebs;

foreach (SPWeb MyCurrentWeb in MyWebSites)
{
SetMaster(MyCurrentWeb);
}

}

private void SetMaster(SPWeb MyWeb)
{
MyWeb.MasterUrl = “/_catalogs/masterpage/YourMaster.master”;
MyWeb.CustomMasterUrl = “/_catalogs/masterpage/YourMaster.master”;
MyWeb.AlternateCssUrl = “/Style Library/YourCSS.css”;
MyWeb.Update();

if (MyWeb.Webs.Count > 0)
{
foreach (SPWeb SubWeb in MyWeb.Webs)
SetMaster(SubWeb);
}
}

As you can see it contains a small recursive function that runs through the
whole site.

Hope it helps.

Greets from Germany

Manfred