Hi all, I've to move users from a legacy system to D5.
In the legacy system the user name for login was the email.
Users will produce some public content.
In many places drupal uses the user.name to refer to users but I can't of course use users' emails to refer to users.
I can't even force the users to change the way they login. So they have to continue to be able to login with email, password.
One way would be to automatically fill name with something auto-generated during import and change the login process (looking for some clean idea that won't involve changing core, form_alter?).
Any other suggestion?
You may find the realname module useful, in combination with some of the others already discussed.
http://drupal.org/project/realname
Luke
On Fri, 31 Jul 2009, Ivan Sergio Borgonovo wrote:
Hi all, I've to move users from a legacy system to D5.
In the legacy system the user name for login was the email.
Users will produce some public content.
In many places drupal uses the user.name to refer to users but I can't of course use users' emails to refer to users.
I can't even force the users to change the way they login. So they have to continue to be able to login with email, password.
One way would be to automatically fill name with something auto-generated during import and change the login process (looking for some clean idea that won't involve changing core, form_alter?).
Any other suggestion?
Ivan Sergio Borgonovo escribió, El 31/07/09 08:27:
Hi all, I've to move users from a legacy system to D5.
In the legacy system the user name for login was the email.
Users will produce some public content.
In many places drupal uses the user.name to refer to users but I can't of course use users' emails to refer to users.
I can't even force the users to change the way they login. So they have to continue to be able to login with email, password.
One way would be to automatically fill name with something auto-generated during import and change the login process (looking for some clean idea that won't involve changing core, form_alter?).
Any other suggestion?
On Fri, 31 Jul 2009 09:35:47 -0300 Leandro Monk monk@cafelug.org.ar wrote:
Ivan Sergio Borgonovo escribió, El 31/07/09 08:27:
Hi all, I've to move users from a legacy system to D5.
In the legacy system the user name for login was the email.
Users will produce some public content.
In many places drupal uses the user.name to refer to users but I can't of course use users' emails to refer to users.
I can't even force the users to change the way they login. So they have to continue to be able to login with email, password.
One way would be to automatically fill name with something auto-generated during import and change the login process (looking for some clean idea that won't involve changing core, form_alter?).
Any other suggestion?
Thanks!
I remember I already grabbed some code from there. At that time I was interested in learning how to redirect to different places users after login. I didn't remember the module also provided logging in with email too.
Since a lot of urls already contains uid I think filling the users.name with uid at import time doesn't look a bad idea.
Maybe to improve user experience what's missing now is to ask to change the "nick" when the user will try to add his first content. Not really sure if it could be something appreciated/useful for most users.
Another solid module for this purpose is Email Registration http://drupal.org/project/email_registration
It creates a username based on the e-mail and allows people to login with e-mail.
Regards, Greg
Quoting Ivan Sergio Borgonovo mail@webthatworks.it:
Hi all, I've to move users from a legacy system to D5.
In the legacy system the user name for login was the email.
Users will produce some public content.
In many places drupal uses the user.name to refer to users but I can't of course use users' emails to refer to users.
I can't even force the users to change the way they login. So they have to continue to be able to login with email, password.
One way would be to automatically fill name with something auto-generated during import and change the login process (looking for some clean idea that won't involve changing core, form_alter?).
Any other suggestion?
I don't have time to find which one but I know there is a module that will allow the user to register/login with email address, and use the portion before the @ as the user name; I forget how it manages duplicate user names. There may even be a module for masquerading the user name.
-- Earnie -- http://r-feed.com/ -- http://for-my-kids.com/ -- http://www.4offer.biz/ -- http://give-me-an-offer.com/
1a. I believe login tobagan gives the option to login with email 1b. hook_form_alter to login form, supply own submit handler, login programmatically 1c. webform or roll your own login form, login programmatically in submit handler 2. Just use the email for the user name, and add core profile or content profilie module for first and last names, etc. 3. Override user.name theme to use profile values
Victor Kane http://awebfactory.com.ar
On Fri, Jul 31, 2009 at 8:27 AM, Ivan Sergio Borgonovo <mail@webthatworks.it
wrote:
Hi all, I've to move users from a legacy system to D5.
In the legacy system the user name for login was the email.
Users will produce some public content.
In many places drupal uses the user.name to refer to users but I can't of course use users' emails to refer to users.
I can't even force the users to change the way they login. So they have to continue to be able to login with email, password.
One way would be to automatically fill name with something auto-generated during import and change the login process (looking for some clean idea that won't involve changing core, form_alter?).
Any other suggestion?
-- Ivan Sergio Borgonovo http://www.webthatworks.it
-- [ Drupal support list | http://lists.drupal.org/ ]
On Fri, 31 Jul 2009 09:52:37 -0300 Victor Kane victorkane@gmail.com wrote:
- Override user.name theme to use profile values
Are you saying that there is a specific place in drupal that is theming users.name everywhere?
That could be nice.
But well I'm exactly the reason I'm not going to use that approach.
Whenever I had to output users.name I never used any such theme function. So maybe some other module I'm using (I'll use) may not be aware of such a function and eg. output something like
Submitted by user@email.com
thanks
BTW SQL is not dead ;)
-
Earnie Boyd -
Greg Knaddison -
Ivan Sergio Borgonovo -
Leandro Monk -
Luke -
Victor Kane