compatible with Shared Email ??

I'm in a similar situation. I developing a site for a local family oriented martial arts club. There are many instances where multiple people in the same family will sign up (IRL), and I'd like to create accounts for them. I cannot guarantee that each member has a unique email address, so I installed the sharedemail module. However, even with it installed, the user_import fails on duplicate email accounts.

No, not compatible, and the requirement to have a unique email address is hardcoded.

I know this is old and the module doesn't seem to be being actively developed, but I think this would be a very useful feature to have incorporated. I would have thought the email check would use a core function rather than within the module, and thus it could lever the shared email module just as easily.

If someone creates a suitable patch I'll be happy to review it.

I am currently working on a system to where all the users are predefined and requires no email. I've found a module called optional_email to disable the use of the email field. It appears you have hardcoded the email requirement. Anyway this could tie into how the registration works? I've read around for the optional_email module and it seems this is a common request among the community.

okletsgo, where is this optional_email module, I am curious, but can't find it.

anyway this is a patch that allows users to be added with duplicate emails.

Thank you for working on this patch aufumy. However, after testing this patch I ran into a problem where the profile option "replace" under the fieldset 'update existing user' no longer works without getting "duplicated error"s. It seems that the patch broke the "replace" option functionality.

I had the same problem and I managed to make this module import multiple users with the same e-mail address by manually altering the user.inc file at the function _user_import_validate_email (line 234).
Basically I commented out the third elseif. I know almost nothing of programing, php, etc. so I have no idea whether this would break something else (updating existing perhaps?).

The patch aufummy supplied didn' t work for me.

This needs to be handled at a more conceptual level: implementing an option to use any field as a key.

I don't have time to write that myself at the moment, but would be useful if someone else could come up for a patch that does that.

This needs to be handled at a more conceptual level: implementing an option to use any field as a key.

Cross post - #887550: Ability to select primary key

For proper support of this feature we need to implement #887550: Ability to select primary key, so I'm marking this as a duplicate.

Here is one hackish solution

http://www.drupaldump.com/user-imports-and-duplicat-emails