Closed (won't fix)
Project:
Twitter
Version:
6.x-3.0-beta2
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
24 May 2010 at 07:46 UTC
Updated:
26 Jul 2014 at 19:23 UTC
Jump to comment: Most recent
Comments
Comment #1
BManuel commentedPlease some one should help me out here
Comment #2
gapo commentedI need this too.
How to get user's password during registration(signing in) to save save it into databe?
Comment #3
michaek commentedThis doesn't seem like an issue for the Twitter module, rather it seems like a question about user Profile fields. http://drupal.org/documentation/modules/profile
Comment #4
BManuel commentedI think this twitter integration is too complicated. Maybe I should put a bounty to get it rewritten
Comment #5
michaek commentedI think I didn't understand what you were describing at first - you mean that when you're signing in with Twitter, there's no way to have a user provide info for their profile fields?
Comment #6
BManuel commentedYes. They sign in, module redirects them to a required email field, they don't fill it out they ain't going nowhere pass that point. In fact there should be a help text explaining why the website needs this. If you can't give me your email, goodbye. Lets just say the emails of the new members are more important to me than their membership. I need the emails for marketing and constant communication purposes. I don't want all my eggs on the twitterverse, it's a fool's paradise.
Do we need to rewrite to achieve this? If yes then how much and how soon can it be done.
Thanks
BM
Comment #7
ayesh commentedAccording to Twitter's Oauth implementation, they never give the email address to consumer.
As a solution, you could use Rules module to redirect users to user/X/edit page so they can set change username/password and ADD email address.
Form submit returns an error when submitting user form without an email address.
Use Rules and create and action on event User registers.(and do not use Immediate redirect, and ignore destination param)
Comment #8
BManuel commentedJust did that with Rules thanks for your wonderful feedback.
I have another issue here http://drupal.org/node/1081210#comment-4616760
Looking for someone who can put this together in a few hours.
BM
Comment #9
BManuel commentedCaveat! when it comes to redirect, if you have any module that depends on the user-email to function you are stocked.
Right now we working on a user_save script to update user accounts with the email we collect.
Another reason why email collection needs to be built into the module (so that it's transfer automatically to user account info)
BM
Comment #10
pfrenssenSome ideas:
Comment #11
xurizaemonYes, this needs to be implemented as part of the signup process. It's not something we can implement in the Twitter module because user registration is outside of the scope of what the module does, but you could look to modules like OpenID Selector which do focus on user rego and handle the "edge cases" of every social networking site having its own set of rules.
Even for sites which provide email address, it's often *optional* to return that data to your site, and you'll need to pick up on cases where people uncheck the email box - either by prompting for email and confirming it (trusting an external site's email confirmation is pretty sketchy anyway) or by sending them back to authenticate and provide the password.
* https://dev.twitter.com/docs/faq#6718
* https://dev.twitter.com/discussions/4019
* https://dev.twitter.com/discussions/6035
Comment #13
marcvangendSo if I understand correctly, this is not fixed, but it won't be fixed here.
Comment #14
pfrenssenI still think this is something that is worth fixing :) The way the module handles user registration atm is confusing to the average user and requires a lot of maintenance.
The module does its user registration in twitter_signin_oauth_callback_submit().
Comment #15
xurizaemon@pfrenssen: how do you suggest we should fix it?
Comment #16
pfrenssenI think a good solution would be to present a form to the user that contains all required user profile fields after the user has authenticated with Twitter. Only after the user has successfully submitted this form the user object is saved to the database, and the email is sent that allows the user to use the one-time login link and set the password. If the user does not complete it, she is not authenticated and no user account is created.
In a standard Drupal install only the e-mail address is required, so this would just be one single field to fill in. If other required fields are present in the user account, this is usually because of business reasons and it would not be desirable to allow any users to register without filling in these required fields.
Having to fill in an additional form makes the Twitter authentication somewhat less easy to use, but Drupal really needs the email addresses or core functionality begins to break (eg password retrieval, editing of user profiles, sending of notification emails, ...).
Comment #17
myDrupal2014_846824658246 commentedHas somebody got an export of his rule for redirect the user to a page when signed in with twitter account?