CiviCRM Community Forums (archive)

Per the request of a client, I wanted a way to bulk update member statuses (for the purpose of setting a large group as inactive).  Updating membership fields in a batch process is done through profiles.  The problem is, without touching the core code, the only membership fields that are exposed in profiles are member id and source.

Allowing for batch updating required editing 3 core files:

--- sites/all/modules/civicrm/CRM/UF/Form/Field.php   (revision 8059)
+++ sites/all/modules/civicrm/CRM/UF/Form/Field.php   (working copy)
@@ -333,7 +333,7 @@
             unset( $membershipFields['membership_end_date'] );
             unset( $membershipFields['member_is_test'] );
             unset( $membershipFields['is_override'] );
-            unset( $membershipFields['status_id'] );
+            //unset( $membershipFields['status_id'] );
             unset( $membershipFields['member_is_pay_later'] );
             $fields['Membership'] =& $membershipFields;
         }

EXPLANATION: Commenting out this unset above allowed for the "status_id" field to be selectable in a membership profile.

--- sites/all/modules/civicrm/CRM/Core/BAO/UFGroup.php   (revision 8059)
+++ sites/all/modules/civicrm/CRM/Core/BAO/UFGroup.php   (working copy)
@@ -1402,7 +1402,7 @@
                        array(''=>ts( '- select -' )) + CRM_Member_PseudoConstant::membershipType( ), $required );           
         } else if ($field['name'] == 'status_id' ) {
             require_once 'CRM/Member/PseudoConstant.php';
-            $form->add('select', 'status_id', $title,
+            $form->add('select', $name, $title,
                        array(''=>ts( '- select -' )) + CRM_Member_PseudoConstant::membershipStatus( ), $required );
         } else if ( $fieldName === 'gender' ) { 
             $genderOptions = array( );   
Index: sites/all/modules/civicrm/CRM/Member/Form/Task/Batch.php

EXPLANATION: The reason for modifying the file above was to properly use the "$name" variable instead of just static "status_id".  The name variable included the member_id in it, and after the modification was then recognized properly by the template file for each member.

===================================================================
--- sites/all/modules/civicrm/CRM/Member/Form/Task/Batch.php   (revision 8059)
+++ sites/all/modules/civicrm/CRM/Member/Form/Task/Batch.php   (working copy)
@@ -223,7 +223,7 @@
                 $membership->id = CRM_Utils_Array::value( 'membership', $ids );
                 $membership->find(true);
                 $membership->free();
-                $value['status_id'] = $membership->status_id;
+                //$value['status_id'] = $membership->status_id;
                 
                 if ( empty( $customFields ) ) {
                     // membership type custom data
Index: sites/all/modules/civicrm/CRM/UF/Form/Field.php
===================================================================

EXPLANATION: The reason for this final modification above was that when submitting the form, whatever value was submitted for status_id was being overridden by the commented out line above.  Basically it would just take the status_id the member currently had and use that value instead of whatever was set in the form upon submission. 

After these edits, it is working properly.  I have not extensively tested how these edits will affect other batch operations, and I'm not 100% sure this is the best way to have gone about this, I'm just listening to Lobo and posting in the forums
-
 Chris

Dave,
I don't understand why these fields are not available for Admins to be able to use for adjusting Membership status and types. Was there some philosophy around not making them available? I don't see it as a special use but a regular function.

In my case, client wants all new and current members to be only flagged as "Current". There is no way to adjust except manually and individually if the fields are not made available for Admin use.

Thanks,
Bruce