I believe it could be some compressors that are messing up with the output or some 3rd party plugins are altering the opengraph tags when Facebook tries to crawl the site.

Did you recently installed any plugins on the site?

I did not install any plugins that I am aware of recently. but, I will go look at the list of plugins and try to figure out if anything else changed. I know that one plugin was recently disabled: "System - Highlight" in order to make EasyBlog Posts continue to work with Smart Search. The only other change was to upgrade EasyBlog to 5.0.42. as well as to upgrade EasySocial, EasyDiscuss and Komento.

I did one other thing that has been upgraded recently which is the JCE Editor. I will go to their site and search to see if anybody is having problems after their upgrade. Although, I have almost never had problems with them. Anything is possible. I am running version 2.6.6

Hey Sean,

Based on the Facebook debugger tool result :

Object at URL 'https://www.drcarney.com/blog/entry/incidence-of-teen-stroke-on-the-rise' of type 'website' is invalid because a required property 'og:title' of type 'string' was not provided.

Warning

Curl Error : OPERATION_TIMEOUTED Operation timed out after 10000 milliseconds with 8078 bytes received

It seems like something to do from your server, the reason why Facebook unable to retrieve those opengraph data from your site, it most likely some where compressed and messed up on your page.

May i know do you have use any compression tool from your server like Cloudflare? If yes, is it possible temporary disabled it first?

Reference link : http://stackoverflow.com/questions/25405457/facebook-open-graph-required-property-ogtitle-of-type-string-was-not-provi

Mark and Arlex,

I am pretty sure you are leading me to the right solution. Thank you so much for looking at this.

I do have GZIP compression on in the Global Configuration and I also recently enabled the CloudFront CDN with the idea it would speed things up. But, possibly it is doing just the opposite.

I will turn off the GZIP compression and the CDN settings which I believe I set in EasySocial and/or EasyBlog.

My guess, and hope, is that the problem will resolve itself then.

I definitely NEED to speed up this site.

Thank you, Sean

Thanks for updating us Sean, let us know how this goes.

I am assuming that the og description tags were there before and were provided by EasyBlog and what I am trying to figure out now is what is removing those tags from the page. Does that seem like the right question to solve?

hey Sean,

If you view page source one of your blog article page, you will see that og:description tag appeared on your page but somehow when the Facebook crawl your site page, somehow Facebook unable to retrieve those og tag.

Is it possible temporary turn off your CDN from your server a while or do you have see any compression feature setting, just turn it off temporary so we can see if this related with this issue or not.

Arlex,

I have turned off minifying and compressing in the template and also everywhere else that I found it. I also turned off the CDN.in the EasyBlog Settings->System -> Content Delivery Network

I have set the General System Environment to Optimized and the Javascript Compression Mode to uncompressed.

Hey Sean,

it seems like still the same even you turn off everything those compression stuff from your server or component.

But I found out if I switch to use Joomla Protostar template then paste your link to Facebook debugger tool, it seems Facebook can able to crawl your Easyblog page, you can check my screenshot here : http://take.ms/0qKqM

Then i switch it back to use your current template, then scrape again from Facebook debugger tool, it show back the previous result -> http://take.ms/ZKN1c

Based on this testing, it seems like something related with your server or your current template.

1. Try check with your hosting provider see whether they have limit the maximum request regarding the https response code 0?
2. Do you remember do you have configure anything special only for your site Easyblog? Because i did test on your Easydiscuss page, it seems Facebook can crawl correctly.

Reference link regarding the server response code 0 : http://stackoverflow.com/questions/19858251/what-does-http-status-code-0-mean

Your help and those images are fantastic.

I will ask my template provider first if they have any idea.

I guess I also need to go through all my EasyBlog settings in case there might be a setting in the EasyBlog configuration that is doing that.

I will report back what I find out.

Sean

Sure, let us know how this goes

The folks from JoomlaBamboo reminded me that we had seen this type of behavior previously and that it was related to Facebook not liking to parse gzip compressed files.

Mark and all,

I did some google searches and found that lots of people have this problem. Mine is a bit intermittent. We had previously fixed it with a plug available here: https://extensions.joomla.org/extension/facebookfix/

I had it installed but it did not seem to be working. I removed it and reinstalled it and it appears to be working although not all of the time. I did notice that it seems to work on all my articles pages (articles are also EasyBlog now but are longer than blogs) and interestingly the big difference on the articles pages is that I am not running any of the EasyBlog modules in the sidebar1 and sidebar2 positions.

Anyhow, I am thinking that the total page load size is the actual primary problem. It might just encourage me to simplify my pages because this Facebook debugger seems to want smaller pages and because I have not been able to get my page speeds anywhere close to where they need to be.

Anyhow, I hope this update is helpful to you in case you run into this with anybody else.

Sean

OK. I narrowed this down to getting the Facebook Debugger to work properly if I turn off the four Easy Blog - Posts List modules from the sidebar1 position. I assume this could be something in those modules or it could be what we would call the straw that broke the camels back in that it might just make the page too large once those are enabled.

Basically I can get the debugger working if I turn off those modules. But, then when I turn back on the modules the debugger starts to not function properly.

Here is a page I have been testing on and off with: https://www.drcarney.com/blog/entry/milk-makes-estrogen-levels-rise

I have been submitting it to the Facebook Sharing Debugger and also the Batch Invalidator over and over:

https://developers.facebook.com/tools/debug/sharing/?q=https%3A%2F%2Fwww.drcarney.com%2Fblog%2Fentry%2Fmilk-makes-estrogen-levels-rise

Ah... I see. Now I believe you have figured out a piece of the puzzle that I was missing which is that it appears that the field "total posts to display" was set too high in all the modules and causing the timeouts.

I have reduced the amount of modules displaying and also the amount of posts to display and suspect this is going to fix that facebook problem.

Thanks for updating Sean, glad that your issues are resolved now.