Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

The editor is able to translate the non localizable value in Web Content

Written By

Adam Kollar

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • We've spotted a new translation-related bug, please follow the steps to reproduce it:

    1. Go to Content & Data -> Web Content and switch to the Structures tab.

    2. Click on the context menu in the top-right corner of the page and select Import Structure.

    3. Set the name to Structure with unlocalized value and select the JSON file attached to this ticket. Please note that the structure contains two text fields, the first is Localizable (can be translated to other languages) and the other one is non Localizable (should be set only in the original language)

    4. Go back to Web Content tab, click "+" and select the created structure.

    5. Type arbitrary data in the original, English language version of the article

    6. Using the Web Content editor language switcher, switch to any other language

  • After switching the language, both fields are editable: Text localized and Text unlocalized as well.

Environment

  • DXP 2023.Q4

Resolution

  • Open a help center ticket and request a hotfix containing LPD-19317 

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?