Closed (duplicate)
Project:
LinkedIn Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 May 2010 at 14:37 UTC
Updated:
4 Jan 2011 at 19:06 UTC
Jump to comment: Most recent file
Comments
Comment #1
socialnicheguru commentedit only happens when I goto to /user page.
Comment #2
socialnicheguru commentedThis error doesn't occur if I select 'tab' on admin/settings/linkedin
does occur if I select 'block' or 'hidden'.
Comment #3
bellesmanieres commentedHi. Might be related with the tab still present in the menu router. Could you try replacing linkedin.pages.inc with the one attached (replace .txt with .inc) ?
(got to go now, so I won't follow up today)
Comment #4
socialnicheguru commentedno didn't work
Comment #5
bellesmanieres commentedAnother try with all caches clearing. #1 and #2 make me think it has to with the tabs menu entry being still present when switching from the tab display.
Once the file is in place, don't forget to go to admin/settings/linkedin and change the display.
Comment #6
socialnicheguru commentedeven after replacing the last file, I get the same error.
entering Tab on /admin/settings/linkedin is fine
entering Block gives me a white screen and same exact error
Comment #7
janwalhof commentedI get the same error: (after hit tab to show linkedin profile).
Fatal error: Call to undefined function linkedin_get_profile_fields() in /www/x/y/z/mysite.nl/public_html/sites/all/modules/linkedin/linkedin.module on line 183
I tried the attachments @3 and #5 without result.
Regards,
Jan Walhof
Comment #8
bellesmanieres commentedShould be be fixed by new version.
Comment #9
Brian Keller-Heikkila commentedThe new version does not work for me. When I click on "Login using LinkedIn" I get the same Call to undefined function linkedin_get_profile_fields() in /var/www/html/.../sites/all/modules/linkedin/linkedin_profile/linkedin_profile.module on line 96
I notice it's a different line now, but same error message. I tried flushing cache but that did not help.
Comment #10
bellesmanieres commentedReopening this.
1. Did you try uninstalling and re-enabling all submodules ?
2. Are you using a standard Drupal install (I see SocialNicheGuru is using Atrium, there might something there, even if it is unlikely) ?
Comment #11
entrepreneur27 commentedI am having a similar problem. I just installed this module because it looks great. If I try and login or if I try and go to "My account" I get this message:
Fatal error: Call to undefined function linkedin_get_profile_fields() in /home/username/public_html/develop/sites/all/modules/linkedin/linkedin_profile/linkedin_profile.module on line 96
I am using the latest Acquia distribution, but I have quite a few contrib. modules including content profile and login toboggan.
Comment #12
deltab commentedI have Content Profile, Realname, Realname Generate, Content Profile Tokens and Panels along with LinkedIn module. On the first install, it worked fine for me. On reinstall, the same error as reported above.
Disabling all the other profile related modules does not help. I tried deleting all LinkedIn fields from database and re-installing. That did not work either.
Comment #13
socialnicheguru commentedI filed another issue because I noticed that I am getting a similar error caused in a sub module of linkedin. http://drupal.org/node/950140
Comment #14
maddentim commentedHello. Having some weirdness with this after I tested posting a status update to linkedin. Then when I went back to the url didn't work. Not for the pathauto url, but the clean url "node/nid". Drush also got hung up and wouldn't work. Just a WSOD or occassionally, the fatal error "call to undefined function linkedin_get_profile_fields".
Looking at where this error is called on line 116 of the linkedin.inc file, the arguments seem wrong.
What is array('id'), TRUE? Should it be array('id' => TRUE) or just array('id') or really just nothing? The second function of the argument is $fields = array() and is used to hold the fields we want to get from linkedin. I am thinking that we are requesting the 'id', so we should ditch the ", TRUE". I am going to see if this works better. Anyone know what is going on here? Am I on the right track?
EDIT: This didn't fix the issue, but I still think it looks wrong.
Comment #15
maddentim commentedNow I am looking at the value stored in the drupal variable table called linkedin_profile_user_page_linkedin_fields
Somehow, some of the in the array fields are duplicated. Once that stops you start getting a string followed by an integer... Something looks afoul. Will look at it further.
Comment #16
maddentim commentedThis is ok I believe. The values have i:0 are not selected.
Comment #17
spiderglow commentedIm having the same problem. Suscribing
Comment #18
janwalhof commentedStill (#7) I'm having the same problem. It's a pitty. Subcribing
Comment #19
maddentim commentedsee here: http://drupal.org/node/950140#comment-3681174
The solution suggested here may help.
Comment #20
bellesmanieres commentedRedirecting this #950140: WSOD: Call to undefined function linkedin_get_profile_fields() in linkedin/linkedin_profile/linkedin_profile.module on line 96, as it provides more infos.