Registration form

no, currently not. However any contributions are welcome!

cool!

I would prefer a separate module, because the nodeprofile module works with every node type and I don't want to loose this abstraction.

A cool way to implement this would be to allow or force users to fill out pageroutes at the registration (or better directly after the registration).

if you want to independend of the CCK, it would be difficult to have per-field granularity. however, you could go for a new boolean formapi parameter 'registration', then your module could get the node form per node_form() and unset all form fields, that don't have the registration value set. still not really beautiful and you will loose all changes that are done by hook_form_alter() on node forms.

So i would suggest to provide this feature by creating

• a cck dependend module that injects the field in the form by hook_user, like yours
• a general module that works with node-forms by providing extra pages => e.g. by using pageroute

So most use-cases should be possible and your module is a fine start for the first method.

To detect, which node types are used as nodeprofile you can use this: (untested)

<code>
$types = node_get_types();
foreach ($types as $type => $type_name) {
  if (is_nodeprofile($type) {
    do_something();
  }
}

However it would be sane to check all types that are in relation with any profiletype (nodefamily-content_type-relations)! Or just check every cck-content-type.. ;)
As you mentioned, a way to check the fields, that should be filled by registration would be fine. E.g. make a checkbox on every CCK field edit page (you can have a look at the fieldgroup module, it also injects an extra field there).

Your form['type'] field could be of type 'value' instead of hidden.

Your rolesignup module sounds really interesting, would be cool to have it in CVS. Then I would suggest to do access checking, if the user is allowed to create a node of the used node-type. Have a look at node_access('create', $node).

cool! I'm really looking forward on your solution!

a short note to your actual code:
You are building the form array out of possible multiple node-forms. Shouldn't you save multiple nodes then?

ah yeah, I overlooked the loop. great!

Hello guys,
Working on a registration form that will create a profilenode as well.
My profilenode cck had fieldgroups enabled and weighted fields within and they somehow get stripped out in the registration form.
I'm pretty much of a newbie to drupal hacking but I'll give it a go...
Will update within the next thread if I learn anything interesting.
Lior

Hi Sym, where is the is_nodeprofile()? I got the following error.

Fatal error: Call to undefined function is_nodeprofile() in /var/www/drupal/modules/registerprofile.module on line 10

Thanks Sym, your registration.module works perfectly! I've installed it on Drupal 4.7.4 along with the following modules: CCK, nodeprofile, node_privacy_byrole, nodefamily and usernode. This lets me in particular use a multiple value select list (via CCK) as one of my user profile fields (which profile.module doesn't allow) and then presents my entire CCK node to the user to fill out during registration - brilliant - and then displays the results when the user clicks on "my account" (via a user_profile.tpl.php) :)

This is a slightly modified version. I added an extra form alter with another form_id. Node forms come with several IDs. with this addition e.g. field-group for CCK fieldsets work too.

Bèr

great work, thanks a lot!