I'm building a publishing site which will support the following cultures:
- de-DE (1031)
- en-US (1033)
- es-ES (3082)
- fr-FR (1036)
- it-IT (1040)
- ja-JP (1041)
- ru-RU (1049)
- zh-CHS (2052)
I can create an instance of every site definition except for the es-ES one.
Here's some more useful background:
I have a general publishing content type
I have a web-scoped content type binding feature that binds the general content type to the Pages library for the web
<ContentTypeBinding ListUrl="$Resources:cmscore,List_Pages_UrlName;" ContentTypeId="MyPublishingContentTypeId"/>
The site definition activates a web scoped feature that activates the content type binding on the web
The error happens when the site definition is activating the content type binding feature:
The element of type 'ContentTypeBinding' for feature 'Lists_WebFeatures' (id: 605fbe29-b242-4d08-abcb-20b8f0300796) threw an exception during activation: List '/es/Pages' does not exist at site with URL 'http://localhost/es'.
The error makes sense, because the correct name for the Pages library in es-ES is Paginas. However, I don't have "Pages" hard-coded anywhere - you can see how I'm using
$Resources:cmscore,List_Pages_UrlName; in the content type binding feature.
For reference, here is the log entry when the de-DE site definition activates the content type binding feature:
Successfully applied ContentType 'MyPublishingContentTypeId' to list 'Seiten' on web 'http://localhost/de'
It correctly applies to Seiten, which is the Pages library in the de-DE culture.
Any thoughts on why this breaks only for the es-ES site definition?
EDIT: Adding a code snippet to show how I'm activating the web-scoped features in onet.xml
<WebFeatures> <!-- Activate SharePoint Publishing features --> <!-- Activate my custom features --> <Feature ID="605fbe29-b242-4d08-abcb-20b8f0300796" /> <!-- Lists - Web Features --> <Feature ID="45f1d638-d9d9-46fb-93d5-b81b09eb2123" /> <!-- Publishing Content - Web Features --> </WebFeatures>
The content type bindings are in "Lists - Web Features".
Get-SPFarm | select buildversionor CA > System Settings > Servers In farm