CMS Page saving fails with "The value specified in the URL Key field would generate a URL that already exists."

[frostblogNet]

Preconditions (*)

1. 2.3.6
2. 2.4.1

Note: 2.4.0 is not affected.

Steps to reproduce (*)

1. Create a magento installation with 2 storeview (f.e. uk, us)
2. Go to Stores -> Configuration -> General -> Web and set "Add Store Code to URls" to Yes
3. Go to Content -> Pages and Create a CMS Page with the identifier "privacy" in the scope of the uk storeview.
4. Now create a CMS Page with the identifier "privacy" in the scope of the us storeview.

Expected result (*)

1. saving both cms page with the same identifier is possible due to the fact that the url is still uniqe
   https://example/uk/privacy vs. https://example/us/privacy

Actual result (*)

1. it is not possible to save the secound cms page.
2. You will see this error in the backend "The value specified in the URL Key field would generate a URL that already exists."

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

The problem here is a new validator in https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Cms/Model/PageRepository.php#L193. This validator is only checking if there is a CMS Page with the same identifier in the hole frontend scope not the scope itself. This works in a single store / storeview shop but not in a multi store / languarge store.

https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Cms/Model/PageRepository.php#L308

[m2-assistant]

Hi @frostblogNet. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hello @frostblogNet

Thank you for your report.

We are not able to reproduce the reported issue using the provided steps on Magento 2.4.1 and 2.4-develop

We have created two Store Views, US and UK

and set Add Store Code to Urls to Yes

Then we create one privacy page for US Store View, and one privacy page for UK Store View. The pages are created successfully

Please, correct our steps if we are missing something.

Thank you in advance

[frostblogNet]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @frostblogNet. Thank you for your request. I'm working on Magento instance for you.

[frostblogNet]

Hello @engcom-Bravo thanks for your quick response this is a bit strange. I will double check and will give you more information.

[magento-deployment-service]

Hi @frostblogNet, here is your Magento Instance: https://df0834ad492cea9470a8659d77c27bcd-2-4-develop.instances.magento-community.engineering
Admin access: https://df0834ad492cea9470a8659d77c27bcd-2-4-develop.instances.magento-community.engineering/admin_a186
Login: 8a8f9b58
Password: 4e99f86e3b26

[frostblogNet]

Sorry I don`t know why but I also can not reproduce this issue again.