Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.7.0
-
Fix Version/s: 4.7.1
-
Component/s: None
-
Labels:None
Description
Looks like the migration tool may not be entirely robust. See the github issue reported here: https://github.com/blesta/gateway-stripepayments/issues/18
Apparently where on the client their default card ID is stored has moved a number of times. We should probably add checks for all the places mentioned just to be sure we are covering our bases
Activity
Jonathan Reissmueller
created issue -
Jonathan Reissmueller
made changes -
Field | Original Value | New Value |
---|---|---|
Rank | Ranked higher |
Jonathan Reissmueller
made changes -
Sprint | 4.8.0 Sprint 1 [ 92 ] |
Jonathan Reissmueller
made changes -
Rank | Ranked higher |
Jonathan Reissmueller
made changes -
Rank | Ranked lower |
Jonathan Reissmueller
made changes -
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 45 minutes [ 2700 ] | |
Worklog Id | 12614 [ 12614 ] |
Jonathan Reissmueller
made changes -
Status | Open [ 1 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
Summary | Stripe Payments: Migration routine incompatible with current API? | Stripe Payments: Migrations from old Stripe gateway does not check all API fields |
Tyson Phillips (Inactive)
made changes -
Status | In Review [ 5 ] | Closed [ 6 ] |