Yes you were dead on, I just deleted the migrations and it worked fine. On Thursday, November 19, 2015 at 4:37:15 PM UTC-5, Eduardo Rivas wrote: > > It looks like you have a migration file inside Mezzanine's source code. If > you see the name of the migration that raises the exception, it's > blog.0007_auto_20151119 (meaning it was created on November 19, 2015, by > your injected field I presume). Remove that file and the associated .pyc > file and Mezzanine should go back to normal. > > Now, regarding field injection in Mezzanine 4, it's not as simple as it > was in the Mezzanine 3 days. There are essentially two ways of doing it: > One is explained by the official docs > <http://mezzanine.readthedocs.org/en/latest/model-customization.html#field-injection-caveats>, > > and the other is a method developed by Josh Cartmell > <http://bitofpixels.com/blog/upgrading-to-mezzanine-4/> (look for the > field injection section in that article). I use the first one, as it is > less brittle and somewhat supported by Django itself. It is not as elegant > though, and will require you to manually maintain the migration history of > all models with injected fields and any model that inherits from them. > > Both methods have the same goal: to make sure that the migrations for your > injected fields exist in your project, not in Mezzanine's source. Doing > otherwise is a nightmare for collaborating with other devs and deploying. >
-- 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.
