Author Topic: Email already in database issue - prevents donation. (Read 1079 times)

nvisioncurtis · September 10, 2009, 04:02:33 pm

Hi,

Why would a contribution page block a donation based on "email is already in the database"?
I've search this one and have not come up with anything... All Drupal user accounts emails are blocked from donating due to email is already in the database"

I have created the contibution page without using any profiles or groups. In fact, its the only thing I am using Civ for at the moment.

It works so long as the user is not an authenticated user otherwise if it finds a user account with the email it wont except it; Even if that user is logged in.

I figure its a configuration problem although I don't think its a permissions problem.
I'm not really sure where to look for the answer...

Getting desparate. Help if you can. Thanks.

petednz · September 10, 2009, 05:24:14 pm

If you aren't using Profiles then I presume you are not asking them to 'set up a drupal account'.
Maybe check your duplicate rules .../civicrm/admin/deduperules?reset=1.
Are people entering a name as well as email address - is the duplicate rule trying to check on both but not getting the name perhaps. Can you flesh out exactly what information you are collecting.

nvisioncurtis · September 11, 2009, 07:24:56 am

Hi Peterd,

First thank you for offering help.

The only information that is gathered is the default fields when creating a contribution page; the email and then the information under "Billing Name and Address" used for Credit card. I did not think a profile or group was needed here as I am barely using CiviCRM other features.

I'm not really sure what they should be. Should I just delete the rules and see what happens?

Currently they are as follows
   Individual     Fuzzy     Default     (Set to Firstname, Lastname, Email)
   Organization   Fuzzy Default     (Set to Co. name, Email)
   Household     Fuzzy Default     (Set to Household. name, Email)
   Individual     Strict Default     (Set to Firstname, Lastname, Email)
   Organization   Strict Default     (Set to Co. name, Email)
   Household     Strict Default     (Set to Household. name, Email)

The book doesn't really explain how these relate. I thought this was more house keeping of data not input filtering.

I did find a post that mentioned a similar issue and changed the Strict rule for Individual. But it did not seem to help at all.

Kiran Jagtap · September 11, 2009, 08:58:17 am

I am not sure this is your use case, but just want to confirm -
lets consider scenario :
- userA and userB both are drupal user and also having civicrm contact record.
- now logged in w/ userA.
- try to make contribution w/ some contribution page.
- give userB email address for contribution.
- now civicrm giving validation error message and not allowing to process.

kiran

nvisioncurtis · September 11, 2009, 10:55:38 am

Hmmm,

That is exactly what I am doing. I only have three accounts right now in testing so the issue is if you are using an email of a drupal account then you have to be logged in with that account.

Okay so there is no problem. I'm just making my own problem

Thanks for clearing that up!

CiviCRM Community Forums (archive)

News:

Author Topic: Email already in database issue - prevents donation. (Read 1079 times)

nvisioncurtis

Email already in database issue - prevents donation.

petednz

Re: Email already in database issue - prevents donation.

nvisioncurtis

Re: Email already in database issue - prevents donation.

Kiran Jagtap

Re: Email already in database issue - prevents donation.

nvisioncurtis

Re: Email already in database issue - prevents donation.