There’s no relationship/connection between the meta tags added to webpage headers, and the social buttons. Social buttons only send a URL — everything else is provided by the meta tags. So, yes, feel free to disable the buttons and/or use different buttons from other plugin(s).
There’s no need to define a featured image. Here’s the relevant part from the FAQ:
Q. How does NGFB find images to include in the Open Graph meta tags?
A. The images used in the Open Graph meta property tags for Posts and Pages are chosen in this sequence:
– A featured or attached image from NextGEN Gallery or the WordPress Media Library.
– An image from the NextGEN Gallery ImageBrowser (in combination with an [nggalbum] or [nggallery] shortcode).
– A preview image from a NextGEN Gallery [nggalbum] or [nggallery] shortcode.
– Image(s) from expanded NextGEN Gallery [singlepic], [nggallery] or [nggtags] shortcodes.
– Image(s) from HTML <img/> tags in the Post or Page content text.
– A default image defined in the NGFB plugin settings.
I’m guessing you’re not using any of these, right?
It looks like you’re using something called “royalslider”. It may get it’s images from NextGEN Gallery, but it’s not generating “NetGEN Gallery compatible HTML”. For example:
<div class="entry-content">
<div id="gallery-1" class="royalSlider rsDefault">
<div class="rsContent">
<a class="rsImg" href="https://theyrep.net/theyrep/wp-content/gallery/sonia-leal-serafim-new-work-draft/theymag-ww-1.jpg"></a><br />
<img class="rsTmb" src="https://theyrep.net/theyrep/wp-content/gallery/sonia-leal-serafim-new-work-draft/thumbs/thumbs_theymag-ww-1.jpg"/>
</div>
To provide this image in the Open Graph meta tags, NGFB Open Graph needs either the width and height (missing from your code), or the NextGEN Gallery image ID (also missing).
NextGEN Gallery provides the images IDs in the form of a <div>
with id="ngg-image-#"
. If that id was included, NGFB Open Graph+ could detect and include those images.
So, you have two options as I see it:
1) add the missing id attributes in the form of ‘ngg-image-#’.
2) or see the FAQ entry “Why does NGFB ignore the <img/> HTML tags in my content?”.
Let me know if there’s something else I can assist you with.
Thanks,
js.