Legacy Knowledge Base
Published Sep. 10, 2025

Subtype missing after importing information template

Written By

Tímea Bihari

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

When an information template is exported from one environment and imported into another, the link to the web content structure's subtype is lost. The template remains linked to the main structure (e.g., Web Content), but not the specific subtype (e.g., News), requiring manual reconfiguration after import.

Reproduction Steps:

  1. In the source environment, create a web content structure with a subtype.
  2. Create an information template and link it to the structure's subtype.
  3. Export the structure (as a JSON file) and import it into the destination environment.
  4. Export the information template (as a LAR file) and import it into the destination environment.
  5. Expected Result: The imported information template is linked to both the structure and its subtype.
  6. Actual Result: The imported information template is only linked to the main structure, and the subtype association is missing.

Environment

  • Quarterly Releases

Resolution

  • This behavior is a known product limitation.
  • The necessary fix requires changes to the product's APIs, which cannot be backported to existing versions.
  • A feature request has been created to address this in a future release. You can track its progress here: LPD-59393.

 

Did this article resolve your issue ?

Legacy Knowledge Base