Cannot create product "URL key for specified store already exists." - pure magento, no migration, no scripts, no categories

[chelevich]

Preconditions (*)

1. Magento 2.4.0 (Enterprise Edition)
2. PHP 7.4

Steps to reproduce (*)

1. Create two websites with a store for each website (website IDs: 1 and 2, store IDs: 1 and 2)
2. Create a product with URL Key "test" (product ID: 1)
3. Assign it to both websites
4. Observe two URL Rewrites created for both stores

• store 1, "test -> catalog/product/view/id/1",
• store 2, "test -> catalog/product/view/id/1"

5. Un-assign the product from website 1, change URL Key to "test2" with "Create redirect" checked, hit Save
6. Observe three URL Rewrites:

• store 1, "test -> catalog/product/view/id/1",
• store 2, "test -> test2",
• store 2, "test2 -> catalog/product/view/id/1"

7. Attempt to create new product assigned to website 1 with URL Key "test"

Expected result (*)

1. In step 6 there should only two URL Rewrites remain for store 2 as the product is unassigned from website 1
2. Should allow to save new product in step 7 with the initial URL Key "test" (new product ID: 2)
3. Three URL Rewrites should exist after save:

• store 1, "test -> catalog/product/view/id/2",
• store 2, "test -> test2",
• store 2, "test2 -> catalog/product/view/id/1"

Actual result (*)

1. Error is thrown in step 7 "URL key for specified store already exists."
2. The error message points to the conflicting URL Rewrite with store 2 although the product is assigned only to website 1

---

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”.

[m2-assistant]

Hi @chelevich. 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 @shikhamis11. 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.

[shikhamis11]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @shikhamis11, here is your Magento Instance: https://e4c51f8456a161e9e80c3c9255cd7b72-2-4-develop.instances.magento-community.engineering
Admin access: https://e4c51f8456a161e9e80c3c9255cd7b72-2-4-develop.instances.magento-community.engineering/admin_4c23
Login: 7b3f7775
Password: 7e76bb9f33d0

[shikhamis11]

Hi @chelevich
I tried to reproduce the issue on 2.4-develop instance. It's working fine. At step 6 there is only 2 url rewrite exists related to the website the product is assigned.
So I am able to create new product on other website with previous product url key.

[shikhamis11]

Can you confirm you are able to reproduce the issue on latest 2.4-develop instance?
Also let us know if require additional steps to reproduce the issue if any

[chelevich]

@shikhamis11 sorry, I cannot reproduce the issue in 2.4-develop.
Probably it's fixed by #31106
I need to find a way to upgrade my 2.4.0

[shikhamis11]

Thanks for the update @chelevich
It seems that changes are not released yet maybe It will be there in 2.4.3.
I am closing this one as it is already fixed.