Do you have a URL so I can take a look? Could be a lot of things.
Thanks,
Andrew
Yes, I can see now.
And what about the shown warning?:
The parser’s result for this metadata did not match the input metadata. Likely, this was caused by the data being ordered in an unexpected way, multiple values being given for a property only expecting a single value, or property values for a given property being mismatched. Here are the input property =>content pairs that were not seen in the parsed result: ‘og:url => , og:locale:locale => ‘
Hi,
I had this problem too…
I edited FB OGP plugin, and add hu_hu locale instead of hu_HU, so my line is:
echo ‘<meta property=”og:locale” content=”hu_hu”>’ . “\n”;
The problem in FB debug disappeared.
Andrew
Thanks for share.
Yes the og:locale debug disappeared but og:url debug persists.
Regards.
My plugin at present shows –
// do locale
echo ‘<meta property=”og:locale” content=”‘ . esc_attr( get_locale() ) . ‘”>’ . “\n”;
echo “<!– // end wpfbogp –>\n”;
Should i Change this to –
// do locale
echo ‘<meta property=”og:locale” content=”hu_hu”>’ . esc_attr( get_locale() ) . ‘”>’ . “\n”;
echo “<!– // end wpfbogp –>\n”;
adityaaguptaa: I would recommend against editing the plugin directly, but you want, you can do this:
echo ‘<meta property=”og:locale” content=”hu_hu”>’ . “\n”;
I’ll make sure this is fixed in the next version. I’m also not sure what’s wrong with Facebook when it has og:locale:locale but I’ll be looking into that as well.
Cool. I’ll wait for the next version to come out. And hope that is soon enough. Thanks!
Pushed an update (2.0.3) that should nuke that Facebook parser mismatched metadata warning.
