Instead of using get or create, why not setting up a post_save signal for the User model so that users always have a profile associated with them?
Cheers, Andre On 7/12/11, Brent <brentba...@gmail.com> wrote: > Thanks for the help guys. > > Micky, that tutorial looks very good. I think I almost have it > working. Just one more error: > > http://dpaste.com/567361/ > > Andre, thanks for mentioning Pinax. I'll give it a shot if this > doesn't work out. I have a year of python experience, but I haven't > written anything web/database related. > > On Jul 12, 11:34 am, Micky Hulse <rgmi...@gmail.com> wrote: >> This tutorial helped me: >> >> http://www.turnkeylinux.org/blog/django-profile >> >> Note: The above tutorial uses an FK to User model... The Django docs >> suggest a OneToOne field. >> >> Hope that helps. >> >> Micky > > -- > 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. > > -- Sent from my mobile device -- 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.
