og:image size recognition issue

  • Resolved rlaflamme

    (@rlaflamme)


    10 years, 5 months ago

    Hello,

    This seems to be a bit of a recent occurrence. I’m not sure if there appears to be an issue with the meta tags being scraped on my site or if a recent change somewhere has caused this to happen. As of today whenever attempt to post a link to Facebook or G+, it is not parsing the og:images correctly. (This was working as of a day or two ago and I have made no changes to the site).

    The current error the scraper is reporting is “Provided og:image is not big enough. Please use an image that’s at least 200×200 px.” Then it will default to the set backup image or a secondary image, depending on the link.

    It mainly is affecting the featured images being pulled – which are all at 200×200 or higher – but it does appear to affect images being gathered in general. To rule out variables, both your plugin and WP are now running at the latest versions, but the issue persists.

    The plugin usually runs along without any issue, so I’m not sure if this is an issue going on with the plugin itself or with the Facebook debugger on their end. Either way, they certainly aren’t parsing correctly, and it is affected on more than just FB. Any thoughts on the matter could help!

    Thanks!

    http://wordpress.org/plugins/nextgen-facebook/

Viewing 15 replies - 16 through 30 (of 33 total)
1 2 3
  • Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 5 months ago

    Oh well that beat me to it! 🙂

    I just gave it a try, and the new sort function works great! I did go in and change it from an ‘rsort’ to a ‘sort’ function (so it’ll grab the first three of the post instead of the last three), but that’s just for our purposes.

    Now I just need to resolve the detached image thing. I tried out the plugin you suggested but it doesn’t appear to be registering still. I’m inquiring with the plugin creator there so hopefully we’ll get the last of this nailed down.

    Thanks again!

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 5 months ago

    This one looks pretty good as well http://wordpress.org/plugins/unattach-and-re-attach-attachments/ and I’ve used this one (very simple) in the past http://wordpress.org/plugins/unattach/.

    As for changing the code, that’ll just paint you into a corner for updates. Instead, add the following to your functions.php file:

    add_filter( 'ngfb_attached_images', 'filter_ngfb_attached_images', 10, 2 );
function filter_ngfb_attached_images( $attach_ids = array(), $post_id = '' ) {
    sort( $attach_ids, SORT_NUMERIC );
    return $attach_ids;
}

    I had assumed most people would want the newest images picked first – do you think I should have gone with a regular sort instead?

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 5 months ago

    BTW, have you rated the plugin yet? 😉

    http://wordpress.org/support/view/plugin-reviews/nextgen-facebook

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 5 months ago

    I’ll certainly be sure to rate it, sure!

    Aside from the attach thing, which I’ll explore more into, the only other thing that still needs to be rectified is the G+ issue. Currently, it is reading all 3 of the og:image tags according to the Google snippet tool, but it is only giving the option to post the first one on G+. I’ve ensured that other sites have the option to select when putting in the links, and that it’s not a browser or system restriction. There seems to be something being read it doesn’t like. I’m not sure why since it too was working until a week or so ago.

    Some research I saw mentioned it could have something to do with schema info? Is that used or necessary with this plugin?

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 5 months ago

    If you have multiple og:images listed, G+ should allow you to scroll through them when sharing. If they’re there, but Google isn’t showing you the option to scroll through them, I expect it might be a caching issue. Try it with a new post or page and see if it works. 😉

    G+ supports both Open Graph and schema, which is a kind of descriptive markup for the content in your page. The upside to schema is that you can create several sections in a page with different content, and Google will be able to parse all those sections for author info, related images, etc. Open Graph describes the whole page in one block. It’s a little less versatile, but more widely supported — also easier to implement (no need to manually edit all your templates).

    Here’s an example of schema markup I did for one of my websites: http://www.google.com/webmasters/tools/richsnippets?q=http%3A%2F%2Funderwaterfocus.com%2Fphotographs%2Fsubjects%2Fanimals%2Fvertebrates%2Ffishes%2Fbony%2Fheavy-bodies-large-lips%2Fsea-bass%2F

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 5 months ago

    Thanks! That helps explains schema to me at least.

    I’m still not getting the option to choose, however. This is happening with a brand new post that’s been up for about 12 hours, and it was created after all of the updates and fixes we’ve worked through:

    http://www.google.com/webmasters/tools/richsnippets?q=http%3A%2F%2Fwww.cardboardrepublic.com%2Farticles%2Fthe-podium%2Fdesigning-under-pressure-creativity-through-limitations

    You’ll see it’s pulling the og:image data just like Facebook, but it doesn’t present me with the option to select. I tried a few older posts as well that I know had image options, but no luck.

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 5 months ago

    Yup.

    <!-- og:image:1 --><meta property="og:image" content="http://www.cardboardrepublic.com/wp-content/uploads/2013/11/ComicBookGuy.jpg" />
