CiviCRM Community Forums (archive)

We have a membership based organization that allows a single membership price for all members of that household. 

We would like to create a CiviMember membership for a household and collect the names and email addresses of all members of that household at the time the membership is created.

Further, ideally each of the household members should then be contacts and take the role current member, like any other individual member contact.  Membership status for the entire household would then be controlled by the settings in the Household Membership, and expire when that membership expires.

I can see how to do this by hand, but is there a way to collect this information and update it at the time the membership is created or renewed?

We set up a Household Membership called Household and set the relationship as Household Member is.  I see there is a Reserved Profile, New Household and have tried adding custom fields to that Profile.  For example, Household Member 1, Household Member 2… 

The trouble is that the Profile - New Household does not seem to be used to create my household membership. 

In the end, it would be wonderful if I could have someone sign up for a household membership and they would be presented with a way to enter the names and email addresses for each family member, and then for each of the family members to added as contacts and marked as the Role Members so that they could take advantage of Member ACL stuff.

It seems to me that there must be a way to do this, but it escapes me presently and I would appreciate any guidance you experienced guys might be able to offer.

Thank you!

I'm pretty sure the only out of the box solution currently for this is using Webform-CiviCRM (Drupal sites only). Beyond that, you'd need to build an extension which modifies the default signup form to inject fields to collect the household members and modifies the post-processing to create the contact and inherited membership records.

There is an extension which does something a bit similar for event registration. Reviewing that code MIGHT be helpful.
http://www.google.com/url?q=http%3A%2F%2Fcivicrm.org%2Fblogs%2Fsarahgladstone%2Fpogstone-releases-extension-parents-registering-children-events&sa=D&sntz=1&usg=AFQjCNHbi7iwMz6ShxkcXdZZnzkvtK4oqg

yes.

but most public forms will only create an individual (since an actual person fills them out, not a household or org).

I would collect all individual info in the front end and link them via relationships in the backend. But we dont what you are trying to do, so this may or may not be useful to you

lobo

Yes, from that perspective the online forms are a bit limited and needs to be generalized going forward. As mentioned in IRC, there is a solution, i.e. webform_civicrm if you are using Drupal.

Would be good to extend and generalize what we can do. However there is a time / resource issue. If your org can help contribute code and/or sponsor this fairly large project (200-400 hours?) that would be super

lobo

This is not directly related but can be used as a potential starting point for other folks who might want to address this issue:

http://civicrm.org/blogs/sarahgladstone/pogstone-releases-extension-parents-registering-children-events

lobo

hey lolas:

any chance u'll can package this as a civicrm extension? might help a few other folks out there

thanx

lobo

I hope I get a chance to package it as an extension. I do have a small amount of time next week that could possibly be allocated that way.

I didn't get a chance to look into whether the new civicrm_webform could have done this. Possibly it could have done a lot of it for us.

Actually I just cleaned up the module, made a few changes and added more notifications to it. It was written more than a year ago so at that time civicrm_webform didn't have that ability.

this suggestion won't scratch all the itches for non drupal sites but would another way to approach it be to have the 'on behalf of' approach reworked so it could also work for HouseHolds?

At least you would get membership created for HH and one contact created and related to it