>
> In your case, you could simply copy and refact the form itself, not
> the entire app, and implement that logic in there.... i think if your
> templates dir is before the app's template dir, django would pick up
> your copy, wouldn't it??? Otherwise you could also just hijack the
> signup view to use your form, but then use contrib.auth for everything
> else.
>
This would lead to a lot of hijacking on that template and writing
essentially a whole new view for the new user. Makes sense but seems like
more of a hassle than it is worth.
I understand you hesitance to fork the auth application, but doing so will
save you a lot of work and hacks like above. You would only need to change
one line of code: in django.contrib.auth.models line 134; email =
models.EmailField(_('e-mail address'), blank=True, unique=True). You can
still update the code through subversion. Chances are before newforms admin
merge you won't have any conflicts with this code. When newforms admin
merges you will need to update your code base any way and in that update add
the same unique=True to the User model in the same file.
I too dislike forking django, but when a contrib application doesn't do what
you want it to, there is really no harm in forking it instead of working
some really ugly hacks in the system. In my opinion that extra argument in
the user model is less likely to break than any hack to get around it.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
