Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.2.6
-
Fix Version/s: 4.2.8
-
Component/s: None
-
Labels:
Description
After batch processing memberships and then running the membership status processor, the status override setting is removed from the batch processed memberships.
This happens consistently for all memberships on our 4.2.6 install. I have also recreated the problem on the demo site by:
- Setting membership status to override and e.g. Deceased
- Creating a profile for search views and add any membership field
- Run a batch update on the memberships
- Run the membership status processor in the scheduled jobs
This results in all the newly set status overrides to disappear. Those that were set prior to my interventions remains in place.