Bump up the log debug level setting in your local_settings.py file and see what your log file says. It can get quite verbose and might point you in the right direction.
Also, what cache are you using? You might switch to file to see if that helps things out. -Chris On Wed, Aug 26, 2009 at 6:02 AM, Aidas Bendoraitis < [email protected]> wrote: > > Hello! > > I created a new project based on Satchmo large. It has a custom > payment module with it's own configuration group. The problem is that > if I change any settings in the configuration, it is saved to the > database, but not loaded, just the defaults are used. The modified > configuration is used only in django development server until restart. > If I save the configuration to LIVESETTINGS_OPTIONS in settings.py and > define 'DB': True, all customized settings are used as expected. > > Details: > I am using Django development webserver with sqlite3 for development > and Apache WSGI with MySQL for production. > > Do you know where the problem might be? How could I debug or track the > behaviour of livesettings? At what point the configuration is > prepopulated from the database (loading, special signal, or > middleware)? > > Best regards, > > Aidas Bendoraitis > senior developer > > studio 38 > pure communication GmbH > Rosenthaler Str. 38 > D - 10178 Berlin > > www.studio38.de > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
