Topic-icon Linkedin and Community Builder profile mapping, correct fiels?

Active Subscriptions:

None
9 years 4 months ago - 9 years 4 months ago #60785 by socialemotional
I've searched the forum and didn't find a solution for the following:

I've got a profile in Community Builder (CB) and when I link an account from Linkedin (LD) or create an account via the LD sign-in, it was meant to map the profile fields but it doesn't get the propper fields, and/or I can't map to the correct fields.

For example:

CB_company field, should map to LDs what? (I have tried the "Current Status/Last Share", but gives me unexpected content)
CB_job, I've tried LDs "Current Position", but doesn't seem to be the correct one!

So, can someone tell me which fields should I use to map to the current company and job? (I can't find any of those in the configuration).

Also, why doesn't it show/allow me to define other CB fields? I can only map the name, middlename, last name and these two, I have more CB fields that don't show up at the SourceCoast Configuration... I've realized that the other fields are not text fields, that's why it doesn't show in the configuration.
Last edit: 9 years 4 months ago by socialemotional.
The topic has been locked.
Support Specialist
We currently display this information in the "Current Position" field. It has information for Position Title, Company Name, Date the position has been held and a description of the Position. I'm going to send you a PM with some code changes that will allow you to map these fields individually. It's been tested briefly on my test site, but needs more detailed tests. But you can check it out and see if it helps you. If so, I'll add it to our tracker for the next release.

Current Status/Last Share is the last post in your feed (within a certain timeframe) so it's not what you want.

-Melissa
The topic has been locked.
Active Subscriptions:

None
It worked, thanks! I hope in a future version it goes into production, I don't like modifying core files.

One thing that is not working as expected is when I link to an account (by entering the username and password), it is not getting the fields from LD (although it links it and I can now log-in via the LD button).

It works when linking to an existing user with the same email (I have that link setting in the configuration).

Also, in my dev environment (my computer), it doesn't give me the option to select an existing user account, but in the dev machine (the same as the production) it does show it.

Do you know why these two sittuations happen?
The topic has been locked.
Support Specialist

It worked, thanks! I hope in a future version it goes into production, I don't like modifying core files.

I should be able to put this in the next release easily. I've added an issue to our tracker so I don't forget.

One thing that is not working as expected is when I link to an account (by entering the username and password), it is not getting the fields from LD (although it links it and I can now log-in via the LD button).

We only perform the profile import on log in to the Joomla site. So if the user logs out and logs in with the LinkedIn credentials, then the profile data should then be imported.

It works when linking to an existing user with the same email (I have that link setting in the configuration).

The profile data gets imported on login so using the login button with that setting should be expected to work.

Also, in my dev environment (my computer), it doesn't give me the option to select an existing user account, but in the dev machine (the same as the production) it does show it.

Could you describe this a little more or maybe show a screenshot? Maybe I haven't had enough coffee yet :) but I don't know where you're expecting to see the option to select an existing user account and it's not happening.
The topic has been locked.
Active Subscriptions:

None
9 years 4 months ago - 9 years 4 months ago #60831 by socialemotional
About the issue that I reported:
"Also, in my dev environment (my computer), it doesn't give me the option to select an existing user account, but in the dev machine (the same as the production) it does show it."

Some details first:

If I click in the sign-in with Linkedin, and my LD user doesn't have an email that matches any user in my site.

In production it shows the registration componente with the login option (to log-in with an existing user, thus mapping this user to the LD user), which is what is expected:
http://imgur.com/a/oUFPd

In dev, the login part is missing, even though the settings in both sites are exactly the same (the production was a clone from the dev, although I cannot swear that some settings could have been changed afterwards, but I am almost certain it hasn't).
http://imgur.com/a/YYuAE

The only difference between the two environements is that the dev is on my computer, and not connected to the outside as the production is, and also the PHP version in dev is 5.6.10, while the production is PHP 5.3.17 (ouch!).

Do you know what could be the problem?

(The images are not showing in the post, please click them to view).
Last edit: 9 years 4 months ago by socialemotional.
The topic has been locked.
Support Specialist
The setting that controls whether you can link to an existing account is JFBConnect > Configuration > General tab > Normal Registration tab > 'Registration Display Mode'. For sanity, could you again verify that it is not set to 'Register Only' on your dev site where it's missing.

If the value is set to Vertical or Horizontal, then I'd suggest inspecting the page in your browser's developer tools or looking at the page source to see if the login section is there, but just hidden. Look for the div with the id "jfbc_loginregister_existinguser"

Unless you've done a template override of our login/register view, those would be the two most likely causes.

-Melissa
The topic has been locked.
Active Subscriptions:

None
It was with Register Only in both (which by design shouldn't show the login form in the first place!), that's odd!

I've changed it to "vertical" and it is ok (and as I wanted it).

I'm leaving it as it is since this is not a problem any more for me, it will become a ghost bug :)
The topic has been locked.
Support Specialist
Glad it's resolved now. By the way, I've already put the code for the mapping the LinkedIn fields individually into the next release and I'll be working on testing it more.
The topic has been locked.