Fixed, but not understood...

Another post suggested that the order of the class declaration inside
models.py was important, so I changed mine to reflect that. Order
became Ingredients, BakedGoods, LabelIngredients.

Also based on reading that post, I changed the LabelIngredients class
to:
<code>
        ingredient = models.ForeignKey( Ingredients , blank = True , core =
True )
</code>

Here's the link for core:
http://www.djangoproject.com/documentation/model_api/#core

The relevant section says:
<quote>It is an error to have an inline-editable relation without at
least one core=True field.</quote>

I think mentioning this in the docs for M2M fields would be called for.

If someone can explain why blank = True , core = True isn't a conflict,
that would be appreciated. As would showing me how to collapse the M2Mi
fieldset.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to