This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 179217 - Invalid links to LinkedIn profiles
Summary: Invalid links to LinkedIn profiles
Status: VERIFIED FIXED
Alias: None
Product: www
Classification: Unclassified
Component: Admin (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: leawang
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 04:31 UTC by Jiri Kovalsky
Modified: 2010-02-01 00:16 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2010-01-05 04:31:39 UTC 
Lea, could you please urgently fix not working Keith Davis' account? He specified his LinkedIn URL in an incorrect format and now can't login and so update the information. I tried to do it as an administrator but couldn't get to the right page either.

Please use this URL instead:
http://www.linkedin.com/in/laurin1

Thanks a lot,
-Jirka
Comment 1 Martin Fousek 2010-01-05 06:20:40 UTC 
I got information about Keith Davis' saved social network links and I wasn't able to reproduce the error with logging in (at least on testnetbeans.org) - I saved the same social network links, logouted and logged in successfully again. So there could be also another issue for this account (information for dev team).
Comment 2 Jiri Kovalsky 2010-01-06 02:53:22 UTC 
OK, so one more user needs the same help. Please fix the following two accounts:

laurin1, http://www.linkedin.com/in/laurin1
manikantannaren, http://in.linkedin.com/in/manikantannareniyer

Thank you!
-Jirka
Comment 3 leawang 2010-01-11 12:17:45 UTC 
Sorry for the delay.  Was on vacation.  Both accounts have been fixed in production.

This is due to a bug (missing profile check: "http://(www.)?([a-zA-Z]{2}.)?linkedin.com/(in|pub|profile)/?") that has been resolved on staging and will be in production next week.  Martin, please add an automated integration test for it when you get a chance.  See rev 375453cf7312edc2787c27392079e8d19303d641 for kenai repo.
Comment 4 laurin1 2010-01-11 12:25:49 UTC 
yea!!!! thank you!!!
Comment 5 Martin Fousek 2010-02-01 00:15:12 UTC 
I think that kenai specs are more suitable for testing of this. I also found another mistake in regexp, so I raised new kenai issue (KENAI-1836) for that with the request for adding also some negative test cases in their specs scripts.
Comment 6 Martin Fousek 2010-02-01 00:16:19 UTC 
On the base of "laurin1" comment I'm verifying this issue.