Magento 2.3 Wrong product url for anchor categories for multiple storeviews

[juharintanen]

Preconditions (*)

1. Magento 2.3.2

Steps to reproduce (*)

1. Regenerate new url rewrite for product

Expected result (*)

1. All product urls with categories are genereted accordingly by correct store view

Actual result (*)

1. Product urls that are generated from anchor categories are missing StoreId and are generated wrong.

Underlined $storeId is missing and needs to be added in code.

[m2-assistant]

Hi @juharintanen. 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.

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

[hostep]

This is most likely a duplicate of #11615, but I'm leaving it open, because this problem definitely needs a lot more attention.

We are awaiting for many months now on #20826 finally getting approved...

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

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

@juharintanen thank you for your report. This this known issue and PR for it is already created.
@hostep I mark this issue as duplicate and close it. You could reopen it if PR won't be merged or issue will appears in the future

Duplicate of #11615

[slavvka]

Hi @juharintanen. Thank you for your report.
The issue has been fixed in #26784 by @hostep in 2.4-develop branch
Related commit(s):

• cb685d15b2b590bdb4d99a3d4ebe563037d0aa31
• acb8642c44d1ecb60ad023c81f6541fa9ebae47d
• 97258e1a9ce97ad32971731eceac8fee32f66b74
• 6cf26dc19e2f80f0c2da445443d0b48a1974fc77
• 0b941218dcc86dcbd518f5400934e995ad1f2e3c
• b0c0c59900b4ddf8d70cf2ae9c9ec12805d13908
• 28fa34531f4c7cd4bcad46500ba027b9b58ff297
• bf514b0b435a75f5688f56f8e9465af9bb3284c1

The fix will be available with the upcoming 2.4.0 release.