CiviCRM Community Forums (archive)

Hi

I'm working with someone who has a complex membership setup with lots of membership types based on age/location etc.
Currently parents are the primary member and the child inherits the membership from the parent. This is causing lots of problems, especially round renewals, as some parents have 4 children.

The system is setup so the parent has the 'can view and update information for' permission with the child relationship.
We are thinking this might mean the parent can login to Drupal, act as the child and then create the Membership on the child's behalf.

Has anyone tried this? Is it feasible?

Cheers
Olly

Actually the rather more important patch for this purpose is still in progress

http://issues.civicrm.org/jira/browse/CRM-13179

I'm hoping to steal the hours to finish it out of my allocated sleep time tonight as I need to catch up on billing hours today

Hi,

I'm afraid CRM-13179 isn't going to happen.

There is still 2 - 6 hours work to do on it & I'm afraid I'm out of energy and am abandoning it. The part about being able to select that you are registering someone you already have permission to for event & contribution pages will be fairly simple to patch on top of 4.4 & I probably will incorporate that into our deployment in a month or so & potentially look at trying to get it into core for 4.6.

However, the key missing piece is still being able to set up the permissioned relationship so that parents can manage child registrations, a secretary can renew co-worker memberships, or people can generally be able to edit people they created (which is a pretty common request).

This requires a schema change to either the uf_field table or the event & contribution_page table. It works in the patch on the above ticket & it really does make that whole flow work but I feel it maybe should be added to the profile instead. However, that's not code I really want to get involved in as it goes from being a change that is invisible except when deliberately configured on a specific event / contribution page to being something that could 'pop out' in all sorts of places. .

I don't necessarily expect to come back to the relationship side of this because it will be hard to manage as a patch on our fuzion deployment due to the requirement for a schema change and I don't want to do this as an extension as I believe it should be in core. I will probably look at using drupal rules instead.

Sure - our fuzion deployment will be publicly accessible on github - for d6 & d7 definitely.

We have a couple of other long-running fixes that haven't gone into core (timezone handling for civimail, events etc, paypal IPN logging & an api to resubmit them) and will possibly add a few more that build on this patch (allowing autocomplete fields in batches, surveys etc) but we try to keep it free from things that will never be in core.