Is it safe to assume that the current ability to update existing users relies on exact matches of email addresses and/or usernames? Are there any plans to implement the ability to find loose matches based on user entity or Profile 2 fields (once that has been added)? In a custom coded (non-Drupal) site, I currently accomplish this type of duplicate matching using MySQL fulltext searches and temp tables. I would be glad to share this code with you if you think it would be a useful addition to the functionality of this module. Perhaps this could be something that users can enable/disable and adjust in configuration settings? I'd love to hear your/others thoughts.

Thanks,
Jason

Comments

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Exact matches is using email address as key.

There are no plans to provide loose matches.