On Thu, Mar 25, 2010 at 2:48 PM, Jim N <jim.nach...@gmail.com> wrote: > 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
See my response to http://groups.google.com/group/django-users/browse_thread/thread/2af584b66b8a38a3/cad58c52a3990830?show_docid=cad58c52a3990830 Cheers Tom -- 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.
