Inherited membership bug in 3.0?

[petednz]

I am not totally sure but believe we had this working in 2.2.x - i will go double check but

On DEMO site I have done the following

- created a membership type with 'inherited membership' for 'employer of' ("PD test Org inherit" if it is still there when anyone checks)

- created a membership page "pd test" http://drupal.demo.civicrm.org/civicrm/admin/contribute?reset=1&action=update&id=5 which requires 'sign up on behalf of'

Now when someone fills in the form, they get the relationship, and the Organisation gets the membership BUT the contact does not get the membership.

Any reason why this is not a bug?

[petednz]

Just tested in Sandbox and not working their either 

(and yes I am verifying that it is not related to the 'pending' process both by 'update pending' and also by doing a free membership)

now to find a 2.2.x to verify this was working somewhere.

[petednz]

And just to confirm that the process of inherited membership IS working for adding contacts back end - it is the process of people joining online which is failing as far as i can tell.

[petednz]

Hmm - so just tested on a 2.2.9 and while the inherited membership is working at the back end, it also doesn't work via the Contribution Page.

Has this always been known or is this something that slipped through the net?

[Eileen]

OK,

So this is a permissions issue.

We are looking at a situation where an anonymous user creates a drupal account and fills in a CiviCRM form as part of the account creation process. On the CiviCRM they fill in their current employer and if their current employer has a membership they inherit it.

Unfortunately this only works when anonymous user has drupal permission to access CiviMember. Otherwise the inherited membership is not created. But if we give this access to anonymous user it exposes other pages to anonymous users.

In the particular use case we have they are using drupal to require an administrative approval so the work around is that when the administrator approves them they disable & enable the relationship but it's a bit unwieldly.

It would seem ideal would be to have a separate acl for adding yourself to an existing membership vs seeing all the civimember financials

[petednz]

Just to add to this - Eileen has pointed out to me that using the inherited membership without some 'approval' process creates a risk since someone could potentially look at a directory of members (if one is published) sign up as am 'employee of' the company and get the membership - and any permissions that might roll from that in terms of Drupal Roles.

Long term we may need to think about having a 'membership approved' checkbox for back end?? and a UI that lets the Contribution Page be set up to require approval of the membership.

[Kiran Jagtap]

I suspect this feature was broken due to wrong variable reference.

code will be part of next release ( v3.0.4, v3.1.beta2 ) both.

would be great if you take a look for patch  and let us know is it working for you.

thanks

kiran

[Eileen]

Sorry it has taken so long to get back to this but I just tested and in the following case:

-Individual signs up for membership on behalf of an org
-Anonymous user does NOT have access civimember
-Pay later

A pending membership is created for the org but not the individual
The correct relationship is created

When the contribution is confirmed the membership for the individual is not created.

This doesn't appear to be fixed

[Eileen]

Hang fire on that - will just test again

[Eileen]

Works just fine!