Just thought I'd add that I went through the exact same thing, spent a couple hours integrating django-registration only to find django- profiles later, gotta say that the little google maps locator in django-profiles is really nifty. I've had to make some modifications to django-profiles to correct what I'd consider deviations from "best- practices", but that may very well be my own bias. Specifically, I added email address collection at registration, auto-login on registration, etc.
On Feb 10, 10:10 am, "Ramdas S" <[EMAIL PROTECTED]> wrote: > James, > > Thanks! I need to learn to ** search better ** :) > > RS > > > > > On Feb 10, 2008 8:18 PM, James Bennett <[EMAIL PROTECTED]> wrote: > > > > On Feb 9, 2008 9:37 AM, Ramdas S <[EMAIL PROTECTED]> wrote: > > > > I am using Django-registration. It works like a charm as far as > > > registering > > > > new users and validating them from potential bots. However, what is > > > the best > > > > practice as far as getting users to feed in more information. > > > > See django-registration's lesser-known companion application: > > > >http://code.google.com/p/django-profiles/ > > > > -- > > > "Bureaucrat Conrad, you are technically correct -- the best kind of > > > correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
