<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: SharePoint: Save Publishing Site as Template in MOSS 2007</title>
	<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/</link>
	<description>ls /usr/lolcat</description>
	<pubDate>Sun, 12 Oct 2008 11:03:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Ben</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10378</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Thu, 11 Sep 2008 07:27:48 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10378</guid>
		<description>This leaves us with a bit of a problem. Now if I want my users to duplicate sites over and over again from a clean beginning I need to hire a developer - I've not been able to find a way to easily roll up an existing site into a solution off the shelf - and with the Sharepoint Gold rush in full swing developers are tough to come buy...

Meanwhile frustrated users Google the problem, find the templates secret page and away they go :-)

How does everyone else deal with this?</description>
		<content:encoded><![CDATA[<p>This leaves us with a bit of a problem. Now if I want my users to duplicate sites over and over again from a clean beginning I need to hire a developer - I've not been able to find a way to easily roll up an existing site into a solution off the shelf - and with the Sharepoint Gold rush in full swing developers are tough to come buy...</p>
<p>Meanwhile frustrated users Google the problem, find the templates secret page and away they go <img src='http://blog.netnerds.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>How does everyone else deal with this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AC [MVP MOSS]</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10351</link>
		<dc:creator>AC [MVP MOSS]</dc:creator>
		<pubDate>Thu, 28 Aug 2008 13:59:50 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10351</guid>
		<description>I wouldn't exactly recommend this as not only is it not supported (there's a reason the product team took the Save Site As Template out for Publishing sites), I've found it to be very problematic.</description>
		<content:encoded><![CDATA[<p>I wouldn't exactly recommend this as not only is it not supported (there's a reason the product team took the Save Site As Template out for Publishing sites), I've found it to be very problematic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10339</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 25 Aug 2008 18:17:14 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10339</guid>
		<description>On the surface, this appeared to work jsut fine.  But one thing that did not come over automatically was the search visibility.  For me, my search visibility setting did not come over.  Rahter, the default "Do not index ASPX pages if this site contains fine-grained permissions".  I had to set this manually.

While I have a feature that will set this to "Always Index ASPX pages" I was wondering if anyone knew why the Site Collection templte did not pick this up.


Thanks

Tom</description>
		<content:encoded><![CDATA[<p>On the surface, this appeared to work jsut fine.  But one thing that did not come over automatically was the search visibility.  For me, my search visibility setting did not come over.  Rahter, the default "Do not index ASPX pages if this site contains fine-grained permissions".  I had to set this manually.</p>
<p>While I have a feature that will set this to "Always Index ASPX pages" I was wondering if anyone knew why the Site Collection templte did not pick this up.</p>
<p>Thanks</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dolly</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10276</link>
		<dc:creator>Dolly</dc:creator>
		<pubDate>Thu, 10 Jul 2008 23:48:37 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10276</guid>
		<description>Hmmm, I've got a problem with Site Templates but it doesn't appear that it's due to the following, "content types are not saved with site templates", as Neil says. I use the link "/_layouts/savetmpl.aspx" to save the template, then upload it and create a site with it and all seems fine.  Our custom content types are all there.

When I attempt to create a site within my new site, however, the site template is *not* available.  I can 'Reset all subsite to inherit these preferred subsite template settings' and it fixes things but I shouldn't have to do this.  Any ideas anyone?</description>
		<content:encoded><![CDATA[<p>Hmmm, I've got a problem with Site Templates but it doesn't appear that it's due to the following, "content types are not saved with site templates", as Neil says. I use the link "/_layouts/savetmpl.aspx" to save the template, then upload it and create a site with it and all seems fine.  Our custom content types are all there.</p>
<p>When I attempt to create a site within my new site, however, the site template is *not* available.  I can 'Reset all subsite to inherit these preferred subsite template settings' and it fixes things but I shouldn't have to do this.  Any ideas anyone?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mina</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10273</link>
		<dc:creator>Mina</dc:creator>
		<pubDate>Tue, 08 Jul 2008 13:05:23 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10273</guid>
		<description>Shail,
How did you work on creating these 10 other departments... What was the most efficient way?
Thanks in advance.</description>
		<content:encoded><![CDATA[<p>Shail,<br />
How did you work on creating these 10 other departments... What was the most efficient way?<br />
Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shail</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10186</link>
		<dc:creator>Shail</dc:creator>
		<pubDate>Wed, 21 May 2008 16:01:35 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10186</guid>
		<description>Guys,

I was using Sharepoint 2003 and now just got into MOSS. Basically, I have a task where we create a site.. say for eg: Department and then add some inbuilt webparts and some custom web parts.. Now I want to use this site as template site for 10 other departments. In SP 2003, I saved the site as template and used it to create other sites.. Did anything change in MOSS or is there any other better way of achieving this?

Thanks in advance for your response!</description>
		<content:encoded><![CDATA[<p>Guys,</p>
<p>I was using Sharepoint 2003 and now just got into MOSS. Basically, I have a task where we create a site.. say for eg: Department and then add some inbuilt webparts and some custom web parts.. Now I want to use this site as template site for 10 other departments. In SP 2003, I saved the site as template and used it to create other sites.. Did anything change in MOSS or is there any other better way of achieving this?</p>
<p>Thanks in advance for your response!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10118</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Wed, 23 Apr 2008 02:03:16 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10118</guid>
		<description>Thanks for the tip, Neil! I wondered if there was a reason.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip, Neil! I wondered if there was a reason.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Wells-West</title>
		<link>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10069</link>
		<dc:creator>Neil Wells-West</dc:creator>
		<pubDate>Fri, 11 Apr 2008 15:13:51 +0000</pubDate>
		<guid>http://blog.netnerds.net/2008/03/sharepoint-save-publishing-site-as-template-in-moss-2007/#comment-10069</guid>
		<description>Hi. This is incorrect. I am consultant with a MS gold partner and the reason you can't/shouldn't save sites with publishing features enabled is because content types are not saved with site templates. What do publishing pages rely on? That's right - page and page layout content types. So if you create a custom page layout content type for your publishing site and want to be able to cerate pages based on that custom content type in otehr publishing sites you will either need to recreate the custom content type or write a feature to deploy it to all sites that require it. Simple really. MS hides links for good reasons....</description>
		<content:encoded><![CDATA[<p>Hi. This is incorrect. I am consultant with a MS gold partner and the reason you can't/shouldn't save sites with publishing features enabled is because content types are not saved with site templates. What do publishing pages rely on? That's right - page and page layout content types. So if you create a custom page layout content type for your publishing site and want to be able to cerate pages based on that custom content type in otehr publishing sites you will either need to recreate the custom content type or write a feature to deploy it to all sites that require it. Simple really. MS hides links for good reasons....</p>
]]></content:encoded>
	</item>
</channel>
</rss>
