It would be nice if the Member registration module checked the applicants e-mail address against those of existing members to make sure that it isn't already in the database.

The problem I'm having is this: people can't remember their login details, they go to the forgotten password form, but can't remember their username, so they just register a new account. I think the Member module would be better from a user's standpoint if this request was implemented to send a password with either the username or the password, and the request above was implemented, which requires the e-mail address to be unique.

What your thoughts, everyone?

Hi Ben,

that sounds as a good idea. I have a project i made the email adress unique via dcaconfig.php, but that doesn't solve the problem with the lost-password form.

In my opinion it would be the best, if the field to be the unique key could be chosen as a parameter.

Regards,

Christian

I have the same problem on my site.
I would appreciate if this feature will be implemented.

I agree with Ben on all counts.

Hi guys,

it is very simple to make the e-mail field a unique field. Open file system/config/dcaconfig.php and add

Code:

$GLOBALS['TL_DCA']['tl_member']['fields']['email']['eval']['unique'] = true;

Regards
Leo

Thanks for the tip, Leo. Is this something that you plan to implement into the core system, since it sounds like a fair amount of us are getting multiple registrations from the same people. The main reason for this is that they can't remember both the e-mail address and username that they used for registration. I think requiring the e-mail to be unique and allowing password resets to be sent by entering the e-mail or username will do much to improve the usability of the registration / member functionality.

I agree, and would like to see an option to "Use Members email address as Membername" added to the core.
So that the membername field didn't need to be filled out, and the email address becomes unique automatically.

At present if the email address is not unique (which requires adding to dcaconfig) AND you check the "skip username" box in the lost password module then Typolight can change the password for the wrong member (if two or more members have the same email address).

The thing I'd like to see is an easy implementation in the signup module that allows a member to join by unique email/password only.
This seems to be a standard now...one less thing to remember for anyone joining up to your site as a member.

Thinking about the logic... maybe if this box was ticked then Typolight eliminates username from all FE forms(signup,lostpassword,login) puts emailaddress into all FE forms instead, and in the database allows the username field to be blank, makes the email field unique, and "IF box ticked,IF username blank and email unique,make username field == email address" . Then in the backend the username AND email address would show as bob@nob.com.

I know its probably not that simple,but a mechanism to make the username field's value be the chosen email's (unique) value would probably avoid majorly rewriting everything.
But maybe then a member (or admin) changing the username or email may present a problem?

Thoughts?

Hi,

I created a ticked (http://dev.typolight.org/ticket/633) for this topic but it was rejected, so I guess this feature will not make it into the core...

But dows anyone knows a simple way to modify the code to use e-mailadresses instead of usernames for registration and login?

Maybe as simple as hiding the username form in the registration form. Then, after registering, copy the e-mail to be the username. Then the users can login by entering their e-mail and password.

Or does anyone has a better solution?