Import social profile data to specific table

JFBConnect uses the standard Joomla User component for storing the basic user profile information. That component only stores name, email and password information. If you want extended information, like first name and last name, you'd need to use an additional extension.

One option that may work for you is the User - Profile plugin that comes with Joomla. That plugin has an xml file which you can edit to add your own custom fields to be asked during registration. JFBConnect has a Social Profiles - Joomla plugin which would let you select how to import social network profile data into the user's extended profile.

The one problem with that method, however, is that the 'name' field for core Joomla will still display, which could be confusing. There's nothing we can do about that in JFBConnect as that field is a requirement of Joomla.

I hope that helps explain,
Alex

We haven't used Easy Profile yet, but I know there are a few JFBConnect users that have them working together.

The Custom DB plugin was meant for just such a circumstance and may work with Easy Profile. Basically, to configure it, you need to:
* Enable the plugin
* In the JFBConnect -> Profiles -> Custom DB section setup your database properly:
* You can leave the database name, user and password blank since you're using the Joomla database
* Set the table name to whatever table Easy Profile uses to store data
* Click "Save"
* In the bottom portion, you should now be able to set which column of the selected table is used to store profile data from each network

Test and, hopefully, that helps get you going.

If you have any questions, just let us know.

Thanks,
Alex

1) We haven't heard of this problem before and will have to look into how better to handle it in the code. For now, I'd recommend editing /plugins/socialprofiles/customdb/customdb.php. Around line 103 at the bottom, you'll see a line that looks like:Right before that, add the following line so it looks like:That should bypass that error and let you re-configure the table name. Once set right, remove that extra line to configure.

2) We don't have a way to pre-fill EasyProfile fields on the fly. However, you should be able to import data into those fields using the Custom DB profile plugin, assuming the profile data and registration data are stored in the same table. That way, when the user goes to the Edit Profile page, the values are already populated as though they filled them in already.

3) Facebook looks to have recently added an "Address" field that is retrievable for each profile. We'll have to look into this more because it seems to allow you to get the users street address, city, state and country, which I'm very, very surprised about. Until this change, all we could get was the "Current Location" field, which was a pointer to a Facebook Page for the user's city. It was a lot more kludgy to get information like city, state and country from that, but possible.. it's also why we just have "Current City, State" as an import option and not country.

I've added this investigation to our to-do list.

I hope that helps, but if you need anything else, just let me know.

Thanks,
Alex

But Custom DB profile plugin is just to import data from social profiles not custom options, right?

Correct. Possibly I'm mis-understanding what you want to do though. Basically, I thought you were wanting that after the user is logged in, they are redirected to their "Edit Profile" page with the data pre-filled on that page with some of their social profile data.

If so, then the Custom DB should be able to help here by pre-populating the data in the EasyProfile database. During registration the data will be imported. The user won't be able to prevent this but, when they are redirected to the Edit Profile page, Easy Profile should be showing the data that JFBConnect stored in the DB for the user. At that point, the user is free to change the data if they want.

I hope that makes sense, but if not, or you if you're looking for something different, please describe it specifically and how its different than what I noted above.

Thanks,
Alex