Multiple joomla accounts with 1 facebook account

JFBConnect will *not* allow the same Facebook user to be connected to the multiple Joomla accounts. You can check the User Map area of JFBConnect and see what 'connections' have been made between Facebook and Joomla users and there should only be one connection between each.

When using JFBConnect, you shouldn't use other extensions for social network login as others may create different associations. We can't control what other extensions do, so if the other extensions you mention are creating multiple connections, that's something you'd need to discuss with them. In general though, you simply shouldn't be using multiple social network login functionality as each could create their own individual connections between users and causing the problems you're seeing.

I hope that helps explain,
Alex

I'm not sure how that would be happening. Can you tell me the process all those users took to link their Facebook account to Joomla? Specifically:
* Were they clicking the Login with Facebook button and logging in with Facebook?
* Were they logging into Joomla and then clicking a Login with Facebook button somewhere else to 'connect' accounts, like in our SCLogin module?
* Are the users all logging in from the same computer, or are they on different computers? This may be a session issue that isn't closing in the browser properly.
* If the same computer/browser, are you logging out of Joomla or Facebook in between the logins?
* Is there anything else you can tell us about the process?
* Are there any extensions that have JFBConnect integration built-in that you are using?

We've *never* seen that happen and there are multiple checks in JFBConnect to prevent duplicate linking of accounts. I don't know of any path that should be creating multiple links between users either, so I'm at a loss. I also just looked at our code and the place where we performing the mapping will look at the Joomla User Id and see if there is already a 'mapping' for that network (facebook). If so, it will only update that row.

So, something is obviously wrong, I just can't tell what and how it would be happening with JFBConnect. That's why knowing if there's some other integration happening it would help as that may be doing it wrong.

Thanks,
Alex

Looks like you may have found a bug when a user tries to 'switch' their Facebook account to a different Joomla user. Not a common situation, but definitely happens and should work.

The fix is very simple, if you're up for making a minor code change. To do so, please edit the /administrator/components/com_jfbconnect/models/usermap.php file. Around line 309, you'll see:Change that to:Let me know how that goes. We have a v5.1.2 release due out tomorrow with a few other bug-fixes, but I'm going to try to streamline this into our test suite and get it into that release as well.

Thanks for notifying us of the issue and describing the steps in such detail.

Alex

Overriding the current connection is the behavior intended with that change. We've had it prevent connections in the past and tried other things as well. The one we settled on as working the best is the method above where a user can re-associate their Facebook account with a different Joomla account, if necessary. This has been how JFBConnect has worked for more than 2 years, but you found a bug that was introduced in the v5.1.0 release at the end of August.

For more of our reasoning.. Sometimes user's have 2 accounts on the same site, sometimes this is accidental (like if you're using the Automatic registration feature of JFBConnect) and the ability to 'switch' the login to a different Joomla account has been beneficial in the past. If we deny the link, then it can lead to confusion as the "Connect this account?" text will always show and the user won't be able to update the association even if they want to. Also remember, that most people have only one FB account, so if they want to make that connection it's usually intentional. When you're testing with multiple accounts, things are different.

If you want, we can gladly help you implement some code to deny the update, but it's not something we'd implement in our code from past experience and feedback from our users.

I hope that helps explain, but your feedback is welcome,
Alex