Legacy Knowledge Base
Published Jun. 30, 2025

Fragment should be accessible with its original name

Written By

Kanchan Bisht

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

  • The export/import of content pages with references to fragments in global is currently limited (using LARs).

  • Steps to reproduce:
    1) Navigate to the Global site
    2) Create a new collection and a new Fragment in it
    3) Export the Collection(LAR export)
    4) Create a new site and a new Content page for it
    5) Put the created fragment on it
    6) Export the site, download the LAR
    7) Restart the instance with a new DB
    8) Import the Collection to the Global site
    9) Create a new site and import the site LAR as well
    10) Edit the imported Content page
    Observed Behavior: Fragment is not editable and the original fragment name is replaced with 'element'
    Expected Behavior: Fragment should be accessible with its original name

Environment

  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

  • The observed behavior is a known concern addressed by LPS-149718, which is already included in Liferay DXP 7.3 Update 4 and Liferay DXP 7.4 Update 19

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base