CiviCRM Community Forums (archive)

Hi @Vishram74,

I've never used the WordPress version of CiviCRM, only Drupal. I have come across the problem you describe twice. It's nasty!

You'll notice if you go to the contact record or Drupal account page for the person attributed with having updated the record that the email address they have is the email of the person who actually did make the activity.

First, to solve, then to prevent. (I'll speak in Drupal terminology, you'll have to do some translating for WordPress, but probably not much.)

To solve.

You need to sever the connection between the CiviCRM contact and the Drupal user.

If the Drupal User has not created any content, then the easiest way to do this is to Delete the Drupal user. After you do that, immediately go to the contact record who has been incorrectly attributed for the activity. Correct the email there. Then recreate the Drupal account.

If it isn't desirable to delete the Drupal user account, then do the following:

Access your civicrm database and go to the table civicrm_uf_match. Find the record that incorrectly matches the CiviCRM contact ID to the Drupal ID. The field "uf_id" is the Drupal id. The field "contact_id" is the CiviCRM contact id. Edit that record to reflect the proper matching.

Prevent:

I'm not 100% sure about this but I have strong hunches it is the following: An administrative user to your site is logged in and wants to add a contribution or an event sign-up or any thing else to someone's record (NOT their own record). I'll use the example of adding a contribution. The administrator should go to: CiviCRM => Contributions => New Contribution and fill out the form there. But let's say we are not talking about recording a donation made by check, but rather that (likely breaking PCI Compliance), the donor gave her credit card number over the phone to the staff person with the intention of having the staff person process the transaction. Since you can't enter a credit card for processing in the admin section of the site, the staff person goes to a publicly facing donation page without logging out first. The result is that the donor's CiviCRM record becomes associated with the currently logged in administrative user. In order for this transaction to have been done "right" (again, this is probably breaking PCI compliance), the administrative user would have needed to log out before going to enter the transaction on a publicly facing page.

The example I gave is with contributions, but it can happen whenever a logged-in user goes to any publicly facing page that has a profile form on which a staff person fills on behalf of someone else.

Hope this helps. Do report back,

Best,

Shai