#11406: Admin broken for subclasses of User
-------------------------------------------+--------------------------------
Reporter: garrison | Owner: nobody
Status: closed | Milestone:
Component: django.contrib.admin | Version: 1.0
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm pretty sure the issues that you've raised can be overcome - it's just
a matter of writing the right code for UserAdmin. #9656 contains a fully
worked example of how to get this to work; consult django-users for more
assistance.
However, there's a larger issue here: people want to use different User
models, both in admin and in their own code. We need a way to make this
easier. I'm going to close this as a dupe of #3011, since that is the
ticket for tracking custom User models.
--
Ticket URL: <http://code.djangoproject.com/ticket/11406#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
