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
simply divide request to User and Profile fields.
https://docs.djangoproject.com/en/dev/ref/forms/api/#prefixes-for-forms
zalun
On 12/15/11 22:46, bazaarsoft wrote:
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 valid data for initial creation. I have all the
form elements for both the User object an my profile object - I just
can't get them to my version of the create_profile method.
Is this correct - a user profile can't have any required fields
(required in the model) except user because the only way to create it
is through the signal?
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
