Controlling publishing features from onet.xml

Vesa "vesku" Juvonen : Controlling navigation options from the onet.xml

Vesa "vesku" Juvonen : Controlling navigation options from the onet.xml — Sun, 14 Oct 2007 21:39:53 GMT

PingBack from http://blogs.msdn.com/vesku/archive/2007/03/23/controlling-navigation-options-from-the-onet-xml.aspx

re: Controlling publishing features from onet.xml

Ray — Fri, 19 Oct 2007 19:36:30 GMT

Well done!!!! I've been looking for a way to define available site templates based on the parent template. This did it.

To control these options through a feature would be even better.

Thanks

re: Controlling publishing features from onet.xml

Shane Perran — Wed, 07 Nov 2007 17:31:15 GMT

Great Post, these are very useful tips to bake into your custom development site definition.

One thing which is noticably missing for me is AlternateCSS and CustomJSUrl.

Cheers and great post.

re: Controlling publishing features from onet.xml

Peter — Thu, 10 Jan 2008 20:05:16 GMT

I created my custom publishing site definition with a custom master page. I didn't make a lot of modifications to the onet.xml file as I only wanted to use my custom master page. When I create the site, however, I get this error: The specified ChromeMasterUrl

'~SiteCollection/_catalogs/masterpage/PublishingMasterPage.master' must be a server-relative url within site collection '/sites/sdfs'.

What does this mean and how do I fix this?

Thanks for any help/suggestion.

re: Controlling publishing features from onet.xml

sonofthesun — Thu, 10 Jan 2008 20:19:00 GMT

This most likely means, that you do not have the configured master page available in the particular site collection (maybe the feature used for master page deployment is not activated in Site Collection level as it should).

In your case the master page should be located in the following url - /sites/sdfs/_catalogs/masterpage/PublishingMasterPage.master

It's good to notice, that you cannot refer to different site collections...

re: Controlling publishing features from onet.xml

Peter — Thu, 10 Jan 2008 21:05:27 GMT

Thanks sonofthesun,

In the onet.xml, I changed this line: <Property Key="ChromeMasterUrl" Value="~SiteCollection/_catalogs/masterpage/MBaseMaster.master"/> as shown in the article above.

"In your case the master page should be located in the following url - /sites/sdfs/_catalogs/masterpage/PublishingMasterPage.master"

But how can I upload this master page to the site collection when it has not been created yet. /sites/sdfs/ is the site I am trying to create using the custom sute definition.

Peter

re: Controlling publishing features from onet.xml

sonofthesun — Sat, 12 Jan 2008 15:37:32 GMT

"But how can I upload this master page to the site collection when it has not been created yet"

This can be done using features. Nevertheless it's recommended to deploy the resources used in the sites using features... this feature is then associated to site definition (onet.xml) to the siteFeatures section.

More information concernign this can be found from the SDK - http://msdn2.microsoft.com/en-gb/library/ms453137.aspx

re: Controlling publishing features from onet.xml

Hema — Mon, 17 Mar 2008 07:05:13 GMT

great post....Thanks a lot.

But How can we specify system master page through ONET.xml?

It`s really an urgent requirement from our side.

Any pointers will be appreciated..

thanks..

re: Controlling publishing features from onet.xml

sonofthesun — Mon, 17 Mar 2008 17:02:20 GMT

Hi Hema,

based on the documentation the attributes on the conficugation element could be used for this. These however do not work as expected, so at least in my cases we have used a custom feature receiver to set the value correctly.

This is demonstrated more deeply in the solution demo, which was released last week - http://blogs.msdn.com/vesku/archive/2008/03/11/dev-days-2008-example-solution-package.aspx

Basic idea is that in the onet xml, you add following to the webFeatures section.

</Properties>

</Feature>

Which will call the custom feature receiver (Microsoft.MCS.Intranet.FeatureHandlers.DefaultMasterPageFeatureReceiver - custom example code), which will set the values correctly in provisioning time.

re: Controlling publishing features from onet.xml

Farrukh — Wed, 16 Jul 2008 10:26:46 GMT

Hi,

I have mt custom master page installed as a feature.

I am activating this feature from onet.xml under "<SiteFeatures>", and under <WebFeatures> i have

...

But my publishing site is aways created with default "BlueBand.master". However when i see site features my custom master page feature is not activated. Then i am able to activate it and apply it using "Site Settings->Master Page".

Another thing to note that, if i change "ChromeMasterUrl" value to a page that doesn't exists e.g. "BlueBand_Custom2.master", it doesn't show me any error.

Any hint, what is wrong with my site definition?

WCM enabled collaboration sites

Vesa "vesku" Juvonen — Sun, 01 Feb 2009 23:55:29 GMT

Usually collaboration sites (team sites) and WCM functionalities (publishing sites) are seen as two totally