With the new itemprop metatags my site stopped validating. I have 3 errors like this one:

Line 28, Column 68: The itemprop attribute was specified, but the element is not a property of any item.

<meta itemprop="name" content="Test Site" />

From what i've understand, itemprop is to be set as microdata to some elements rather then to be set in head.

http://schema.org/docs/gs.html#microdata_itemprop

CommentFileSizeAuthor
#24 metatag-n2389929-24.patch4.04 KBdamienmckenna
#22 metatag-schemaorg-page-set.patch1.02 KBmichee.lengronne
#18 metatag-schemorg-page-set.patch962 bytesmichee.lengronne
#11 metatag-schemorg-page-set.patch1.09 KBmichee.lengronne
#10 metatag-schemorg-page-set.patch962 bytesmichee.lengronne

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Postponed (maintainer needs more info)

If you check the HTML5 spec it's completely valid:

What validator are you using?

Anonymous’s picture

Anonymous (not verified) commented

The one from W3C. Maybe i am doing it wrong:

http://validator.w3.org/check?uri=reg.io%2Fc%2F52%2Ftalhof&charset=%28de...

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Postponed (maintainer needs more info) » Active

Yes, and another HTML5 validator also shows the same:

https://html5.validator.nu/?doc=http%3A%2F%2Freg.io%2Fc%2F52%2Ftalhof

Darn :-\

Anonymous’s picture

Anonymous (not verified) commented

From what i've found here it seems like itemprop is not supposed to be in head after all: http://html5doctor.com/microdata

The example states something like this:

<p itemscope>
  <span itemprop="name" itemscope>Jessica Spengler
    <meta itemprop="likes" content="Mameshiba">
  </span>’s fans are always really raucous.
</p>

Did not know you can use meta like this and the website even states some browser don't know this too. Pretty confusing.

rpayanm’s picture

rpayanm
he/him
Primary language Spanish
commented

You can check this
http://stackoverflow.com/questions/29123445/validation-error-the-itempro...

scor’s picture

scor commented

Could someone post the HTML markup that is generated and that is not validating? (ideally a full page src please)

rpayanm’s picture

rpayanm
he/him
Primary language Spanish
commented

Here the code:

<!DOCTYPE html>
<html>
<head lang="en">
  <meta itemprop="name" content="The Name or Title Here">
  <meta itemprop="description" content="This is the page description">
  <meta itemprop="image" content="http://www.example.com/image.jpg">
  <meta charset="UTF-8">
  <title>My title</title>
</head>
<body>
  My body.
</body>
</html>
tunaman’s picture

tunaman commented

@rpayanm It seems to originate from the Google+ sub module, disabling it removes those tags. Nobody uses Google+ anyway right?

capogeannis’s picture

capogeannis commented

Used for better search result listings, better nav interface in those results for mobile, etc:

https://developers.google.com/structured-data/site-name

https://developers.google.com/structured-data/rich-snippets/products

michee.lengronne’s picture

michee.lengronne
Primary language French
commented
StatusFileSize
new metatag-schemorg-page-set.patch962 bytes

In fact the itemtype is not set in the html tag. The patch above solves the issue. Your html template needs to be modified.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented
StatusFileSize
new metatag-schemorg-page-set.patch1.09 KB

This patch is better as it takes the schemaorg module into account.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Needs review

@michee.lengronne: Thanks, I'll test out your patches in the next few days.

Please don't forget to update the issue status to "needs review" when you upload a patch, that'll kick off testbot and let others know there's something to review.

Status: Needs review » Needs work

The last submitted patch, 11: metatag-schemorg-page-set.patch, failed testing.

scor’s picture

scor commented

The markup should be independent of whether the schema.org exists because the schema.org module outputs a different markup (RDFa) than what's being added in this patch (microdata). Patch #10 is the way to go.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented
Status: Needs work » Needs review

Right. I just saw that after the patch submitted.

The last submitted patch, 10: metatag-schemorg-page-set.patch, failed testing.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented
Status: Needs review » Needs work

Resubmitting

michee.lengronne’s picture

michee.lengronne
Primary language French
commented
Status: Needs work » Needs review
StatusFileSize
new metatag-schemorg-page-set.patch962 bytes

Now.

Status: Needs review » Needs work

The last submitted patch, 18: metatag-schemorg-page-set.patch, failed testing.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

@michee.lengronne: You need to check that the variable exists before appending to it.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented

Right.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented
Status: Needs work » Needs review
StatusFileSize
new metatag-schemaorg-page-set.patch1.02 KB

there

createchlondon’s picture

createchlondon commented

Please may I ask what's happening with this fix? The issue with the Google+ meta tags is that it's adding a element. According to Google it should be Your WebSite Name so what is the point of this meta tag?

If it's going to be meta itemprop instead of title itemprop then it needs to be a child element of an itemscope. Please can we elevate this issue for a fix as it's causing problems with accessibility error testing.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
StatusFileSize
new metatag-n2389929-24.patch4.04 KB

Updated to clean up the installation instructions, README.txt, etc.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Needs review » Fixed

Committed. Thanks everyone!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.