Store switcher doesn't work multistore setup with different product urls

[sreichel]

Preconditions (*)

1. any version
2. +1 storeview

Steps to reproduce (*)

1. goadmin product edit page
2. switch to second storeview
3. set another URL in seo section
   3.1. default URL: some-name.html
   3.2 storeview URL: some-localized-name.html
4. check product on frontend
5. use storeswitcher more then once

Tested on https://pr-18895.instances.magento-community.engineering (2.3-dev) with product "Dekor Test".

Expected result (*)

1. redirects between storeview

Actual result (*)

1. redirect to home page

[magento-engcom-team]

Hi @sreichel. 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 $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[hostep]

This is related to #14674 I believe, but I'm not sure if it's an exact duplicate.

There is however a comment in there, which might solve your problem (untested).

[sreichel]

@hostep it is maybe relatet, but not the same.

On Stores -> Configuration -> Web , I set "Add Store code to URLs" to "YES"

I've default setup, w/o changing anything in config - see test instance.

For the comment ... not tested, but i guess it doesnt solve it, since target pathes uses same store id there ...

        $currentRewrites = $this->urlFinder->findAllByData([
            UrlRewrite::TARGET_PATH => $oldRewrite->getTargetPath(),
            UrlRewrite::STORE_ID => $targetStore->getId(),
        ]);

I think we wood need all latest target urls for all available storeview with storeview based category/product URL.

@sidolov @orlangur is it possible to set up test instances with different base URLs (subdomain/subfolder)?

[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

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

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97088, MAGETWO-97089 were created

[magento-engcom-team]

Hi @janakbhimani. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your 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-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!

• 3. 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

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

[magento-engcom-team]

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

• 927ca80fca4c1ec298df925c137dba7d1d799808
• b36dc042a8ac9c414c65dffa7538ea1af1fc412f
• 3d882cf115c48654012105c217aa8e0f09a92372
• c7b4aaebf9898229196cb2287c8d5da57e2b01ef
• 54a403993d2b6f919f018230854a33e1f8984e14
• 618d8e3c5ad7ac77f8d35ecce23788816a0b445d
• 8a05dbb95cdb2162fb0b859d26a31d670e8b658d

The fix will be available with the upcoming 2.3.1 release.

[magento-engcom-team]

Hi @sreichel. Thank you for your report.
The issue has been fixed in #21140 by @janakbhimani in 2.2-develop branch
Related commit(s):

• bd1e5380e64634a2275d224c2c08e8d1dcd974e7
• a8861035b34da209b00d4a37a7704208853c0d0c
• 78df524058bfeb23368cb865047e185aec80345b
• 7ebc03ffcd0a4ace268488112e101971cc2ad661
• 7e4fe31d4b3ae19c8a462598b77b4bdf4fa4c36f

The fix will be available with the upcoming 2.2.9 release.

[AnotherAlexSmith]

@magento-engcom-team tell me please, when 2.2.9 will be available?

[hostep]

@AnotherAlexSmith: since Magento releases a new version every 3 months, it is expected that 2.2.8 will be released end of February and 2.2.9 end of May.

[TimQSO]

I guess this ticket should be reopened. The switches now works while not being logged in. But when you login with a customer account, the behaviour is like described in this ticket.

[hostep]

@GuiltyNL: that's a new bug being tracked in #24942

[TimQSO]

@hostep Thanks!