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. > I had this happen once after an unfortunate series of events where I'd > accidentally overwritten the hidden "key" value for the Authorize module > with a blank. > Hope that helps. -- 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.
