Hi all,
Has anybody come across issues when Facebook returns a value for the username field that has already been taken?
In the above case, the user is redirected to the normal drupal registration form, without the option of specifying an alternative username, as would be the preferred solution for me.

thanks for reading.

CommentFileSizeAuthor
#1 fbconnect.autoname.patch3.15 KBfarez

Comments

farez’s picture

farez commented
Title: Unique username issue » PATCH for Unique username issue
Version: 6.x-2.0-beta1 » 6.x-2.x-dev
StatusFileSize
new fbconnect.autoname.patch3.15 KB

I've created a patch that will handle conflicts when Fast registration is enabled, attached. There's an admin setting to enable or disable this option. If enabled, and there's a name conflict, it will create a new random username which looks like 'fbuser123'. If disabled, then it will behave as the original code, i.e. throw an error message if there is a name.

farez’s picture

farez commented
Title: PATCH for Unique username issue » Unique username issue
vectoroc’s picture

vectoroc commented
Component: Miscellaneous » Code
Category: support » feature
Status: Active » Needs review

in github

YK85’s picture

YK85 commented

Could there possibly be a 3rd option notifying the user that the username is already taken and to choose a new username, then they will finish registration and account linked to their facebook account?

  • vectoroc committed 8629aa7 on 
    synced with github

\#965354 by farez : Unique username issue
\#967542...