On Wed, Jun 9, 2010 at 5:02 PM, [email protected] <[email protected]> wrote:
> Hi all, > > We're still using 0.8 but I recognize the problem still exists in > livesettings on trunk (please don't recommend upgrading - of course we > have our reasons :) Below is a very simple example of what we're > trying to deal with (in pseudocode): > > @transaction.commit_manually > function fulfill_order: > try: > prepare order (with db changes) > attempt CC capture through satchmo payment module > update order (with db changes) > commit > return happy page > except: > rollback > return angry page > I'm the primary author of the Livesettings system, threaded_multihost, and of Bursar. Actually, I don't think your issue would be that difficult to work around. We already monkey-patch Site.objects.get_current. We could instead allow for an explicit setting of the site before any call to _get_site_id in sensitive situations. Basically, wrapping the operation with a "no need to bother the DB, here's your site" operation. I'd accept that patch to threaded-multihost.multihost_patch.py if you wrote it. In addition, and more importantly, Bursar doesn't use Livesettings, because it is inappropriate to be switching around payment options on-the-fly for most sites, and because it is unnecessary overhead. Satchmo will shortly be moving to Bursar for payment processing, and this issue will (mostly) go away. -- Bruce Kroeze http://www.ecomsmith.com It's time to hammer your site into shape. -- 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.
