I'm the author of the livesettings module. What I've seen in the past is that errors from livesettings, the dreaded "SettingNotSet" come up as a symptom of some other configuration issue. That is, if there are other problems, for some reason, the system first responds by throwing a SettingNotSet error. The problem, in almost all cases, is not the livesettings module, but the error gets masked by the SettingNotSet error.
I'd love to see that get more transparent, but I really really doubt the OP's problem in livesettings. In my experience, that has *never* been the case. It is always a misconfiguration elsewhere. Any ideas about how to make this more transparent are welcome, and I will be on the Satchmo Sprint. On Tue, Dec 22, 2009 at 10:24 AM, Bob Waycott <[email protected]> wrote: > Perhaps we should see if a concerted effort could be made during next > weekend's sprint to get this resolved. > > > On Tue, Dec 22, 2009 at 11:56 AM, franck bret <[email protected]>wrote: > >> well bob, how to use settings is well documented in django >> documentation, but the problem is not here, and i could confirm that i >> encounter exactly the same strange behaviour even if i'm in django / >> satchmo project folder... >> All of the post of this thread are related to the fact that >> live_settings module is not consistent and for the same reason i say a >> few post ago is very hard to debug. >> I've also tried to deactivate livesettings and pass in settings.py a >> full dictionary with all possible and required livesettings values, >> but the problem still remain the same... >> >> >> 2009/12/22 Bob Waycott <[email protected]>: >> > davis, >> > The typical way of using manage.py shell without setting the environment >> > variable is like this: >> > python manage.py shell --settings=settings >> > (if you are in your project dir and your settings.py is in the same dir) >> > That enables Django to load up all the necessary settings for shell to >> work. >> > >> > On Fri, Dec 18, 2009 at 10:20 PM, davis <[email protected]> wrote: >> >> >> >> I found that when using this fix I had to set the >> >> DJANGO_SETTINGS_MODULE environment variable in order to use the >> >> manage.py shell. >> >> >> >> On Dec 18, 5:34 am, captainmish <[email protected]> wrote: >> >> > On Nov 23, 12:16 am, "Eric R. Palakovich Carr" <[email protected]> >> >> > wrote: >> >> > >> >> > >> >> > >> >> > > I've been having the same problem and I've found a one-line hack >> that >> >> > > doesn't touch the Satchmo source code. From what I can see, the >> >> > > product.config module isn't being loaded in the same order as when >> you >> >> > > run the development server. In fact, it isn't being loaded at all >> >> > > before the exception is thrown and that is where the product >> settings >> >> > > are loaded. >> >> > >> >> > > So add this to your settings.py >> >> > >> >> > > # HACK: Fixes SettingNotSet CATEOGORY.SLUG exception that occurs on >> >> > > production >> >> > >> >> > > import product.config >> >> > >> >> > > This resolves the issue, but it doesn't solve the root of the bug. >> >> > > I'm new to deploying software using wsgi on Apache, what would be >> the >> >> > > difference in loading modules between django's development server >> and >> >> > > mod_wsgi? >> >> > >> >> > I tried this, but now ./manage.py test fails saying settings.py not >> >> > found (or import error) - I can import product.config from the >> >> > (virtualenv) python shell though! Anyone have any idea what I'm doing >> >> > wrong? >> >> >> >> -- >> >> >> >> 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]<satchmo-users%[email protected]> >> . >> >> For more options, visit this group at >> >> http://groups.google.com/group/satchmo-users?hl=en. >> >> >> >> >> > >> > -- >> > >> > 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]<satchmo-users%[email protected]> >> . >> > For more options, visit this group at >> > http://groups.google.com/group/satchmo-users?hl=en. >> > >> >> >> >> -- >> Franck Bret >> --------------------- >> 06 03 90 65 98 >> Fax : 09 59 95 85 96 >> >> -- >> >> 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]<satchmo-users%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/satchmo-users?hl=en. >> >> >> > -- > 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]<satchmo-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/satchmo-users?hl=en. > -- Bruce Kroeze http://www.ecomsmith.com It's time to hammer your site into shape. -- 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.
