I know that topic is old, but I also find a method for this functionality.
I don't found so I create it by myself.
See this commit:
https://github.com/egorsmkv/simple-django-login-and-register/commit/a8ca21f1a6bb4fa4eacbc4e904d9ce9adebdf576
On Wednesday, 12 January 2011 03:18:09 UTC+2, Micah C
You're welcome. Enjoy!
--
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
Shawn,
Thank you so very much. This is coming along quite nicely. Your answers have
been perfect.
On Wed, Jan 12, 2011 at 9:19 AM, Shawn Milochik wrote:
> Without changing or subclassing the User model (which shouldn't be done,
> because it causes problems), I don't know how you can put the uni
Without changing or subclassing the User model (which shouldn't be done,
because it causes problems), I don't know how you can put the unique e-mail
address constraint on the database, except manually via your database's own
tool. I don't know if that can cause problems with Django's ORM, and it
Ah yes, thanks again.
I tinkered with the django-registration and was a bit more than I need.
While the username can store an email address, it's 30 character limit
prevents me from relying on that. Looking over an existing database I have,
there are quite a few email addresses over that characte
If you're using 1.3, you can make the e-mail address the username, which will
automatically require it to be unique.
I haven't used django-registration, but many others have, so maybe they'll be
able to answer. On face-value, I'd say that your question is a bit off, though;
django-registration
Thanks for the great information. I've tinkered with it and it seems to be
working pretty good. Still need to make the email unique but all in all a
pretty good solution.
What do you think about using django-registration instead? Does anybody know
of a pro/con comparison of the built-in auth versu
Yes, it's very easy to do.
For the e-mail address as the login, all you have to do is create your own auth
backend. That is a LOT simpler than it sounds -- just a few lines of code.
http://docs.djangoproject.com/en/dev/topics/auth/#writing-an-authentication-backend
As for the need to activate t
8 matches
Mail list logo
