I'm not trying to get get in the way of refactoring this registration procedure/tables in core, but I believe some contrib modules might help you get over these problems at the moment:<br><br><a href="http://drupal.org/project/email_verify">
http://drupal.org/project/email_verify</a><br><a href="http://drupal.org/project/inactive_user">http://drupal.org/project/inactive_user</a><br><br>Cheers,<br>- Amr Mostafa<br><br><div><span class="gmail_quote">On 4/17/07,
<b class="gmail_sendername">Karthik</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In a site with ~33000 users, I found that about ~1900 sign-ups were<br>never completed and essentially clutter up the user table. I am<br>looking for opinions on the pros and cons, if any, of streamlining the<br>default sign-up procedure to:
<br><br>a) Sign-up form only contains an e-mail field that the user fills in<br>to confirm authenticity.<br>b) The e-mail field is stored in a separate table along with the<br>sign-up URL token.<br>c) The sign-up e-mail contains nothing besides a sign-up URL which the
<br>user clicks as opposed to the current e-mail which contains a number<br>of choices.<br>d) The user is presented with a web page where he selects his<br>username, password and assorted details (other than his e-mail for the
<br>first time) and is logged in immediately.<br>e) Only after successfully completing step d) is the user account<br>added into the user table.<br>f) Perhaps an e-mail is sent upon successful completion of the<br>procedure for future reference.