On Mon, Jul 11, 2011 at 2:49 PM, Matthew Talbert <[email protected]> wrote:
> On Mon, Jul 11, 2011 at 2:10 PM, Bruce Kroeze <[email protected]> wrote:
>> Take a look at the second to last item, where it is getting the processor.
>> Add a new log statement, showing the key it is trying to get. Note the
>> key. It may be obviously wrong.
>> Then, go in via the shell and try to get that processor by that key. Does
>> it exist?
>
> Thanks, I will try this. However, it is looking up the key based on
> the order authorization, which I've confirmed does have the correct
> key.
OK, the key is now "PAYMENT_PAYMENT_AUTHORIZENET". Obviously the first
PAYMENT is redundant. Any idea how to find where that's coming from?
satchmo/apps/payment/utils.py does this:
processor = get_processor_by_key('PAYMENT_%s' % authz.payment)
but in the database, the authorization is already saved as
PAYMENT_AUTHORIZENET so it's getting doubled. Is this a bug in
Satchmo?
Thanks,
Matthew
--
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en.
