No problem, fixing this issue was too hacky anyway - too many incompatible changes, even too specific. Imagine another payment modules requiring such or similar functionality. Hope there will be some generic consistent solution in upcoming Satchmo versions.
Rails/Spree look like more mature product. In comparison you can simply define your own payment methods with or without delayed payment just with web admin interface, ie. not writing a simple line of code ! It was very easy to launch a basic custom project, there are support modules/controllers for everything you can imagine. On the other hand in comparison with Satchmo/Django it's a bit more 'heavier' on system resources and Ruby although a great language I find it a bit hairy with many special cases. It also lacks the unambiguousness and straightforwardness of Python. On Thursday, January 31, 2013 10:50:18 PM UTC+1, Stanislav Mihaylov wrote: > > Yep, unfortunately I noticed the same problem, so I ended up returning it > to the original source code and rather modifying the view that is connected > to the templates to display a different message when the payment module is > COD. That's the best way I could think of, but in the admin records the > order is still displayed with completed payment and status 'New'. Good luck > with Rails! > > On Thursday, January 31, 2013 12:19:36 PM UTC, David Unric wrote: >> >> Hi, >> >> I've made modified Satchmo sources by your instructions but >> unfortunatelly checkout process does not finish, it stops with "To complete >> this order, you need to pay the $xx.xx balance remaining on this order." . >> >> Probably have to wait until half-baked checkout/payment code will be >> fixed & tested in an upstream. >> I'm forced the custom shop I'm working on to do in Spree/Rails now, >> although I'm more familiar with Python and its library. Next time, maybe. >> >> On Saturday, January 26, 2013 6:58:13 PM UTC+1, Stanislav Mihaylov wrote: >>> >>> Actually you can ignore the logic about changing order status to 'Temp' >>> and then 'New', because by default the status before confirmation is None - >>> displayed as (None) and after confirmation gets to 'New'. So you can just >>> leave it like that. I am currently wondering if there is any cron job to >>> delete every order with status of None that has a time stamp older than >>> e.g. 24h. If you find anything like that, please share it. >> >> -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To unsubscribe from this group and stop receiving emails from it, send an email to satchmo-users+unsubscr...@googlegroups.com. To post to this group, send email to satchmo-users@googlegroups.com. Visit this group at http://groups.google.com/group/satchmo-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
