I am trying to integrate 6.x-2.1-beta1 into a working web site that uses Content Profile Registration. None of the Content Profile fields are available for mapping in the Janrain config screens.

When users use the Janrain login widget for the first time, none of the Registration form fields are pre-populated. Not even the username and email.

I found the patch for 6.x-1.x (http://drupal.org/node/885954) but the code is very different in that version. I am hoping that someone is working on this feature or can help me with a new patch.

CommentFileSizeAuthor
#12 interdiff-1197012-10-12.txt11.73 KBkalman.hosszu
#12 1197012-12.patch12.1 KBkalman.hosszu
#10 content_profile-1197012-10.patch13.53 KBfinne

Comments

pdumais42’s picture

pdumais42 commented

Is this working now or is there a roadmap for supporting Content Profile and Content Profile Registration in the 6.x-2.1 release?

http://drupal.org/project/content_profile

geokat’s picture

geokat commented

Not that I know of.

pdumais42’s picture

pdumais42 commented

Thanks for the quick reply geokat. That is disappointing. The 2.x release is the one we need - but we have already deployed with Content Profile.

Someone posted a patch to support Content Profile fields in version 1.3. http://drupal.org/node/885954#comment-3774390 The 2.x code base appears to be a complete rewrite. I cannot see how I can take what was done in the 1.3 patch and start doing "the same thing" in the 2.1 code. Would you agree or am I just not trying hard enough? I admit I asked here before I spent too much time trying. I didn't want to duplicate effort if it was already in development elsewhere.

There are over 31,000 web sites using Content Profile. Many could be using Janrain if they had the option.

How best can I help to add this feature to the 2.1 branch?

reinis.berzins’s picture

reinis.berzins commented

A temporary solution is to use this module: http://drupal.org/project/auto_nodetitle to generate a title field value of the Content Profile node, using a token. Otherwise first login would display an error alert and ask to complete the Content Profile information manually.

jim kirkpatrick’s picture

jim kirkpatrick commented

Subscribe... I used the patch in #885954: import profile data into sites using the content profile module for profiles before and it worked very well...

Anonymous’s picture

Anonymous (not verified) commented

I need this feature too, I'll be glad to help if I can.

Anonymous’s picture

Anonymous (not verified) commented

hi,
Could you be more specific on the process to accomplish this please ?
I really have to find a solution, even a temporary one, to map fields to content profile.
We've subscribed to a "plus" account on Janrain and are now really disappointed...

Thanks.

venusrising’s picture

venusrising commented

We were considering janrain but the lack of content profile support is a dealbreaker

Anonymous’s picture

Anonymous (not verified) commented

Since Janrain's main concurrent costs now 20K$ per year, I don't have any other solution that trying to adapt something for this one...

finne’s picture

finne
Primary language Dutch
Location Amsterdam
commented
Version: 6.x-2.1-beta1 » 6.x-2.3
Status: Active » Needs review
StatusFileSize
new content_profile-1197012-10.patch13.53 KB

I had to implement importing Janrain 6x-2.3 data into Content Profile fields. This is the patch I wrote. I tried to remain generic. Currently the import works only on connecting an account or logging in, not on user register. There is a hook to map custom data fields in your own submodule. The basics only work when the content profile field is singular and a simple data type. I hope others can use this too.

addmysupport’s picture

addmysupport commented

Hi,

I had the original issue I created at http://drupal.org/node/1890628 marked as a clone of this Content Profile feature request.

We use Content Profile on a Drupal 6 website. This is not compatible with Janrain Engage default module for Drupal.

Content Profile is a common D6 module used on over 25,000 sites.

We have a Janrain pro license (basically we pay for it.)

I have lowered my ambitions (and hopes) for using Janrain Engage and would be happy to find a solution that does not include all the available field mapping options and only makes Janrain Engage work to:

1. Allows user to log in with Janrain Engage and create an account on our site.

2. Add more than one social profile to an account "Linked accounts" and allow login with any one of these (a lower priority)

To achieve the initial registration step Drupal only needs to map:
Email
Username

If this can create the user account they can then be directed to complete the optional form details after log in. (e.g. redirected to the profile edit form after using Engage to create the account)

There are patches to the main janrain engage drupal module. See the drupal.org module issues page http://drupal.org/node/885954 but these are for the 6.1 version not 6.2

The patch suggested above - #10, Posted by finne for 6.2 - suggests it doesn't allow new user registration which is my primary need.

Background
Janrain 6.x-2.3 is already configured on our system - but currently shows a token error due to incompatibility with our use of Content Profile mentioned above. Once we switched off Content Profile users could register but their name data was missing (blank profiles) and normal registrations were not possible due to missing registration form fields. this is documented in http://drupal.org/node/1890628

Can anyone assist with this?

(Sorry George... but Janrain Engage have been hopeless and left me stranded!)

Thanks
Chris

kalman.hosszu’s picture

kalman.hosszu commented
Issue summary: View changes
StatusFileSize
new 1197012-12.patch12.1 KB
new interdiff-1197012-10-12.txt11.73 KB

I fixed the coding standards of patch.

kalman.hosszu’s picture

kalman.hosszu commented
Version: 6.x-2.3 » 6.x-2.x-dev

I forgot to change the branch.

rebekahgolden’s picture

rebekahgolden commented
Status: Needs review » Closed (won't fix)

We're expanding field mapping in the new version of our module for Drupal 7. With hooks and rules you should be able to write connectors between these two modules. We no longer support Drupal 6.

Thanks! Rebekah