Skip to content
This repository has been archived by the owner on Jul 20, 2022. It is now read-only.

Profile with send email in advanced settings causes off behavior #95

Open
shawnholt opened this issue Sep 30, 2015 · 4 comments
Open

Profile with send email in advanced settings causes off behavior #95

shawnholt opened this issue Sep 30, 2015 · 4 comments
Assignees
Labels

Comments

@shawnholt
Copy link

When profile creation includes an email notice, the extension will create a (duplicate) contact for the recipient. We have [email protected] notified. I noticed hundreds of duplicate contacts created for [email protected]. It looks like the email lookup must be failing. I'm also getting FK constraint errors adding to the mailing queue - not sure if that is related.

@JoeMurray JoeMurray assigned JoeMurray and pradpnayak and unassigned JoeMurray Sep 30, 2015
@sanjayjaindc
Copy link

I see a situation where mailings are creating duplicate contacts - the contact is in a smart group that is being used mailings, each time a mailing goes out a duplicated is created.... so the first time 1 was created, the next time there were 2 contacts, so 2 more were created... 4 the following mailing and so on.

Interestingly the contact name and email happen to be [email protected]

@JoeMurray JoeMurray added the bug label Nov 12, 2015
@JoeMurray
Copy link
Member

There was problem with the DAO search on contacts using email caching results. If the first search returned no contact, and contact was created, eg for a multiple registration on events page for a cc or bcc email, then contact was improperly created again. Second, once there are multiple contacts with an email, normal search for a contact with the email fails since there are more than one. We are addressing both conditions in next release.

@pradpnayak
Copy link
Contributor

Can you please update the extension and check if still get error

Here is the download link:
https://github.com/JMAConsulting/biz.jmaconsulting.mte/archive/v2.1.beta.zip

@ginkgomzd
Copy link

It looks like we are having the same problem on one of our instances.
We have v2.1 of the extension installed.
Did the code in the zip archive linked above make it into the 2.1 release? Is there any reason for us to test it? Or are we at square one with resolving this bug?

Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants