Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Staging publication fails with a duplicate entry on LayoutSEOEntry error

Written By

Madeleine Clay

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

  • Staging publication is failing in my environment with the following UI error:
An unexpected error occurred with the publish process. Please check your portal and publishing configuration.
The model.resource.com.liferay.layout.seo.model.LayoutSEOEntry [layoutId] could not be imported because of the following error: org.hibernate.exception.ConstraintViolationException: could not execute batch.
  • This error is in the logs:
Caused by: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '[layoutId]' for key 'IX_63195F59'

Environment

  • Quarterly Releases

Resolution

  • This issue was fixed in 2024.q3.1 by LPD-35629

Additional Information

  • This issue occurs in the rare case when both the master and the homepage share the same layoutId.
  • Sharing the same layoutId doesn't immediately cause conflicts since the master's layout is private and the page's layout is public, but attempting to publish changes from staging to production can cause conflicts if there are modifications to both the master and the homepage.
  • The conflicts arise during the import of LayoutSEOEntry due to the layoutId ambiguity. This results in an error that prevents publishing from staging.

 

 

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