Can you give me an example URL? I had a look at this one http://www.matsuritimes.com/nagahama-hikiyama-matsuri-kodomo-kabuki/, and it looks fine to me…
Thanks,
js.
BTW, if you have a full-webpage cache enabled, you may have to disable it to see the debug information being added (or wait until the cache for that webpage has expired).
Thanks,
js.
Wow! You have really found one without this problem, so easily…
Other posts seem to be affected: Example 1 Example 2 Example 3
I use Google Pagsspeed Service, I expired the cache after turning debugging on.
The only difference is that the post you have pointed to has a featured image of a different size.
And the second “set” of og:image, og:width, og:height (that is empty in other posts) points here to a previously (!) defined featured image. There is nothing in the post now (at least to my eyes) that points to http://www.matsuritimes.com/images/th-nagahama-hikiyama-kodomo-kabuki.jpg
Ok, I confirmed it… I took a page http://www.matsuritimes.com/kyoto-arashiyama-mifune-matsuri/ that initially had the same problem. Its featured image was set to: http://www.matsuritimes.com/images/th-kyoto-mifune-matsuri.jpg and resulting section of OpenGraph meta values looked like this:
<meta property=og:image content="http://www.matsuritimes.com/images/th-kyoto-mifune-matsuri.jpg"/>
<meta property=og:image:height content=213 />
<meta property=og:image:width content=320 />
<meta property=og:image content=""/>
<meta property=og:image:height content=""/>
<meta property=og:image:width content=""/>
<meta property=og:image content="http://www.matsuritimes.com/wp-content/gallery/cache/1528_crop_320x320_kurumazaki-jinja-parade-gissha-ox-cart.jpg"/>
<meta property=og:image:height content=320 />
<meta property=og:image:width content=320 />
Then I uploaded a new featured image (http://www.matsuritimes.com/images/kyoto-mifune-matsuri-dragon-boat-front.jpg) and now I get:
<meta property=og:image content="http://www.matsuritimes.com/images/kyoto-mifune-matsuri-dragon-boat-front-320x320.jpg"/>
<meta property=og:image:height content=320 />
<meta property=og:image:width content=320 />
<meta property=og:image content="http://www.matsuritimes.com/images/th-kyoto-mifune-matsuri.jpg"/>
<meta property=og:image:height content=213 />
<meta property=og:image:width content=320 />
<meta property=og:image content="http://www.matsuritimes.com/wp-content/gallery/cache/1528_crop_320x320_kurumazaki-jinja-parade-gissha-ox-cart.jpg"/>
<meta property=og:image:height content=320 />
<meta property=og:image:width content=320 />
I tried to search the SQL db post tables for references to the old file (http://www.matsuritimes.com/images/th-kyoto-mifune-matsuri.jpg) with no success so far (of course it still remains in media, but it shouldn’t be referenced, I guess).
I made some changes in the last version to filter out duplicate from any/all sources (featured, attached, shortcodes, etc.), and I’m pretty sure it gets for empty values as well… Hm. Very interesting.
The PageSpeed service appears to be stripping comments from your pages as well. Any chance you could turn that off? The NGFB debug output would probably tell us exactly where the problem is (it’s very complete).
Thanks,
js.
Oh, sorry. Indeed PageSpeed Service scraps off comments.
I added exceptions for a post referencing an old featured image and a post with one of the og:image empty.
I looked at the debug info, but have no clue. For the second one it just confirms the output – empty record in an array = empty value.
For the “correct” post (referencing the old featured image): post 455 is an old image in WP media (why is it still referenced?), post 463 is the new one.
Both posts have warnings about duplicate image, but why?
Please take a look at it, maybe you will spot what’s wrong.
Ok, in the first instance, it shows a duplicate and the old image because they are “attached” to the post. So, you have a featured image, two attached images, etc.
Checking on the second…
js.
For the second, I think the duplicate attachment is causing the issue… Normally I’d suggest upgrading to the DEV code, but I’m currently making big changes.
Instead, have a look at the NGFB settings page and uncheck the “Include Empty og:* Meta Tags” option.
Thanks,
js.
Thank you for prompt answer.
I don’t really understand what you mean by “attached image”.
First, let’s talk the “empty” case. What I do is open a post in WP, click on “featured image”, upload an image. And that’s all. I see no room for any duplicate in this procedure. Is there?
For the second case and old image appearing – I understand that it might somewhere remain as attached, but not featured anymore. Still I see no way for neither (old or new) to be duplicated.
The images I use are separate from the images in the post itself, as for the images in posts I use NextGen Gallery only. They have separate path.
Images can be attached to posts without being featured images – and you can have both, which will be detected as duplicates. It’s not a problem though – the plugin will just ignore duplicates.
The empty OG tag is a problem though. The checkbox I suggested should fix the issue.
You can also upgrade to the latest DEV version (5.0dev4) from http://downloads.wordpress.org/plugin/nextgen-facebook.zip. You’ll need to download and install it manually. I’ve been running it on several websites w/o any errors/problems.
Thanks,
js.
Yes, thanks, you were right. The checkbox did resolve the issue. I don’t know why it was checked though if default was unchecked, never mind.
As for attached posts. I attached some photos by mistake to a wrong post and then corrected just by changing the featured image. I thought I was done, but old images still remained attached. Indeed your plugin showed them as an option in OG meta values.
I already cleaned up my db, but maybe for your future users it would be valuable to add an option to exclude images attached to a post and not referenced directly?
