URL Rewrites are overwritten

[AnshuMishra17]

Preconditions (*)

I am able to reproduce the issue of the following Magento Open Source version

1. 2.2.6
2. 2.2.7

Steps to reproduce (*)

1. Add multiple websites, for example I have three websites, each website has its own store and corresponding store view.
   
2. Go to Catalog -> Product -> select any product and edit it.
   For example, I have selected product with id 1 (Joust Duffle Bag)
3. From Store view dropdown, select Default Store View.
4. Under the Search Engine Optimization, uncheck the Use Default Value checkbox for URL Key and modifiy the URL key and save the product.
   
5. Now, in Marketing -> URL rewrites, try to find the url rewrite for your selected product and you will able to see your new rewrites.
6. Now, from the product listing page, select the same product as in step 2 and select update attributes from the Actions dropdown.
   
7. Select the website tab and in Add product to websites select any new website and save.
   For example, my product was already in main website, so I have selected website 2.
8. Now again go in Marketing -> URL rewrites and try to find all the url rewrites for your product.
   You will see the URL rewrites that has been generated in step 4 and step 5 no longer exist and you will only see the latest rewrite that has been generated in step 7.
   

Expected result (*)

URL rewrites for all the websites should exist.

Actual result (*)

URL rewrites are overwritten.

[magento-engcom-team]

Hi @AnshuMishra17. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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-engcom-team 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-engcom-team 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

• Next steps are available in case you are a member of Community Maintainers.

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

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

[magento-engcom-team]

Hi @maheshWebkul721. 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-engcom-team 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-engcom-team 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

• Next steps are available in case you are a member of Community Maintainers.

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

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

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98330, MAGETWO-98331 were created

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

[magento-engcom-team]

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

• 7cacec1f4b4abe09d991c79f4e15cb465056b670

The fix will be available with the upcoming 2.3.2 release.

[Ctucker9233]

@magento-engcom-team Shouldn't this stay open until the the 2.2 backport is merged? This is how a lot of bug fixes get lost.

[ghost]

Hi @Ctucker9233 there is a backport PR, -> #21358

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!