<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Developing a Custom Master Page (Master Pages and SharePoint part 3 of 6)</title>
	<atom:link href="http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6/feed" rel="self" type="application/rss+xml" />
	<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6</link>
	<description>SharePoint Magazine is an online Magazine dedicated to the world of SharePoint</description>
	<pubDate>Tue, 06 Jan 2009 12:01:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: ggalipeau</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-540</link>
		<dc:creator>ggalipeau</dc:creator>
		<pubDate>Wed, 17 Dec 2008 03:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-540</guid>
		<description>Hey Bikram,&lt;br&gt;There are a few ways to do what you are suggesting. What I usually do is create custom site definitions for each kind of site. These site definitions can have references to different master pages. Then, when someone goes and creates a site, they just have to pick the correct site definition from the choice of templates on the create new site page. The last article in this series explains how to create site definitions. This might seem overkill, but you can get a lot of other benefits from using site definitions including turning features on or off depending on the site definition chosen. Anyways, that is what I typically do.&lt;br&gt;Good luck,&lt;br&gt;Gregt</description>
		<content:encoded><![CDATA[<p>Hey Bikram,<br />There are a few ways to do what you are suggesting. What I usually do is create custom site definitions for each kind of site. These site definitions can have references to different master pages. Then, when someone goes and creates a site, they just have to pick the correct site definition from the choice of templates on the create new site page. The last article in this series explains how to create site definitions. This might seem overkill, but you can get a lot of other benefits from using site definitions including turning features on or off depending on the site definition chosen. Anyways, that is what I typically do.<br />Good luck,<br />Gregt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bikram K Bhuyan</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-538</link>
		<dc:creator>Bikram K Bhuyan</dc:creator>
		<pubDate>Tue, 16 Dec 2008 06:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-538</guid>
		<description>Hi Greg,&lt;br&gt;&lt;br&gt;I have the following requirement which might be very basic to you. But it will be good if you could provide some pointer to this.&lt;br&gt;&lt;br&gt;1. I have created a WSS site in which I have created a new master pages based on my sites&#39;s look and feel and created most of the pages. This is working fine.&lt;br&gt;2. There are 10% of the pages which does not fall into the standard look and feel. Like many pages has content without the any header and footer etc.&lt;br&gt;&lt;br&gt;Could you please suggest how to create these 10% of the pages which does not follow the normal master page structure.&lt;br&gt;&lt;br&gt;I guess I need to create multiple master pages. But not sure how to use the other master pages as when I create a new pages using the "Site Setting" option it takes the default master page.&lt;br&gt;&lt;br&gt;Please provide some solution to this issues.&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;Bikram.</description>
		<content:encoded><![CDATA[<p>Hi Greg,</p>
<p>I have the following requirement which might be very basic to you. But it will be good if you could provide some pointer to this.</p>
<p>1. I have created a WSS site in which I have created a new master pages based on my sites&#39;s look and feel and created most of the pages. This is working fine.<br />2. There are 10% of the pages which does not fall into the standard look and feel. Like many pages has content without the any header and footer etc.</p>
<p>Could you please suggest how to create these 10% of the pages which does not follow the normal master page structure.</p>
<p>I guess I need to create multiple master pages. But not sure how to use the other master pages as when I create a new pages using the &#8220;Site Setting&#8221; option it takes the default master page.</p>
<p>Please provide some solution to this issues.</p>
<p>Thanks,<br />Bikram.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ggalipeau</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-430</link>
		<dc:creator>ggalipeau</dc:creator>
		<pubDate>Fri, 14 Nov 2008 19:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-430</guid>
		<description>Hi Janajit,&lt;br&gt;The best way to do this is to create a custom site definition and activate it from there. So, when a new site is created from the site definition it will also activate the correct features. I will be showing this when I do the final article of the series.The basica process is to add the GUID of the feature to the onet.xml file in the site definition.&lt;br&gt;However, you might want to attach a feature to a non-custom site definition (i.e.: one of the out of the box ones). Or to one you have already deployed and don&#39;t want to change. Well, there is a way to do this also. It is called feature stapling. I would suggest searching the internet for feature stapling. There are a lot of good articles on it.&lt;br&gt;Hope this helps,&lt;br&gt;Greg</description>
		<content:encoded><![CDATA[<p>Hi Janajit,<br />The best way to do this is to create a custom site definition and activate it from there. So, when a new site is created from the site definition it will also activate the correct features. I will be showing this when I do the final article of the series.The basica process is to add the GUID of the feature to the onet.xml file in the site definition.<br />However, you might want to attach a feature to a non-custom site definition (i.e.: one of the out of the box ones). Or to one you have already deployed and don&#39;t want to change. Well, there is a way to do this also. It is called feature stapling. I would suggest searching the internet for feature stapling. There are a lot of good articles on it.<br />Hope this helps,<br />Greg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janajit</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-427</link>
		<dc:creator>Janajit</dc:creator>
		<pubDate>Fri, 14 Nov 2008 02:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-427</guid>
		<description>Hi Greg,&lt;br&gt;  I will bother you once more.All your previous suggestions were so helpful.I want to have certain fetaures activated by default when I create a site collection.Is there a way to do this?</description>
		<content:encoded><![CDATA[<p>Hi Greg,<br />  I will bother you once more.All your previous suggestions were so helpful.I want to have certain fetaures activated by default when I create a site collection.Is there a way to do this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ggalipeau</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-384</link>
		<dc:creator>ggalipeau</dc:creator>
		<pubDate>Tue, 28 Oct 2008 21:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-384</guid>
		<description>Hi Janajit,&lt;br&gt;You might want to post these kind of issues to the msdn formuns for SharePoint: &lt;a href="http://social.msdn.microsoft.com/Forums/en-US/category/sharepoint/"&gt;http://social.msdn.microsoft.com/Forums/en-US/c...&lt;/a&gt; . There are lots of MVPs and SharePoint enthusiasts like myself that answer questions there.</description>
		<content:encoded><![CDATA[<p>Hi Janajit,<br />You might want to post these kind of issues to the msdn formuns for SharePoint: <a href="http://social.msdn.microsoft.com/Forums/en-US/category/sharepoint/" onclick="javascript:pageTracker._trackPageview('/social.msdn.microsoft.com');"></a><a href="http://social.msdn.microsoft.com/Forums/en-US/c.." onclick="javascript:pageTracker._trackPageview('/social.msdn.microsoft.com');" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/c..</a>. . There are lots of MVPs and SharePoint enthusiasts like myself that answer questions there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ggalipeau</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-382</link>
		<dc:creator>ggalipeau</dc:creator>
		<pubDate>Tue, 28 Oct 2008 21:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-382</guid>
		<description>Yes, you don&#39;t want to modify anything in the 12 hive directly. There are usually other ways to do these things through adding new custom features.</description>
		<content:encoded><![CDATA[<p>Yes, you don&#39;t want to modify anything in the 12 hive directly. There are usually other ways to do these things through adding new custom features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janajit</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-381</link>
		<dc:creator>Janajit</dc:creator>
		<pubDate>Tue, 28 Oct 2008 02:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-381</guid>
		<description>I am facing another problem Greg.This time its to do with custom groups and permission levels.I want to create custom groups and permision levels.In order to accomplish this I am using an XML config file for specifying custom groups and permission levels and I am using SPFeatureReceiver to create the custom stuff during portal creation by referring to this feature from my onet.xml. The problem is even though I am using Properties["vti_associatevisitorgroup"] = group.ID.ToString() to hide Visitors ,Members and Owners(default groups), these are persisting after the collaboration portal gets created.Whats really beats me is its all working finne with team sites.The problem is cropping up for the collaboration portal alone.Please help me out.I am in a bad stuck.</description>
		<content:encoded><![CDATA[<p>I am facing another problem Greg.This time its to do with custom groups and permission levels.I want to create custom groups and permision levels.In order to accomplish this I am using an XML config file for specifying custom groups and permission levels and I am using SPFeatureReceiver to create the custom stuff during portal creation by referring to this feature from my onet.xml. The problem is even though I am using Properties["vti_associatevisitorgroup"] = group.ID.ToString() to hide Visitors ,Members and Owners(default groups), these are persisting after the collaboration portal gets created.Whats really beats me is its all working finne with team sites.The problem is cropping up for the collaboration portal alone.Please help me out.I am in a bad stuck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janajit</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-380</link>
		<dc:creator>Janajit</dc:creator>
		<pubDate>Tue, 28 Oct 2008 02:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-380</guid>
		<description>Well I did modify the files in the features folder ie I modified the Publishing,PublishingResources and SiteSettings features(Changed tags in associated xml files) .So what you are suggesting is I create custom featurs and modify them?</description>
		<content:encoded><![CDATA[<p>Well I did modify the files in the features folder ie I modified the Publishing,PublishingResources and SiteSettings features(Changed tags in associated xml files) .So what you are suggesting is I create custom featurs and modify them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ggalipeau</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-372</link>
		<dc:creator>ggalipeau</dc:creator>
		<pubDate>Sat, 25 Oct 2008 01:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-372</guid>
		<description>Hey Janajit,&lt;br&gt;You said you modified the manifest files - do you mean you actually modified files in the 12 hive to do this? Or, did you accomplish this in another way (i.e.: wrote a new feature or something else)? The reason I ask is that you shouldn&#39;t modify files in the 12 hive. If you didn&#39;t do that then your approach is fine and you should be able to remove the custom action changes by changing the custom feature again.</description>
		<content:encoded><![CDATA[<p>Hey Janajit,<br />You said you modified the manifest files - do you mean you actually modified files in the 12 hive to do this? Or, did you accomplish this in another way (i.e.: wrote a new feature or something else)? The reason I ask is that you shouldn&#39;t modify files in the 12 hive. If you didn&#39;t do that then your approach is fine and you should be able to remove the custom action changes by changing the custom feature again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janajit</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-367</link>
		<dc:creator>Janajit</dc:creator>
		<pubDate>Thu, 23 Oct 2008 15:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-367</guid>
		<description>Hi Greg,&lt;br&gt;&lt;br&gt; Thanks a lot for your suggestion.I managed to hide the link in another way though.I modified custom action settings in the manifest files of SiteSettings,Publishing and Publishing resources features to drop the links.What do you think about this way and the next question that arises is Can I add the links back for a particular site collection once I have dropped them by modifying the aforesaid features.Could you please suggest a method to unhide the links which I dropped using customaction tags of Sitesettings, Publishing and PublishingResources features.</description>
		<content:encoded><![CDATA[<p>Hi Greg,</p>
<p> Thanks a lot for your suggestion.I managed to hide the link in another way though.I modified custom action settings in the manifest files of SiteSettings,Publishing and Publishing resources features to drop the links.What do you think about this way and the next question that arises is Can I add the links back for a particular site collection once I have dropped them by modifying the aforesaid features.Could you please suggest a method to unhide the links which I dropped using customaction tags of Sitesettings, Publishing and PublishingResources features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ggalipeau</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-357</link>
		<dc:creator>ggalipeau</dc:creator>
		<pubDate>Wed, 22 Oct 2008 02:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-357</guid>
		<description>Hi Janajit,&lt;br&gt;Sorry it took me so long to reply, I have been away for a few days. Anyways, I would suggest doing this with permissions. You shouldn&#39;t give anyone permissions to get to that link if you don&#39;t want them to do that. Even if you want to give people Admin permissions, you might want to consider making a custom Admin permission group that can do everything except this.</description>
		<content:encoded><![CDATA[<p>Hi Janajit,<br />Sorry it took me so long to reply, I have been away for a few days. Anyways, I would suggest doing this with permissions. You shouldn&#39;t give anyone permissions to get to that link if you don&#39;t want them to do that. Even if you want to give people Admin permissions, you might want to consider making a custom Admin permission group that can do everything except this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janajit</title>
		<link>http://sharepointmagazine.net/technical/customisation/developing-a-custom-master-page-master-pages-and-sharepoint-part-3-of-6#comment-346</link>
		<dc:creator>Janajit</dc:creator>
		<pubDate>Wed, 15 Oct 2008 23:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=749#comment-346</guid>
		<description>Hi I its a great article.I have one question however.I have designed a custom master page without using the designer.Now since I do not want users to be able to tinker with my  custom master page in any way I want to disable the master page selection link in Site Actions&#62;&#62; Site Settings&#62;&#62;Look and Feel&#62;&#62; Master Page link.How can I do that? Could you please help me?</description>
		<content:encoded><![CDATA[<p>Hi I its a great article.I have one question however.I have designed a custom master page without using the designer.Now since I do not want users to be able to tinker with my  custom master page in any way I want to disable the master page selection link in Site Actions&gt;&gt; Site Settings&gt;&gt;Look and Feel&gt;&gt; Master Page link.How can I do that? Could you please help me?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
