Did you try what I suggested for :
https://groups.google.com/forum/#!topic/mezzanine-users/CBqb6srpmqU ?
The issue seems the same: using a relationship field with a string
parameter in the EXTRA_MODEL_FIELDS both relies on the class_prepared
signal. Re-raising it should help.
Le vendredi 20 m
Looking deeper, Mezzanine seems to be simply looking for the field type,
then passing the arguments into the Django method contribute_to_class for
the sender model. (See
http://blog.jupo.org/2011/11/10/django-model-field-injection/). I'm going
to pursue this further, but it looks like Django it
I'm seeing the same thing, trying to ad a ManyToManyField to all pages.
>From my settings.py:
EXTRA_MODEL_FIELDS = (
(
"mezzanine.pages.models.Page.blog_categories", #let blog posts be
displayed below content on pages
"ManyToManyField",
("blog.BlogCategory",),
Hi everyone,
I'm getting the same error exactly while running the schemamigration
command:
TypeError: 'NoneType' object has no attribute '__getitem__'
In my case the model is cartridge.shop.models.Product but the situation is
really really close:
EXTRA_MODEL_FIELDS = (
# Four-item seque
Make sure you run a south schemamigration on the blog app itself:
Something like:
manage.py schemamigration blog --auto
On Tuesday, July 29, 2014 10:14:18 AM UTC-4, Beau Severson wrote:
>
> I was also wondering the answer to this. I'm trying to add a new M2M field
> to the BlogPost model and
I was also wondering the answer to this. I'm trying to add a new M2M field
to the BlogPost model and I keep getting the exact same error. Is this a
bug for mezzanine using south? My EXTRA_MODEL_FIELDS contains the following:
(
"mezzanine.blog.models.BlogPost.industry",
"ManyT
