CiviCRM Community Forums (archive)

Hi,

We just upgraded a CiviCRM 2.2.7 installation to 3.3 and discovered a mechanism that worked fine in 2.2.7 now corrupts membership data in 3.3.

We have a Membership custom data field that is set manually to flag records for printout; when they're all printed, we clear that flag by using "Batch Update Members via Profile," using a Membership Profile that contains just that one item.

After the update is run, every Membership record that was part of the update has its Membership Expiration Date cleared. (Start Date and Member Since remain unchanged.) It shows up blank. At some point (we haven't figured out exactly where), it eventually gets repopulated with the default value (one year from Membership Start Date), but that's often not the right value.

Is this a known bug? Is there a patch? It's pretty painful (scary, too, to see membership data silently corrupted.)

Robert

I've reproduced this on the demo site.

Here's the test membership record for "J User". You'll see that it has an end date and a new custom field called "Print Switch," whose value is currently set to "Renewal."
http://drupal.demo.civicrm.org/civicrm/contact/view/membership?action=view&reset=1&id=31&cid=112&context=home

Now, if you do a Membership search for that field and that value (Print Switch=Renewal), the search will turn up just that record.
http://drupal.demo.civicrm.org/civicrm/member/search?reset=1

Select the contact, do "Batch Update Members via Profile,", then choose profile "Print Switch Update." Set the value of Print switch to "Off" and click "Update Memberships."

Now, if you go back and look at the contact's membership, you'll see that the expiration date has vanished.
http://drupal.demo.civicrm.org/civicrm/contact/view/membership?action=view&reset=1&id=31&cid=112&context=home

We're using 3.3. A patch (or even a suggestion of where to investigate) would be greatly appreciated.

Robert

That fixes it, thanks!

Robert