Update 1: This is not an issue with my module. The same thing happens when doing authorization captures through setting order to shipped in the *dummy*module.
Update 2: the db updates shown below *do* work, but I looked further in the log and I found a rollback-style update that sets the orderpayment object back to 'LINKED' and orderauthorization.complete back to False. Is this supposed to happen? I have DEBUG set to True in my project settings and LIVEis set to False in payment.config. On Monday, 27 August 2012 17:07:07 UTC-4, Marconius Cuthemustard wrote: > > re: PaymentProcessor.record_payment() not updating OrderPayment or > OrderPaymentAuthorization objects > > This happens when settings.CAPTURE is set to False, and I change an > order's status to "shipped" in order to capture the authorizations. It's > weird, because everything seems to work fine, but nothing changes. Even > when I looked at the `satchmo.log` I find these two lines: > > Mon, 27 Aug 2012 16:40:04 django.db.backends DEBUG (0.000) UPDATE > "shop_orderpayment" SET "payment" = 'PAYMENTSPRO', "amount" = > '78.9200000000', "time_stamp" = '2012-08-27 16:40:04.887587', > "transaction_id" = '1234567890ABCDEF', "details" = NULL, "reason_code" = > 'None', "order_id" = 1000718 WHERE "shop_orderpayment"."id" = 179 ; > args=(u'PAYMENTSPRO', u'78.9200000000', u'2012-08-27 16:40:04.887587', > u'1234567890ABCDEF', u'None', 1000718, 179) > > and > > Mon, 27 Aug 2012 16:40:04 django.db.backends DEBUG (0.001) UPDATE > "shop_orderauthorization" SET "payment" = 'PAYMENTSPRO', "amount" = > '78.9200000000', "time_stamp" = '2012-08-27 16:34:16.585738', > "transaction_id" = 'FEDCBA0987654321', "details" = 'AVS code: X, CVV2 > match: M', "reason_code" = 'na', "order_id" = 1000718, "capture_id" = 179, > "complete" = true WHERE "shop_orderauthorization"."id" = 29 ; > args=(u'PAYMENTSPRO', u'78.9200000000', u'2012-08-27 16:34:16.585738', > u'FEDCBA0987654321', u'AVS code: X, CVV2 match: M', u'na', 1000718, 179, > True, 29) > > Both of which show very valid sql. But nothing actually changed in the db. > The authorization was *not* marked as complete and the payment was not > updated in any way. I even ran the sql manually it in the dbshell for fun > and it worked. > > Anyone have an idea what can cause this? > > thanks, > > Marco > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/satchmo-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
