Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-3276

Stripe Payments: Migrations from old Stripe gateway does not check all API fields

    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 Jonathan Reissmueller created issue -
        jonathan Jonathan Reissmueller made changes -
        Field Original Value New Value
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Sprint 4.8.0 Sprint 1 [ 92 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked lower
        jonathan Jonathan Reissmueller made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 45 minutes [ 2700 ]
        Worklog Id 12614 [ 12614 ]
        jonathan Jonathan Reissmueller made changes -
        Status Open [ 1 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        tyson 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 Tyson Phillips (Inactive) made changes -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              24/Sep/19

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 45 minutes
              45m

                Agile