> The Google Checkout payment processor empties the cart once it > receives a call back from the google checkout server that the payment > has been completed. (That's an incoming HTTPS request from the google > servers to the plone server.)
Also please see this critical bug discussion regarding the destruction of a cart: http://code.google.com/p/getpaid/issues/detail?id=209&sort=priority&colspec=ID%20Type%20Status%20Priority%20Release%20Component%20Summary%20Owner The bug might be triggered by the way how cart is destroyed. Someone with heavy Zope experience could investigate - I think my own time is little limited and I am not yet ascended to the land of Zope gods. -Mikko > > > The usability feature of that is that the user can use their back > button to go back to the shop (or follow the links on the google > checkout review page) and still have their cart intact. > > Meanwhile the Google Checkout processor for getpaid does not yet > bother with orders. Google checkout itself provides order management. > However if a site allows the shopper to chose from several processors > then it could make sense for someone to add in order support for that > processor too. (That would not be particularly hard to do. The > mechanical parts of receiving the notifications are already > implemented.) > > -- > Michael Dunstan > > > > -- Mikko Ohtamaa Managing director, Red Innovation Ltd. +358 40 743 9707 www.redinnovation.com Every problem is solvable if you can throw enough energy drinks at it --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" 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/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
