Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Error saving images in a custom structure after add a translation

Written By

Daniel Martinez Cisneros

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

A client encountered an error when using the 2024.Q2.(4+) versions while attempting to save a Journal article with translations using a custom structure. The issue could not be reproduced in the 2024.Q3.X versions.

Steps to Reproduce:

  1. Create a new structure with an image field (or import an existing structure with the same configuration).
  2. Create a web content article and add a translation for Spain.
  3. Publish the web content article.
  4. Edit the web content article and click on "View Source."

Expected Behavior:

The generated XML should include all fields, including the translation item for Spain.

Current Behavior:

The translation item for Spain is not being added to the XML

Environment

  • 2024.Q2.4 - 2024.Q2.12

Resolution

The issue can be resolved by applying the fix LPD-24613. This fix ensures that the translation item is correctly added to the XML when the web content article is saved.

Open a support ticket to get this fix.

 

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