First step is to remove all configurations from it, except for one and give this configuration ID = 0. You might have noticed that when you added the empty element to your project, Visual Studio automatically created a feature for you. This confirms that we can now create a sub site based on our Cool Site template, but that wasn’t what we set out to do. Open up Central Administration and go to Application Management > Create site collections. Click on the Browse button and select the .wsp file from the Debug or Release folder in the bin folder of your Visual Studio project. If you do so and click OK, the Cool Site template will be used to fully provision our newly created site collection and you will be able to browse to it. Go back to Visual Studio and first clean up by right-clicking on your project’s name in the solution explorer and choose Retract. Next click on your project’s name in the solution explorer again and in the Properties pane change the value for Sandboxed Solution from True to False.
Deploy the solution again by right-clicking on your project’s name in the solution explorer and selecting Deploy. Now go back to Application Management > Create site collections and fill in a Title and a URL. Basically from a user interface perspective the web template now behaves exactly like a site definition would. Hi Pallavi,There is no way to determine whether a site or web template has been used to create an existing site, the only thing that's stored is the site definition they were originally based on. Hi Mirjam, small question: Is it possible to hide te webtemplate from te user interface in case you only want a administrator to use him with scripts? As a side note, you can create your web template within SharePoint and then use it to provision Site collections. Thanks a ton !!I added a property bag to the site collection's root web and my solution now works fine! Hi Christian,I never succeeded in adjusting a site that was saved as a template in Visual Studio and deploying it again, but I would assume you can savely remove that property from the ONET.xml.
Hi Carlos,Unfortunately is't not possible to deploy a web template to a specific web application. Problem: You want to create an WSP for your site however, the "Save site as template" link is missing from the "Site Settings" page as shown below. A site is the key place within SharePoint to bring together all the people, content and activities associated with a particular process, project or group.  And if the process or project is regularly repeated within your organization having a site template for it saves a lot of time and helps to ensure consistency and facilitate continuous improvement. There are any number of scenarios where you might use a SharePoint site template, for this example we are using a recruitment process, but you could equally well set one up for any regularly repeated process or project you manage: training courses, audits, conferences and sales exhibitions, product testing, office moves, procurement, risk assessment, staff appraisals – the list goes on. To get a SharePoint template that fits your processes perfectly you are going to have to make your own – and thankfully it’s exceptionally easy to do – so here’s how.
Before you even switch on your computer you need to sit down and think about the business process you are working with: the content, activities and people you will bring together in your site template.
Recruitment Procedures: hiring policy, pay scales, interviewers guidelines, equal opportunities policy etc.


