[drupal-devel] [feature] Single step account creation and login
Issue status update for http://drupal.org/node/4942 Post a follow up: http://drupal.org/project/comments/add/4942 Project: Drupal -Version: 4.6.2 +Version: cvs Component: user.module Category: feature requests Priority: normal Assigned to: amanuel Reported by: mathias Updated by: killes@www.drop.org Status: patch (code needs review) I actually disagree with Dries and Steven. I let firefox maintain all my passwords and couldn't care less what my actual pw for any Drupal based website is. If we let the user provide a password then I at least woudl want to havd Drupal suggest one for me. killes@www.drop.org Previous comments: ------------------------------------------------------------------------ Sat, 03 Jan 2004 23:49:54 +0000 : mathias Under special circumstances, i would like a new user to be able to choose their own password and be automatically logged into the site without needing to check their email. I feel this is necessary for my ecommerce module, where after anonymous users are ready to "Proceed to checkout", they need to create an user account to continue. It is tedious for the customer if they have to stop, check their email, log into the site and then resume the checkout process. I'm game to code this (if this has potential to be part of the core), i just need some feedback on the best way to tweak user_register. ------------------------------------------------------------------------ Sun, 04 Jan 2004 06:18:07 +0000 : moshe weitzman +1 for this. I don't think you will get much objection to this much needed usability enhancement. ------------------------------------------------------------------------ Thu, 08 Jan 2004 05:48:40 +0000 : mathias Attachment: http://drupal.org/files/issues/user.module-quick_acount.patch (7.11 KB) This is a prototype patch to make sure i'm going in the right direction. I feel this patch is about 95% complete, the outstanding issue being page redirection after quick-account creation. It introduces and new option under the user admin settings "Public registrations" called "Visitors can create accounts and sign in immediately.", allowing visitors to submit their own passwords upon account creation. This is important in an ecommerce site where a new customer wants to the checkout process to be as easy and seamless as possible. ------------------------------------------------------------------------ Thu, 08 Jan 2004 10:22:09 +0000 : moshe weitzman i read through the patch. looks good to me. a few notes - we should still send a password via email to users who choose their ow password. with some text tweaking, we should be able to send the same welcome email to 'generated password' registratants, and 'user specified password' registrants. - I think we need a setting for minimum length of a password. the password textfield should inform users of this requirement. - you don't actually relinquish control after saying "/* Let the developer control where the user is redirected. */". i assume this part isn't finished yet. nice work. ------------------------------------------------------------------------ Thu, 08 Jan 2004 13:46:07 +0000 : flevour Are there any anti-bot checks around, e.g. randomly generated images that contain text or numbers to insert in a box? Congrats for your work :p // flevour ------------------------------------------------------------------------ Thu, 08 Jan 2004 13:54:19 +0000 : Bèr Kessels I had another idea. that would be to filter all emailadresses (in content too) into a link to the feedback module. thus http://www.mysite.org/feedback/mailto/me/mysite.org the feedback can then print a form that can send the message to me@mysite.org. Would this be a good feature or not? Ber ------------------------------------------------------------------------ Thu, 08 Jan 2004 13:56:36 +0000 : Bèr Kessels sorry folks. placed this in the wrong box. Was updating another feature, and reading this one (to see if it was the same one) i then, by accident, filled replyed here. :( Ber ------------------------------------------------------------------------ Thu, 08 Jan 2004 16:49:56 +0000 : Dries Showing an image with random generated text that a user is supposed to copy, makes your website inaccessible for visually impaired: they can't be read by a screen reader. ------------------------------------------------------------------------ Thu, 08 Jan 2004 17:07:02 +0000 : mathias Responding to Moshe's comments: - we should still send a password via email to users who choose their own password. with some text tweaking, we should be able to send the same welcome email to 'generated password' registratants, and 'user specified password' registrants. That is a good point. I'll update the patch. - I think we need a setting for minimum length of a password. the password textfield should inform users of this requirement. Agreed. In my patch i checked to make sure the password was at least six characters long, but this should be an element that can be tweaked by the admin. It might be best to make this a global password length system variable. - you don't actually relinquish control after saying "/* Let the developer control where the user is redirected. */". i assume this part isn't finished yet. Yep, that's the part i'm still working on. Thanks for the critical eyes. ------------------------------------------------------------------------ Wed, 14 Jan 2004 04:31:06 +0000 : mathias Attachment: http://drupal.org/files/issues/user_0.module-quick_acount.patch (7.95 KB) The patch has been updated and is ready for final review, and commit. ------------------------------------------------------------------------ Wed, 14 Jan 2004 22:37:53 +0000 : Dries Not sure. Wouldn't it make more sense (and result in better/less code) to let the user *always* choose his password and to introduce a admin setting to control whether e-mail addresses should be validated by e-mail? ------------------------------------------------------------------------ Sun, 15 Feb 2004 17:02:38 +0000 : moshe weitzman moving out of patch queue until a cleaner implementation is submitted ... this feature is still quite valuable. ------------------------------------------------------------------------ Fri, 05 Nov 2004 19:21:49 +0000 : Nick Nassar I agree with Dries that it makes a lot of sense to always let the user choose her password. It's a pain to copy and paste in a randomly generated password, then change it. Hash link based verification is much easier. That's really a seperate issue from an option to disable verification. ------------------------------------------------------------------------ Fri, 22 Jul 2005 22:11:42 +0000 : amanuel Attachment: http://drupal.org/files/issues/user4.6.2.patch (4.25 KB) Following Dries's suggestion, I have implemented a "Enable Email Verification" option to user.module. The attached patch does the job. With this patch the system by default will ask for a password. If Email Verification is turned on in the settings, the system will send the password via email. $edit['destination'] is carried so as to allow the user to return where they were (shopping cart etc.) Any comments? Amanuel ------------------------------------------------------------------------ Sat, 23 Jul 2005 05:48:08 +0000 : mathias I want users to be able to enter their own passwords upon account creation, but this patch still needs some work. - The email verification checkbox in user admin settings is confusing. I'm assuming that it applies to any of the selected registration options? However when I select that only site admins can create new user accounts, the accounts I create don't get any emails sent for the user to verify. - When a user signs up and enters his/her own password I think they should be logged in automatically rather than taken to a screen asking them to click the login button. - User entered passwords aren't validated. We should check to make sure they're at least six characters and verify the password strength level to some degree (i.e. same characters, all lowercase letters.) ------------------------------------------------------------------------ Fri, 29 Jul 2005 05:09:30 +0000 : Steven I agree with Dries. Random-generated passwords are hard to use. We already have optional hash-link functionality on signup, so I think we should always use it.
I'm with Dries and Steven. Letting firefox maintain passwords is great, on your own computer. Come over to my house and try to access your account from my computer and you'll make a long face. killes wrote:
I actually disagree with Dries and Steven. I let firefox maintain all my passwords and couldn't care less what my actual pw for any Drupal based website is. If we let the user provide a password then I at least woudl want to havd Drupal suggest one for me.
On Sun, 7 Aug 2005, Robert Douglass wrote:
I'm with Dries and Steven. Letting firefox maintain passwords is great, on your own computer. Come over to my house and try to access your account from my computer and you'll make a long face.
Robert, posting your replies to drupal-devel is not helpfull. Please reply on the issue and I will reply there as well. Cheers, Gerhard
On 7-Aug-05, at 10:20 AM, Gerhard Killesreiter wrote:
On Sun, 7 Aug 2005, Robert Douglass wrote:
I'm with Dries and Steven. Letting firefox maintain passwords is great, on your own computer. Come over to my house and try to access your account from my computer and you'll make a long face.
Robert, posting your replies to drupal-devel is not helpfull. Please reply on the issue and I will reply there as well.
This brings up an interesting point, actually -- virtually all code discussions take place via issues now. Should we split the mailing lists to be drupal-devel for development discussions and drupal- issues for where project issues get sent. We talked about setting up a drupal-consultants list because people that *don't* code but *do* configure/maintain/administer a lot of Drupal sites were hesitant to post here. Could drupal-devel be this list? -- Boris Mann http://www.bmannconsulting.com
Boris Mann <borismann@gmail.com> writes: % We talked about setting up a drupal-consultants list because people % that *don't* code but *do* configure/maintain/administer a lot of % Drupal sites were hesitant to post here. Could drupal-devel be this % list? No, let's keep drupal-devel for development discussions Create a new list for drupal-issues for debugging of issues and create a new list drupal-consult or drupal-var for discussions of what it takes to install drupal for a client and the places this does not work well. ----- John Sechrest . Helping people use . computers and the Internet . more effectively . . Internet: sechrest@peak.org . . http://www.peak.org/~sechrest
and definately don't debate the mailing list configurations on drupal-devel. we have drupal-infrastructure for this.
Boris Mann <borismann@gmail.com> writes:
% We talked about setting up a drupal-consultants list because people % that *don't* code but *do* configure/maintain/administer a lot of % Drupal sites were hesitant to post here. Could drupal-devel be this % list?
No, let's keep drupal-devel for development discussions Create a new list for drupal-issues for debugging of issues and create a new list drupal-consult or drupal-var for discussions of what it takes to install drupal for a client and the places this does not work well.
Moshe, I think it's reasonable to have this discussion here, since the issue affects members of the list (many of whom likely aren't subscribed to drupal-infrastructure) Boris, your proposal mirrors a discussion we had Saturday at Portland DrupalCon 2005. I think it's a good idea. Our discussion boiled down to the observation that people come to drupal.org (and the mailing lists) from many backgrounds and areas of interest. Many (most?) visitors/subscribers finds the site and the lists noisy, and lacking the information they want (perhaps only because they can't find it easily) Kaliya identified this as an issue of scaling, and I'm inclined to agree. What works well for 50 modules and 10,000 users might well start to break down for 250 modules and 50,000 users. Everything starts to change - the types of users, the types of issues, and the types of interactions/communication. It was proposed (yet again?) to organize drupal.org into sub-sites supporting distinct users / roles. Furthermore, it was felt that having 'project (module?) centric' view would be helpful. So perhaps rather than having a mailing list addressing all issues, one could have a per-project/per-module subscription. Djun On 8 Aug 2005, at 12:00 PM, Moshe Weitzman wrote:
and definately don't debate the mailing list configurations on drupal-devel. we have drupal-infrastructure for this.
Boris Mann <borismann@gmail.com> writes: % We talked about setting up a drupal-consultants list because people % that *don't* code but *do* configure/maintain/administer a lot of % Drupal sites were hesitant to post here. Could drupal-devel be this % list? No, let's keep drupal-devel for development discussions Create a new list for drupal-issues for debugging of issues and create a new list drupal-consult or drupal-var for discussions of what it takes to install drupal for a client and the places this does not work well.
-- Djun M. Kim, Director djun.kim@cielosystems.com Cielo Systems Inc. http://www.cielosystems.com Strategic Software Research Tel: (604) 739-3941 302 - 1298 10th Avenue West FAX: (604) 739-3943 Vancouver, BC, V6H 1J4 Mobile:(778) 895-1379
participants (7)
-
Boris Mann -
Gerhard Killesreiter -
John Sechrest -
killes -
Moshe Weitzman -
puregin -
Robert Douglass