[Bugfix/8.0] Payment exceptions not being caught #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lasley
added a commit
that referenced
this pull request
Jun 1, 2016
…t-exceptions-not-being-caught to release/8.0 * commit 'd0bc0ced3b12e7e1ea4cd89b3ad898c908f42b54': [FIX] Test errors in payment_authorize_auto_reconcile [FIX] acquirer search security in payment_authorize_auto_reconcile [FIX] Validation error import in payment_authorize_auto_reconcile
lasley
deleted the
bugfix/8.0/LABS-164-payment-exceptions-not-being-caught
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1 & Adds tests
@stephen144 - Mind double checking that this fixes on your end as well? Turns out it was both the custom exception, and a security issue on the payment acquirer search.