Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Are custom IContent types localizable?



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?

Jan 28, 2013 0:37

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

Edited, Jan 28, 2013 9:45

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

Jan 28, 2013 9:47
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.