i thought of something along those lines. that's exactly the kind of
thing that i was originally searching for -- a way to do it without
cluttering things up and without building a bunch of unnecessary
infrastructure or hacking core django code.
unfortunately, when you do those nice reset emails,
thanks again. writing that login view is what i meant by re-
implementing the login. my terminology is probably confusing. there is
a generic login view in django.contrib.auth.views that does what you
are saying, only [obviously] without the custom redirect logic that i
want. i just copied and pas
thanks for your reply, shawn. that's a good idea, and i already have a
one-to-one table inherited from User where i can stash the initial
encrypted password. the only thing i don't like about doing it this
way is that i am currently trying to use as much generic, built-in
django as i can and that
i am working on a project where i need to create a number of users
(standard django User objects who will login to the site using the
vanilla django auth framework) along with random passwords (rather
than allowing the users to sign up and supply their own passwords).
after the site launches, staf
4 matches
Mail list logo