Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now
7

There's a property for the list instance called something like ShowOnQuickLaunch, and you want to set that to false.


6

PROBLEM SOLVED :-) :-) The bug of trying to set the xsllink property through the template seems to be a recognised bug. I'm even sure MS are aware of this as when looking at how they have created their site definitions it seems pretty uninstinctive. The Solution DO NOT SET OR DEFINE THE XSLTLISTVIEWWEBPART IN THE TEMPLATE instead just define a webpart ...


5

You could loop through all the existing sub-sites with a PowerShell script, and use the feature cmdlets to activate the feature on existing sites. Using this method you could also insert some logic/conditions to enable or not enable the new feature if that is useful.


5

You basically have to create a custom SPWebEventReceiver and activate your mandatory feature under "WebProvisioned" method, like this: public class YourWebEventReceiver : SPWebEventReceiver { public override void WebProvisioned(SPWebEventProperties properties) { base.WebProvisioned(properties); // Activate your mandatory ...


4

With the SharePoint 2013 tools they removed the Site Definition project template, but added Site Definition as a project item. So you have to create an empty SharePoint 2013 Project and the add a new item of type Site Definition


4

You can control this with the publishing navigation feature. Take a look at the InheritGlobalNavigation key. <WebFeatures> ... <Feature ID="541F5F57-C847-4e16-B59A-B31E90E6F9EA"> <Properties xmlns="http://schemas.microsoft.com/sharepoint/"> <Property Key="InheritGlobalNavigation" Value="true"/> <Property Key="...


4

Have you had a chance to look over the following link? http://blogs.msdn.com/b/vesku/archive/2010/10/14/sharepoint-2010-and-web-templates.aspx#sitetemplate "One of the consideration with the site templates is also the fact that unless you import them to Visual Studio and modify its settings, they are only available on site collection level (site collection ...


4

Are you missing custom solutions in your new 2010 farm, that exist in the 2007 farm? Compare the installed features/solutions in both farms. However, you really should upgrade to SP2. The preupgradecheck stsadm command was added in SP2 and is very good at identifying where you're going to have issues. The upgrade alone may even solve your problems.


3

Feature stappling simply means having a list of features to activate everytime a certain site definition is used (or in natural language stating "Do activate these features when any of the Site definition ID is created"). Basically there is always a Stappler (the actual feature linking one or more site definion ID with the actual features) and a Staplee (...


3

Technical Details Feature stapling is implemented through a Feature that is specifically designed to staple other Features to one or more site definitions. Feature stapling allows a Feature to be stapled to any new sites created from any site definition or from specific site definitions based on the template name identified in the appropriate WEBTEMP.xml ...


3

You can know what is the current default master page by using this way: In MS SP Designer: In the masterpage folder, right-click the master page that you want to know, If this master page is already the default master page for the site, the "Set as Default Master Page" command is unavailable. So, this master page is the current default master page. In this ...


3

One thing to remember here is that if a page shows the master page definition as "~masterurl/default.master", this does not mean that the master page is actually a file called "default.master". This is actually a tokenization used in the MasterPageFile attribute, and loads whatever value is set in the object model for SPWeb.MasterUrl or SPWeb.CustomMasterUrl ...


3

If I remember correctly the flow is: Site Collection Scoped Features Web Scoped Features Lists Modules Your stapled features would be shot in after Site collection scoped features or Web scoped features (depending on scope) and hence the lists is not guaranteed to be created before the lists. Found a source here: http://blogs.msdn.com/b/chrischiaro/...


3

A site definition defines a unique SharePoint site. Site definition is a combination of multiple files like .xml, .aspx, .ascx, and .master page, .gif , .doc etc and are stored in C:\ProgramFiles\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\SiteTemplates directory. But Site Templates are created from an existing site and are stored in ...


3

Perhaps your issue has something to with something SharePoint Designer is doing. Try resetting the master page to the site definition, then download a copy of your master page from the master page gallery using the web UI. Rename the file and make a minor modification and upload it back via the web UI with the new name. Then select the new master page in ...


2

SharePoint MCM Mirjam van Olst has written everything about the provisioning order: http://sharepointchick.com/archive/0001/01/01/site-definition-provisioning-order.aspx Bottom line is that building pages with web parts using Site Definitions is very complex, and often leads to bad solution designs. I would suggest that you look into using WebTemplates ...


2

I think you should have the required values in respective SPWeb objects WebTemplate and Configuration properties. Some example of a console application here.


2

This has been quite a wild goose chase! There definitely was a mistake in cmscore.es-ES.resx, however, it's fixed in the service pack for the language pack: http://www.microsoft.com/download/en/details.aspx?id=26621 I had no idea that a service pack was available for the language packs; it makes sense because SP1 and the CUs didn't address any language-...


2

Run the following code in your C# Console Application and you'll get the listing all your sub-sites with their respective site definitions using (SPSite ospSite = new SPSite("http://server/")) { SPWebCollection webs = ospSite.AllWebs; foreach (SPWeb web in webs) { try { string template = web.WebTemplate; ...


2

It is not possible. All webs have site definition. The name of definition you can get by this code: string id = string.Format("{0}#{1}", web.WebTemplate, web.Configuration) To see what definition is used you can compare result string with values in this post.


2

Use the NavBars Element in the onet.xml file ... <NavBars> <NavBar Name="SharePoint Top Navbar" ID="1002"></NavBar> </NavBars> That will display your global navigation within the Site Definition ... In a non publishing site, you should be able to use web.Navigation.UseShared = true; ... where web is SPWeb type. In a publishing ...


2

This is a bit tricky, I must say. If you use Get-SPWebTemplate, I think you only get the built-in templates. If you want to find a custom site-template, you have to dance a little... Here is what I have used, supplying the GUID along with name of the custom Site Template. Notice my $sitetemplatename - that last hash is part of the name; it isn't a comment. ...


2

Your question is not really clear, but when you want to look at the standard onet.xmlor webtemp.xml files you just have to check the 15-hive. The onet.xml for the Standard Team site is located under: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPlATE\SiteTemplates\sts\xml Two important notes about this: Under SiteTemplates ...


2

Well, after restarting SQL, IIS nothing seemed to help. So I restarted the box and bingo. Powershell is finding my template. Love SharePoint!


2

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\ In there they had modified \GLOBAL\default.master and various other .master files in \LAYOUTS\


2

There is the CSOM method LoadAndInstallApp which might help. Available via JavaScript and .NET.


2

As you mentioned, site definitions should not be changed once it is provisioned. It is just not supported. A great blog on this topic is here. An extract from the same link Biggest challenge with the site definition is that we are not allowed to change the onet.xml file after it has been used to provision any sites in the environment. This is just not ...


2

Check if the safe control entry is there in the web.config, if not, add it, then the masterpage should work. Basically when you "edit" the masterpage you are unghosting it and that causes the Sharepoint to use type-safe parsers for all unghosted content.


1

I'm sure you found a workaround for this by now. I'm posting this for anyone still looking for the answer. All you need to do is use the correct namespace: "urn:schemas-microsoft-com:sharepoint:TagCloudWebPart" <UserScope xmlns="urn:schemas-microsoft-com:sharepoint:TagCloudWebPart">UnderUrlEveryone</UserScope>


1

You need to develop what I call a "service pack" to deploy against the existing sites. In this case your service pack would contain a module with the site pages and any other resources that might be required. If your solution is only adding new artifacts to the site, the process is pretty straightforward. If you are changing things like list structures, ...


Only top voted, non community-wiki answers of a minimum length are eligible