We just fixed a similar issue in Mezzanine by moving the variable from the model onto the form field class:
https://github.com/stephenmcd/mezzanine/commit/67c7c67df7053b846fed36da4448e385af3a746e I've opened an issue on Cartridge to track doing something similar: https://github.com/stephenmcd/cartridge/issues/271 I suspect in Cartridge we'll need to set it on the order explicitly when it gets created, rather than changing a form field. First person to implement the fix gets a free copy of Cartridge or Mezzanine (not both, sorry). On Wed, Nov 4, 2015 at 5:07 PM, Chris Trengove <[email protected]> wrote: > In Cartridge's Order model, the status field has its choices set to the > value of SHOP_ORDER_STATUS_CHOICES, which is available for customization in > the project settings.py module. But with the new Django migrations, editing > this setting triggers a migration, which of course is then stored in > Cartridge's migrations directory. > > Does anyone have any suggestions as to how this might be avoided? > > -- > 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. > -- Stephen McDonald http://jupo.org -- 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.
