mezzanine.pages.fields.MenusField sets its choices and default on the basis of hte PAGE_MENU_TEMPLATES setting (see here:https://github.com/stephenmcd/mezzanine/blob/e2b0aa6d6fbf699f3e1c68a4a522f5abaf40bbb6/mezzanine/pages/fields.py#L14).
This means that if this menu is changed and then the migrations framework is run, an AlterField operation is added. Here's an example of a migration that is added by this change: https://dpaste.de/iiAv To put it another way: If you blank the migrations for the pages app and run them again, you get a different initial migration for the field. Here's the output: https://dpaste.de/GocA Do we want this? Or do we need to figure out how to silence it somehow? -- 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.
