Recreate site from template - publishing feature

I have a site with Publishing feature activated and I need to recreate the same site on another server (actually, it is many sites). How can I do that? I don't have "save as template" option, but i have created template through url /_layouts/savetmpl.aspx.
But, how can I recreate this site on another server (also publishing feature activated)?
Or is the approach with saving site definition better solution? How do I do that, can I recreate site from site definition??

You can use the template you created by downloading it from the Site Template Gallery of your current site. Then take the .stp file and upload it to the site template gallery of the new server where you want to make the template available. After
that, the template should become available in your creation dialog.
A better way to recreate the site exactly as is, on another farm, is to use either Powershell or good old STSADM.
Execute this from the current server in a SharePoint Powershell window:
stsadm -o backup -url http://your-site-url-here -filename SiteFileName.bak -nolock
Then copy the SiteFileName.bak file to a server in the target farm and from a SharePoint Powershell window, execute this:
stsadm -o restore -url http://new-target-url-to-use -filename C:\Path-to-Backup-file\SiteFileName.bak
If the site already exists and you wish to overwrite it, simply add the -overwrite switch to the above command.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint
Wher I try to save template to another site, I don't have it available when I want to create new site (because of Publishing feature), I have only two templates from Publishing template, not Custom.
These Powershell commands are great, but this only works for top level site. Is there similar solution for subsites?

Similar Messages

DW CS4 not updating sites from template. Why?

Ok, this has become quite annoying. Can anyone tell me if this is a common occurrence with DW, because I just started my website and, if it's going to do this, I'd just as soon use Adobe GoLive or something else to create the site.
Here's an rerun of what happened:
Created Template
Saved Template
File > New > Page from template > My Site > My Template > Checked box that says update page from template > Create
Save new site (blah.html)
Make change to template
Save template, doesn't update newly created site (in fact, doesn't even show that it is).
Rebuilt site cache, same nonsense. Tried to update manually via modify / templates menu, same nonsense. Resaved template, recreated page, same nonsense.
Irritated. This process is taking way too long for something that shouldn't be happening. Anyone know of a surefire fix, as this has happened a couple of times.
Oh, and yes, when I open the page, there is a marker in the top right corner identifying the template which it is associated with (in case anyone was wondering).

I have DW CS4, not DW4 (sorry about that).
Still, I read through the SSI information you sent me and that looks.... less of a hassle.
I'll go that route.
Thanks!

Cross Site collections navigation with publishing feature enabled into sharepoint 2010??

Hi,
Is it possible to cross site collection navigation in share point 2010 with publishing feature enabled? Right now we have a site collection with all the departmental sites within it. We are trying to create separate site collection with separate content
database for each department for better management. But problem with Global navigation as OOB does not provide cross site collection navigation functionality, So looking for multiple site collections or navigation for more than one site collection under single
umbrella. i was able to get the cross site collection navigation in my development env without publishing feature enabled using below link. But problem with production environment, as all the site collections and sites are publishing feature enabled. how i
am gonna do cross site navigation with publishing feature enabled?
http://www.itsolutionbraindumps.com/2011/10/sharepoint-2010-cross-site-collection.html
Any link or suggest will be greatly appreciated !

Hi,
According to your description, my understanding is that you want to create cross site collections navigation with publishing feature enabled in SharePoint 2010.
Publishing sites (sites with publishing infrastructure) have their own navigation API, and it is much more complicated task to preserve cross-publishing sites navigation.
We need to implement our own custom navigation provider.
Please refer to the link below about the cross site collections navigation with publishing feature enabled:
http://sadomovalex.blogspot.com/2010/12/cross-site-and-cross-site-collection.html
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Cannot save site as template (An Unknown Error Has Occurred) even with the correct permissions/settings?

