Magento 2.3.2 wrong product url with multiple store views

[LouNik1984]

This issue is similar to (not the same as) #16134 which is marked as closed even if the url issue is not fixed:

Preconditions (*)

• magento 2.3.2 (fresh install) on nginx 1.12.2 and php 7.1.31

Steps to reproduce (*)

• create two or more store views
• create products programmatically (code instead of backend admin)

Expected result (*)

• on frontend, url for products should be www.domain.com/url-key-of-product for all store views

Actual result (*)

• on frontend, only the default store view has the correct url, the other store views all show the /view/id/{product_id}/s/{url-key} url

Notes

• differently from issue #16134, backend has no issue (checkboxes are all checked, url key fields are correct on all store views)
• cleaning cache (from cli and backend) doesn't solve the issue
• reindex doesn't solve the issue
• using https://github.com/olegkoval/magento2-regenerate_url_rewrites extension works: after I run php bin/magento ok:urlrewrites:regenerate --entity-type=product I can finally see all the correct urls in all the stores
• category urls have issues too: if you create a category programmatically, the category on frontend is visible only in the default store view, while in backend all the other store views misses the url key field entirely. Again running olegkoval extension php bin/magento ok:urlrewrites:regenerate --entity-type=category fixes the problem

[m2-assistant[bot]]

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

@LouNik1984 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[bot]]

Hi @vikalps4. 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: :point_down:

• [ ] 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!

---

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

[m2-assistant[bot]]

Hi @shikhamis11. 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: :point_down:

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

[kingletas]

@LouNik1984 one thing you want to verify is that the product is associated with the other stores and it has generated the URLs. When you see URLs like catalog/product/view/{id} it usually means the URL rewrite was not found. Another thing, for the no default store you may start seeing the store __param if you access them from a separate store.

[LouNik1984]

"one thing you want to verify is that the product is associated with the other stores and it has generated the URLs"

I'm not sure I understand correctly, but when I open the backend I can see that the website is correctly flagged for all store views, so apparently everything is right but if I check the rewrite table in database then the rows corrisponding to the other stores are missing (only the default store is there). Saving the product from backend, clearing cache and reindex doesn't help. Olegkoval works because it adds the missing rows in the rewrite table.

"When you see URLs like catalog/product/view/{id} it usually means the URL rewrite was not found"

Yes, that's exactly the issue: the urls from additional stores are not written in the rewrite table. Olegkoval extension fixes this by adding the missing record in the database table.

I did a bunch of tests and I think I understood the issue:

I usually create the product for all store views and then update the products with only those fields which are store specific (such as description which changes based on store language). Because of this I only add the store_id key on product update. I test the product creation by adding the store_id = 0 and it seems to work: if I create a product specifying store_id = 0 in the data array, then the urls are created for all store views.

[LouNik1984]

I noticed something else, this time during the update of the product:

if I try to update a field for a specific store view (eg: the description field on the german store view), the new value is correctly saved but all the "use default value" checkboxes gets unchecked. I think that only the edited field should have the box unchecked

[m2-assistant[bot]]

Hi @engcom-Charlie. 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: :point_down:

• [ ] 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-Charlie]

Hello @LouNik1984

We are not able to reproduce this issue on the latest 2.3-develop branch by provided steps.

Testing scenario:

1. Create two or more store views

2. create products programmatically (code instead of backend admin) My code:

3. Check product URL on all store views

Result: on frontend, URL for product = http://magento2pr3.loc/sample-simple-product11132555558885.html for all store views Default store view: test1: test2:

URL Rewrites:

So i have to close this issue.

Thanks for your report!