Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Use django-registration, not a local copy. | Wookey | 2015-06-10 | 1 | -133/+0 |
| | | | | This old one is uses deprecated hashcompat. | ||||
* | 3rd attempt at getting the right syntax for the CSRF protection in | Wookey | 2013-07-02 | 1 | -1/+1 |
| | |||||
* | Add CSRF protection to registration form (and remove annoying second | Wookey | 2013-07-02 | 1 | -8/+5 |
| | | | | password) | ||||
* | [svn] A few registration updates | pjrharley | 2009-05-30 | 1 | -0/+2 |
| | | | | | | -display an error for nonmatching passwords -display an error for short passwords -dont direct people to http://http://sitename.... | ||||
* | [svn] Add user registration and user profiles. | substantialnoninfringinguser | 2009-05-13 | 1 | -0/+134 |
Used modified versions of django-registration and django-profiles , both on bitbucket. The Person model is now set up as the profile for auth.User s. I set up a requestcontext so that settings is automatically passed to every template, no need to repeat ourselves in views. However, this needs to be refined: I will soon change it to only pass a subset of settings. E.G. we do not need to be passing the DB login and password! Copied from http://cucc@cucc.survex.com/svn/trunk/expoweb/troggle/, rev. 8231 by aaron @ 1/29/2009 11:02 PM |