Hi all, The link below gave the answer. The difference was that I initially subclassed User .. I went with an extra table with 1-to-1 relation instead as the example stated
Trick under admin is to subclass UserAdmin and re-register the User thingy. Works like a charm! Hope this helps, if you dig up the same issue :) Regards, Gerard. Gerard wrote: > Found a solution that's getting me closer to my goal > > http://www.thenestedfloat.com/articles/displaying-custom-user-profile-fields-in-djangos-admin > > Regards, > > Gerard. > > Gerard wrote: >> Hi all, >> >> I've subclassed Django's User object (also accessible under Admin) to extend >> the user profile. But the 'CustomUser' model ends up in the Myapp list >> instead of under Auth. I need it 'top level' otherwise I and up with users >> for every seperate module/app in my project. Would this be possible? >> >> And when using the admins passwd change dialog "change password form." it >> returns an error: >> >> Warning at /admin/myapp/userprofile/4/password/ >> >> Truncated incorrect DOUBLE value: '4/password' >> >> Anybody seen this before? >> >> >> Thanx a lot. >> >> Regards, >> >> Gerard. >> >> >> Reference: >> http://scottbarnham.com/blog/2008/08/21/extending-the-django-user-model-with-inheritance/ >> >> > > -- self.url = www.gerardjp.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
