Hello,

Please check a page with OG data provided by this module, add a facebook like button.
Try to like this page and Facebook will give you an error.
Go onto this Facebook page, you'll see why: https://developers.facebook.com/tools/debug

Some required data are missing. In html section you should have more metatag:

<meta property="fb:admins" content="your_admin_id"/>

Some others metatags can be added, Facebook debugger shows them.

I putted "major" priority because any OG sharing is broken.

Thanks

Files: 
CommentFileSizeAuthor
#10 Screen Shot 2013-02-25 at 8.33.48 AM.png44.14 KBklucid

Comments

It seems that I have a problem like yours. Only Facebook doesn't say a tag is missing, they are in the wrong order ?

On the debug page I get the following warnings:

Open Graph Warnings That Should Be Fixed
Extraneous Property: Objects of this type do not allow properties named 'http://purl.org/dc/terms/title'.
Extraneous Property: Objects of this type do not allow properties named 'http://rdfs.org/sioc/ns#num_replies'.
Parser Mismatched Metadata:
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 properties that were not seen in the parsed result: 'http://purl.org/dc/terms/title, http://rdfs.org/sioc/ns#num_replies'

Any idea how to fix this ? When a like-button is clicked it counts but nothing shows up on the users wall...

If there's a specific required order for the Open Graph tags we can very easily adjust the output, we just need to know what order they should be in.

Maybe it's not the order but the fact that there are multiple values for a property..

What's even stranger.. I inspected the source code and the mismatched Metadata isn't in there every time ?
The website I'm building now is http://www.desnellevlucht.be (in Dutch) maybe seeing / clicking yourself may help solving the problem :-s I'm confused at the moment :D

edit:

On the Facebook Open Graph developer page I found the following:

The Open Graph protocol defines four required properties:

og:title - The title of your object as it should appear within the graph, e.g., "The Rock".
og:type - The type of your object, e.g., "movie". See the complete list of supported types.
og:image - An image URL which should represent your object within the graph. The image must be at least 50px by 50px (though minimum 200px by 200px is preferred) and have a maximum aspect ratio of 3:1. We support PNG, JPEG and GIF formats. You may include multiple og:image tags to associate multiple images with your page.
og:url - The canonical URL of your object that will be used as its permanent ID in the graph, e.g., http://www.imdb.com/title/tt0117500/.

In addition, we've extended the basic meta data to add a required field to connect your webpage with Facebook:

fb:app_id - A Facebook Platform application ID that administers this page.

It's also recommended that you include the following properties as well as these multi-part properties.

og:site_name - A human-readable name for your site, e.g., "IMDb".
og:description - A one to two sentence description of your page.

If a user likes your URL using a Like button, a News Feed story similar to the one below will be published to Facebook. The og:title links to og:url and the og:site_name is rendered pointing to your site's domain automatically.

On a user's profile, og:type defines which category your link will appear within; og:image is the image thumbnail.

And the code example:

<title>The Rock (1996)</title>
    <meta property="og:title" content="The Rock"/>
    <meta property="og:type" content="movie"/>
    <meta property="og:url" content="http://www.imdb.com/title/tt0117500/"/>
    <meta property="og:image" content="http://ia.media-imdb.com/rock.jpg"/>
    <meta property="og:site_name" content="IMDb"/>
    <meta property="fb:admins" content="USER_ID"/>
    <meta property="og:description"
          content="A group of U.S. Marines, under command of
                   a renegade general, take over Alcatraz and
                   threaten San Francisco Bay with biological
                   weapons."/>
    ...

Version:7.x-1.0-alpha6» 7.x-1.0-alpha8
Status:Active» Postponed

This is at least dependent on, if not a duplicate of, #1694838: fb:admins or fb:app_id; lets deal with it first and then return to this issue.

Version:7.x-1.0-alpha8» 7.x-1.x-dev
Status:Postponed» Active

Ok, we now have the fb:admins and fb:app_id meta tags, lets see how well it works now.

@Robrecht Wellens: which page on your site doesn't FB like? It looks okay for
http://www.desnellevlucht.be/
http://www.desnellevlucht.be/nieuws (apart from no og:description)

Same question for original submitter.

@Robrecht Wellens:

OK, I found the errors you reported for http://www.desnellevlucht.be/node/44
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww...

It says the raw OG data is:

Meta Tag: <meta property="og:site_name" content="Caf&#xe9; De Snelle Vlucht" />
Meta Tag: <meta property="og:url" content="http://www.desnellevlucht.be/node/44" />
Meta Tag: <meta property="http://purl.org/dc/terms/title" content="Anderlecht - FC Brugge" />
Meta Tag: <meta property="http://rdfs.org/sioc/ns#num_replies" content="0" />
Meta Tag: <meta property="og:image" content="http://www.desnellevlucht.be/sites/default/files/styles/hoofding/public/headers/logo_0.png" />
Meta Tag: <meta property="fb:app_id" content="477937575551926" />
Meta Tag: <meta property="og:type" content="activity" />
Meta Tag: <meta property="og:title" content="Anderlecht - FC Brugge" />

It's complaining about items 3-4, which are

<meta about="/node/44" property="sioc:num_replies" content="0" datatype="xsd:integer">
<meta content="Anderlecht - FC Brugge" about="/node/44" property="dc:title">

These *look* like they come from some other module that is doing Dublin Core stuff? Metatags DC would have emitted something like:

<meta property="dcterms.title" content="Anderlecht - FC Brugge" />

And doesn't support the num_replies field at all.

I'm having a similar problem with this page:
http://pickerssupply.com/new-and-used/samick-db-5-delta-4-string-electri...

The Facebook debugger is telling me this:

