Hey there,

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

Regarding this issue, I think you have to manage your blog URL format first then temporary disable your site compression (Javascript/CSS) setting from your server or 3rd party plugin first.

Because Facebook unable to retrieve your opengraph meta data from your single blog entry page.

Ok I will try this but I think it's something more.

If you go to my template style settings and click on galatea default, then click on base outline from the dropdown on the left, then page settings, you'll see that I have configured OG settings into the head. Could these be over riding all other OG tags ?

Maybe I should only set those for the homepage and not all pages ?

Ok I will try this but I think it's something more.

If you go to my template style settings and click on galatea default, then click on base outline from the dropdown on the left, then page settings, you'll see that I have configured OG settings into the head. Could these be over riding all other OG tags ?

Currently I am not really sure is it because of this caused this, but you can give it a try.
Based on what i checked, if this override the original Easyblog opengraph meta tag data, that Facebook debugger tool should able to retrieve those opengraph meta tag what that template overridden it, but it seems like that is not, because Facebook unable to retrieve the correct opengraph meta data, look like some where cached the HTML.

Hi

the issue is resolved for bunnylifestyle but still happens for myvirtualgaming

for myvirtualgaming, the og tags are coded into my master template header, could this be the case?

You can see here that all autoposted EB and EA content just shows my main OG image with generic text

https://www.facebook.com/mvghockey/?ref=bookmarks

It seems like your vghl.myvirtualgaming site template did hardcoded Opengraph data on any pages at header, this is why Facebook already use this Opengraph data to populate your preview link, you can check my attached screenshot below.

May i know where you added this on your site? Is there a way temporary to remove it?

Once you remove these code, you have to temporary disable your site JCH plugin, so it will load the latest changes.

Hi,

It is in my main template rtcorvus index.html

If I remove it from there my website doesn't have any images or text when I share my website. Is there a workaround for this?

I've applied some fix into your template index.php file, those extra Opengraph data only populate on the site if that is not Easyblog and Joomla article page, you can check my attached screenshot below.

So Facebook can able to retrieve the correct blog title, image and content now, but i realised the image still doesn't populate on the Facebook preview, I am not really sure what is the reason and Facebook doesn't return any error.

Perhaps you can wait for few days and recheck again regarding this.

I see the same issue as well for EA articles but havent tested EB yet.

One issue now though is the image I had saved as my og_image is no longer being pulled and FB is using a random image

https://developers.facebook.com/tools/debug/sharing/?q=vghl.myvirtualgaming.com

Actually, FB is completely ignoring my OG data now and filling it in on its own

Inferred Property
The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Missing Properties
The following required properties are missing: og:url, og:type, og:title, og:image, og:description, fb:app_id

I did applied some fix into your template index.php file , Facebook should able to respect your specific og:image now. http://take.ms/NjirV

I see the same issue as well for EA articles but havent tested EB yet.

I think i did explained you before, Joomla article page doesn't render Opengraph data by default, you have to take a look which 3rd party plugin can able to support this from https://extensions.joomla.org/tags/open-graph/ .

Basically EasyArticle component is just allow user can easier to manage their article post in frontend, it doesn't involved any the article layout stuff.