Re: [mezzanine-users] Re: EXTRA_MODELS_FIELDS broken with Django 1.8 ?

2016-01-26 Thread Stephen McDonald
On Tue, Jan 26, 2016 at 8:32 PM, xBlake wrote: > Thanks ! > > Is somebody already working on the fix ? > I can attempt to investigate the guts, but not sooner then in the next > week. But won't like waste my time if already done by other person. > According to the issue Ed linked to, no one has

Re: [mezzanine-users] Re: EXTRA_MODELS_FIELDS broken with Django 1.8 ?

2016-01-26 Thread xBlake
Thanks ! Is somebody already working on the fix ? I can attempt to investigate the guts, but not sooner then in the next week. But won't like waste my time if already done by other person. Btw. unsetting *EXTRA_MODELS_FIELDS* not only allows migrations to proceed, but also allows run of apps ba

Re: [mezzanine-users] Re: EXTRA_MODELS_FIELDS broken with Django 1.8 ?

2016-01-25 Thread Eduardo Rivas
That's a post about upgrading to Mezzanine 4.0. The issue described in the original message is new and started with the recent release of Mezzanine 4.1. You can follow the progress here: https://github.com/stephenmcd/mezzanine/issues/1513 -- You received this message because you are subscribed to

[mezzanine-users] Re: EXTRA_MODELS_FIELDS broken with Django 1.8 ?

2016-01-25 Thread Salar Rahmanian
This post covers it: http://bitofpixels.com/blog/upgrading-to-mezzanine-4/ On Monday, January 25, 2016 at 3:03:51 PM UTC-5, xBlake wrote: > > Hi, > > after an upgrade to Cartridge 0.11.0, Mezzanine 4.1.0 and Django 1.8.8 to > an existing project, migrations have stopped working. > I'm getting fo