Ok - thanks - I was misunderstanding - thanks for the clarification. Cheers, Ruppert
On Feb 5, 2010, at 9:30 PM, Adam Heath wrote: > Tim Ruppert wrote: >> I'll ask around and see if we're doing exactly this workflow. I know for a >> fact that we are utilizing Google Checkout and returns are being processed >> no problem. > > Nonono. Googlecheckout is not being used. It's just existing at > specialpurpose/googlecheckout. > >> >> Cheers, >> Ruppert >> -- >> Tim Ruppert >> HotWax Media >> http://www.hotwaxmedia.com >> >> o:801.649.6594 >> f:801.649.6595 >> >> On Feb 5, 2010, at 2:18 PM, Ean Schuessler wrote: >> >>> Adam Heath wrote: >>>> Tim Ruppert wrote: >>>> >>>>> I haven't looked at it myself recently Ean, but I'm pretty darn sure that >>>>> we are processing returns, thru Google Checkout, on a version that's at >>>>> least branched from around the beginning of December. >>>>> >>>> Try processing a vendor return, that has a shipment attached, but that >>>> isn't connected to googlecheckout, with specialpurpose/googlecheckout >>>> available as a component. You'll get a NPE, because googlecheckout >>>> assumes an order item is available. >>>> >>>> This is due to the googlecheckout component adding an eca that >>>> *always* runs when an Shipment changes status, and then in >>>> sendItemsShipped, assumes anc order is attached to the shipment; this >>>> isn't the case when a Return is being processed. So, this would fail >>>> in *all* situations when googlecheckout is available as a component, >>>> and you aren't actually using a component. >>>> >>> Basically right. You have to attempt to generate an outgoing shipment >>> off a vendor return. This can't work because the GoogleCheckout code >>> tries to look up the order for the shipment, which doesn't exist in this >>> case. Tim, if you have a fix for that can you check it in? >>> >>> -- >>> Ean Schuessler, CTO >>> [email protected] >>> 214-720-0700 x 315 >>> Brainfood, Inc. >>> http://www.brainfood.com >>> >> >
smime.p7s
Description: S/MIME cryptographic signature