Extraneous Property: Objects of this type do not allow properties named 'http://purl.org/dc/terms/title'.
Parser Mismatched Metadata: 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 properties that were not seen in the parsed result: 'og:site_name, og:title, http://purl.org/dc/terms/title'

And then telling me all of those meta tages are preset :/

I'm getting the same on all of this type of node (there are a few hundred, but they all seem to act the same).

Also, while looking into this (and solving a problem I was having with multiple images) I noticed I have some duplicate meta tags - namely og:site_name and og_title. I know it's off topic, but if anyone has any suggestions, I'd be much obliged.

Hi,

Same message from facebook debug tool #8, am keen to understand what this warning means and what I should be doing about it, but haven't found anything yet. Anyone?

:wq

StatusFileSize
new44.14 KB

Hi All,

Same issue here. It's strange, some articles will share on Facebook properly, while others just show a generic shortened link.

I've been digging around trying to see anything that seems like it could cause the problem and my only remotely possible solution would be that the order of the OG meta tags aren't as listed in #3. I believe og:title should be first?

See attached. In my source code, the og:title doesn't appear until line 26. In comment #7 above, the og:title seems also to appear last.

This helped to me to make Facebook debugger happy:

// hook_html_head_alter().
//removing "suspicious" metatags
//put this function into template.php

function THEME-NAME_html_head_alter(&$head_elements) {
unset($head_elements['rdf_node_title']);
unset($head_elements['rdf_node_comment_count']);
}

thanks to Clive

I think part of the problem is the meta tag sorting. I ran the test on a page from my blog and the debugger page gives the following error:

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 properties that were not seen in the parsed result: 'dcterms.type, dcterms.format, dcterms.date, dcterms.title, dcterms.identifier, dcterms.creator, dcterms.language'

I'll see if I can improve the meta tags sorting and hopefully this will help.

Hi,

I don't think that the sorting or the content of the attributes is the problem.

The problem is the wrong attribute name:
The attribute name property is not defined in meta tags. Use the attribute name name in the meta tags and it should work.

Gerd

I've committed a fix for the issue Gerd raised in #1969428: Dublin core: Extraneous Property: Objects of this type do not allow properties named 'dcterms.type'., lets see if that helps.

+1
I changed the module (version beta5) by hand on my productive site and facebooks parser doesn't have this problem any more.

Gerd

there are other meta tags that still use the property attribute:
They're probably emited my a different piece of code:

<meta property="og:type" content="article" />
<meta property="og:url" content="http://www.nlpankern.com/professionell-ankern/vergleich-deiner-realitaetsstrategien" />
<meta property="og:site_name" content="Professionell Ankern - vom NLP-Practitioner bis zum Coaching" />

in metatag_opengraph.module, function theme_metatag_opengraph: when I change property to name, this works fine for me, too.
Sorry, I'm a developer but no php developer:

/**
* Theme callback for an OpenGraph meta tag.
*/
function theme_metatag_opengraph($variables) {
  $element = &$variables['element'];
  element_set_attributes($element, array('#name' => 'name', '#value' => 'content'));
  unset($element['#value']);
  return theme('html_tag', $variables);
}

Gerd

Please let me know if beta6 resolves the problems, thanks.

Nope, the code change in Comment #18 seems not to be part of beta6.

the og: values are still emitted into the property attribute.

Gerd

Status:Active» Fixed

After updating my site to beta6 I'm no longer seeing these errors on my personal site: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww... Feel free to reopen if the problem persists on your site.

Status:Fixed» Closed (fixed)

Now that v7.x-1.0-beta7 is out, I'm closing this in the interest of keeping the issue queue clean.

Version:7.x-1.x-dev» 7.x-1.0-beta7
Priority:Major» Normal
Status:Closed (fixed)» Active

Hi All,

I am using latest metatag 7.x-1.0-beta 7 and I am facing these warning when test it with facebook debugger. Any idea how to fix it? Thanks!
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww...


Extraneous Property: Objects of this type do not allow properties named 'http://rdfs.org/sioc/ns#num_replies'.
Extraneous Property: Objects of this type do not allow properties named 'http://purl.org/dc/terms/title'.
Parser Mismatched Metadata:
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 properties that were not seen in the parsed result: 'http://rdfs.org/sioc/ns#num_replies, http://purl.org/dc/terms/title'

Status:Active» Closed (fixed)

@jayson13: Try disabling the core RDF module, see if that fixes it.

For anyone following this, there's another issue that's also causing problems for OG tags: #1978568: Don't output line breaks in meta tags

Thank you!!!
#24 fixed the problem :)

I have disabled the RDF module, but I'm still getting these errors:

Extraneous Property: Objects of this type do not allow properties named 'og:region'.
Extraneous Property: Objects of this type do not allow properties named 'og:locality'.
Extraneous Property: Objects of this type do not allow properties named 'og:longitude'.
Extraneous Property: Objects of this type do not allow properties named 'og:postal-code'.
Extraneous Property: Objects of this type do not allow properties named 'og:street-address'.
Extraneous Property: Objects of this type do not allow properties named 'og:country-name'.
Extraneous Property: Objects of this type do not allow properties named 'og:phone_number'.
Extraneous Property: Objects of this type do not allow properties named 'og:email'.
Extraneous Property: Objects of this type do not allow properties named 'og:latitude'.
og:image should be larger: Provided og:image is not big enough. Please use an image that's at least 200x200 px. Image 'http://nomadsland.ch/sites/default/files/styles/slide/public/images/slides/slide_2175a_0.jpg?itok=ive1pPRO' will be used instead.
Parser Mismatched Metadata: 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 properties that were not seen in the parsed result: 'og:region, og:locality, og:longitude, og:postal-code, og:street-address, og:country-name, og:phone_number, og:email, og:latitude'

Is this related to this issue?

Issue summary:View changes