I am still trying to resolve this.

I tried to ban the login for the newest duplicate of the user in their profile and when I try to save it reports that the user already exists (with a stack trace).

I thought about deleting the newest of the two duplicate entries, but resisted in case if took both of them out.

Stuck on this.
Cheers
Ade

Please try a manual change in the f_members table. Back it up, and delete one of the member rows. I will have to come back to this issue next week, as I am away this week.

The underlying bug was already fixed on your site, when we did the facebook update for you recently.

It was allowing Facebook to suggest a username even if there was a conflict.

Interestingly, Facebook returned a username rather than human name, even though the API docs for Facebook say the 'name' field we use is "The user's full name". I note this user has this as their *account name* on Facebook.


To fix this I would advise renaming one in the f_members table, then using the merge members feature.

Hi Chris,

This bug does not seem to of been fixed.

I have another user who has managed to create a new account of the same name :-(

His username is sheepwagon.

Ok, so I can correct it as before but would like to stop it happening again.

Any ideas ?

Cheers
Ade

I have found another cause. When a member joins with Facebook they are forced to complete their profile, and at that point the username can be changed from the normal Facebook default and no confliction check is done. That is now fixed.
(On most sites Facebook signup is instant, which is why I did not notice this - but when there are required CPFs it isn't)

Cheers for fixing this quickly Chris