Thanks.
On Fri, Oct 10, 2008 at 11:37 AM, Carl Meyer <[EMAIL PROTECTED]> wrote:
> RegistrationForm is a normal Form instance. Most errors will be
> attached to specific fields, and thus will be in
> form.field_name.errors, as documented. Errors not associated with any
> particular field are ava
On Oct 10, 7:44 am, "Chris Spencer" <[EMAIL PROTECTED]> wrote:
> That might be the problem then. I dislike the default markup, so I'm
> using my own. How do you find if the form as errors?
> Usinghttp://docs.djangoproject.com/en/dev/topics/forms/as a guide, I've
> tried using form.has_errors, for
That might be the problem then. I dislike the default markup, so I'm
using my own. How do you find if the form as errors? Using
http://docs.djangoproject.com/en/dev/topics/forms/ as a guide, I've
tried using form.has_errors, form.errors and form.message.errors, but
Registration doesn't seem to use
On Oct 8, 11:56 pm, "Chris Spencer" <[EMAIL PROTECTED]> wrote:
> Yeah, this has been a big let down. What I'd hoped would be a few
> minutes setting up a basic site framework has turned into several
> hours wasted on boilerplate. The lack of docs, templates, and strange
> bugs like these leads me
Yeah, this has been a big let down. What I'd hoped would be a few
minutes setting up a basic site framework has turned into several
hours wasted on boilerplate. The lack of docs, templates, and strange
bugs like these leads me to think that django-registration isn't fully
baked. I'm simply writing
Does anyone know of an example for using
django.contrib.auth.views.password_change?
All the docs seem to mention is how to specify it's template. After
poking around in the code, I found it exposes new_password1 and
new_password2 and I setup a basic form. However, it never redirects to
the defaul
6 matches
Mail list logo
