-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
Fixed logging too many exceptions for payment methods #3181
Conversation
This reverts commit 86a3073.
This PR fixes Sales > Orders > View any Order. No more lines in exceptions.log. We still have the same issue in Customers > Manage Customers > Edit any Customer. Will you create a new PR for Customers? (PHP 8.1) |
I thought it was the same but I’ll check it out asap! |
@addison74 I've added the fix for the customer detail page in this PR because it was sharing part of the code ;-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested. No more warnings in the exceptions.log file related to the missing payment methods. For both sections in Backend (View Order and Edit Customer).
In #3179 @addison74 pointed out that, using the backend, and opening an order detail page, some exceptions were logged about missing payment methods.
This is because the list of payment methods tries to load the model (for the payment method) and logs an exception if it's not found.
This is ok in some cases (when the order was paid with a method that has been removed later) but not in all the other cases.
So I thought to kinda rewrite the getPaymentMethodList method of Mage_Payment_Helper_Data.
If I'm not mistaken the before/after output of the getPaymentMethodList method stays the same:
before:
after:
Related Pull Requests
#2939
Fixed Issues