That might be the route I take. It means multiple emails to the user, but that might be okay since replicating the user_register_submit function would mean making sure we keep it consistent with the core user module.

Thanks!

On Jun 8, 2011, at 1:37 PM, Ms. Nancy Wichmann wrote:

> You could make your user submit fire first (using array_unshift for the handlers) and allow the standard email to go out after you have done your thing.
>
> Nancy
>
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
>
>> From: Jeff Hartman <lists@jeffhartman.com>
>> To: development@drupal.org
>> Sent: Wednesday, June 8, 2011 2:33 PM
>> Subject: Re: [development] User registration email
>>
>> I still want to keep the standard user registrations emails since this is a custom page with a registration form for people to sign up for an event. We still get people creating accounts for the site for other purposes.
>>
>> The event registration page just happens to be creating a Drupal user account at the same time to simplify the account creation process for people visiting for this specific purpose.
>>
>> >> A client I am working for asked to have a special landing page set up for user registration for an event. The registration form uses user_register to create a Drupal account (using Drupal 6). Form works great, creates account and logs people in upon account creation.
>> >>
>> >> How do I go about creating and sending a custom email that includes the new account username and auto-generated password? Do I need to create my own user_register_submit function to override the current (seems redundant) or is there a simpler way.
>>
>