Discovered that save_model() is still available even if I don't
inherit admin.ModelAdmin, which avoids the metaclass conflict.

On May 31, 10:36 am, Lee <[email protected]> wrote:
> I'm trying to create a class that inherits from both models.Model and
> admin.ModelAdmin, so that I can use models.ManyToManyField and
> save_model() from admin.ModelAdmin. Unfortunately this combination
> gives "metaclass conflict: the metaclass of a derived class must be a
> (non-strict) subclass of the metaclasses of all its bases". I've
> googled on the error message and tried a couple of the suggestions but
> with no luck. Anyone know the correct way of doing this?
>
> Thanks for any help.
>
> Lee

-- 
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?hl=en.

Reply via email to