Skip to main content

Enabling Publishing Feature disables "Save Site as Template link"

SharePoint Server 2007 with Office SharePoint Server Publishing Feature activated on farm/site collection, but not on every site within the site collection. Those sites without the Publishing Feature activated include the Save Site as Template link under the Look and Feel section on the Site Settings page of the site.

Those sites with the Publishing Feature activated do not include the Save Site as Template link. But, if you hard code the Save Site as Template URL parameter into the browser address line, appended to the current site address, that is, http://server_name/sitedirectory/sitename/(underscore)layouts/savetmpl.aspx , you can still save those sites as templates. Sites created from those templates then include the Publishing Feature activated by default.
Labels:

Comments

Anonymous said…
Think twice before doing this. It is not supported by Microsoft. We did this at a customer site to make a lot of sites based on such templates.
By doing this I ran into an issue with sites made with this template. Look at this link for more info. Microsoft had a look at the problem and they said they would not look any further because we made template in a not supported way.
December 17, 2008 at 1:37 AM
essae said…
Wonderful article...............
Truck weighing scale
July 2, 2012 at 5:49 PM
Post a Comment

Popular posts from this blog

SharePoint: How to create a custom action to open Word Documents using "Edit in Microsoft Word".

Imagine you have a SharePoint custom search webpart, and on your search results, you return word documents, you will obviously want to at times be able to open them in your MS Word client program for editing. So basically, depending on your office client installed on your local machine, there are 2 different approaches that can be made for Office 2003 and Office 2007/10, using the same function " editDocumentWithProgID2 ". For Office 2003: - If your document libraries versioning settings have got "Require Check out" ticked, then you will first want to check out the document using: onclick ="CheckoutviaXmlhttp(‘{SiteURL}’, ‘{DocumentDownloadURL}’)" - Then to open the document, you use: onclick =" return editDocumentWithProgID2(‘ {DocumentDownloadURL} ’, ”, ‘SharePoint.OpenDocuments’, ’1′,’ {SiteURL} ’, ’0′);" href ="#" - and now combining the above 2 actions into one clickable action: onclick ="CheckoutviaXmlhttp(‘ {SiteURL} ’, ‘ {...
2 comments
Read more

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.
8 comments
Read more

How to Scope your SharePoint Projects

The "SharePoint project scope" is all of the things that must be produced to complete a SharePoint project. These 'things' are called deliverables and you need to describe them in depth as early in the SharePoint project as possible, so everyone knows what needs to be produced. Take these 5 Steps to scope your SharePoint projects: Step 1: Set the Direction Start off by setting the direction for the SharePoint project. Do you have an agreed SharePoint project Vision, Objectives and Timeframes? Are they specified in depth and has your customer agreed to them? Does everyone in the SharePoint project team truly understand them and why they are important? Only by fixing the SharePoint project direction can you truly fix the SharePoint project scope. Step 2: Scope Workshops The best way to get buy-in to your SharePoint project scope is to get all of the relevant stakeholders to help you define it. So get your SharePoint project sponsor, customer and other stakeholders in a ...
1 comment
Read more