Hi Paul, Mezzanine fetches the default profile form via the default value of ACCOUNTS_PROFILE_FORM_CLASS, so if you're seeing a form, it means loading a form via that setting is working.
I would run with a debugger and insert a breakpoint where the form class is fetched in accounts/views.py, here: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/accounts/views.py#L123 Have a look at what class you get back from get_profile_form(), and have a look at the value of settings.ACCOUNTS_PROFILE_FORM_CLASS at that point. Do they correspond? Cheers, Alex On Tue, Dec 9, 2014 at 5:47 PM, paul thomas <[email protected]> wrote: > I doesn’t seem to matter if I set this correctly or incorrectly there is > no effect as far as I can see, it goes straight through. > ACCOUNTS_APPROVAL_REQUIRED does have an effect, AUTH_USER_MODEL does have > an effect. > > > I'm trying to extend the clean method to put verification for captcha. > > It is not a question the class, becuase it doesn’t matter if the class is > there or not there is no error, it appears not to override. > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
