You can't do it in admin site without tinkering.
If you create users inside a view (i.e. during the registration
process), there is no need to use signals - you can simply create a
profile with data from registration form.
If you use django forms, use them with prefix kwarg, this will allow to
In all the examples I've seen of creating the user profile at the time
a User is created, I always see the use of the signal and the profile
table's fields (except for user) have to be nullable. I don't see a
way to break in to the creation process using the signal scheme such
that you can pass in
Without having to use django-registration or django-profile, I've
discovered that it's easy enough to seamlessly concatenate a user form
and a profile form for data entry, then to create a separateuser
object and profile object from the same resulting request.POST, then
connect and save the object
On szept. 10, 06:51, Rodney Topor wrote:
> Suppose one wants to store additional information about a user in a
> separate profile class as described in the documentation. When a user
> registers, the form displayed should show (all) fields from class User
> and (some) fields from class Profile.
Suppose one wants to store additional information about a user in a
separate profile class as described in the documentation. When a user
registers, the form displayed should show (all) fields from class User
and (some) fields from class Profile.
What is the best way to define this form?
What i
5 matches
Mail list logo
