Sometimes I have problems with the resolution of resources in content type resource values.

Let me give an example from my dev box.

This is a newly created content type.

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <!-- Parent ContentType: $Resources:LzCtDS (Lenze.Sharepoint.Type\LzCtDS) (0x010078a8230787d64c89852afa2751db1ee70103) -->
  <ContentType ID="0x010078a8230787d64c89852afa2751db1ee7010308"
               Name="$Resources:LzCtDS_ST"
               Group="$Resources:LzGroupDS"
               Description="$Resources:LzCtDS_STDesc"
               Inherits="TRUE"
               Hidden="FALSE"
               Version="0">
    <FieldRefs>
    </FieldRefs>
  </ContentType>
</Elements>

Resources came from one resource file in solution (de-de, en-us and neutral), referenced by DefaultResourceFile property in Feature.

Ive deployed the feature on my development box and activated it. A look into C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\Resources shows that the resource files are freshly updated and contains the values referenced in the CT (for all three de-de, en-us and neutral).

  <data name="LzCtDS_ST" xml:space="preserve">
    <value>DS_ST</value>
  </data>
  <data name="LzCtDS_STDesc" xml:space="preserve">
    <value>DS_ST: Solution Tools</value>
  </data>

And this is how it looks in an site with English as language

Site Content Type Information
Name: DS_ST
Description: $Resources:LzTypeDS,LzCtDS_STDesc;
Parent: DS
Group: DS Content Types

and with german as language

Informationen zum Websiteinhaltstyp
Name: DS_ST
Beschreibung: DS: Drive Sizing
bergeordnetes Element: DS
Gruppe: DS Inhalts Typen

As you can see, in English language, the resolution of the resource is missing (only description, name is ok). And I german the description is wrong (comes from element LtCtDS and is the wrong language)

ive no idea why this happens. Its currently on my dev box and our sharepoint 2013 staging system. But in testing environment, everything is fine. I think it could be a "caching" problem?

• Edited by spille 56 minutes ago