Here is what FACEBOOK DEBUGGER displays
Open Graph 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.
og:image should be larger Provided og:image is not big enough. Please use an image that’s at least 200×200 px. Image ‘http://thecrewenews.co.uk/wp-content/uploads/Monster-Mash-2012.jpg’ will be used instead.
Just to inform….. Images are BIGGER than 200×200 px so this issue is ruled out.
For EVERYONE having this issue, I recommend installing –
http://wordpress.org/plugins/wp-facebook-open-graph-protocol/
This will overwrite the Jetpack OG META TAGS and fix the issue of not selecting your featured image when posting to Facebook.
This plugin has the MISSING Meta Tag OG_IMAGE included and this is why it works and Jetpack doesn’t….. As you CAN SEE BELOW….
Raw Open Graph Document Information
Meta Tag <meta property=”fb:admins” content=”**************” />
Meta Tag <meta property=”fb:app_id” content=”*****************” />
Meta Tag <meta property=”og:url” content=”http://thecrewenews.co.uk” />
Meta Tag <meta property=”og:title” content=”The Crewe News” />
Meta Tag <meta property=”og:site_name” content=”The Crewe News” />
Meta Tag <meta property=”og:description” content=”Bringing you all the latest Community & Charity News from around our area” />
Meta Tag <meta property=”og:type” content=”website” />
Meta Tag <meta property=”og:image” content=”http://thecrewenews.co.uk/wp-content/uploads/Crewe-News-logo-with-banner1.jpg” />
Meta Tag <meta property=”og:locale” content=”en_us” />
Thank you jetpack for over seeing this vital error.
Now go fix it 🙂
Hi!
Your site used to have several major errors because of an anti-right-click script that you had, which placed a div in the head when it shouldn’t. That’s why it didn’t work before. I’m glad you took my advice and got rid of that script now.
Images are BIGGER than 200×200 px so this issue is ruled out.
I have seen cases where an image was more than 2000px by 2000px and FB still gave that error and used a different image. This is not Jetpack’s fault, it is FB doing something wrong. Since you are not using Jetpack anymore, I can’t tell you why no og:image was provided for that URL. If you want to reactivate Jetpack to try and troubleshoot, let me know.
I’m glad you found another plugin to your liking, but please don’t blame Jetpack for the prior issues you had because of that anti-right-click script you had.
Firstly, I have NOT removed the plugin just temp disabled it (as there is that fault with it) whilst awaiting the author to respond to fix it.
Secondly the first post IS JETPACK’s incorrect OG tags and is missing the OG:IMAGE tag.
The second lot of meta tags are how they are suppose to look……
So to fix this i have HAD TO fix it, something that everyone at jetpack refuse to agree is the problem (The proof is there to see) because everything is now working 100% perfectly.
When Jetpack accept the problem and fix it, I will return to using it fully again as i love it.
So PLEASE work on correcting this visible problem instead of telling everyone to run through ‘scripted fault finding’ that never gets anyone anywhere. You are just making people turn elsewhere.
Thanks for all the help.
Will continue using other Jetpack features as they are excellent.
P.s. my meta tags still work perfectly when my WP Copy Protection plugin is active, so stop blaming it on that.
And what about <meta name=”twitter:site” content=”@jetpack” />
I would like to change @jetpack to my twitter @…
Anyone know how to make this?
kimso, in the future please start your own thread, especially for unrelated issues:
http://codex.wordpress.org/Forum_Welcome#Where_To_Post
To answer your question, this is something we’re hoping to include in a future Jetpack release, so follow http://jetpack.me/news/ to find out when it’s released!
