Cameron,
Sorry for the delay. I'll try to answer all the questions as best I can, but if I missed something, let me know:
sorry this profile is not available for instance heres my own link: www.facebook.com/profile.php?id … 7541727654
This is a bug in JFBConnect that we didn't realize until now. With the new
Facebook Graph API v2
, Facebook returns a unique, Application specific ID for each user. That means that the ID we import for the user isn't the 'real' ID of the user.. and the way that we link to their profile isn't correct anymore. We used to directly link to each user profile, but with Graph API v2, we'll need to do that a different way.. I'm not sure what that way is yet though, but I've added it to our to-do list for a 6.1 bug-fix release.
First / Last Name Issues
I'm not sure why the user's name from Facebook wouldn't be imported properly. That's generally standard, public information and Facebook should always return that data. Can you tell me (or Private Message me) the user's name? All I can think is that there may be some special character or something else that's preventing the data from being saved properly. Other than that, it would mean that Facebook isn't returning their first or last name for some unknown reason.
As for why the user isn't being saved properly, that is likely an issue with Community Builder itself. If a user's data doesn't validate properly, CB will reject the saving of the entire user and won't write anything to the database tables. In that case, the user will be created in Joomla, but CB won't have any information about them. To fix, what I'd recommend is:
a) Marking the firstname and lastname fields as not required. CB treats these fields differently anyways and they'll still be required on the standard CB registration page. Not requiring them will simply make it so that JFBConnect could save a user who doesn't have these fields, for some reason.
b) Run the "Sync Users" feature of CB to import any users from Joomla that aren't properly created on their own. That way, you don't have to run the SQL manually.
Additionally, make sure that the other CB fields you have setup aren't marked as required. If *any* required field is not filled out by JFBConnect (either because you don't have an import mapping setup or because that user doesn't have that field in their social network profile), CB will not let us save the user. Thinking about the above actually, it's possible the user's first/last name was imported, but some other field wasn't, which made it so the CB user data wasn't saved. I hope that last part makes sense.
Please let me know if that helps explain things, but if you have any questions, just let me know.
Thanks,
Alex