Thanks Tim, Yes, I just saw this. I was subclassing auth.User because I didn't know the right way to do it.
Now I am on the right track. Just one thing I can't figure out. "When a user profile model has been defined and specified in this manner, each User object will have a method -- get_profile() -- which returns the instance of the user profile model associated with that User. [¶] The method get_profile() does not create the profile, if it does not exist." So the profile is the model that I've created to hold the extra stuff about my user, and it's not automatically created. I can't quite picture where or how it would get created. I have a couple of ways to create a user - through my app when someone takes some actions, or through the django admin. If anyone cares to expound, or share some sample code, that would be great. Thanks, Jim On Mar 24, 7:47 pm, Tim Shaffer <timster...@gmail.com> wrote: > I think this could all be simplified a bit if you used a UserProfile > model instead of subclassing auth.User. > > http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-... > > Was there a specific reason you were subclassing auth.User? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
