legacy-knowledge-base
公開されました Jun. 30, 2025

After upgrading from DXP 7.3 to the Quarterly Release, the web content field value is overwritten by the last translated value

投稿者

Ahmed Abdin

knowledge-article-header-disclaimer-how-to

knowledge-article-header-disclaimer

legacy-article

learn-legacy-article-disclaimer-text

Issue

  • I upgraded from DXP 7.3 FP2 to 2024.q1.13. Since then, when I try editing web contents or creating new ones from scratch, the translation are totally broken ( for example, the French is overwritten by the English one).

Reproduction Steps:

  • Start 2024.q1.13 + the DB

  • Go to Content and Data --> Web Content and add a basic web content, add a translation to it (you can change the title with the translation as well), then publish.

  • Open the web content and check the value of the default content field.

Actual Result: The default locale content field value is overwritten by the translated content value.

Expected Result: The default and translation values should have their own set values.

Note: if you add several translations, publish, and edit the web content, you will see that the default locale content field and other translated fields are overwritten by the last translated content.

Environment

  • Liferay Quarterly Release 2024.q1.13

Resolution

  • This issue is most probably caused by the migration to the Data Engine. It seems that due to strict Security Policy, the web hosting provider didn't have the "Accept-Language" header attribute in its whitelist, so it wasn't shared with Liferay and the request's answer was always the default local.
  • So, whitelisting the "Accept-Language" header attribute in the web hosting provider resolves the case.
did-this-article-resolve-your-issue

legacy-knowledge-base