<!-- og:image:1 --><meta property="og:image:height" content="194" />
<!-- og:image:1 --><meta property="og:image:width" content="259" />
<!-- og:image:2 --><meta property="og:image" content="http://www.cardboardrepublic.com/wp-content/uploads/2013/11/FlagMap_of_USSR-300x205.png" />
<!-- og:image:2 --><meta property="og:image:height" content="205" />
<!-- og:image:2 --><meta property="og:image:width" content="300" />
<!-- og:image:3 --><meta property="og:image" content="http://www.cardboardrepublic.com/wp-content/uploads/2013/11/idea-300x243.jpg" />
<!-- og:image:3 --><meta property="og:image:height" content="243" />
<!-- og:image:3 --><meta property="og:image:width" content="300" />

    I’d say the images are probably too small.

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 5 months ago

    I thought about that possibility as well, so I started testing out some other sites ability to post. Many I tried had images smaller than those and were still selectable. So, I’m worried that the size isn’t the issue, and since the article is new, it doesn’t make a lot of sense that caching would be an issue.

    For sake of argument, I tried turning off the plugin and seeing what responses I could get, but caching sort of made that experiment futile.

    It’s becoming a bit of a head scratcher, especially since it was working until last week… :/

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 5 months ago

    Well, it might come back by itself – I know Pinterest and LinkedIn, for example, often have issues. If everything checks out with the Facebook Debugger, then I’d just wait and see if things fix themselves. The Facebook debugger is really the best validation source. And don’t forget, these social websites are always changing one thing or another – we can only make sure that our meta tags are accurate and available.

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 4 months ago

    Thanks JS for all the help! I just wanted to respond and let you know that G+ did indeed resolve itself, so that is no longer an issue.

    Now if only I could get the scraper to be taking inserted images I’d be golden! (Not sure if 6.16 addressed that at all though)

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 4 months ago

    I’m not sure what you mean by ‘inserted images’ – which social website should be doing what in your opinion?

    BTW, I noticed above there was a mention of the ‘ngfb_attached_images’ filter. Note that in the upcoming 6.17.0 version, the ‘ngfb_attached_images’ filter has been renamed to ‘ngfb_attached_image_ids’.

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 4 months ago

    Thanks for the heads up on the filter ID change.

    What I have is a post that is essentially a news post that gets duplicated every week. The post HTML data (layout, images, formatting, etc.) are copy and pasted and then some of the text itself is changed. The main image for this is a 200×200 file that is not being seen by the Facebook debug tool.

    Last we spoke you mentioned the Un-Attach plugin as a way to fix that (so that the image could be considered attached to multiple posts) but so far it has not worked, and the developer has yet to reply to my inquiry there unfortunately. :/

    I was hoping that merely having it in the code would allow it to be scraped (even going so far as to explicitly mention the width / height and ‘data-share-src’ tag in the HTML, but alas it has no effect, and I’m at a loss. I know it’s unrelated to my original issue though. (I think)

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 4 months ago

    So you have an image in your post that you would like Facebook to pickup and use when that post is shared. Correct?

    This image is taken from the Media Library, or added manually in the HTML as an <img/> tag?

    If it’s from the Media Library, is the original image in the Media Library large enough? Say at least 600x315px?

    What are the Image Dimensions you’ve specified on the Open Graph+ General settings page?

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    10 years, 4 months ago

    That is the short of it yes.

    The image is from the Media Library, and with the Un-Attach plugin I guess it allows the image to be attached to multiple posts using the same image. The image is not added via the “Add Media” button when the posts are made though, the <img> info is merely copied from the HTML of the previous post.

    The image in question is a 200×200 exactly, and I know that file size is able to be taken from the FB scraper because if I save the image, upload it as a new image with a different name, and save it, the scraper sees the image in the post immediately and throws no errors. (Just for reference the OG+ setting is at 300×300 with Auto-Resize checked)

    I’m just trying to avoid having to have to duplicate and upload the same image every week.

    Plugin Author JS Morisset

    (@jsmoriss)

    10 years, 4 months ago

    So the original, full size image, uploaded to the Media Library, is 200×200?

    js.

Viewing 15 replies - 16 through 30 (of 33 total)
1 2 3
  • The topic ‘og:image size recognition issue’ is closed to new replies.