Submit Feedback
Legacy Knowledge Base
Published 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

Written By

Ahmed Abdin

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

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

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
Did this article resolve your issue ?