0

The New SharePoint Site page has a Template Selection section which can contains multiple tabs. For example, Meetings and Collaboration. These are controlled in webtemp.xml using DisplayCategory. While hiding and unhiding different OOTB templates, I somehow ended up switching the order of the tabs so that Meetings show up first. Can't seem to find any references on how to control the order of the tabs and make Collaboration first again.

Eugene Katz
  • 5,208
  • 7
  • 40
  • 49

2 Answers2

1

Is this a Publishing Site? If so, check Site Settings > Page Layout and Site Template Settings to see if any Site Templates are being restricted. From what I can tell in Reflector, the TemplatePicker control calls SPWeb.GetAvailableWebTemplates, which should consistently return OOTB templates first followed by any custom templates. TemplatePicker then loops through the templates and creates a tab each time it encounters a new SPWebTemplate.DisplayCategory.

Rich Bennema
  • 10,295
  • 4
  • 37
  • 58
  • Not a publishing site. When creating a subsite, the only two tabs I have showing are Meetings and Collaboration. I just need to have Collaboration show first. – Eugene Katz Feb 26 '10 at 20:37
  • I created a new answer (and removed the original comment) since the original answer might be helpful in the future for someone with a Publishing site. Thanks. – Rich Bennema Mar 02 '10 at 21:03
1

Has webtemp.xml been reordered or edited so that Team Site, Blank Site, and Document Workspace are now either below the Meetings sites or are marked as hidden? I captured the output of GetAvailableWebTemplates for a test Team Site and the first 12 templates match the contents and order of an OOTB webtemp.xml. If any of those Collaboration templates are visible in your list, try moving it above the Meeting templates, save, and recycle the app pool.

Rich Bennema
  • 10,295
  • 4
  • 37
  • 58
  • Yes, all the collaboration templates which appeared above the meetings ones were set to hidden=true. Moving the meeting ones all the way to the bottom fixed the problem. – Eugene Katz Mar 03 '10 at 12:13