Upon registering for an event, a user is not automatically assigned to a group. It should register the accounts created from the commerce order (could be multiple users registered at once) and assign them to the group for which the product is referenced. It should, also potentially assign a group to users who just sign up on the site (not pay and register) in order to allow authenticated users to submit session proposals prior to paying for an event.

I think the route to take would be to add a new rule that would ideally assign an admin-configured group to users who register and sign up on the site. For conferences that are multi-year like Design 4 Drupal Boston, it would mean each year adjusting which event is the "current" event. For users REGISTERING, they would simply be assigned to the group associated with the product purchased.

Are there rules already in place that I'm not seeing? Are there any that are being developed that I can help with?

Comments

japerry’s picture

japerry
Location KOMK
commented
Project: Conference Organizing Distribution » Conference Organizing Distribution Support Modules

Moving to the cod support queue

deanochips’s picture

deanochips commented

here is the rule i used to do it, just change the value to whatever the node id of your event is.

{ "rules_mandatory_group" : {
"LABEL" : "Mandatory Group",
"PLUGIN" : "reaction rule",
"REQUIRES" : [ "rules" ],
"ON" : [ "user_presave" ],
"DO" : [
{ "data_set" : { "data" : [ "account:og-user-node" ], "value" : { "value" : [ "13" ] } } }
]
}
}

aburrows’s picture

aburrows commented

Are we talking abou the /user/register form or the individual og forms?

pcorbett’s picture

pcorbett commented

Individual OG forms? I was specifically speaking to the account that gets created for anonymous users purchasing access to a group. Thinking more globally, it would make sense to have (if not already) an OG-specific signup/registration (/user/register/X) where X = OG Event ID.

japerry’s picture

japerry
Location KOMK
commented
Version: 7.x-1.0-alpha2 » 7.x-1.x-dev
Priority: Normal » Major
Issue summary: View changes
Issue tags: +COD 7.x-1.x Beta 3 Radar

Bumping to latest. We should integrate with the new ticket module.

kclarkson’s picture

kclarkson commented

when a user is created through the user registration form they are not added to the default event.

How to add users to the default group ?
How to add users to non default group ?

japerry’s picture

japerry
Location KOMK
commented

What needs to happen here is some additional rules around the ticket state completed status. When the ticket state is set to complete, we add them to the group.

The group membership is only planned for permissions at the moment. You'd still want to use the user information from the ticket module to generate event attendees. In other words, the OG side of membership should be transparent and automatic. Which means we also need to be able to remove group members as well if we cancel their registration.

kclarkson’s picture

kclarkson commented

@japerry,

that makes sense to me.

So are you saying we need to create 2 rules ?
-OG Assign to Group when ticket is purchased and registered
-Remove Group Membership if ticket is canceled

kclarkson’s picture

kclarkson commented

This brings up another interesting question.

How is a an individual who is submitting the session able to select their session track ?

I know in some cases you don't want the presenters to be able to select they session track but in the case where you do want them to select their "suggested track", they are not added to the default group upon account creation.