On Wed, Nov 18, 2009 at 7:29 PM, Alessandro Ronchi < alessandro.ron...@soasi.com> wrote:
> > > http://dpaste.com/122205/ > is my log file. > > Traceback shows it is dying during the load of middleware. You would not get a pretty debug page for this even with DEBUG=True and running the development server: you'd get a bare traceback, which is what you see in the Apache log. This is code that is not covered by the exception-catching-turn-it-into-a-pretty-page try/except block. Ultimately it says (stripping out the referrer and leading timestamp, etc): File "/var/www/vhosts/ hobbygiochi.com/django/satchmo_src/satchmo/apps/livesettings/functions.py", line 67, in get_config raise SettingNotSet('%s config group does not exist' % group), SettingNotSet: <unprintable instance object> Which seems to imply something wrong with your satchmo config. I don't know satchmo but it seems to be trying to complain about a config group not existing. However it seems to run into trouble reporting the name of that group. That <unprintable> message might be implying the group name has non-ASCII data in it, which is making the SettingNotSet instance unprintable. That may be a clue or may be completely wrong -- it's just the only kind of situation where I've seen that sort of <unprintable> message crop up. Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=.
