I have created two roles and a content type for each role, for use with the content_profile module. When users register themselves, everything works fine. But when the admin user creates other users at /admin/user/user/create, there is no easy way to control the following at user creation:
1) which profile fields are presented
2) which profile nodes get created
I created a little custom module that removes all of the profile fields from the user creation form, but nodes for both roles get created anyway.
We probably need to think through the best way to control this, so I'll start off with a few thoughts.
1) Default to showing no profile fields. (but add a configurable setting about whether to show or hide them by default.)
2) When showing profile fields, observe the "Hide these fields during registration" settings that are on the content type config page.
3) When selecting roles for a user, dynamically reveal the relevant profile forms as needed.
OK, that's a starting point. Any other thoughts?
Does this issue belong in content_profile instead of here?
Comments
Comment #1
bcn commentedFirst off, that's a good explanation of a use case that I think is quite typical. I'm feeling though that points you've outlined are more a content_pofile_registration issue than here. It's up to you, or the AAR maintainer to decide what queue it should belong in...
That said, I definitely agree that it would be perfect from a UX point of view to have the various content_profile fields be exposed by the action of clicking a particular role.
You might be interested in this http://drupal.org/node/301464
Comment #2
cyberswat commentedDuplicate of #369359: Disable AAR on Admin Add User page