FYI : here is the code for doing the registration process, with confirmation email. http://peyman-django.blogspot.com/2010/03/full-easy-authentication-using.html
On Mar 20, 12:55 pm, Peyman <[email protected]> wrote: > Thank you for your reply. > After having a look at its code, it seems that django-registration > provides the signup feature, and uses contrib.auth for the rest. > > I looked at the source code of the djangoproject.com site itself (for > me, should use the best practices), and what a surprise : django- > registration is the app used for registration. > So, I just do not know what to think : why the django developers do > not add the signup feature to contrib.auth? It is just a few lines of > code, since it would need the same toolkit required by password_reset > to generate and check a unique link sent to the user. > > Perhaps this has already been discussed, or perhaps it is planed. (*) > > -- Peyman > > * : just wondering, do Django developers read these posts or it there > any other way to share with them? > > On Mar 19, 8:52 pm, Bjunix <[email protected]> wrote: > > > > > I would strongly suggest to go with contrib.auth as quite a lot in the > > django universe revolves arround it. > > > Remember you can also write your own login/logout/... views but still > > using contrib.auth's models, forms and other utils. > > > You may also want to have a look at > > django-registration:http://bitbucket.org/ubernostrum/django-registration/ > > > On Mar 19, 5:09 am, Peyman <[email protected]> wrote: > > > > > - in contrib.auth.views, the login sends no error for authentication > > > > failures, and sends the page again silently. > > > > My mistake: the form.errors contains the authentication error. > > > > On Mar 19, 1:46 pm, Peyman <[email protected]> wrote: > > > > > Hi all, > > > > > I need an authentication system for my website; quite a common need > > > > today, isn't it? > > > > I have decided to figure out if I can use django.contrib.auth. I > > > > have the following problems : > > > > > 1. start a new project, and just do the minimum: > > > > *in settings: > > > > - a database > > > > - a template path > > > > - the django.contrib.admin app > > > > *then syncdb > > > > *in urls: uncomment the admin urls > > > > *add in your template folder, the file requested by the view > > > > password_change in contrib.auth.views : > > > > - registration/password_change_form.html > > > > - this file contains a simple text > > > > > Problem : trying to access http://<your.site>/admin/password_change > > > > will render -- after login -- your template in registration/ > > > > password_change_form.html instead of the admin one. I can't find out > > > > why. > > > > > 2. strange things in code : > > > > - in contrib.auth there is a UserCreationForm provided, but there > > > > seems to be no view for it or for any signup page. > > > > - in contrib.auth.views, the login sends no error for authentication > > > > failures, and sends the page again silently. > > > > > I hope I am wrong in all this, due to the fact that I am a new django > > > > user. Your help is welcome. > > > > Also : instead of contrib.auth, what is generally used for > > > > authenticating users? > > > > > Thanks > > > > -- Peyman -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
