Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.5.8
-
Fix Version/s: 4.6
-
Component/s: CiviMember
-
Labels:None
-
Documentation Required?:None
Description
I have tested on http://d45.demo.civicrm.org/ and have found there are several issues with cascading membership statuses. Membership statuses on individuals who have inherited a membership from an organization are failing to have their membership status updated after their relationship to their organization is changed, or changes to the organization's status are changed.
To reproduce:
SETUP:
1. Create 2 relationship types (or use existing): "is employer by", "is managed by"
2. Create a parent org (or use the default org)
3. create a new membership type linked to the parent organization with cascading enabled for the "is managed by" relationship
4. create a new organization contact (or use an existing), and create a membership for the organization using your new membership type
TESTS:
1. create a new individual with a relationship to the organization, give it the relationship "is managed by"
Q. Does the new individual receive a membership:
A. FAILED, no membership is created until you manually re-save the membership via the organization
2. change the relationship type on the individual to the relationship type "is employee of" (should not qualify for a membership)
Q. Does the membership get revoked from the individual?
A. FAILED, no membership is revoked until you manually re-save the membership via the organization
3. remove the individual's relationship from the org (is no longer an employee of)
Q. Does the membership get revoked from the individual?
A. FAILED, no membership is revoked until you manually re-save the membership via the organization
4. ensure there is at least one indvidual with an inherited membership from an organization, then remove the membership from the Organization (delete)
Q. Does the membership get revoked from the individual?
A. YES (this is the only test that passed)
5. ensure there is at least one indvidual with an inherited membership from an organization, then delete the organization completely from the system
Q. Does the membership get revoked from the individual?
A. FAILED, membership is not revoked from the individual
In all cases, running the job "Update Membership Statuses" has no effect.
Attachments
Issue Links
- duplicates
-
CRM-9386 Creating relationship via API doesn't create inherited memberships
- To Backport