Hiding Warning Messages

It’s not a suggestion – it’s an important warning. You should upload a larger image, or reduce the Image Dimensions on the NGFB General settings page. 114px is crazy small for an original image. You should upload images larger than 1200px (in both width and height), and set your Image Dimensions to 1200×1200 cropped. This will give you better visibility on Facebook.

js.

I understand. I noticed that the Pro version offers an option to ignore smaller images and settings for individual pages/posts types, etc. Would either of these options end up with those warnings not displayed?

I’m just checking for any option to get rid of these messages. I don’t want/need to share these on Facebook.

Thanks!

The option help explains that: “NGFB Pro will attempt to include images from the img html tags it finds in the content. The img html tags must have a width and height attribute, and their size must be equal or larger than the Image Dimensions you’ve entered on the General settings page. Uncheck this option to include smaller images from the content, Media Library, etc. Unchecking this option is not advised – images that are much too small for some social websites may be included in your meta tags.”

So, in your example, unchecking that option would accept the image that’s 114x114px, which is much too small for Facebook.

A better solution would be to use the Custom Settings on each Post/Page to define an image ID that’s large enough.

js.

Yes, I saw that explanation. I just wanted to double check if it would hide the error/warning messages. I appreciate the assistance and fast response.

BTW, that warning will only show when the meta tags are generated, and the meta tags are saved to the transient cache for 6 hours, so you should only see that warning once every 6 hours (unless you update the post/page and the meta tags have to be rebuilt).

Those warnings are actually very important – it’s one (of many) reasons that makes this plugin special. NGFB will not provide images that are too small, and it provides the correct image size for each intended use (Facebook, Twitter, etc.). You *really* should aim to upload larger images, and let WordPress create additional sizes as needed (thumbnail, medium, large, etc.). This is the way images in the Media Library are *supposed* to work. ??

js.

Hi JS,

I use NGFB pro and I’d really like to have the option to suppress these. On some WordPress pages I receive about 20 of your warnings whenever I update the post. Also for websites that I run for other users who are less technically inclined, they think these are errors or viruses and freak out.

I have plenty of large images that NGFB uses, but I still get warnings for smaller images on the page. It’s a bit of a problem when the page has several dozen images.

Perhaps an option to suppress the warnings as long as NGFB has found > 0 image with sufficient dimensions?

Thanks!
Nathan

NGFB will stop looking for images (and issuing warnings) when it has found the number of images required (1 by default for Open Graph meta tags). If you use a featured image, for example, and it is large enough, then you should not see any warnings.

js.

Thanks for the clarification, js.

This means that NGFB is ignoring the featured image on all my pages, posts and portfolio items. This might be an issue with the theme so I’ll look into it. Thanks!

Nathan

If you turn on debug mode, and provide a URL to an example Post/Page, I can have a look and let you know. ??

js.

Hi js,

Actually it is recognizing featured images now.

Just to clarify, when setting minimum image dimensions in NGFB settings, how does the Crop checkbox function?

I don’t want NGFB to crop the image down to the minimum dimensions I’ve set, I just want it to be a minimum requirement. Is that how this works?

For example, I’ve set mine to 700W x 300H. But I don’t want my taller images to be forcibly cropped down to 300 pixels in height. If they’re taller, then all the better.

Thanks!

It’s not a minimum – it’s the image size that will be used. Tall images are not suggested by Facebook and others – they prefer horizontal images.

See https://surniaulula.com/codex/plugins/nextgen-facebook/faq/why-doesnt-facebook-show-the-correct-image/ and https://developers.facebook.com/docs/opengraph/howtos/maximizing-distribution-media-content/#images for more info.

js.

Hi JS,

I have purchased the Pro version for both my websites now.

See this page, debugging enabled:
https://thrilleredge.com/9-special-ops-secrets-for-seeing-in-the-dark/

The featured image I’m using is media id 1891. it is 1600 x 603 pixels.

My minimum size is now set to 800 x 400, no cropping.

I receive errors for several images but no error for this image. Having said that, it doesn’t show as an option when I try to share on Facebook. Only a few post images do.

I also have specific large images set for my home page, https://thrilleredge.com. This image is about 2000 x 1000 pixels. Media ID is 692.

