CiviCRM Community Forums (archive)

I have a saved export set for exporting Members (not contacts) in which I am exporting both Home Phone and Work Phone. When I first set up the export sets, they are set up properly, with the dropdown menus reading Individual--Phone--Home--Phone and Individual--Phone--Work-Phone. And this exports properly. I save this set for future use.

However, if I come back later and try to use this saved export set, only the first 3 menus are shown; the last menu (which selects from among Phone, Mobile, Fax, etc.) isn't shown. And if I use the export set, the phone numbers are not exported.

If I play around with the Location drop-downs, after a couple of tries I can get the final menu to appear. But I can't get it to stay saved; each time the saved menu is selected, the last (fourth) column menu is missing.

You can see in the attached file what it looks like when I'm setting up the export set (left), and what it looks like when I try to re-use that saved set (right).

I tried this out on the demo server, and it works properly on the demo. So it seems pretty clear that the bug got fixed from 2.2.7 (which we're using now) to 3.1. We'd like to hold off upgrading for several months until we're in a slow period (because every upgrade seems to break something and we don't like to do upgrades when we've got a lot going on). So what I was wondering was, is there a simple patch to 2.2.7 that would fix this issue to tide us over until we can properly upgrade?

Hi Kurund, thanks for your reply. When I said "I tried this out on the demo server, and it works properly on the demo", what i was trying to convey was that I did try it out on http://drupal.demo.civicrm.org, which is running CiviCRM 3.1. The issue doesn't arise on the demo server, from which I infer that the bug was fixed somewhere between 2.2.7 (our version) and 3.1 (the demo version). So, I know that one way of resolving *this* bug is to upgrade to 3.1, but the process of upgrading introduces new problems (in fact, we tried the upgrade on a copy of our site and ran into db errors, which are being addressed elsewhere in a different thread).

What I was hoping for was that someone could say "oh yes, here's the bug that was fixed in 3.1., and you should look in this file to see what changed", and then we could just patch our current installation to tide us over until we can get the upgrade to work.

Thanks,

Robert

Thanks, Kurund, I'll look through there.