Magento2: Magento 2 Stores -> Configuration redirects to dashboard

[Mitrajsinh]

Preconditions (*)
newly setup of magento 2.2.8.
Stores -> Configuration redirects to the Dashboard.

Steps to reproduce (*)
Enable : - Add Secret Key to URLs from Backend
Go to order section After That click on store > config

Expected result (*)
Access to the Stores -> Configuration page

Actual result (*)
I'm being redirected to the dashboard

[m2-assistant[bot]]

Hi @Mitrajsinh. 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 2.3-develop instance - upcoming 2.3.x release

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

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

• [ ] yes
• [ ] no

[m2-assistant[bot]]

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

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

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

• [x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

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

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

• [x] 6. Add label Issue: Confirmed once verification is complete.

• [x] 7. Make sure that automatic system confirms that report has been added to the backlog.

[krishprakash]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-22366-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[krishprakash]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-22366-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

:white_check_mark: Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99227 were created

Issue Available: @krishprakash, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[krishprakash]

Note: This issue is not reproduced on 2.3.x.

[gwharton]

I got so fed up of this that I disabled adding Secret Key to URLs from Backend. After the update to 2.2.8 It changed from being a one off every now and again, to 100% of the time for me. Disabling secret key as workaround.

[nocturnalfrog]

Looks like https://github.com/magento/magento2/pull/18018 is to blame.

[m2-assistant[bot]]

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

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

[sarfarazbheda]

I am able to replicate the issue on Magento 2.2.8 after the upgrade.

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @sarfarazbheda. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @sarfarazbheda, here is your Magento instance.
Admin access: https://i-22366-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sarfarazbheda]

I am able to replicate issue with above instance. Steps:

• Enable Add Secret Key to URLs
• Go to Sales-> Orders
• Navigate to any other menu

[pemann]

Occurs for me also after I upgraded to 2.2.8 (from 2.2.3)

[ghost]

+1, I'm seeing it after upgrading to 2.2.9 from 2.2.7

[lupett]

+1 2.2.8 -> 2.2.9

[elvinristi]

this seems to fix the issue what is in 2.3 branch for app/code/Magento/Backend/Block/Menu.php

• https://github.com/magento/magento2/commit/956f36132e3438acfea61a3e4cd41b43e1bd1fc0

     {
         $routeId = $this->routeConfig->getRouteByFrontName($match[1]);
         return \Magento\Backend\Model\UrlInterface::SECRET_KEY_PARAM_NAME . '/' . $this->_url->getSecretKey(
-            $routeId,
+            $routeId ?: $match[1],
             $match[2],
             $match[3]
         );

It seems to be also already in 2.2-development branch but not part of 2.2.9

• https://github.com/magento/magento2/commit/5be13c5da3f73360fef761c9a4f368bf715927fd#diff-69ae04f06b2a290de8d689525dfe33e0R222

[wjpbill]

Hello everyone

Did anyone find a fix for this. I'm running 2.2.8 and for the minute have disabled secret keys in the admin and it's working again but wondered if there's a code fix anywhere for 2.2.8?

[elvinristi]

@wjpbill check previous comment https://github.com/magento/magento2/issues/22366#issuecomment-508707963

[wjpbill]

@wjpbill check previous comment #22366 (comment)

That work, thank you very much. It was driving me around the bend.
The only problem I have now is that stupid "Attention, Something Went Wrong" popup with it's associated "There was a technical problem blah blah" error when you click a menu item. It always goes way when I close it but it's so irritating and nothing in the logs.

[ghost]

@wjpbill, we only get that message when viewing an order on the admin. We haven't investigated it. It seems to go away after showing up 1 time.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you 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 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. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[engcom-Bravo]

Hello, @Mitrajsinh

Thank you for contribution and collaboration!

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

We are closing this issue due to _branch 2.2-develop was closed and Magento no longer accepts pull requests and issues to the v2.2 release lines to focus all development efforts on v2.3._
See Accepted pull requests and ported code for more details

If you still faced this issue on 2.3 please create a new Issue with all required details according to Issue reporting guidelines

[aashworth-ldg]

Occurs for me also after I upgraded to 2.2.8 (from 2.2.3)

Same for me.