Magento 2.4.7-p3 : Unable save "/" in the product url_key

[mohammadbharmal]

Preconditions and environment

• Magento 2.4.7-p3

When creating a product in Magento 2.4.7-p3 with a url_key containing a forward slash ("/"), such as "test/product-123", Magento automatically replaces the "/" with a hyphen ("-") upon saving the product. As a result, the URL becomes "test-product-123".

However, if a manual URL rewrite is created for the same product, it is possible to save the original URL format "test/product-123" through the rewrite. This inconsistency in behaviour between automatic URL key generation and manual URL rewrites can lead to confusion and potential issues with URL management.

Steps to reproduce

• Create a product in Magento 2.4.7-p3 with the url_key set to "test/product-123".
• Save the product.
• Observe that Magento replaces the "/" with "-", resulting in the URL "test-product-123".
• Create a manual from the Marketing > SEO & Search > URL rewrite for the same product and set the URL to "test/product-123".
• Save the rewrite and note that the original URL format "test/product-123" is now accepted.

Expected result

Magento should either consistently allow or disallow the use of forward slashes ("/") in url_key values across both automatic product saving and manual URL rewrites.

Actual result

Magento replaces "/" with "-" during product save but allows "/" in manual URL rewrites, leading to inconsistent URL handling.

Additional information

No response

Release note

No response

Triage and priority

• 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 @mohammadbharmal. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

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, join the Community Contributions Triage session to discuss the appropriate ticket.

[mohammadbharmal]

@magento I am working on this

[mohammadbharmal]

@magento give me 2.4-develop instance

[m2-assistant]

Hi @engcom-Delta. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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-Delta]

Hi ,

Thanks for your reporting and collaboration.
We have verified the issue in latest 2.4-develop instance and the issue is reproducible.
Kindly refer the screenshots.

Steps to reproduce

1. Create a product in Magento 2.4.7-p3 with the url_key set to "test/product-123".
2. Save the product.
3. Observe that Magento replaces the "/" with "-", resulting in the URL "test-product-123".

4. Create a manual from the Marketing > SEO & Search > URL rewrite for the same product and set the URL to "test/product-123".

5. Save the rewrite and note that the original URL format "test/product-123" is now accepted.

Thanks.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14016 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.