Site Template propagation removed in DXP 2026.Q1, but inherited template pages do not allow adding child pages directly on site

Development Upgrades
1

Hi,

We recently migrated our project to Liferay DXP 2026.Q1. Our existing implementation is heavily based on Site Templates.

As per the Liferay documentation, Site Template propagation is no longer supported as of Liferay DXP 2026.Q1. The documentation says that if we make changes to a Site Template, we must manually copy the same changes to the sites based on it.

However, we are now facing a deadlock situation.

Current setup:

  • Existing sites were originally created using a Site Template.
  • Parent pages in the site are inherited from the Site Template.
  • After migration to DXP 2026.Q1, we need to add a new sub-page under one of those inherited parent pages.

Issue:

  1. If we add the new sub-page in the Site Template, it does not reflect in the existing site because propagation is no longer supported.
  2. If we try to add the new sub-page directly in the site, Liferay does not allow it because the parent page was created/inherited from the Site Template.
  3. Because of this, we cannot add the required sub-page either through the Site Template or directly on the site.

Expected behaviour / clarification needed:

What is the recommended approach in DXP 2026.Q1 for existing projects that were built using Site Templates and now need to maintain or extend the page hierarchy?

Specifically:

  • Is there any supported way to “detach” or convert inherited Site Template pages into normal site pages so that child pages can be added directly?
  • Is there any migration utility, configuration, API, or recommended script to break the dependency between a site and its Site Template?
  • For existing customers using Site Templates before 2026.Q1, what is the recommended migration path when new pages or sub-pages must be added under inherited template pages?
  • Is this limitation expected behaviour, or should the UI allow adding child pages directly since propagation has been removed?

This is blocking us because the documentation says to apply changes directly to the site, but the site does not allow adding a child page under a template-created parent page.

Please suggest the recommended solution or workaround for this scenario.

Thanks.

2

Hi @Jayesh_Goswami

This appears to be a known issue that matches what you’re experiencing. It’s being tracked under LPD-81578 ( Jira ), which relates to site propagation.

According to the ticket, the fix is scheduled to be included in the 2026.Q2.0 release.

Thanks
Priyank Gajera