> But if you use the user-profile approach, how do you create a single
> form for entering user data and profile data, and how do you process
> this form data in a view, including user creation, without handling
> each field separately, which is not in the Django (DRY) spirit?
You can display two
But if you use the user-profile approach, how do you create a single
form for entering user data and profile data, and how do you process
this form data in a view, including user creation, without handling
each field separately, which is not in the Django (DRY) spirit?
Rodney
On Sep 16, 4:03 am,
I guess if you subclassed the User model, you'd have to change all
places that use it to use YourUserModel instead, otherwise there's no
point (someone correct me if I'm wrong). So I'd stick with the user-
profile approach.
Erik
On 15.09.2008, at 17:33, Brot wrote:
>
> Hello,
>
> what is y
Hello,
what is your preferred way for additional information for the user
modell?
Do you still use the User-Profile or do you subclass the auth.user
model?
What are the pros and cons?
~Bernd
--~--~-~--~~~---~--~~
You received this message because you are subscribe
4 matches
Mail list logo
