In the registration messages, the Drupal core new user messages is like

Thank you for registering at [site:name]. You may now log in by clicking this link ...
After setting your password, you will be able to log in at [site:login-url] in the future using:

username: [user:name]
password: Your password

And shoud be:
username: [user:mail] (also you can use: [user:name])

I tired to use hook_mail_alter() but the [user:name] tag is already replaced by the username.
I don't know how to "catch" [user:name] in the message before it is being replaced. If someone helps with an idea I can make the patch.

#3 README.txt1.7 KBgreggles
Members fund testing for the Drupal project. Drupal Association Learn more


greggles’s picture

Title: User account activation message » Create README.txt - document the need to change user mails

The project page already mentions this, but it wasn't super clear. I've added some headings and reworded things a bit to make it more clear.

We should probably also have a README.txt with the project that mentions this.

greggles’s picture

We should also mention (as the project page does) that you can grant people the ability to change username per #1563190: Optional field for user name.

greggles’s picture

Status: Active » Needs review
1.7 KB

Here's a file for review.

Also, I merged #1546054: Add README.txt idea to fix confusing validation message into this.

ptmkenny’s picture

The README.TXT looks good; one thing I would suggest is to mention that Email Registration plays well with the RealName module, which can be a big help in some use cases. I use Email Registration and RealName together on my site; this allows users to log in with their e-mail address but specify the name that appears in posts (a field on the user profile) and have that displayed instead of the randomly generated username provided by Email Registration.

greggles’s picture

Title: Create README.txt - document the need to change user mails » Create README.txt - document various setup instructions
Version: 7.x-1.x-dev » 6.x-1.x-dev
Status: Needs review » Patch (to be ported)

Now committed -

Not sure if this should be ported or not.

@ptmkenny - interesting idea. I've added it to the project page for now.

greggles’s picture

Status: Patch (to be ported) » Fixed

Indeed it was needed. I tweaked the paths for 6.x vs. 7.x and committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.