I created some test custom site definitions but I want to delete them now. How can I do that???
View Complete Post
If one has created a custom site definition in sharepoint 2007, Once the whole site is migrated to sharePoint 2010 will that "custom site definition" created in 2007 will work without breaking in SharePoint 2010?
If No, what has to be done to make it work on 2010.
What to do , so that custom site definition tab should appear at site collection level only?
What to do , so that custom site definition tab should appear at subsite level only?
what to do , so that particular site definition tab should not appear at particular subsite level at all.
IÃÂ am trying to create a custom site definition based on publishing site definition. But i get following error while trying to create a site collection based on this definition.
"The Office SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated."
below is my custom webtemp:
How to use Picture Library feature available at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\FEATURES\PictureLibrary
to create the custom picture library with site definition.
custom picture library has one more column with dropdown values .
After search on google. I found that picture library List to be specified in onel.xml as follows
-- speciify picture library list
here how I can specify my own picture library,Please let me know in exact words
I am creating a custom site definition, which is based on STS site definition ( so my site is also a team site, just with the difference of name ). For that I have created a SharePoint 2010 site definition project in VS 2010. It works fine.
Now what I want to do is to create a custom master for this site definition. And I want to keep this master page in same project. Can someone tell me how to do it ?
Note : I am adding a module to this project ( which adds a feature to the project, when there was no module, there was no feature in the project ). Next I am referring that feature in one.xml file under configuration->site feature node. I do not want
to have a feature, I want it to be part of site definition. But can I embed in such way that every time a site is created based on my site definition, master page also get deployed to root site of site collection
I am making a custom site definition. I am able to embed master page in my site definition. This is corresponding
thread for it.
Now in same way I want to embed style sheets with site definition. How I can do it ?
First I will explain what I was trying to achieve.
I wanted to create a site definition or site template with some common features e.g. document library with custom columns and then create many sub sites using that template or site definition.
But the idea is that once all the sites have been created and up and running, if it is required in future to modify the document library to either add or remove some columns then I will simply modify the template/site definition and then apply it globally
and all the sites will get updated automatically which were created using that template/definition.
I discovered that I can not get it done using site templates as they are just snap shot of sites and any modifcation can only be applied to new sites created based on template not the ones which were already created.
So, if I go with Site Definition option, what is the best way to do it. Create a custom document library and then create list template based on that and then add it on site definition ?
Or create a feature and do it via code in feature activation.?
Or perhaps there is another better way to do it?
Any help is appreciated
I want to create a new site definition which, when provisioned, includes an instance of a custom list. The custom list definition is contained in a feature as part of the site definition project. What's the best method for creating an instance of this custom
I can think of a few ways to do it:
- Modify the onet.xml for my site definition to include an instance of the list
- Use feature stapling to enable my custom list defintion feature when a site is provisioned using my new site definition and include a list instance in the feature.
Is there another more suitable method?
I am migrating from SharePoint 2007 to Sharepoint 2010.
We hae 2 custom workflows to be migrated.I have deployed the respective wsp which were used in Sharepoint 2007 site.But it did not help and i got errors.
Do i need to change my site definiton or my wso before deploying the same to Sharepoint 2010
I need to create a custom site definition for Blog(SharePoint 2010) using visual studio 2010. So can anyone please provide the steps to create that? Thanks in advance.
I have a requirement to create about 40 site collections and want to do them using powershell. That part is not that big of a deal.
But I have a requirement to create a "basic" team site collections template with some branding changes. Namely, replace the image of blond lady in a suit with a company logo and add a web part (contact details) in the right hand column. I will
also need to change the welcome text of the left hand column. Also, on these site collection pages I would need to remove the current navigation from the left hand side.
I attempted to make the changes and "save as a template" in the Site Settings menu but I keep getting errors when I attempt to create a new site collection based on it. So I am now trying to decide if a custom site definition would not work better.
So I guess my question is more or less: which route, for the amount of work I need to accomplish, makes better sense?
I have a custom Site definition which is made up of team Site Template(STS). In that I have populated lists and content types according to my requirement. Now I need to provision a WIKI site as a sub site in that Definition. I have used Provision data attribute
of Configuration element in webtemp file and defined structure for it. But my site is not being created. The same approach is working with default Publishing sites provided by MOSS 2007(Publishing and collaboration Portals). I suspect that Publishing feature
needs to be activated in my template before using provisioning attribute. Is that true. If yes please throw some light on that process. if no, guide me through the next possible solution.
I created several version of site templates with different name. Next I removed the older versions in solution gallery but in the list of template sites still are showed.
I searched for cmdlet in PowerShell witho no luck. The custom templates does not shown in SP-WebTemplate command. So I don´t know how to remove this templates from SharePoint, if the gallery solution is empty. I remove the solutions
from recycle bin in the site and site colleciton scope but with the same results. And I first deactivate the solution and next remove the solution but nothing works to remove the template from site template.
The odd thing is that in my SharePoint 2010 development Virtual Machine removing the solutions remove the site templates of the creation site option. But in the Production Server recently migrate to 2010 it does not work.
Any solution in code, cmdlet or some else could help.
Thanks in advance!