CiviCRM Community Forums (archive)

As it is right now, two emails are sent on a membership signup. However, I only want one email to be sent. How do I include the username, the password and the URLs of the Drupal email in the CiviCRM email receipt?

Thanks,

Mikael

Pretty sure Michał is that it's not easily possible to send out a regular password reminder. Drupal goes to some efforts to make sure it doesn't know what your user's passwords are. Drupal can check if they gave the right password, but the passwords aren't stored in a readable format so you can't readily email them out.

(I respect that you may have a good reason for doing this, but do consider whether seeing their SECRET PASSWORD in a plaintext email will give your users the screaming heebie-jeebies. Your users may thank you to avoid this entirely, even if you do find a method!)

Methods to achieve the same ends depend if you need them logged in as a Drupal user also, or just as a CiviCRM contact (which limits their authenticated activities to CiviCRM data), or if you really really do need to send their password in an email.

For a CiviCRM "Click here to (do X)" then you can also skip the login entirely by using {contact.checksum} in your CiviMail message. That way you get them authenticated as a CiviCRM user only, not a Drupal user, but you can do all your fundraising, address update, survey stuff OK still. They will be recognised as CiviCRM contacts but not as Drupal users with this method.

For a Drupal login, you could look into user_pass_reset_url($account) which is the Drupal user.module function to generate a nice clickable URL to log the user in and let them reset their password. Or you can just link them to example.com/user/password to self-serve a login reset email if they actually want one.

CiviCRM's method is better for working with the general public, Drupal's is really intended for when you actually NEED a password reminder.

(Wondering now if there's a Drupal module to generate a login-and-redirect URL, that might be a handy method to get best of both worlds. Mmm.)

If you really wanted to email out passwords every month, you'd need to roll your own method to store Drupal passwords plaintext (either in the users table or elsewhere), which would be A Very Bad Idea, even though it'd be quite easy to do.