Hi,

I've been testing my website using facebooks debugger https://developers.facebook.com/tools/debug

For my pages, it reports the following warnings:
Extraneous Property: Objects of this type do not allow properties named 'dcterms.type'.
Extraneous Property: Objects of this type do not allow properties named 'dcterms.format'.
Extraneous Property: Objects of this type do not allow properties named 'dcterms.date'.
Extraneous Property: Objects of this type do not allow properties named 'dcterms.title'.
Extraneous Property: Objects of this type do not allow properties named 'dcterms.identifier'.
Extraneous Property: Objects of this type do not allow properties named 'dcterms.language'.
Extraneous Property: Objects of this type do not allow properties named 'dcterms.creator'.

This warnings disappear, when I disable the module Meta tags: dublin core
The meta tags containing this terms look like this:

I think facebooks parser is correct, since http://dublincore.org/documents/dc-html/ defines metat tags the following way:

The problem seems to be to use the attribute name "property" instead of the correct attribute name "name".

Gerd

CommentFileSizeAuthor
#2 metatag-n1969428-2.patch457 bytesDamienMcKenna
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

GerdC’s picture

The issue tracker ate parts of my post:

The meta tags containing this terms look like this:
meta property="dcterms.format" content="text/html"

I think facebooks parser is correct, since http://dublincore.org/documents/dc-html/ defines metat tags the following way:
meta name="DC.title" content="Services to Government"

DamienMcKenna’s picture

Status: Active » Needs review
FileSize
457 bytes

This patch changes the meta tag from using the 'property' attribute to the 'name' attribute.

DamienMcKenna’s picture

Status: Needs review » Fixed

Good catch. Committed.

GerdC’s picture

+1
I changed the module by hand and facebooks parser doesn't have this problem any more.

Gerd

DamienMcKenna’s picture

Status: Fixed » Closed (fixed)

1.0-beta6 is out, so I'm closing this issue in the interest of keeping the issue queue clean.

GerdC’s picture

I confirm that beta6 fixes the problem.

Thanks,
Gerd