-
-
Notifications
You must be signed in to change notification settings - Fork 438
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
Orphaned ACL resource exceptions are now logged only in developer mode #3642
Conversation
This code is not complete. Better delete orphan records (and maybe add log otation, or patch it away?) I see more pros then cons with logging. |
Sorry @sreichel this is not intended to resolve the orphan data but only to not log an exception every time i log in in the backend until we have a solution |
I recommend to apply this change temporarily via the composer patcher if this causes you problems. The original code also had a (commented out) part in, which automatically cleans it up. Iam not a fan of this, but making it configurable would also be an option. Would one of these options be acceptable? |
I agree with @Flyingmana that logging is a good way to find and cleanup problems, and I agree with the sentiment of the original PR thus I'd leave it as it is, cleanup should be quite easy and there's #3647 on the way |
what if we wrap the exception in this if statement?
|
acceptable for me |
Perfect for me. It does not fill logs in production, but pops up in local env ... @Sdfendor |
I agree, it's acceptable. |
Perfect! |
can please someone provide a better title for the PR based on the new changes? |
done |
Description (*)
more details here:
#3625
Revert
https://github.com/OpenMage/magento-lts/pull/2339/files#diff-1048571d4baf38d246708d5953af464948b5591c2c8d648036394d6101ba8022
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)