Sounds like a python path issue. You'll see at the top of settings.py in latest Mezzanine, for consistency with Python 3.3:
from __future__ import absolute_import ... which answers the questions as to what's changed. You probably need to add to sys.path somewhere or other in order to satisfy uwsgi - good luck. On Fri, Jan 3, 2014 at 10:36 AM, Tim Walzer <trwal...@gmail.com> wrote: > I ran into a strange problem today when setting up a new project. > > I'm setting up a new project with Mezzanine 3.0.4, Cartridge 0.9.1 and > Django 1.6.1. I am setting up the website on a Nginx -> Uwsgi stack on AWS. > > The project was created using '*mezzanine-project -a cartridge > project_name'* > Now the problem is that when I try to load the site the local_settings are > not imported from settings.py, so the site crashes when trying make sure > that SECRET_KEY is set. When I move SECRET_KEY in to settings.py it then > crashes on the DATABASES info. > > Now the stranger part is that when I run management commands like '*python > manage.py createdb'* then local_settings is imported properly and the > data in local_settings is used. > > This is the 3rd Mezzanine/Cartridge site that I've setup on this > server/stack and the other 2 had no problem. So what could be causing this > behavior? > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mezzanine-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
