Legacy Knowledge Base
Published Jun. 30, 2025

Renaming a fragment set folder creates a duplicate fragment set

Written By

Rita Schaff

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

  • Renaming a fragment set's folder and redeploying it creates a duplicate fragment set in Liferay DXP.

Environment

  • Liferay DXP 2024.Q1.5+

Resolution

  • This is expected behavior. The folder name serves as an identifier for the fragment set. Changing the folder name and redeploying creates a new set. If the override option is selected during deployment, fragments in the original set are moved to the new set.
  • Avoid manually modifying exported fragment sets to prevent this duplication.
  • The following feature requests have been submitted to improve fragment set management:
    1. LPD-44908: Add unique identifiers for fragment set deployments, allowing developers to control set updates.
    2. A feature request to enforce unique fragment set names within a scope, preventing accidental duplicates caused by folder renaming.
  • A related issue, where renaming a folder moves fragments to the new set and leaves the original set empty, is documented in this article: Renaming a folder set moves the existing fragment into the new fragment set and leaves an empty duplicate set.
Did this article resolve your issue ?

Legacy Knowledge Base