Looks like a migration in your onepage app is referencing the pages.Page table before it's created in the DB. IMO it has something to do with your models and migrations. Can you check if the error happens when running createdb locally in a blank Postgres DB? Might be easier to debug in your dev machine.
Also, are you using sqlite while developing? It is sometimes more forgiving with migration issues than Postgres (at least that's been my experience since Django incorporated migrations in 1.7). My recommendation is to also use Postgres in development to catch these errors early; or use sqlite in production :P -- 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.
