Needs work
Project:
LinkedIn Integration
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2011 at 10:15 UTC
Updated:
21 Mar 2012 at 15:29 UTC
Jump to comment: Most recent file
Comments
Comment #1
kotnik commentedOk, patch that you can find here can be applied to 6.x-1.x-dev of Linkedin module.
Basically, this patch makes registration with Linkedin possible. When you try to login with Linkedin account, if there is no user associated with that Linkedin account, one will see registration form and upon entering all required fields a new Drupal account will be created that is connected with Linkedin account.
Comment #2
davad commentedThanks. This might be just what I need for a project I'm working on.
Comment #3
davad commentedLooks good. I rerolled it so it can be applied from within the module's directory, and I removed the old line of code you commented out.
Comment #4
davad commentedCommitted the patch to git.
Comment #5
amrit_b commentedWhy dosen't it creates a new user in Drupal and logs him in to the system as soon as you click in connect linkedin button?
@davad: Is it okay if I submit a patch for this?
Thx
Comment #6
shaneonabike commentedSorry to re-open this issue but this patch doesn't seem to work (if I should create a new issue I can do that sorry I don't know the protocol with that stuff).
Here are a few issues:
* The returned form is has no submit button in my usage
* You are setting $form['name']['#default_value'] = $data['name']; when there is no $data object
Comment #7
shaneonabike commentedAlso I noticed in debugging that your call to drupal_prepare_form doesn't seem to work properly.
If you have content profile installed then it seems to sorta destroy the form and you lose the submit button. It's not clear to me why yet but I think it's due to a form_state value that is not being set.
PS - The only way to patch this was to literaly remove that prepare line and now I can actually submit and it works.
Comment #8
davad commented@ShaneOnABike If this patch isn't working for you on an install with just drupal and this module, you are more than welcome to reopen this thread and post any information you find or patches you roll. If it looks like it's being caused by a conflict with another module, like the content profile, please open another thread with the relevant details and a link back to this one.
Comment #9
shaneonabike commented@davad: Great! I have a solution that seems to be working for the most part. I need to change a few things b/c Content Profile is not getting called and I think it's a similiar issue to #761254: not working with content profile module ? or #277512: Using drupal_goto in form submit handler prevents the use of multiple submit handlers
I'll roll a patch and get back to you.