You are here

README.txt in LinkedIn Integration 6

Same filename in this branch
  1. 6 README.txt
  2. 6 linkedin_auth/README.txt
  3. 6 linkedin_status/README.txt
  4. 6 linkedin_profile/README.txt
Same filename and directory in other branches
  1. 7 README.txt
=== LINKEDIN INTEGRATION ===

Maintainers:  Pascal Morin (bellesmanieres) Greg Harvey (greg.harvey) David
Landry (davad) Kyle Mathews (kyle_mathews)

see http://drupal.org/node/919412

/*********************************************
Installation/initial configuration

   1. LinkedIn Integration requires the OAuth.php library. You can either :
          * install the Oauth module from http://drupal.org/project/oauth (both
          * version 6.x-2 and version 6.x-3 are supported). You don't need to
          * activate it, the module only uses the library it provides.  download
          * the OAuth.php library from http://code.google.com/p/oauth/ and
          * specify the full path on the module admin interface
   2. Enable the base Linkedin module as usual.  
   3. Request an API key by registering at 
https://www.linkedin.com/secure/developer and creating a new application. Fill 
the required fields (name, etc) and pay attention to
          * provide an "Integration URL" : this field must match the URL of your
          * server this means you'll need a separate key for each stage or
          * development server.[@todo : is this still true ?] leave the
          * "Callback URL" blank, the module takes care of this.
   4. Configuration : go to admin/settings/linkedin and fill the "API key" and
"Secret key" fields with the keys you got from
https://www.linkedin.com/secure/developer. If you downloaded the library
directly from http://code.google.com/p/oauth/, you should see an additional
"OAuth library full path" field above : don't forget to include the filename.
5. Usage : Users will have to associate their LinkedIn account with their local
Drupal account (at user/%user/edit/linkedin) to use any functionality provided
by submodules.


/*********************************************
Troubleshooting

If you encounter troubles, please check the following points :

    * Integration URL : integration url you gave at
    * https://www.linkedin.com/secure/developer is the actual one from wich you
    * are issuing request.  Callback URL : do not specifiy a callback url at
    * https://www.linkedin.com/secure/developer.  Server time : an out of sync
    * server will issue a wrong timestamp. Linkedin.com requires that the
    * timestamp must be within 5 minutes of accurate.  Permissions : get sure
    * users have the right to use the features provided by the submodule you are
    * trying to use.

Also, the module offers a "debug mode" (see admin/settings/linkedin) that will
try to give useful infos.


/*********************************************
Developer use

If you want to implement you own module, you can use the following :

<?php linkedin_get_profile_fields($uid, $fields = array ()) ?> Fetch fields from
a LinkedIn profile. Copes with public/private LinkedIn profile depending on the
currently logged in user.  Parameters : $uid : the uid of the Drupal user.
$fields : an array of field's names to retrieve (see
http://developer.linkedin.com/docs/DOC-1061 for a extensive list) Return value :
A structured array of fields and their values (or the error message received
from the API as an array)

<?php linkedin_get_fields($url, $tokens) ?> Fetch fields from a LinkedIn
profile.  Parameters : $url : full request url to a LinkedIn API ressource (see
API doc for syntax) $tokens : the user tokens, as an array containing keys
'token_key' and 'token_secret' with their value Return value : A structured
array of fields and their values (or the error message received from the API as
an array)

<?php linkedin_put_profile_field($uid, $body, $field = 'current-status') ?> Let
us 'put' data into user profile.  Parameters : $uid : the uid of the user we
want to access infos $body : The content to be sent.  $field : the field we want
to update. At now, only 'current-status' is available from the API.  Return
value : http answer from the API (or the error message as an array)

<?php hook_linkedin_user_settings_page($form_state, $account) ?> Let modules add
their form elements to the user preferences edit form at
user/%user/edit/linkedin. Must return an array of form elements.

<?php hook_linkedin_admin_page() ?> Let modules add their form elements to the
admin settings at admin/settings/linkedin. Must return an array of form
elements.

<?php hook_linkedin_user_edit_perms() ?> Mainly useful only if you don't use any
of the bundled sub-modules. This function is called from the access callback at
user/%user/edit/linkedin to check if the user has the right to access his own
LinkedIn setting ! It shall return an array of permissions, typically the return
would be the same than the one from your hook_perm().  Note that user is granted
access if he has any permission implemented by a module using this hook. That
mean you cannot deny access through this function and got to make checks in
hook_linkedin_user_settings_page if you want to be selective on what to display
to the user.

File

README.txt
View source
  1. === LINKEDIN INTEGRATION ===
  2. Maintainers: Pascal Morin (bellesmanieres) Greg Harvey (greg.harvey) David
  3. Landry (davad) Kyle Mathews (kyle_mathews)
  4. see http://drupal.org/node/919412
  5. /*********************************************
  6. Installation/initial configuration
  7. 1. LinkedIn Integration requires the OAuth.php library. You can either :
  8. * install the Oauth module from http://drupal.org/project/oauth (both
  9. * version 6.x-2 and version 6.x-3 are supported). You don't need to
  10. * activate it, the module only uses the library it provides. download
  11. * the OAuth.php library from http://code.google.com/p/oauth/ and
  12. * specify the full path on the module admin interface
  13. 2. Enable the base Linkedin module as usual.
  14. 3. Request an API key by registering at
  15. https://www.linkedin.com/secure/developer and creating a new application. Fill
  16. the required fields (name, etc) and pay attention to
  17. * provide an "Integration URL" : this field must match the URL of your
  18. * server this means you'll need a separate key for each stage or
  19. * development server.[@todo : is this still true ?] leave the
  20. * "Callback URL" blank, the module takes care of this.
  21. 4. Configuration : go to admin/settings/linkedin and fill the "API key" and
  22. "Secret key" fields with the keys you got from
  23. https://www.linkedin.com/secure/developer. If you downloaded the library
  24. directly from http://code.google.com/p/oauth/, you should see an additional
  25. "OAuth library full path" field above : don't forget to include the filename.
  26. 5. Usage : Users will have to associate their LinkedIn account with their local
  27. Drupal account (at user/%user/edit/linkedin) to use any functionality provided
  28. by submodules.
  29. /*********************************************
  30. Troubleshooting
  31. If you encounter troubles, please check the following points :
  32. * Integration URL : integration url you gave at
  33. * https://www.linkedin.com/secure/developer is the actual one from wich you
  34. * are issuing request. Callback URL : do not specifiy a callback url at
  35. * https://www.linkedin.com/secure/developer. Server time : an out of sync
  36. * server will issue a wrong timestamp. Linkedin.com requires that the
  37. * timestamp must be within 5 minutes of accurate. Permissions : get sure
  38. * users have the right to use the features provided by the submodule you are
  39. * trying to use.
  40. Also, the module offers a "debug mode" (see admin/settings/linkedin) that will
  41. try to give useful infos.
  42. /*********************************************
  43. Developer use
  44. If you want to implement you own module, you can use the following :
  45. Fetch fields from
  46. a LinkedIn profile. Copes with public/private LinkedIn profile depending on the
  47. currently logged in user. Parameters : $uid : the uid of the Drupal user.
  48. $fields : an array of field's names to retrieve (see
  49. http://developer.linkedin.com/docs/DOC-1061 for a extensive list) Return value :
  50. A structured array of fields and their values (or the error message received
  51. from the API as an array)
  52. Fetch fields from a LinkedIn
  53. profile. Parameters : $url : full request url to a LinkedIn API ressource (see
  54. API doc for syntax) $tokens : the user tokens, as an array containing keys
  55. 'token_key' and 'token_secret' with their value Return value : A structured
  56. array of fields and their values (or the error message received from the API as
  57. an array)
  58. Let
  59. us 'put' data into user profile. Parameters : $uid : the uid of the user we
  60. want to access infos $body : The content to be sent. $field : the field we want
  61. to update. At now, only 'current-status' is available from the API. Return
  62. value : http answer from the API (or the error message as an array)
  63. Let modules add
  64. their form elements to the user preferences edit form at
  65. user/%user/edit/linkedin. Must return an array of form elements.
  66. Let modules add their form elements to the
  67. admin settings at admin/settings/linkedin. Must return an array of form
  68. elements.
  69. Mainly useful only if you don't use any
  70. of the bundled sub-modules. This function is called from the access callback at
  71. user/%user/edit/linkedin to check if the user has the right to access his own
  72. LinkedIn setting ! It shall return an array of permissions, typically the return
  73. would be the same than the one from your hook_perm(). Note that user is granted
  74. access if he has any permission implemented by a module using this hook. That
  75. mean you cannot deny access through this function and got to make checks in
  76. hook_linkedin_user_settings_page if you want to be selective on what to display
  77. to the user.