MOSS 2007 – Save site as a template missing

This is just a quick one for Tony.  😉

If you are trying to save a site as a template in WSS v3 or MOSS 2007 you will find that the link “Save site as template” is only available under Look and Feel at the Top Level of the site collection.  Doesn’t really help if you want to save a sub site as a template now does it?  If you would like to save a sub site as a template you need to append _layouts/savetmpl.aspx to your sub sites url.  I am guessing Microsoft just forgot this link and it will be around by the time we go RTM.

So just to make it clear.  If your subsite is

You would go to

and then you would be able to save the site as a template.

Shane SharePoint Help


Why I think you should be mindful of using FrontPage 2003 with SharePoint.

This whole pile of information comes from me being emailed the following question after telling someone not to use FrontPage.  “Shane, do you have a recommended list of HTML editors we should be using with Sharepoint?”


FrontPage (FP) is the recommend and only editor for SharePoint.  I am just not a fan of its uncontrolled/unplanned usage.  In the hands of a trained professional it can used to accomplish some tasks otherwise impossible but, it is a last resort.  Most things can be done using the standard SharePoint user interface.  If large scale, consistent, or more complex changes are necessary then I recommend the use of custom site definitions.  Only in extreme cases do I recommend the use of FP.  Here is a list of reasons why I don’t like the use of FP.


1.        UnGhosting – This causes a page to be broken from the default template connection and stored independently in the database.  This has a performance penalty (See Mike Fitzmaurice blog and causes you to lose the ability to do site wide changes later.   More information on ghosting you can read 

2.       Upgrading – Down the road when you do choose to do upgrades you will have unique challenges around each page that you have edited with FP.  You will be at a minimum redoing the work.  If you use Site Definitions you also will have to deal with them at upgrade time but, if you are consistent in your site definition you will be able to create a mapping file to automate the upgrade.

3.       Lack of control – If you let whomever would like use FP to make changes then you will never retain a consistent brand or look and feel.  Maybe one page will have the navigation bar on the bottom of the page the next page will have it on the left.  How will users find things?  The out of the box pages may be considered ugly (I like them) but at least they are consistent.  Once a user get used to finding things on one site they will know how to find them on the next.  If people start changing things on a whim then all bets are off.


So yes FP is the only HTML editor for SharePoint but fortunately you normally don’t have to use it.  Any type of color, branding, or look and feel changes should be made using style sheets, templates, themes, site definitions or more pratically a combination of those.  The only reasons I do use FP is:


1.       Data View Web Part – Just awesome.  Allows you to view that business data you have in databases right in SharePoint without in work on the users part.  It can do lots more but I will let you go elsewhere if you want more info. 

2.       Modifying Navigation – You can edit the links in the nav bar of a site using FP without unghosting.  Remember when you open a site with FP as long as you don’t have to hit save to keep your changes you haven’t unghosted your site.

3.       Backup/Restore – You can use FP backup/restore to move sites around.  It really is just a graphical view of smigrate.exe.  More info on how to move the site from Microsoft.   

I hope this helps clear up the age old question why I feel you should use FrontPage sparingly and yes I do expect people to disagree with me but such is life.  J