> In the meantime, please submit a ticket with this issue and we'll fix it. > Even better, would be to submit a patch since I'm not sure I have a Fedex > key myself. > Cool, I'll create a ticket and a patch.
> I'd recommend sticking with Satchmo trunk and Django 1.0. I know trunk isn't > bug free but the pain of 0.7 -> 0.8 migration with Satchmo is probably > pretty high because of all the changes we had to make to get Satchmo running > on Django 1.0. You've identified one gap but I don't think it means that > Satchmo 0.7 is a better choice. Having just gone through the migration on our staging store, it actually wasn't too bad. The hardest part (really just a bit tedious) was going through each of the templates in the app directory and merging in changes since .7. I think we'll launch with the trunk.... thanks, joe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
