creation of organic groups

I've just started playing with Rules and yes, you can configure Rules to create a node of specified type when a user registers, but at the moment I can't see how to populate the node body (you can populate the node title) nor how to drag in info from the user profile (tho' you have access to username and uid etc.). You can also populate CCK fields.

Rules looks very powerful so it certainly *should* be able to do the sort of thing you are after but whether your specific requirements have been coded up yet is another question. Good luck!!

Might be worth asking in the Rules "group" ... see the bottom of the main Rules project page, under "Useful links".

you already have actions to create a node, and then to set group settings on that node. I don't know about "profile promotion" event.

@2: you can probably access user profile fields by using the PHP evaluation box (you may need to activate PHP module first). $account->profile_fieldname will probably return the value of the relevant field, so if there was a way to populate the node body (which I've not found yet, but may well be there!!) you could set its value something like

print 'This group has been created by ' . check_plain($account->profile_fullname) . ' who lives at ' . check_plain($account->address);

where fullname and address are the 2 profile fields you have set up. http://api.drupal.org/api/function/check_plain/6 prevents cross-site scripting attacks via the user input.

A completely different approach might be to use ? content profile module which makes users into nodes IIRC, and set the relevant content type to be a group node. This would avoid having the group info duplicated in the user's profile.

Aha, found it, you would need to use the Action "Execute custom PHP code" (make sure PHP module is enabled). This lets you modify the $node_added that was created in an earlier step directly, e.g.

$node_added->body = 'This group has been created by ' . check_plain($account->profile_fullname) . ' who lives at ' . check_plain($account->address);
return array("node_added" => $node_added);

Once there is an action to populate the node body directly, and once tokens for user profile fields are available, you wouldn't need to do it this way.

Looks fixed to me.

Updated component.