> which to my understanding is saying that migration 0033 is looking for content within migration 0032, which it can't find.
yes, check that you committed the file, I've had this kind of error too many times just because after creating the migration I forgot to git add If you removed your migration files you may try to recover them from your version control. Alternatively ou may create an initial migration file that reflects the current state of your production DB and fake apply the migrations On Wed, Jan 4, 2017 at 4:57 PM, Richard Jackson <rjackso...@gmail.com> wrote: > > Hi there - I'm incredibly inexperienced and using a Mezzanine-powered > site, but this should still be an issue with my lack of Django > understanding: > > My site <http://richardjacksonmusic.com/> is currently down ("Internal > Server Error") due to mishandled migrations. When I try to deploy the code > to WebFaction I get the error message: > > django.db.migrations.graph.NodeNotFoundError: Migration > vital_theme.0033_auto_20161220_1741 dependencies reference nonexistent > parent node (u'vital_theme', u'0032_sitewidecontent') > > ...which to my understanding is saying that migration 0033 is looking for > content within migration 0032, which it can't find. > > I think I've caused issues by messing up the migrations files (even > locally removing all files in the migrations folder aside from __init__.py > and making fresh migrations locally) and pushing up local databases which > aren't matching what the uploaded code wants to see. Essentially I think > I've messed up a lot and am not sure how to unmess this up. > > The site is working locally with a suitable version of the database, with > one single, fresh, 0001_initial migration file. > > Please let me know the best course of action; I was expecting to be able > to deploy the files and for the migration files to be overwritten but this > hasn't been the case. > > Thanks, > > Rich > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/1da1bf5d-656e-4ca9-a2a4-6ce462f89451%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/1da1bf5d-656e-4ca9-a2a4-6ce462f89451%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6tLOwXQpx_h91x-HgRC9QyQtHvs-Ei0QNcw_H95i6MEfcA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
