dnzengou / simple-linkedinphp

Automatically exported from code.google.com/p/simple-linkedinphp
0 stars 0 forks source link

Cannot get all of the comments use coments($uid) function. #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Share a new update in LinkedIn
2. Add more than 10 comments to the new update 
3. Call comments($uid) function with the $uid return by updates($options = 
NULL, $id = NULL)

What is the expected output? What do you see instead?
I want to get all of the comments associate with the new update in LinkedIn. 
But I get only part of the comments, less than 10 comments.

What version of the product are you using? On what operating system?
I use 3.1.1 on Win7

Please provide any additional information below.

I have read the API document in developer.linkedin.com, and I know we can add 
parameter called "start" & "count" to the API call link. I have tried it, but 
it does not always work, I mean sometime I just get "<total="0">".

Original issue reported on code.google.com by ZhouCong...@gmail.com on 10 Nov 2011 at 6:33

GoogleCodeExporter commented 8 years ago
What type of updates are you trying to retrieve (i.e. SHAR, CMPY, VIRL)? 

Does it work for some of the update types? 

Are you seeing this failure when retrieving the comments of VIRL updates only? 

Can you post an actual update key that fails so that I can attempt to duplicate 
the problem?

Thanks

Original comment by p...@fiftymission.net on 11 Nov 2011 at 5:05

GoogleCodeExporter commented 8 years ago
Thanks.

I just want to get the updates of SHAR, and I have not trid the other types.

I will provide you the necessary parameters:

AppKey:7g2io9yhbwir
AppSecret:iTK8j20bGpXpiFGK
Oauth token:3dfc6f3f-49bb-4886-a963-487eb023593e
Oauth token secret:876f85be-66a9-4a1f-86c5-bffcce7fe416
Update key:UNIU-150579907-5538109067945316352-SHARE(This update has less than 
10 comments).
Update key:UNIU-150579907-5540669651547070464-SHARE(This update has more than 
10 comments).

Original comment by ZhouCong...@gmail.com on 11 Nov 2011 at 8:16

GoogleCodeExporter commented 8 years ago
I've verified that the comments() method of version 3.1.1 is working properly 
for key UNIU-150579907-5538109067945316352-SHARE - see this demo:

http://simplelinkedin.fiftymission.net/demo/adhoc/retrieveComments.php

The exact call being made is:

LinkedIn->comments('UNIU-150579907-5538109067945316352-SHARE');

For key UNIU-150579907-5540669651547070464-SHARE, it does indeed return 
<total="0">, but looking at the LinkedIn REST console at 
http://developer.linkedinlabs.com/rest-console/, that share does not seem to 
have any comments, as the following query also returns 0 comments:

http://api.linkedin.com/v1/people/~/network/updates/key=UNIU-150579907-554066965
1547070464-SHARE/update-comments

So in short, the class is returning the exact same values that the platform is 
returning - not sure why you are getting 0 comments returned for that share, 
but check it yourself on the REST console to verify.

Original comment by p...@fiftymission.net on 11 Nov 2011 at 7:27

GoogleCodeExporter commented 8 years ago
Update: The LinkedIn platform appears to intermittently be returning 0 comments 
for shares that have more than one... run the REST console linked above and 
simply re-run it a number of times to see this in action.

So in short, this looks like a bug on the LinkedIn API side. Can you verify you 
are seeing the same thing?

Original comment by p...@fiftymission.net on 11 Nov 2011 at 7:35

GoogleCodeExporter commented 8 years ago
Thanks!

I have tried it at the LinkedIn REST console. I think it's a real bug on the 
LinkedIn API side. 

Thanks again.

Original comment by ZhouCong...@gmail.com on 14 Nov 2011 at 1:00

GoogleCodeExporter commented 8 years ago

Original comment by p...@fiftymission.net on 14 Nov 2011 at 1:19

GoogleCodeExporter commented 8 years ago
FYI, I've verified that this is a known issue with the platform.

Original comment by p...@fiftymission.net on 14 Nov 2011 at 6:16

GoogleCodeExporter commented 8 years ago
Do you mean it is a known issue in LinkedIn platform? And they have not fixed 
it now?

Original comment by ZhouCong...@gmail.com on 15 Nov 2011 at 2:59

GoogleCodeExporter commented 8 years ago
Correct - it is currently a known bug that they have scheduled to fix.

Original comment by p...@fiftymission.net on 15 Nov 2011 at 3:05

GoogleCodeExporter commented 8 years ago
OK, Thank you!

Original comment by ZhouCong...@gmail.com on 15 Nov 2011 at 4:28