Adding simple products to a certain store view picks wrong category name (default) instead of store view category name

[Munktells]

When adding a product to a certain store view under "Product in Websites", it chooses the wrong category name, namely the default category name, and not the store view category name. Note that this is not true for all category names, the product is added to, just one for some reason, when the product exists in several categories.

Preconditions (*)

1. Install latest Magento and set up two or more store views.
2. Add a default scope category, and a specific category, for each store view.

Steps to reproduce (*)

1. Add a simple product, and choose the store view for the product:

2. The thought category name for the actual store view:

Expected result (*)

1. The category name should be "storlekar" from the corresponding store view categories

Actual result (*)

1. Magento is choosing the wrong category name (the default category name):

2. It should be "storlekar" and not "sizes" for this category:

Additional info from Engcom

We could reproduce the issue via the following steps

1. Create the following Category structure

2. Create two Websites, two Stores, two Store Views

   While creating Stores, assign the same previously created Category to both Stores

3. Go to Catalog - Categories. Switch to the second StoreView, and rename sizes to storlekar for example 4 Go to Catalog - Products and Add a new product. While Creating the product, do not assign it to any Category. Select the second website under Product in Websites
4. Save the Product
5. Switch to the second Store View
6. Assign the product to the to storlekar category and Save the product
7. Go to Marketing - URL Rewrites and observe the Request Path to the product

Actual Result The Request Path is sizes/sprod.html

Expected Result The Request Path is storlekar/sprod.html

[m2-assistant[bot]]

Hi @AlldoGroup. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

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

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

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

[engcom-Bravo]

Hello @AlldoGroup

Thank you for your report

Which Category do you select from the Category tree when creating a Product. Example:

Thank you in advance

[Munktells]

Hello @engcom-Bravo

Like this, and the problem only occurs when choosing the category "30x40 cm" under "sizes" (storlekar):

It chooses this category name "Sizes" (ID72) - All Store Views:

It should choose this category name "Storlekar" (ID72) - Diplomram.se View:

[engcom-Bravo]

@AlldoGroup Thank you for the quick response

Seems like we are able to reproduce the described behavior, I have only one last question: Did you manually rename the Size Category into Storlekar?

Thank you

[Munktells]

Hello @engcom-Bravo

We usually create all defaults (All Store Views) in English first, then we switch to a created store view, and make changes/translation accordingly. This is done to all categories and products.

So yes, this is done manually, no imports nor scripts.

Hope that this answers your question. Thanks,

[engcom-Bravo]

We confirm that the issue is reproducible on the latest Magento 2.4-develop. Additional info from Engcom is added to the description.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Bravo Thank you for verifying the issue. Based on the provided information internal tickets MC-39329 were created

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

[dverkade]

@magento-engcom-team @engcom-Bravo I can confirm this is an issue. We're running into this issue with clients having multiple store views as well.

If you rename a URL key on store view level it will rewrite ALL the current URLs of the products attached to the one you are saving for ALL storeviews. Changing the URLs for all products under that category.

Regarding priority and severity this is now set as an S3 and P3 and I do not agree. SEO friendly URLs are a key part of ecommerce stores and messing this up will have huge impact in SEO scores. Such a loss of basic and core functionality should be qualified as an S1 and P1 issue. It affects critical data and functionality. Users need to have a workaround in place in order to work correctly with URL rewrites on the storeview level. It changes critical data in other storeviews which is not the expectation and there's no clear path on the workaround. It needs a fix immediately as it's having a huge impact on users.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[dverkade]

Ready for dev tickets should not be closed automatically. Posting a comment here to remove the stale bot and keep it open.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[Munktells]

What's the status on this ticket @engcom-Bravo ?

[pagesailor]

Any status update on this issue @magento-engcom-team @engcom-Bravo ?

[engcom-Bravo]

Hi @Munktells,

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

The request path is wrong with respect to that particular store view.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12041 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.