Skip to content
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

"Something Went Wrong" error for limited access admin user #11700

Closed
expgabe opened this issue Oct 24, 2017 · 6 comments
Closed

"Something Went Wrong" error for limited access admin user #11700

expgabe opened this issue Oct 24, 2017 · 6 comments
Assignees
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: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@expgabe
Copy link

expgabe commented Oct 24, 2017

Preconditions

  1. Magento 2.2
  2. CentOS Cpanel 66.0 with Engintron Nginx for cpanel, Apache 2.4.28, MySQL 10.2.9-MariaDB , PHP 7.0

Steps to reproduce

  1. Login as an admin user with limited access
  2. Something went wrong error pops up after every page load
  3. Server Logs and Magento Logs don't record any errors

Expected result

  1. Logs should point to the error.

Actual result

  1. [Screenshot, logs]
@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Oct 24, 2017
@magento-engcom-team
Copy link
Contributor

@expgabe, thank you for your report.
We've created internal ticket(s) MAGETWO-82713 to track progress on the issue.

@magento-engcom-team magento-engcom-team added 2.3.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 25, 2017
@RomaKis RomaKis self-assigned this Nov 3, 2017
@okorshenko
Copy link
Contributor

The issue has been fixed and delivered to 2.2-develop branch. Will be available with 2.2.2 release

@magento-team
Copy link
Contributor

Hi @expgabe. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1286 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming patch release.

@magento-team magento-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Jan 26, 2018
@george-vlahakis
Copy link

@okorshenko
Copy link
Contributor

Hi @georgios-2317
this is a private repository with limited access that's why you got 404

@philsmcc
Copy link

It is usually just this..
Say you only want to give someone access to add products...

Enable "Catalog", and under system, you can also enable "notifications" under "System".

The error usually comes from the message that tells you that one of your cache types is invalidated but is is being blocked because the user does not have access to receive system messages and notifications, so it throws an error. You may also need to give access to some of your theme's and modules properties that produce notifications or if it is related to adding products or whatever task you want to assign to that role.

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: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

7 participants