Magento 2.3.1 - URL rewrite rules are not creating for product after update url key

[Vishrootways]

Summary (*)

We are facing an issue with URL rewrite rules in fresh Magento 2.3.1 version. Issue: URL of the product does not getting updated after change URL key of category in multi-website setup. (NOTE: This issue is not coming when only one website is set up)

Preconditions (*)

Fresh Magento 2.3.1 One category which has one product. Multi website setup.

Steps to reproduce (*)

1. Go to the category at admin side.
2. Update URL key of category.
3. Save category.

Expected result (*)

Rules should be created/updated for the category and all products which are assigned to this category as well it should be created for all websites.

Actual result (*)

New URL rules are created with updated the key for the category but not created for the product. NOTE: URL rules of the product are created for the second website which does not default website, rules only not created for the mail website product.

[m2-assistant]

Hi @Vishrootways. 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.3-develop instance - upcoming 2.3.x release

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

@Vishrootways do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @AlexWorking. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

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

[AlexWorking]

As the reporter says "NOTE: URL rules of the product are created for the second website which does not default website, rules only not created for the mail website product." It's that for the 2.3 version. In 2.2-develop it's right the opposite - rules not created for the second (non-default) website product meening /category-url-key/product-url-key.(html).

[magento-engcom-team]

✅ Confirmed by @AlexWorking
Thank you for verifying the issue. Based on the provided information internal tickets MC-17160, MC-17161 were created

Issue Available: @AlexWorking, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[Vishrootways]

@AlexWorking Thank you for reviewing issue we are getting and confirm that it's an issue in Magento. Please let us know if you want any additional information from our side to find and solve this issue.
Thanks,
Vish

[sta1r]

#mmuk2019 assign to me

[magento-engcom-team]

@sta1r thank you for joining. Please accept team invitation here and self-assign the issue.

[m2-assistant]

Hi @sta1r. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

Hi @Vishrootways. Thank you for your report.
The issue has been fixed in #23309 by @sta1r in 2.3-develop branch
Related commit(s):

• 8fe7c88bf68c7eec7eb761f7b7690d73a9bb2ec1
• 60b577e3fa998ab9b4b85b0fb486cf542d626168
• 32de2806b5ea38b8d0b424838a5424f8279a6276
• 0da86ab8610b690d7ac149059f9b7c36e136f914
• 2d0fb70cb99fe7866eee251376a2de08dd2eab0c

The fix will be available with the upcoming 2.3.3 release.