Active
Project:
Janrain Social Login
Version:
7.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Oct 2010 at 15:56 UTC
Updated:
13 Jul 2012 at 05:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ericdrogers commentedDitto!
Comment #2
kreynen commentedsubscribe
Comment #3
kreynen commentedThis patch just adds the CiviCRM field options to the UI. Additional code needs to be added to rpx_core.module to actually process the values. I might be missing something, but it looks like it will be relatively easy to add additional code to process the CiviCRM values if CiviCRM in enabled the way Profile2 is handled in the _rpx_import_user_data function.
Comment #4
Anonymous (not verified) commentedSubscribe
I did not see any CiviCRM code in rpx_ui.module. Is CiviCRM Profile field mapping already part of the current version, at this moment 7.x-2.1?
Are there plans to integrate civicrm mapping in Janrain Engage (formerly RPX)?
On civicrm.org I saw a post from kreynen: http://forum.civicrm.org/index.php/topic,19941.msg83221.html#msg83221. They speak about webform-civicrm (and Profile2) as possible solutions for this problem. Is this issue solved in webform-civicrm (or Profile2)? I cannot find any issues in these modules.
My main question, is CiviCRM Profile field mapping already posible and how can that be done?
Comment #5
petednz commenteddoes this relate to the profile2 module and if so how?