Re: Save as Template (Subsite or List) by richard
richard
Wed Jun 11 10:08:39 CDT 2008
On Jun 10, 10:14 am, Rosa <Rosa_Shel...@hotmail.com> wrote:
> Hi,
>
> Is there any thruth in the fact that saving a list or site as template
> causes problems with the dependencies of the site? In other words will
> I experience problems with my new site if I have to change something
> on the master page?
>
> I am asking because I have been advised not to use "save as template"
> with the explanation that it may be a source of issues for later on.
>
> Please advise, as using this feature would save me a lot of time and
> repetitive work.
>
> Thanks
> Rosa
As long as you follow best practice you won't have a problem, and
"Save Site as Template" can be used. You don't say which version of
SharePoint you are using but it shouldn't make a difference.
The built-in site templates are provided using what used to be called
"Site Definitions" (I don't know if the terminology has changed in WSS
v3). Site definitions are held on the web front-end servers and
consist of collections of XML, HTML and ASPX files.
When you use "Save Site as Template", it basically stores the
differences/changes from the site definition it was originally created
from.
So I could envisage a scenario where you use "Save Site as Template"
and then make a destructive change to the site definition it was
created from - this would probably negatively impact the sites created
using that template.
*However* best practices says that you should not modify the built-in
site definitions, at all. Doing so would leave you in an unsupported
configuration. There is not really any reason to do this anyway. If
you need to modify/customise the built in site definitions, then you
create your own copy to work on.
As long as you understand and follow the rules, you will have no
problem
Richard