Fix ProAccountBans module #1934
Merged
Conversation
This file contains 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
gbp
force-pushed
the
fix-pro-account-ban-module
branch
9 times, most recently
from
d41b88d
to
86d7b23
Compare
Since Stripe API version upgrade [1] in core this hasn't worked as expected. This is because of changes to ProAccount#update_stripe_customer required to support the newer API and changes to prevent deprecation warnings. [1] mysociety/alaveteli#8405
gbp
force-pushed
the
fix-pro-account-ban-module
branch
from
86d7b23
to
dd78be9
Compare
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.
Since Stripe API version upgrade [1] in core this hasn't worked as expected.
This is because of changes to ProAccount#update_stripe_customer required to support the newer API and changes to prevent deprecation warnings.
[1] mysociety/alaveteli#8405