Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Status Future consideration
Product DXP Cloud Platform
Categories Infrastructure mgmt.
Created by Guest
Created on Dec 22, 2021

RELATED FEEDBACK

Custom cultures in DXP

We are facing an issue with non-existing english language cultures for local markets. Ex en-IT. We would like the possibility to add custom cultures in DXP with CMS 12.

  • Post comment
  • Guest
    Reply
    |     Mar 7, 2023

    Language branches should be decoupled from culture and ideally allow independent setting of CurrentCulture and CurrentUICulture.

    As an example if I want to create a variant for English ex-pats in Spain I would likely want a language branch URL of /en-es/, a CurrentCulture to be en-GB and CurrentUICulture to be en-ES - and to be able to use translations to create content specific for that region in English.

    I have managed to achieve something similar on CMS 11, that will work on DXP, by using a migration script to manually insert custom language branches directly into the database (as EPiServer.UI.Admin.EditLanguageBranches is fixed to only allow the list of system cultures). And I have replaced the default IUpdateCurrentLanguage implementation such that I can remap CurrentCulture and CurrentUICulture. So far I've not encountered any problems, and CurrentUICulture seems to be quite happy to be a custom culture that doesn't exist on the OS.