By Quentin Lotts Y0283632-X on Tuesday, 20 October 2015
Posted in Technical Issues
Replies 9
Likes 0
Views 455
Votes 0
Hi,

Since upgrading to latest version when we autopost the link in facebook is incorrect and therefore results in a 404 error.

This is the link structure we are getting:

ourdomain.com/administrator/blog/blog-article-title.html

It was previously correct as follows:

ourdomain.com/blog-article-title.html

Please advise how to correct ASAP as we now have a deadlink on Facebook.

Thanks
No problem Quentin and I do apologize for the inconveniences caused.
·
Thursday, 22 October 2015 19:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Site credentials are supplied with support ticket #230784
·
Tuesday, 20 October 2015 02:42
·
0 Likes
·
0 Votes
·
0 Comments
·
More issues:

Previous Facebook posts show as not having been shared to Facebook but that is not correct.

Also - LinkedIn share - we get success message but the post does not reach LinkedIn. It was previously working fine.

It seems this latest upgrade has caused various issues.
·
Tuesday, 20 October 2015 03:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Please replace the attached file in: ../administrator/components/com_easyblog/includes/oauth/adapters/facebook/ and see how it goes. As for the linkedin, can you provide your backend and Linkedin account access so we can check the configuration? You can provide it in the Site Details below the reply form.
·
Tuesday, 20 October 2015 15:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Why was this client.php file not provided with the latest version of the component? This is the second time that I've been told I need to upload a different version of the file! I've uploaded and the autopost now works correctly with the correct blog post link coming across to facebook.

Can you explain why we had "/administrator" appearing in the blog post link previously?

Also, you have not advised why the autopost icons indicate that posts already previously shared with Facebook have not already been shared. This continues to be the case.

LinkedIn was correctly synchronised previously and 3 blog posts had already appeared there correctly after publishing, and that was as recently as a few weeks ago. So I know those credentials are correct. I cannot supply you with the LinkedIn credentials because you won't be granted access without verification codes, due to your location, and this ends up being a pain for clients. I'll try revoking access and will try re-authorising and will see if that helps.

Meanwhile I'd be grateful for an explanation as to why all these things are going wrong. An upgrade is supposed to improve the situation but in this case it has cost me already 5 hours on non-paid work. I've used easyblog for years and I value it as a component and also the support I receive however it is frustrating when issues keep recurring when upgrading.
·
Tuesday, 20 October 2015 16:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Quentin,

I am really sorry for the delay of this reply and the inconvenience caused.

This is actually a bug when you compose a blog post from your backend where it will include the /administrator path inside the url. This bug were just discovered in version 5.0.28 and will be include in version 5.0.29 later on.

Also, you have not advised why the autopost icons indicate that posts already previously shared with Facebook have not already been shared. This continues to be the case.

I am sorry but I'm not quite understand here. Can you explain on the issue further?

By the way, please note that our forum do not share the same information with our crm system hence we will not able to view your site details if you not include it in this forum. If you are requested to submit your site details, you may do so under the tab Site Details below. Please be rest assured that these information will only be visible to the support team from Stack Ideas. You can also store this in your site details area here, http://stackideas.com/dashboard/site to avoid having to enter these information multiple times.

Thank you for your kind understanding and please advise.
·
Wednesday, 21 October 2015 16:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Why release an upgrade if it's buggy? So you test before releasing it?

The post on LinkedIn wasn't coming across so I had to revoke access and then try again. The post now comes across but with an incorrect hyperlink!

This is what we get: http://domain.co.ukhttp://domain.co.uk/article-title.html

I can't even see how I would set up a redirect link for this in htaccess!

My client as you can imagine is not impressed with this situation and I'm disappointed in your extension.

Please advise how to resolve ASAP.
·
Thursday, 22 October 2015 02:38
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Quentin,

This issue is already fixed in 5.0.29 . Since you haven't updated to 5.0.29 yet, I have manually patched the site and it works fine now.
·
Thursday, 22 October 2015 16:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

I had to revoke access and the reauthorise before the post came across in LinkedIn. It's finally coming across with the correct link. Thank you for patching the site.

Q
·
Thursday, 22 October 2015 19:02
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post