url_rewrite deleted or contain wrong url_key when saving product on storeview

[mveldhuizen]

Preconditions and environment

Magento version: => 2.4.7
Multiple storeviews in 1 website (example default and german)
Configuration:

• catalog/seo/product_use_categories = yes
• catalog/seo/generate_category_product_rewrites = yes

Steps to reproduce

Example 1:

1. Create a new product (test-product)
2. Edit product in scope of storeview (example german)
3. Add product to a category in this scope
4. save the product

Example 2:

1. Create a new product (test-product) and add product to a category (in global scope)
2. Edit product in scope of storeview (example german)
3. Change url-key of the product in this scope
4. save the product

Expected result

Example 1:

Product should have rewrite urls for both store views:

Example 2:

Product should have valid url rewrites for both stores and use the correct url_key for each store:

Actual result

Example 1:

Product does not have a url_rewrite for the other storeview:

Example 2:
The url_rewrite without any category link is removed. And the product url within the category of the default storeview now contains the url_key from the german store.

Additional information

I think the new system in magento 2.4.7 for saving url rewrites for multiple stores is the issue. This was introduced in: #35053

app/code/Magento/CatalogUrlRewrite/Model/ProductScopeRewriteGenerator.php:219 checks if store is global (which it is not) and then runs generateCategoryUrlsInStoreGroup which has some flaws which result in deleted or broken url_rewrites

There is a workaround when the product has wrong url_rewrites. You can edit the product in admin store and update the categories (add one, save, remove it again). This regenerates the url_rewrites and as it is saved in admin store the url's will be correct. This bug only happens when saving in a specific storeview.

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 @mveldhuizen. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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.

[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).
• 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

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

[roman-michak-hh-global]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @roman-michak-hh-global. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @roman-michak-hh-global, here is your Magento Instance: https://9726342261dda0c8388f43250298023a.instances-prod.magento-community.engineering
Admin access: https://9726342261dda0c8388f43250298023a.instances-prod.magento-community.engineering/admin_3c92
Login: eb915a8d
Password: 8f199513b96d

[engcom-Bravo]

Hi @mveldhuizen,

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.

Example 1: It seems to be working fine. Product should have rewrite urls for both store views

Example 2: product url within the category of the default storeview now contains the url_key from the german store.

Hence Confirming the issue.

Thanks.