Hi Hassan,
I have tried sharing a stream item in my local and it seems to share the link correctly. Am I missing something here?
For the url in the screenshot, are you referring to the url below the image and content? If that is so, only your domina url will be shown and not the specific post url. Once you share on FB, when you click on the shared item it will still direct you to the specific post.
If your issue is relating to the url when clicking on the stream item, perhaps you can provide us your backend and ftp access at http://stackideas.com/dashboard/site so we can help you check this out? Can you also inform us which stream item you want to share so we can help you test?

Hello Raymond,

Thanks for the response.

Yes, I was referring to the URL in the screenshot below the image and content.

If the URL, Image and content remain the same for each share, and not specific those who see it on Facebook may not know there is any difference between different shared posts and may not see the need to click to read the full post on our site.

On Twitter, it is ok as it is as the actual URL of the stream is visible, but for Facebook and Linkedin where the site description is also included, this can cause some confusion and not achieve desired results.

Is there no way this can be addressed (so that the actual content is what is displayed) any time soon?

Regards

Hassan

Hey Hassan,
By right different shares should contain different images and content. Can you provide us access as mentioned above and the post experiencing this issue so we can better investigate this?

Hey Hassan,
To add to my reply, how Facebook share works is that Facebook will grab the content from your site. This means that if your content is not accessible to them(restricted permission), then FB would not be able to grab the content. You should treat Facebook as a guest user. So whichever content not accessible to guests, the same will apply to Facebook. This results in FB not being able to retrieve the data. Try clicking on the link below as a non-logged in user and see if you can access it.
http://take.ms/cnNmO
If you cannot view the page as a non-logged in user, then Facebook will also not be able to retrieve the image and content of that stream from your site.

Hello Raymond,

So what is the way out of this because I am sure a lot of users will want to use the Social Share to share their posts to Facebook?

I have tried it even with posts that I have set to be viewable by the public.

Hassan

Hey Hassan,

I am sorry for the delay of this reply,

I've checked in this public stream (http://www.icom.ng/belong/stream/item/101), when I view this page source ( view-source:http://www.icom.ng/belong/stream/item/101 ) I noticed there got 2 `og:description` tag, another one is come from jfbconnect.

For some reason, Facebook always take jfbconnect og:description instead of Easysocial og tag, you can check my attached screenshot below. May i know is there a way temporary disable jfbconnect og:description tag?

Hello Arlex,

I got across to the guys at JFBC and they suggested the following:
"If you'd like to disable specific tags like the description and image tags from being set by JFBConnect, I'd suggest going into JFBConnect backend and updating our Skip Tags setting. In the JFBConnect > Open Graph > Configuration tab and setting 'Skip Tags' to be "og:description,og:image". Let us know if you narrow anything down to JFBConnect causing the issue and we'll gladly help. "

I followed the step to skip the tags but the result is still the same.

Regards

Hassan

Hello Raymond,

I have created new posts and made them public but the result is still the same.

I also used the Facebook debugger as recommended on a public post. Please see the result also attached.

[Warnings That Should Be Fixed:


Inferred Property - The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property - The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Parser Mismatched Metadata - The parser's result for this metadata did not match the input metadata. Likely, this was caused by the data being ordered in an unexpected way, multiple values being given for a property only expecting a single value, or property values for a given property being mismatched. Here are the input properties that were not seen in the parsed result: 'fb:app_id, og:locale:locale, og:site_name'


See attached.

Thanks

hey Hassan,

I am sorry for the delay of this reply,

Perhaps you can share with me which stream post you trying to share? Because in Easysocial have different kind of stream type, once you provide us those stream URL, then I will troubleshoot on this.

You can check my attached screenshot below, how to get the single stream permalink from the dashboard.

Hello Arlex,

Thanks for your patience. I think it is working fine now. I have tried sharing all the public posts and they are sharing as they should.

Kind regards

Hassan

Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.