| commit | 6313e21b672486082d0c11879826b15b4eb6661e | |
| author | Laszlo Papp <djszapi@archlinux.us> | |
| Sat, 5 Dec 2009 19:30:47 +0000 (5 20:30 +0100) | ||
| committer | Sebastian Nowicki <sebnow@gmail.com> | |
| Sun, 20 Dec 2009 11:28:38 +0000 (20 19:28 +0800) | ||
| tree | 02ded955af7ba8b5e301fc46aad076401a7b8f04 | treesnapshot (tar.gz zip) |
| parent | 12a95f8c92205cbfbc7e4ff80d568e83309455e4 | commitdiff |
Fix login error message
The issue was that no error appeared after trying to log in with an
invalid username or password, just the prompt was got back. This is
because the "has_errors" form attribute was renamed to "errors" in
Django 1.0.
Changing form.has_errors to form.error in the login template solved the
problem
Signed-off-by: Laszlo Papp <djszapi@archlinux.us>
Signed-off-by: Sebastian Nowicki <sebnow@gmail.com>
The issue was that no error appeared after trying to log in with an
invalid username or password, just the prompt was got back. This is
because the "has_errors" form attribute was renamed to "errors" in
Django 1.0.
Changing form.has_errors to form.error in the login template solved the
problem
Signed-off-by: Laszlo Papp <djszapi@archlinux.us>
Signed-off-by: Sebastian Nowicki <sebnow@gmail.com>
| archlinux/templates/registration/login.html | diffblobblamehistory |