Recruitment Forms: application form, equal ops monitoring form, interview score card, pro forma letters. I am sure there is more, but you get the idea, you need to think about the content, people and processes you want to bring together in your site template. You can’t actually create a site template from scratch in SharePoint – you first have to create a site and then save it as a template. On the “New SharePoint Site” page there isn’t much you need to do.  Give the site a name, in this case “Recruitment” seemed to make sense, give it a URL – best done by just adding the name of your site, and from the “Select a Template” box choose either Blank or Team Site – either will do just as well. Now go back to your list of the people, content and activities that make up your process and think about how best to handle them within SharePoint.  Remember that the cardinal rule of content managment within SharePoint is that we only want to have one version of any one item of content, so you need to spend some time thinking about what content needs to exist within the sites that you will be creating from your template, and what content already exists elsewhere, so that you can simple provide links to it. Document Libraries for applications and proforma recruitment documents (so things like blank Job Descriptions and Invitations to interview, where we will want to keep completed versions of the documents for our records) configured with metadata.
Content Editor Web Part – to display links to relevant information located within the main HR site, like Recruitment Procedures. You can save to your template pretty much anything you see from the “Create” page within your site:  any kind of list or library, communication, tracking, sub-site or page. Having set up your site and filled it with all the stuff you need, you can now save it as a template, a very simple process again. Right, so now we have our site template, lets create a new site from it.  In our example we are going to hire a SharePoint Trainer, so from our Recruitment site “Site Actions” tab we are going to choose “Create” and then under the Web Pages heading, choose “Sites and Workspaces”. We are going to go through exactly the same process here as we did to create our Recruitment site.
A site template that’s tailor made for your own business processes with just a couple of hours work aren’t you the clever one! So let’s say your recruitment policy changes and you need to update your template – how do we do that?
Go to the very top level of your site and from the “Site Actions” tab select “Site Settings”.
From the “Galleries” list select “Site Templates”, click on “edit” next to the template you want to get rid of, click “delete” and you’re done. So, that’s our brief run down on Site Templates and how to use them.  We hope you found it useful – and if you have any other tips on the subject we would love to hear them.
Tags: SharePoint, Training Did you enjoy this post? When creating a subsite from a site template, can the new subsite use the permissions from the site template? I seem to only be able to inherit permissions from the parent site or have no permissions at all. You can use the ONET.xml from a standard site definition as a base, but you will have to make some adjustments to work around the fact that not everything you can use in a site definition is supported in a web template. However if you are working in an on-premise SharePoint environment where you can deploy full-trust or farm solutions and you have to create multiple site collections based on the same web template you might want to consider another approach. This will deactivate the feature and remove it from the site collection you deployed it to. Visual Studio will re-package your solution and because we chose to deploy it as a farm solution this time it will deploy it to the Farm Solutions Gallery in Central Administration.


You will now notice that you can select your web template straight away from the template selection control on the create site collections page. Not only can you create site collections based upon it, but because the web template was deployed using a farm scoped feature site owners will also be able to use the web template to create sub sites from any site collection in your SharePoint environment. You can create site collection based on web templates, both in a hosted and in an on-premise environment, using either a sandboxed, or a farm solution. If you create a web template it's a best practice to add a feature that stores the web template used and its version in the property bag of the site, but if you are using save site as template to create your template you can't really add your own feature to that.
You can do this by going into Site Settings and browsing to Page layouts and site templates under Look and Feel. I read articles related to web templates but no where I found how can I create web template using my own site which I already customized. The best thing you can do is to create your web template in a site collection scoped feature and then create a solution that activates that feature on all sites within that one particular web application.
If you are working with SharePoint 2007 you can either create a site template by saving a site as a template from the UI (in 2007 this will create a .stp file), or you can use Visual Studio to create a site definition. Your SharePoint administrator will be able to tell you whether you have the permissions you need – and if you don’t ask the administrator nicely and they might grant you some extra permissions. Visual Studio will now package your solution for you and because we chose to deploy it as a sandboxed solution it will deploy it to the Solution Gallery of the site collection you set at the deployment target when creating the project.
Because of that, browsing to the site will redirect us to the Template Selection page right away.
Retracting the solution using Visual Studio won’t remove it from the site collection where you uploaded it to manually. That makes sense, because we deployed it as a sandboxed solution to a single site collection. The manage farm solutions page will show your solution and it will tell you that the solution has been deployed. Be aware that using this feature means you will have to enable new templates that can be used manually. If you copy the ONET.xml file into your empty element make sure the Deployment Type is set to ElementFile. Go to Site Actions > Site Settings and click on the Solutions link in the Galleries section. That means it won’t be available when creating a new site collection from Central Administration.
If we are using a hosted environment like Office 365 we will only be able to deploy sandboxed solutions, so we will have to make do with that. You don’t have to do that, but I find that if your solution grows a bit bigger it is helpful to do so.



Marriage for green card penalty
How to impress a girl classmate
Free promo codes doubledown casino bonus
How to get married again in skyrim on xbox




Comments to «Create site as template sharepoint 2010»

  1. karizmati4ka1 writes:
    You want to bring back that feeling are searching for but let males.
  2. Ramincik writes:
    Point is, these pebbles make you appear the.