Front end validation doesn't always work like it is supposed to so you
shouldn't really rely on it.
On Mon, Aug 1, 2011 at 6:09 AM, lokesh wrote:
> hi,
> i think Best way is front end validation. instead of modifying auth
> models.
> lokesh s
>
>
>
> On Aug 1, 12:43 pm, bruno desthuilliers
> w
Awesome, that's the way I'm going about it. Thanks for the responses.
-James
On Mon, Aug 1, 2011 at 5:09 AM, lokesh wrote:
> hi,
> i think Best way is front end validation. instead of modifying auth
> models.
> lokesh s
>
>
>
> On Aug 1, 12:43 pm, bruno desthuilliers
> wrote:
> > On Aug 1, 7:
hi,
i think Best way is front end validation. instead of modifying auth
models.
lokesh s
On Aug 1, 12:43 pm, bruno desthuilliers
wrote:
> On Aug 1, 7:28 am, James DeMichele wrote:
>
> > Hello,
>
> > I have a question about tweaking the django.contrib.auth.models.User class.
> > I noticed tha
On Aug 1, 7:28 am, James DeMichele wrote:
> Hello,
>
> I have a question about tweaking the django.contrib.auth.models.User class.
> I noticed that Django doesn't allow for overriding of attributes of "Field"
> instances, such as "email" or "first name". Yet, I'd like to my email and
> first name
4 matches
Mail list logo