I've recently create a site template on our SharePoint online environment which did originally have site publishing features enabled. This was done by setting the appropriate flag to enable saving as a template and then using the url /_layouts/15/savetmpl.aspx to save it.
When creating a site from this template i get intermittent errors indicating something went wrong but with no further detail other than a correlation ID. It's not every time and it happens occasionally when using the site.
A couple of questions on this.
a) What with the publishing infrastructure is not supported within Site Templates.
b) What is the best approach to create a custom site template where i can have a custom front page containing web parts and content, based on the publishing page layouts. I've searched through a significant number of posts online and cannot find a definitive answer to this.
Any help is much appreciate. Thanks in advance.
Grant
Please follow the below steps to create Site using custom template :
1.Firstly create site using custom template and select "upload site template later" or "upload solution later".
2.Then go to your created site and firstly enable publishing feature before uploading your site template to the solution gallery.
3.After that just go to the "Solutions" under "Web Designer Galleries" and upload your "Site template".
4.Now go to Site settings and select "Sites and workspaces" under "Site Administration".
5.And you can create your Custom site. you can see your uploaded Site template in Custom tab
Feel free to ask question if you have any doubt.
Related
I have tried to save the SharePoint communication site as a template that contains apps. I have faced the below error.
Sorry, this site can't be saved as a template. It contains apps that don't work in templates.
Please check social.technet.microsoft.com link for the same issue.
The above link suggests removing apps and saving the template of the site. But I will need a site template with apps. Can anyone suggest how to save SharePoint communication site as a template with apps?
Refer to this official article:
https://learn.microsoft.com/en-US/sharepoint/troubleshoot/sites/fails-saving-site-as-template
If the site contains apps that can't be saved as part of the template, it's necessary to remove any affected apps that are listed in the error message, and then save the site as a template.
If you want to use the app after you save the site as a template, you'll have to add it to the site again.
If you want to use the app in a new site based on template, you need to manually add it in the new site.
I have created SharePoint Site, from which I created a site template, now I need to create similar sites under same site collection using the Site Template. In order to automate this functionality I created the Site Template and try to create new sites from this template using SharePoint Designer Workflow using web services. But while performing this am getting below error.
"The site template requires that the Feature {bf8b58f5-ebae-4a70-9848-622beaaf2043} be installed in the farm or site collection"
To troubleshoot this issue I tried to create the site using the same site template manually, which am able to perform successfully.
I found that above GUID {bf8b58f5-ebae-4a70-9848-622beaaf2043} refers to Power View feature, which I found activated in my site collection, But am not using any power view related functionality in my application.
I would be grateful, if anyone let me know how to resolve this issue.
It seems like the issue is with the template. That error is saying before you create the site template, enable that feature at the site level on the template site before saving the site as a template. I had a similar use case about a year ago to automate all our private team site creation. I found this article very useful.
https://sharepointryan.com/2013/09/10/create-a-sharepoint-site-spweb-using-rest-in-spd-2013-workflow/
In the dictionary for the json request, set WebTemplate to the template / solution ID from your site collection.
Hope it helps.
I know how to in the settings activate publishing feature on a site but is it possible to have this by default when a new site is created from the UI?
I have some customized stylesheets and when a new team site is created it doesn't load these but instead looks like a sharepoint site out of the box. When I go to settings and activate publishing features the page reloads with the custom stylesheets. I wish to not have to do this every time a new site is created. Is there a solution to this?
Thanks in advance.
I guess you could either:
Build a site template (can't remember if these store feature activations)
Build a custom site definition, and activate the features you need
Build a stapling feature to tie your feature to the site definition
I'm creating a PerformancePoint (henceforth PP) Dashboard that contains a web report to be deployed to the a SharePoint web application that I had created. I followed the instruction in the link below.
Deploy a PerformancePoint dashboard to a SharePoint site
In summary, following the instructions in the link, I published the Dashboard to the PP site. Then, I added my account in PP as Creator in the Application level, Editor in both the Dashboard and the Web Report. In the SharePoint site, I added my account under Contributor. I even added the PerformancePointDefault.master just to be sure.
Now, when I deploy my Dashboard to a Report Library, I was able deploy the folder for the Dashboard, but not the Dashboard Page file.
I googled for this, but I could not find any article helpful.
UPDATE 2009-09-30:
I was able to resolve the issue by creating another site collection. Maybe the first site collection is messed up.
I had the EXACT same problem. I was about to take the best advice I could find and delete my site collection and create a new one from scratch, but by the grace of God, I had one final thought.
In our case, the site created was originally http://ServerName but we later added a host header (i.e. http://BiSite). I had been deploying the dashboard using the host header the entire time, so I decided to try using the original name of the site using the server name and viola, the dashboard finally deployed correctly, pages and all.
When you publish a dashboard in MOSS, you have to make sure that you select Publish a Major Version in the dashboard page's drop-down in the report library.
Why is this a community wiki? Seems like there should be a right answer to this question...
I know that creating a site template from a MOSS publishing site is not currently supported by Microsoft.
Can anyone tell me if creating a basic site, then turning on the publishing feature, then creating a site template is supported - I would guess not as it's probably the same as creating a publishing portal?
You can staple the publishing feature onto your site template.
From KB 986908:
You can create a stapling feature to staple the Office SharePoint Server Publishing feature to specific site templates. For example, see the Feature.xml file in the "Drive:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Features\PublishingStapling" folder. To staple the Office SharePoint Server Publishing feature to all site templates, use the TemplateName="GLOBAL" property. This property staples a particular feature to a site definition if the site definition does not specify the AllowGlobalFeatureAssociations property. (Only the Shared Services Provider site template and the Blank Site site template use the AllowGlobalFeatureAssociations="FALSE" property.)
For example, when you use the TemplateName="GLOBAL" property to staple the Office SharePoint Server Publishing feature, a site that is based on the Team site template uses the system master page that is configured for the root site of the site collection.
you can still access the save template webpage, and save it...
for example http://localhost/website/_layouts/savetmpl.aspx
and it works like a charm :-)
I don't think what you're describing will work (like you said, it's basically the same thing as a Publishing Portal), but there appears to be a workaround. According to this post from the SharePoint Solutions Team (apparently not related to Microsoft), you can create a publishing site, customize it as needed, deactivate the publishing feature, create a site template from it, create a new site based on the template, and then activate the publishing feature on your new site.
It sounds like this works, but is not officially supported by Microsoft. Be careful, since it may mostly work, but I wouldn't be surprised if some small pieces of it break.
We wrote our own tooling to solve the export problem. We can create site columns, content types, master pages, page layouts etc in the Publishing site, and export selected items to a WSP package for deployment to other servers.
The tool SPSource takes a similar approach, but creates a Visual Studio solution for compilation. The result can be packaged with WSPBuilder.