I've upgraded Mezzanine. New errors. Trying to fix them first. Thanks. On Thursday, January 28, 2016 at 12:01:36 PM UTC+3, George M wrote: > > Hi Eduardo, > Methinks you're right. > The problem seems to be that pages_page has an unapplied migration which > also isnt working. I've been using mysql locally. > I've switched to postgresql and this is my new error. > Creating tables... > Creating table pages_page > Creating table pages_richtextpage > Creating table pages_link > Running deferred SQL... > Traceback (most recent call last): > File "manage.py", line 14, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", > line 338, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", > line 330, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", > line 390, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", > line 441, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python2.7/dist-packages/mezzanine/core/management/commands/createdb.py", > > line 60, in handle > interactive=self.interactive) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", > line 120, in call_command > return command.execute(*args, **defaults) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", > line 441, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", > > line 179, in handle > created_models = self.sync_apps(connection, > executor.loader.unmigrated_apps) > File > "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", > > line 317, in sync_apps > cursor.execute(statement) > File > "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line > 79, in execute > return super(CursorDebugWrapper, self).execute(sql, params) > File > "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line > 64, in execute > return self.cursor.execute(sql, params) > File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line > 97, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File > "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line > 62, in execute > return self.cursor.execute(sql) > django.db.utils.ProgrammingError: relation "django_site" does not exist > > Is it a problem with my mezzanine installation? From here > https://github.com/django/django-contrib-comments/issues/30 > > On Wednesday, January 27, 2016 at 7:12:21 PM UTC+3, Eduardo Rivas wrote: >> >> Never mind, I think the problem is that you're not using migrations with >> your onepage app. I believe that any app that depends on another app >> that uses migrations (like mezzanine.pages) must also use migrations >> itself. >> >
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
