Facebook Publicize, og:desscription field and Jetpack

Thanks for giving that a try. We’ll work on getting this fixed, and I’ll post again here as soon as I have some news.

Jeremy, Just touching base as I haven’t heard any updates on these issues. I’ve been doing the workaround by not touching that 140 character publicize field, which has allowed me to get text published into my FB post. But Twitter still is a problem in that I only get my title and the full URL. Has any of this been fixed yet and I’m just not seeing it yet pushed out to the world?

Has any of this been fixed yet and I’m just not seeing it yet pushed out to the world?

We’re still working on it I’m afraid. I’ll let you know as soon as something changes!

Jeremy, was your team working on the auto-post features on the 4th of July at all? My blog did not post on Facebook tonight (it normally posts at 6pm). I checked the Facebook debugger and saw an error shortly after my blog auto-posted correctly on Twitter and Googleplus, but not Facebook. The error is no longer showing up in the scrape, but I was hoping you could check your logs to see if anything happened around 6pm.

Here’s my blog link that didn’t post, that I had to do manually…

https://thetwelfthstep.com/2015/07/04/thought-for-the-day-117/

Facebook did indeed reject that Publicize post on Saturday. Here is the error we received:

Object Missing a Required Value: Object at URL 'https://thetwelfthstep.com/2015/07/04/thought-for-the-day-117/' of type 'website' is invalid because a required property 'og:title' of type 'string' was not provided.

It seems Facebook wasn’t able to grab the Meta Tags when it crawled your post. It seems ok now, though. Did you temporarily deactivate your Open Graph plugin, by any chance?

If not, your site might just have been too slow when Facebook crawled that post.

Let me know if it happens again!

Jeremy, two things. One, you marked this topic as resolved but we decided we were going to keep it open until you fixed the prior issues above it that dealt with your twitter and Facebook auto post changes including the long URL truncation and the fact that the 140 character field caused the excerpt to not post on FB. Right?

Also, my post was only a one sentence thought with no pictures. What could cause the meta tags to not grab correctly if that’s the case? Could the server running my site been that slow?

Right?

My bad, I had forgotten about that.

What could cause the meta tags to not grab correctly if that’s the case? Could the server running my site been that slow?

It’s hard to say. Your site could be too slow, but it could also be an issue with Facebook’s bot. I’d suggest asking your hosting provider to check your raw access logs, to see if they can see anything wrong when Facebook’s both accessed the site, right after the post was published.

I’m pretty sure it’s probably GoDaddy. I’m on a joint server and about every four weeks or so, no pattern or anything, my FB doesn’t post. My actual site is fine and not overloaded with any pics or long posts so I’m going to gander its really the multiple sharing server I’m on which had thousands of other blogs on it. Anyway, so what’s the status of the issue with the Twitter URL truncation issue with auto post and also the fact I can’t currently use the box to change the 140 character message for FB without it not showing the excerpt?

what’s the status of the issue with the Twitter URL truncation issue with auto post and also the fact I can’t currently use the box to change the 140 character message for FB without it not showing the excerpt?

We’re still working on that, and I’ll let you know as soon as I have some news.