Views: 1581
Number of votes: 2
Average rating:

Localizations in PropertyValueList

The PropertyValueList property type ca be really useful for things that don't have a need for reuse, or doesn't have a view. If you've used it you might have noticed that the editor experience, especially in regards to localizations, hasn't been optimal.

In Per's blog post from 2015, the question on how to localize arose, and Kai de Leuw answered with:


That worked really well, up until a few weeks ago.

In Episerver CMS UI 11.12, something was introduced, that broke this functionality. But have no fear, it can still be done, and it's even cleaner.

Now, your POCOs are localized in the same way that other content types are localized.

Provided you have a POCO like this:

public class Contact {
    public string Name { get; set; }
    public string Country { get; set; }

You can localize it with an XML like this:

<?xml version="1.0" encoding="utf-8"?>
  <language name="English" id="en">
            <caption>Contact name</caption>
            <help>The name of the contact.</help>
            <caption>Country of origin</caption>
            <help>The country of origin for the contact.</help>

Happy localizing!

Nov 22, 2018

( By valdis, 11/23/2018 6:55:28 AM)

hmm.. think I should really dig into this built-in localization thingy and try to remove xpath based things there as well ;)

Stephan Lonntorp
( By Stephan Lonntorp, 11/23/2018 8:09:04 AM)

@valdis Totally off-topic, but why? The XML based localization stuff (or your DbLocalizationProvider for that matter) should, in my opinion, only be used for translation of the Episerver UI. Everything else is content, and should be managed as such.

Treating UI texts as content enables editors to do A/B testing, scheduling and anything else that the CMS allows. While your DbLocalizationProvider certainly solves the editability challenge that the XML-based system has, and is a fine piece of engineering, in my opinion it solves a problem that shouldn't be a problem.

( By valdis, 11/26/2018 2:15:37 PM)

because you would not have these stringly-typed problems ;)

Please login to comment.