Hi everyone,
We're currently experiencing some issues saving a site as an template.
This is the error we get in the event viewer:
Exception information:
Exception type: InvalidOperationException
Exception message: Error saving solution to temporary file
at Microsoft.SharePoint.SPSolutionExporter.ExportWebAsSolution()
at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl, Action`1
solutionPostProcessor, Boolean activateSolution)
at Microsoft.SharePoint.ApplicationPages.SaveAsTemplatePage.BtnSaveAsTemplate_Click(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
I've looked everywhere for this error and all the sites point to a permission issue; I've check that already: it isn't. We've tried creating this template via PowerShell, C# command line application, SharePoint Designer and the savetmpl.aspx page at the
site itself: no result; Yes, it is a publishing site, but that didn't stop us. We've created a site template from a different site and the publishing feature was also enabled there.
Later this site really helped me into digging deeper into the logs: http://www.sharepointblogs.be/blogs/vandest/archive/2014/05/23/sharepoint-how-to-troubleshoot-issues-with-save-as-template.aspx
The annoying part is: the folder that is being created by the web application pool user when saving the site as a template is totally empty!
How can this be? Did I miss something? Could someone help me with this issue?
Thanks in advanced!
With kind regards,
M. Hekman

Hi ,
According to your description, my understanding is that you encountered the error “Error saving solution to temporary file” when you tried to save a publishing site as a template.
For your issue, please make sure you have set the SaveSiteAsTemplateEnabled property of your publishing site to true. You can refer to the PowerShell script as below:
# Get a reference to the target site
$web = Get-SPWeb http://Intranet.SWRanger.com/Publishing
# Update the property bage value and set it to the string value "true"
$web.AllProperties["SaveSiteAsTemplateEnabled"] = "true"
# Commit the property change to server
$web.Update()
Reference:
http://blogs.msdn.com/b/how24/archive/2013/06/13/save-publishing-site-as-a-template.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Remove reference to Publishing Feature from site template

Hi all, I have a custom site collection which I package as a wsp to deploy as a custom solution template to multiple sites.
Accidentally, years ago I've activated Publishing Features in my site template and then disabled them. I still work and create new templates from my site without any problems (ShP 2010).
Now, I've installed SharePoint 2013 and updated my site template to 2013. Then, I've created the new wsp but when I try to apply my template to a new site collection I receive an error message: "Failed to instantiate file "AlternateMediaPlayer.xaml"
from module "Style LibraryMedia Player_Features\PublishingResources": Source path "Features\PublishingResources\AlternateMediaPlayer.xaml" not found."
How could I remove all the reference to features belonging to Publishing Features?

Hi Elena_B,
According to your description, my understanding is that you want to remove reference to publishing feature from site template in SharePoint 2013.
You can do as the followings:
extract all files from WSP file by (a tool or) changing the wsp file to cab file and then extract all files to a working folder.
edit the Onet.xml file to remove the unsupported features and save the changes.
create a ddf file for makecab.exe to repack the wsp
run cmd: makecab /f my.ddf to generate the new WSP file
More information, please refer to the link:
http://lassewikmark.wordpress.com/2009/11/16/howto-remove-unused-features-from-a-site-template-file/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/37e96410-7fb9-462b-a3e7-c150f2de7107/site-template-and-disabled-feature?forum=sharepointadminprevious
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

How to recreate an already published site from a saved copy....

I recently lost a drive and was only able to salvage my documents folder in which I had saved a copy of an already published iWeb site. How do I relink these files? The site is fully funktional and I have all the files on the same computer...I've reinstalled the app..Now what???
PowerBook 17' Mac OS X (10.4.5)

The file that you need is in your domain.sites file, it lives here:
User / Library / Application Support / iWeb / Domain.sites
If you dont have this file, then you cannot do anything other than start again, maybe copy paset from the published site.
All you need to do is put your old domain.sites file in the location above and open iWeb.
You may need to create the /iWeb folder, to do this open iWeb, add a page, any page and then Quit iWeb. This creates a domain file in the /iWeb folder and tells iWeb where to look for it. Delete this new domain file and replace it with your old one.
Will
1GHz G4, 15" PowerBook, Airport Network, 1G iPod Mini Mac OS X (10.4.5) Getting Started with iWeb - Tips here

How do I revert my iWeb published site (the actual published site in internet is up to date) the one on my repaired computer is old from a time machine back-up and out of date?

The question is above I repaired my hardrive and the iweb site is from an old time machine back-up. In the web my site is up to date and I want to update my computer stored iWeb site to the site in internet ?

You need to copy and paste the content from the published files back into iWeb and recreate any missing pages since iWeb has no import facility.

Missing "Save Site as Template" For Publishing Sites in Project online 2013

First I created Sub site using Project Template under the site collection.
Now I want to this Sub site Save as a Site Template. When I went for Save site as Template in site setting. Under Site Action there is no option for “Save site as Template”
marylu

"Publishing Feature" may be enabled at your site , The Publishing feature does not support the Save Site as Template option.
http://support.microsoft.com/kb/2492356
Some workaround -
http://www.learningsharepoint.com/2013/05/03/missing-save-site-as-template-for-publishing-sites-in-sharepoint-2013/
http://blogs.msdn.com/b/how24/archive/2013/06/13/save-publishing-site-as-a-template.aspx
Thanks
Ganesh Jat [My Blog |
LinkedIn | Twitter ]
Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

Noteboard webpart in community site with publishing feature enabled

Hi All
Noteboard webpart works fine as long as publishing site/web feature is not enabled
but after it is enabled people with contribute permissions can not see the noteboard comments of the people with Moderate/Full control/Site collection access and vice versa.
Is this the bug or there is the solution for this ? whts that?
SP Page: http://www.facebook.com/SharePointQ SP Blog: http://swatipoint.blogspot.com

Hi,
Please try to disable the publishing feature to check whether it working or not. Or try to restart Distributed Cache service.
If you do not activate the publishing infrastructure feature, the note board will appear to work, but will not store comments correctly. The note board does not use the correct url for the page, so the notes stored using the web part, will differ from
the notes stored using the Tags and Notes button.
https://donalconlon.wordpress.com/2011/03/02/adding-the-social-note-board-to-a-sharepoint-blog/
I suggest you activate the publishing infrastructure site collection feature, then add a new Noteboard web part in a page, then check whether the issue still exsits or not.
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Publishing Feature for Site Collection

Hi..
I am having 5 different Site Collections in SharePoint Site and from 1st Site Collection we are redirecting to other using Top Link bar, but when we enable Publishing Feature for Different Site Collections the Top Link bar changed..i want to have Standard links
for all
Ravindranath

Publishing feature is applicable to a Site Collection and its sites.
Quick Approach
A quick solution will be to manage the Navigation (via Site Actions -> Site Settings -> Look and Feel -> Navigation -> Navigation Editing and Sorting -> Global Navigation) for all 5 site collections and add same links. This will show the same
top links for all your site collections.
Correct approach -
For using same navigation (top links) across site collections withing same web application, you need to implement Global Navigation. Google this and you'll find lots of good articles to implement this - Create an xml for site map, copy this to your web application
directory, add the provider in web.config, update the master page to bind the provider to SiteMapDataSource.
This is a proper approach where if you update the xml, changes get applied to all site collections.

Turn off publishing feature without messing up the SharePoint site

Hi,
Is it possible to turn off the publishing feature (after it was turned on), without goofing up the SharePoint site and creating problems? I want to save a site as a template and just discovered that that option is not available when publishing is enabled.
Why does Microsoft make these decisions arbitrarily? Ugh!
Thanks! Patti N.

There are many ways to tweak and achieve the target i.e. saving publishing site as template, but if you try creating a new site using that template on a non-publishing site, it will surely gonna fail with some generic error
Even if you deactivate the ft and then save site as template, it will fail when you try creating another site using that template on a non-publishing site. So basically, it can only create a new site using that template only if the destination site have
the publishing ft activated
SharePoint does not support Save Site as Template option with the Publishing features turned on. The supported method to create templates for publishing sites is to use a site definition template and using a feature XML.
Please refer:
https://support.microsoft.com/kb/2492356?wa=wsignin1.0
To answer your question, Why does Microsoft make these decisions arbitrarily?
when you activate the Publishing ft is the ability to use Web Content Management and create custom Page Layouts and change the way you can mange and display the information.You can manage Content and how this content will be shared to all users, you can
work with Content types and associate with Pages to change and categorize you information and display to public, i use for SharePoint internet Site because is a very easy way to users create new content and display to public this information, there
another features you can use with publishing feature like active the Output Cache this feature will improve performance in the page load because the webpart, metadata and page will be stored in cache, you can also define if you want to manage the
profiles for this cache, anonymous access or authenticated users.
All these changes happen when you activate publishing ft and wont get revert when you deactivate the feature, Hence it is not possible
To know more about publishing ft, please refer
https://technet.microsoft.com/en-us/library/ff628963(v=office.14).aspx

Is it possible to set up device channels in Team site if I activate publishing feature?

Hi All,
Is it possible to create device channels for my team site. I inadvertently created this as team instead of Publishing site. Please advise.
Dinesh

Hi Dinesh,
If you want to access SharePoint 2013 out-of-box device channel then it requires SharePoint Publishing Features at site collection, please enable SharePoint
Server publishing site infrastructure in team site
Other Approach:
Device channel work with "User Agent Strings", you can read browser user agent string at run time and apply custom master page/CSS, however you need to do customize master page/CSS for all devices
The User Agent String as I’m sure we all know identifies which browser you are using to connect with it is sent from the Client to the Server within the initial headers and contains certain tokens like Operating System, Browser, etc.
reference : http://blogs.technet.com/b/christwe/archive/2012/11/02/sharepoint-tidbit-sharepoint-2013-device-channels.aspx
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP)

The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.

Hi All,
I am trying to activate the Publishing feature for a SharePoint website using a custom Site Definition File. The problem I am getting
is when I try to use the custom site template I get an error message:
New-SPSite : The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.
The custom
Site Definition File snippet is show below:
<?xml
version="1.0"
encoding="utf-8"?>
<Project
Title="SiteDefinition1"
Revision="2"
ListDir=""
xmlns:ows="Microsoft
SharePoint"
xmlns="http://schemas.microsoft.com/sharepoint/">
<NavBars>
</NavBars>
<Configurations>
    <Configuration
ID="0"
Name="SiteDefinitionDelegateControls2">
      <Lists/>
      <SiteFeatures>
        
        <Feature
ID="{3bae86a2-776d-499d-9db8-fa4cdc7884f8}"
Name="FeatureDefinition/15/3bae86a2-776d-499d-9db8-fa4cdc7884f8"
/>
        
        <Feature
ID="{a392da98-270b-4e85-9769-04c0fde267aa}"
Name="FeatureDefinition/15/a392da98-270b-4e85-9769-04c0fde267aa"
/>
      ...Other Site Features
      </SiteFeatures>
     <WebFeatures>
        
     <Feature
ID="{94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb}"
Name="FeatureDefinition/15/94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb"/>
     ... Other Web Features
      </WebFeatures>
      <Modules>
        <Module
Name="DefaultBlank"
/>
      </Modules>
    </Configuration>
</Configurations>
<Modules>
    <Module
Name="DefaultBlank"
Url=""
Path="">
      <File
Url="default.aspx">
      </File>
    </Module>
</Modules>
</Project>
I hope you can help
Colin

As the error says. The Publishing Infrastructure feature must be activated at the Site Collection level where you are creating a new site PRIOR to turning on the Publishing feature. So if you are trying to use this site definition to create a
new Site Collection then its not going to work. If you are trying to create a sub site then make sure that Publishing Infrastructure is enabled in the site collection before trying to create a sub site with this site definition.
Internally Microsoft does this for the Publishing Portals using custom code. Here's an article that discusses how to do it in SharePoint 2010.
http://msdn.microsoft.com/en-us/library/office/gg615465(v=office.14).aspx
Compare what's in the article to one of the Publishing templates available out of the box in 2013 and you should be able to find the assembly that is used to load the Publishing features.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Sharepoint 2013 (Danish): Deploying site from a custom template fails with error "Duplicate content type"

I cannot create a site-template in my own language (danish) and deploy a site based on the template.
I created a template from a "fresh" SharePoint project site with no tampering.
When trying to deploy a new site based on the templat I get the following error:
In Danish:
Beklager, men noget gik galt
Det blev fundet et navn på en dubletindholdstype "billede".
Tekniske oplysninger
Fejlfinding af problemer med Microsoft SharePoint Foundation.
Korrelations-id: 96646c9c-3213-a088-c6c4-537b0815313c
Dato og klokkeslæt: 21-06-2014 10:23:36
In English:
Sorry, something went wrong
A duplicate content type name "billede" was found.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 0b656c9c-52ee-a088-c6c4-5132070e3c4e
Date and Time: 21-06-2014 10:31:35

Need details from ULS logs about Correlation ID: 0b656c9c-52ee-a088-c6c4-5132070e3c4e
Check below:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/e955e737-e12e-4afa-b446-bb6e0f05e9b1/duplicated-content-type-error-creating-a-sharepoint-2010-site-from-a-custom-site-template?forum=sharepointgeneralprevious
http://aramacciotti.wordpress.com/2012/04/04/the-case-of-the-duplicated-contenttype/
http://community.office365.com/en-us/f/154/t/69416.aspx
If this helped you resolve your issue, please mark it Answered

My images look blurry when I export or publish my site from Muse. Why and how do I fix it?

My images look blurry, jagged, pixelated and low quality when I publish or export my site from Muse. Is there any way to avoid or fix this problem?

The primary cause of blurring images is the less than Photoshop-quality image downsampling algorithm currently used in Muse (that was compounded in early betas due to a bug in the JPEG compression library we were using at that time). Due to work we've done for Beta 7 to improve image encoding performance we now have the infrastructure in place to enable us to take a much better image resampler/resizer (after Beta 7), so this source of blurring will be addressed.
The other source of blurring is unique to opaque images containing line art or otherwise containing hard edges and large areas of solid color. When an image is opaque Muse will encode it as JPEG (if it's altered in Muse is a way that requires re-encoding). For line art this will introduce JPEG compression artifacts that can be noticeable depending on your eye and the specific image involved.
There are (at least) to ways to avoid these JPEG compression artifacts:
Resize your image before placing and avoid applying any effects (rounded corners, drop shadow, etc.) or doing any cropping or resizing in Muse. If the image is unaltered your original JPEG, PNG or GIF will be passed through unaltered.*
Put at least one pixel of transparency in your original image. (It could be a single 99% opaque pixel.) This will force Muse to encode as PNG. PNG compression is lossless and thus doesn't introduce any compression artifacts. However, an average PNG can be 5 times the size of a JPEG for the same image, so there is an impact to webpage download performance.
*For PSD files Muse has to encode the original PSD data into some web-friendly image format. If an image is resized in Photoshop and placed Muse won't resize/resample the image data, but it will encode it as JPEG or PNG depending on whether it contains transparency.

Recreate site from template - publishing feature

Similar Messages

Maybe you are looking for