This page has moved to Adobe Experience League and will be redirected soon.
MDVA-33606: Users get error when saving CMS page assigned to hierarchy
MDVA-33606: Users get error when saving CMS page assigned to hierarchy
The MDVA-33606 patch solves the issue where the users get Unique constraint violation found error when saving a CMS page assigned to hierarchy tree. This patch is available when the Quality Patches Tool (QPT) 1.1.3 is installed. The patch ID is MDVA-33606. Please note that the issue was fixed in Adobe Commerce 2.4.3.
Affected products and versions
The patch is created for Adobe Commerce version:
- Adobe Commerce (all deployment methods) 2.4.1
Compatible with Adobe Commerce versions:
- Adobe Commerce (all deployment methods) 2.4.1-2.4.2-p2
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches
package to the latest version and check the compatibility on the QPT landing page. Use the patch ID as a search keyword to locate the patch.
Issue
When trying to save a CMS page assigned to hierarchy tree, users get the following error message: Unique constraint violation found.
Steps to reproduce:
- Create a new CMS page. Set the scope to All Store Views. This is your CMS Page 1.
- Create a new store view. This is your Store View 2.
- Go to Content > Hierarchy > Add the CMS Page 1 to hierarchy tree.
- Change the scope to Store View 2.
- Uncheck "Use the parent node hierarchy".
- Add CMS Page 1 to this scope and save it.
- Now change the scope to Default Store View.
- Uncheck "Use the parent node hierarchy".
- Add CMS Page 1 to this scope and save it.
- Go to Content > Pages > Add New Page.
- Title the page as Page 2.
- In the Page in Websites section, assign to All Store Views and both store views (Default Store View and Store View 2) and click Save Page.
- In the CMS edit page, open the Hierarchy tab.
- Assign Page 2 to Store View 2 node, Default node, and All Websites node.
Expected results:
You are able to assign the CMS page to all three nodes without any error.
Actual results:
You get the following error: Unique constraint violation found.
Apply the patch
To apply individual patches, use the following links depending on your deployment method:
To learn more about Quality Patches Tool, refer to:
For info about other patches available in QPT, refer to the Patches available in QPT section.