Are custom IContent types localizable?

Jouni Huttunen
Member since: 2010


Are language branches and CultureSpecific-attribute supported with custom IContent types (

It is possible to create multiple branches for custom IContent types using ContentRepository. But it seems like CultureSpecific-attribute is ignored, and content editing in Episerver edit view is only allowed for master branch. For all the other branches the edit view shows fields as disabled for editing. Is this by design, or why even the name is not localizable?

#65340 Jan 28, 2013 0:37
  • Jouni Huttunen
    Member since: 2010

    The custom type must also implement ILocalizable interface. What would I do without Reflector.

    #65350 Edited, Jan 28, 2013 9:45
  • Per Bjurström
    Member since: 1999

    You need to implement the interface ILocalizable to support multiple languages.

    #65351 Jan 28, 2013 9:47