It does not show as an option when sharing on Facebook. I’ve tried setting the URL in the NGFB panel, and I’ve also tried the media ID number. Neither have any effect.

In the NGFB settings, I have a Default Image ID set for the same image, 692. Just in case a page has no decent image.

I’ve disabled the CDN and the minify plugin for now. Thanks for taking a look, JS!

Nathan

The support thread is about another subject, and the www.ads-software.com suppotrt forum is for the free version only. It would be best if you opened a new support ticket for the Pro version at https://support.ngfb.surniaulula.com/support/tickets/new.

Thanks,

js.

FYI – You have another plugin adding Open Graph meta tags:

https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fthrilleredge.com%2F9-special-ops-secrets-for-seeing-in-the-dark%2F

<meta property='og:site_name' content='ThrillerEdge'/>
<meta property='og:url' content='https://thrilleredge.com/9-special-ops-secrets-for-seeing-in-the-dark/'/>
<meta property='og:title' content='9 Special Ops Secrets for Seeing in the Dark'/>
<meta property='og:type' content='article'/>
<meta property='og:image' content='https://thrilleredge.com/wp-content/uploads/2014/05/10708795534_9ca66b55cf_h-700x263.jpg'/>

And these are the meta tags from NGFB:

<meta name="generator" content="NGFB Pro 7.4.8L" />
<meta itemprop="description" content="This might sound like the premise for a porno (bow chicka wow wow) but it’s really about how your eyes work in darkness. Your eyes use cones for color and fine detail. Rods on the other hand see only in black and white, but they’re a thousand times more sensitive to light. Oh, and there’s..." />
<meta property="og:locale" content="en_US" />
<meta property="og:site_name" content="ThrillerEdge" />
<meta property="og:url" content="https://thrilleredge.com/9-special-ops-secrets-for-seeing-in-the-dark/" />
<meta property="og:title" content="9 Special Ops Secrets for Seeing in the Dark" />
<meta property="og:description" content="This might sound like the premise for a porno (bow chicka wow wow) but it’s really about how your eyes work in darkness. Your eyes use cones for color and fine detail. Rods on the other hand see only in black and white, but they’re a thousand times more sensitive to light. Oh, and there’s..." />
<meta property="og:type" content="article" />
<!-- article:tag:1 --><meta property="article:tag" content="adorable bunny" />
<!-- article:tag:2 --><meta property="article:tag" content="pirate dog" />
<!-- article:tag:3 --><meta property="article:tag" content="secrets" />
<!-- article:tag:4 --><meta property="article:tag" content="special ops" />
<!-- article:tag:5 --><meta property="article:tag" content="techno-thriller" />
<!-- article:tag:6 --><meta property="article:tag" content="twilight" />
<meta property="article:published_time" content="2014-03-30T08:57:41+00:00" />
<meta property="article:modified_time" content="2014-05-24T07:59:40+00:00" />
<!-- og:image:1 --><meta property="og:image" content="https://thrilleredge.com/wp-content/uploads/2014/05/10708795534_9ca66b55cf_h-800x301.jpg" />
<!-- og:image:1 --><meta property="og:image:height" content="301" />
<!-- og:image:1 --><meta property="og:image:width" content="800" />
<!-- og:image:2 --><meta property="og:image" content="https://thrilleredge.com/wp-content/uploads/2014/05/nathanblog7-577x400.jpg" />
<!-- og:image:2 --><meta property="og:image:height" content="400" />
<!-- og:image:2 --><meta property="og:image:width" content="577" />
<!-- og:image:3 --><meta property="og:image" content="https://thrilleredge.com/wp-content/uploads/2014/05/nathanblog5-648x400.jpg" />
<!-- og:image:3 --><meta property="og:image:height" content="400" />
<!-- og:image:3 --><meta property="og:image:width" content="648" />
<meta name="description" content="This might sound like the premise for a porno (bow chicka wow wow) but it’s really about how your eyes work in darkness. Your eyes use cones for color..." />

js.

Ah, it was my parent theme!

The developer gave me this to add to my functions.php:

function nectar_after_setup () {
    remove_action( 'wp_head', 'add_opengraph', 5 );
}
add_action('after_setup_theme', 'nectar_after_setup");

Thanks for your help, js!