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]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
