I had the same problem with one of my Satchmo stores. I had a hard time reproducing it. I ended up writing a daemon that watched the satchmo.log file for that "maxiumum recursion depth exceeded" screen and restarted the website. Not a clean solution by any means, but it kept the site "up".
On Sep 17, 8:47 pm, "Chris Moffitt" <[EMAIL PROTECTED]> wrote: > Ok. It's a definite bug. Can you please add a ticket with this traceback as > well as the steps you took to reproduce it. > > Thanks, > Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
