Project

General

Profile

Actions

Feature #7292

closed

LinkedIn link on member page

Added by Raffi Khatchadourian almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Daniel Jones
Category name:
-
Target version:
Start date:
2017-01-01
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Could there be a form to add a LinkedIn profile URL at the member page (e.g., https://commons.gc.cuny.edu/members/khatchad)? There is already one for twitter and GitHub. Thanks!


Files

bp-social-media-profiles.diff (1.49 KB) bp-social-media-profiles.diff Boone Gorges, 2017-01-05 11:38 AM
Actions #1

Updated by Raffi Khatchadourian almost 8 years ago

Interestingly, there is a field for LinkedIn on https://commons.gc.cuny.edu/members/khatchad/profile/edit/group/1/. But, despite populating that field, I don't see a LinkedIn line on the profile.

Actions #2

Updated by Boone Gorges almost 8 years ago

Thanks for the report, Raffi.

There was a bug in the way that the Commons's profile fields were being mapped onto the social media sites, such that the lookup was failing when the name of the profile field (such as "LinkedIn Profile Link") wasn't exactly the same as the social network's name ("LinkedIn").

Dan, I think you were the last to touch this. I've attached the patch that I've applied as a hotfix to the production site. It seems to correct the logic for me, but I would like a second look from you.

Actions #3

Updated by Boone Gorges almost 8 years ago

  • Target version changed from 1.10.7 to 1.10.8
Actions #4

Updated by Raffi Khatchadourian almost 8 years ago

I see it.

Actions #5

Updated by Boone Gorges almost 8 years ago

Thanks, Raffi.

Dan, I've still got the hotfix in place. When you get a chance, please have a look to see if my change makes sense.

Actions #6

Updated by Boone Gorges almost 8 years ago

  • Target version changed from 1.10.8 to 1.10.9
Actions #7

Updated by Daniel Jones almost 8 years ago

Hey Boone and Raffi - sorry about the long delay here. The change looks right to me. Should I push it to 1.10.x or is it better for you to handle that end, Boone?

Actions #8

Updated by Boone Gorges almost 8 years ago

Cool - thanks, Dan. If you could implement and push, that'd be great. Thanks!

Actions #9

Updated by Boone Gorges almost 8 years ago

  • Target version changed from 1.10.9 to 1.10.10
Actions #10

Updated by Boone Gorges almost 8 years ago

  • Target version changed from 1.10.10 to 1.10.11
Actions #11

Updated by Boone Gorges almost 8 years ago

  • Target version changed from 1.10.11 to 1.10.12
Actions #12

Updated by Boone Gorges over 7 years ago

  • Target version changed from 1.10.12 to 1.10.13
Actions #13

Updated by Boone Gorges over 7 years ago

  • Target version changed from 1.10.13 to 1.10.14
Actions #14

Updated by Daniel Jones over 7 years ago

Actions #15

Updated by Boone Gorges over 7 years ago

  • Status changed from Assigned to Resolved

Thanks!

Actions

Also available in: Atom PDF