Thanks for your help. Perhaps I should have been more clear and included more information, because that is exactly what I was asking about. I was hoping that someone had already solved this problem and could fill me in on how they got it working. Btw, my first post was written in pieces while distracted and working entirely from memory, so please forgive me for any nonsensical or incorrect statements. I don't have an excuse today though :P
This is what I eventually did: When I first tried to override the fieldsets I recieved an error telling me that my custom fields could not be found. This happened because the UserAdmin class also specifies custom forms for editing (as well as adding), which are bound to the User model. I subclassed the user form classes in order to override the meta class and tell them to use my custom model instead of the User model (and also add in some extra fields on my custom model). I could have just used model forms, but I decided to subclass the user forms for two reasons: 1) it won't feel like I am "short-circuiting" any framework code and if changes/enhancements are made to the user form classes I can also take advantage of them (or they may break me, but thats another story) and 2) the add form includes extra logic that I didn't want to duplicate. This got me what I wanted, an edit form with all of my custom fields as well as a working change password form. I noticed that the add form didn't work though. It only included the username and password (with confirmation), so I added my fields to the form class and copied the admin create user form (/auth/user/add_form.html) into my project directory and added my custom fields. I'm not entirely happy about having to do that. It seems like little thought has been put into custom user models in regards to the admin site. Ideally all that I would have to do is inherit from UserAdmin and override the fieldsets, but maybe I'm asking too much. On Aug 28, 3:23 pm, Karen Tracey <[email protected]> wrote: > On Fri, Aug 28, 2009 at 10:20 AM, Bryan <[email protected]> wrote: > > > So, my "solution" was to duplicate this logic in my admin class, and > > it works just fine now. Anyone have any better ideas? > > Base your admin class on the UserAdmin class. Inherit whatever you need from > it and override whatever you want to customize yourself. > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
