Tuesday, July 27, 2010

SharePoint 2010 Meeting Workspaces and Blogs are not MUI enabled

A while ago I wrote about the new multilingual capabilities of SharePoint 2010 based on the Multilingual User Interface (MUI) – see Multilingual User Interface (MUI) in SharePoint 2010 – Part I and Multilingual User Interface (MUI) in SharePoint 2010 – Part II. But beware – apparently not all site definitions support the MUI.

If you try to enable alternate languages for a SharePoint 2010 meeting workspace you will get an error stating “this site is based on a template that does not not support alternate languages”.

Now if you want to find out which webtemplates support MUI you can run the following Powershell script:

$siteUrl = "http://hades/"
$site = get-spsite $siteurl

$site.GetWebTemplates("1033") |foreach {Write-Host $_.Title $_.Name  $_.SupportsMultilingualUI;}

you will get a listing of all installed webtemplates within thesite collection specified by the url parameter. Notice the SupportsMultilingualUI property of the SPWebTemplate object – for the Meeting Workspaces and Blog site definitions this will return False.

Next is the complete listing returned on an install with SharePoint Server 2010 Enterprise Edition.

Global template GLOBAL#0 True
Team Site STS#0 True
Blank Site STS#1 True
Document Workspace STS#2 True
Basic Meeting Workspace MPS#0 False
Blank Meeting Workspace MPS#1 False
Decision Meeting Workspace MPS#2 False
Social Meeting Workspace MPS#3 False
Multipage Meeting Workspace MPS#4 False
Central Admin Site CENTRALADMIN#0 True
Wiki Site WIKI#0 True
Blog BLOG#0 False
Group Work Site SGS#0 True
Tenant Admin Site TENANTADMIN#0 True
Access Services Site ACCSRV#0 True
Assets Web Database ACCSRV#1 True
Charitable Contributions Web Database ACCSRV#3 True
Contacts Web Database ACCSRV#4 True
Issues Web Database ACCSRV#6 True
Projects Web Database ACCSRV#5 True
Document Center BDR#0 True
(obsolete) Records Center OFFILE#0 True
Records Center OFFILE#1 True
Shared Services Administration Site OSRV#0 True
PowerPoint Broadcast Site PowerPointBroadcast#0 True
PerformancePoint PPSMASite#0 True
Business Intelligence Center BICenterSite#0 True
SharePoint Portal Server Site SPS#0 True
SharePoint Portal Server Personal Space SPSPERS#0 True
Personalization Site SPSMSITE#0 True
Contents area Template SPSTOC#0 True
Topic area template SPSTOPIC#0 True
News Site SPSNEWS#0 True
Publishing Site CMSPUBLISHING#0 True
Publishing Site BLANKINTERNET#0 True
Press Releases Site BLANKINTERNET#1 True
Publishing Site with Workflow BLANKINTERNET#2 True
News Site SPSNHOME#0 True
Site Directory SPSSITES#0 True
Community area template SPSCOMMU#0 True
Report Center SPSREPORTCENTER#0 True
Collaboration Portal SPSPORTAL#0 True
Enterprise Search Center SRCHCEN#0 True
Profiles PROFILES#0 True
Publishing Portal BLANKINTERNETCONTAINER#0 True
My Site Host SPSMSITEHOST#0 True
Enterprise Wiki ENTERWIKI#0 True
Basic Search Center SRCHCENTERLITE#0 True
Basic Search Center SRCHCENTERLITE#1 True
FAST Search Center SRCHCENTERFAST#0 True
Visio Process Repository visprus#0 True

 

CustomErrors setting in SharePoint 2010 for debugging purposes

On a SharePoint 2010 development machine you typically want to see the full stack trace when an error occurs. In SharePoint 2010 you will need to modify 2 web.configs:

  • Underneath “[systemdrive]:\inetpub\wwwroot\wss\virtualdirectories\<port>”
  • In the layouts directory underneath the SharePoint root directory or 14 hive – “[systemdrive]:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS

The settings that you need to change are still the same:

  • Change Debug=”true”
  • CallStack=”true”
  • CustomErrors=”Off”

Happy SharePointing …