By RICHARD TAYLOR on Thursday, 17 January 2019
Posted in Technical Issues
Likes 0
Views 557
Votes 0
When setting up LinkedIn auto-posting, creating the linkedin app using your out-of-date documentation and then Authorising EasyBlog I get 5 blank select's in "Select Company To Autopost To" and posting fails. If you update your documentation on Linkedin then I can check I've done it correctly before going further?
Hey Richard,

It seems like Linkedin updated their app configuration page again and the whole workflow also quite different now.

From what my research, it seems like that we are required to apply for the LinkedIn Partner Developer Program in order to gain enough access to the API.

https://business.linkedin.com/marketing-solutions/marketing-partners/become-a-partner/marketing-developer-program#get-started

Currently I am not really sure whether really need to apply this to access API or not, but I already submit my application to review, you can check my attached screenshot below.

Because now Linkedin returning this response when trying to get the Linkedin user account data e.g. company page.


string(60) "https://api.linkedin.com/v1/companies/?is-company-admin=true" array(2) { ["linkedin"]=> string(282) " 403 1547791145037 3ST9OILU3B 0 Member does not have permission to get companies as admin. " ["info"]=> array(26) { ["url"]=> string(60) "https://api.linkedin.com/v1/companies/?is-company-admin=true" ["content_type"]=> string(22) "text/xml;charset=UTF-8" ["http_code"]=> int(403) ["header_size"]=> int(530) ["request_size"]=> int(532) ["filetime"]=> int(-1) ["ssl_verify_result"]=> int(20) ["redirect_count"]=> int(0) ["total_time"]=> float(0.531) ["namelookup_time"]=> float(0) ["connect_time"]=> float(0.078) ["pretransfer_time"]=> float(0.203) ["size_upload"]=> float(0) ["size_download"]=> float(282) ["speed_download"]=> float(531) ["speed_upload"]=> float(0) ["download_content_length"]=> float(282) ["upload_content_length"]=> float(0) ["starttransfer_time"]=> float(0.531) ["redirect_time"]=> float(0) ["redirect_url"]=> string(0) "" ["primary_ip"]=> string(11) "103.20.94.4" ["certinfo"]=> array(0) { } ["primary_port"]=> int(443) ["local_ip"]=> string(12) "192.168.1.31" ["local_port"]=> int(51611) } }


Basically what I mean is this error Member does not have permission to get companies as admin. but I did checked my company page, already assigned to the page admin when i create this company page that time, i think the only thing is do not have enough permission to get this data.

For now you can try submit your application for API access first.
·
Friday, 18 January 2019 14:11
·
0 Likes
·
0 Votes
·
0 Comments
·
I have applied for the program using the link above, and given the ClientID of the APP created previously. The response is

"Thank you for submitting your application for access to LinkedIn’s Marketing APIs.
After reviewing, we plan to reach out within 30 business days alerting you of the status of your application."

I sincerely hope its not going to take 30 days. I'll let you know when anything happens.

Additionally, as a suggestion only, When the auto-posting fails it would be helpful to be able to have an actual reason why it failed, either by showing the JSON/REST response etc. Would probably save you guys some work.
·
Saturday, 19 January 2019 00:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

"Thank you for submitting your application for access to LinkedIn’s Marketing APIs.
After reviewing, we plan to reach out within 30 business days alerting you of the status of your application."

Yes, I also applied this yesterday, because we didn't know if those social network got any update from their end, this is why we can't test this immediately.

I also waiting for their response, do us update if you get some response from Linkedin.

Additionally, as a suggestion only, When the auto-posting fails it would be helpful to be able to have an actual reason why it failed, either by showing the JSON/REST response etc. Would probably save you guys some work.

Thanks for your input, we will see if we can improve this in the future.
·
Saturday, 19 January 2019 10:38
·
0 Likes
·
0 Votes
·
0 Comments
·
Nothing from Linkedin yet, and I'm concerned that their 'application process' states:

We will be gradually granting access to the Ad Tech, Marketing Analytics, Community Management, and Audience Management API programs and will review applications based on your fit and timing. If your application is approved we will email you with next steps. Please note, LinkedIn will not approve every application submitted.

Which fills me with zero confidence. Eitherway we can do nothing but wait and see. Please let me know if you find a way around this that doesn't rely on Linkin's dithering.
·
Tuesday, 22 January 2019 20:38
·
0 Likes
·
0 Votes
·
0 Comments
·
I will discuss with our developer regarding this and see if we can find another way to handle this.

And I will keep you update then.
·
Wednesday, 23 January 2019 11:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Can you try download my attached file and replace into this and see how it goes.

JoomlaFolder/administrator/components/com_easyblog/includes/oauth/adapters/linkedin/client.php

Make sure this table #__easyblog_oauth doesn't have stored any linkedin data.
·
Wednesday, 23 January 2019 19:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Yep, that fixed it. Had to dump records from easyblog_oauth table. I assume this should now show up in the next release? or do I need to keep replacing the file?

Also, as a side note, are you planning in adding auto-post for other networks?

Thanks again.
Rich
·
Thursday, 07 February 2019 21:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Richard,

Glad to hear that the issue has been resolved now. Yes the fix will be included in the next release.

Also, as a side note, are you planning in adding auto-post for other networks?

Currently we do not have any plan for this yet.
·
Friday, 08 February 2019 12:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Well it worked for a while but now we're back here again.

{"linkedin":"{\"serviceErrorCode\":100,\"message\":\"Not enough permissions to access: POST \/ugcPosts\",\"status\":403}","info":{"url":"https:\/\/api.linkedin.com\/v2\/ugcPosts","content_type":"application\/json","http_code":403,"header_size":498,"request_size":903,"filetime":-1,"ssl_verify_result":0,"redirect_count":0,"total_time":0.323098,"namelookup_time":0.004137,"connect_time":0.028722,"pretransfer_time":0.082471,"size_upload":402,"size_download":98,"speed_download":303,"speed_upload":1244,"download_content_length":98,"upload_content_length":402,"starttransfer_time":0.32308899999999996,"redirect_time":0,"redirect_url":"","primary_ip":"185.63.145.4","certinfo":[],"primary_port":443,"local_ip":"","local_port":39988},"success":false,"error":"HTTP response from LinkedIn end-point was not code 201"}
·
Saturday, 18 May 2019 02:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

Perhaps you can start a new thread on our forum regarding this new issue and provide us with your following details so we can better have a check?

1. site backend access

2. FTP access

3. Linkedin login access
·
Saturday, 18 May 2019 10:28
·
0 Likes
·
0 Votes
·
0 Comments
·
That's a great idea, but I'm obviously not going to be posting that stuff in a forum. Please let me know how to securely provide these details and I will.
·
Saturday, 18 May 2019 18:46
·
0 Likes
·
0 Votes
·
0 Comments
·
The reason why I request you start a new thread on our forum is because it would help other moderator easier to follow up your current issue if I am not around since this is different error if you compare with your initial issue.

By the way, you can include your following details under https://stackideas.com/dashboard/site , this part only our moderator can able to access it.

1. site backend access
2. FTP access
3. Linkedin login access
·
Sunday, 19 May 2019 12:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Continued on new ticket as requested.
·
Monday, 20 May 2019 19:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Richard, we will continue check on this on your new ticket.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.
·
Tuesday, 21 May 2019 07:52
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post