• Resolved rlaflamme

    (@rlaflamme)


    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!

    https://www.ads-software.com/plugins/nextgen-facebook/

Viewing 3 replies - 31 through 33 (of 33 total)
  • Thread Starter rlaflamme

    (@rlaflamme)

    That is correct. And as I mentioned, a newly uploaded one registers just fine with the debugger. One just copy and pasted from html code, not so much.

    Plugin Author JS Morisset

    (@jsmoriss)

    Upload a larger image (larger than 1200x1200px would be best) to the Media Library, then use a media size that’s 200×200 in your post. Check that the img html tag has a ‘data-wp-pid’ attribute. It should, but make sure, since that’s how the plugin recognizes media IDs.

    If you do that, NGFB will be able to provide an image of the proper size in the open graph and twitter card meta tags (plus the pinterest and tumblr buttons).

    js.

    Thread Starter rlaflamme

    (@rlaflamme)

    That may have done it, actually.

    The IMG code did not have the data-wp-pid=”#” in it, but when I plugged that into the HTML and scraped a known bad page for it, that took care of it, even with the existing image.

    I think that is the last bit of this lengthy saga. Thanks ever so much for your assistance!

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