Skip to content

Getting wrong frontend-controller, when using storecodes in urls #15565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
EliasKotlyar opened this issue May 29, 2018 · 2 comments
Closed

Getting wrong frontend-controller, when using storecodes in urls #15565

EliasKotlyar opened this issue May 29, 2018 · 2 comments
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Progress: PR Created Indicates that Pull Request has been created to fix issue

Comments

@EliasKotlyar
Copy link
Contributor

EliasKotlyar commented May 29, 2018

Preconditions

  1. PHP 7.0
  2. Magento 2.2.4

Steps to reproduce

  1. Create a Store with 2 StoreViews like "de" and "en". "de" is the default storeview
  2. Set 'Stores' > 'Configuration' > 'General' > 'Web' > 'Add Store Code to Urls' to 'Yes'
  3. Set "web/default/front" from Store "en" to somehing different like "catalog/product/view/id/productid"
  4. Go to "domain.com/en"

Expected result

I will see the product page

Actual result

I see the default CMS-Page

More information

Not reproducable in 2.2.2, 2.2.3
Reproducable on 2.2.4.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label May 29, 2018
@EliasKotlyar EliasKotlyar changed the title Storecode gets redirected Getting wrong frontend-controller, when using storecodes in urls May 29, 2018
@EliasKotlyar EliasKotlyar mentioned this issue May 29, 2018
4 tasks
@magento-engcom-team magento-engcom-team added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Jun 1, 2018
@magento-engcom-team
Copy link
Contributor

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

The fix will be available with the upcoming 2.2.6 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Jun 4, 2018
magento-team pushed a commit that referenced this issue Jun 4, 2018
magento-team pushed a commit that referenced this issue Jun 4, 2018
 - Merge Pull Request #15566 from EliasKotlyar/magento2:bugfix/15565
 - Merged commits:
   1. 1cbb265
   2. 4d886b2
magento-team pushed a commit that referenced this issue Jun 4, 2018
gelanivishal pushed a commit to gelanivishal/magento2 that referenced this issue Jun 4, 2018
gelanivishal pushed a commit to gelanivishal/magento2 that referenced this issue Jun 4, 2018
gelanivishal added a commit to gelanivishal/magento2 that referenced this issue Jun 4, 2018
gelanivishal added a commit to gelanivishal/magento2 that referenced this issue Jun 4, 2018
@sidolov
Copy link
Contributor

sidolov commented Jun 19, 2018

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

The fix will be available with the upcoming 2.3.0 release.

@sidolov sidolov added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Progress: PR Created Indicates that Pull Request has been created to fix issue
Projects
None yet
Development

No branches or pull requests

3 participants