Thanks Ryan.
Yes, it looks like that link went stale (actually, the content was probably deleted at some point by the user). And thanks for picking up on the missing tag in the XvFB9 link - I’ll need to look into that.
The better example though would be http://fn.cr/9cah4 - If you view source on that page, you’ll see the appropriate tags:
<meta name=“twitter:card” content=“summary”/>
<meta name=“twitter:image” content=“http://i.imgflip.com/1n6sc.gif”/>
<meta name=“twitter:title” content="Time for some Bruins.
“/>
<meta name=“twitter:site” content=”@Fancred"/>
<meta name=“twitter:app:id:iphone” content=“614787471”/>
It is admittedly missing the description tag, which we’ll be patching soon, but the validator is complaining about missing the twitter:card tag, which is clearly there.
Late last night I did track down what I think the answer is in this case however. Or if not the cause, at least a fix. We added the following meta tag to the page:
<meta http-equiv=“Content-Type” content=“text/html; charset=UTF-8”/>
and the validator started working.
This is strange for a few reasons:
- The http headers already specified the content type as text/html
- We already had a meta tag of <meta charset=“utf-8” />
- While declaring this tag is a good practice, I don’t see it as a requirement anywhere, and all browsers I’ve tested work fine without it
So… I’m not positive what the root cause is - I’m happy to help find it if the validator can spit out more useful messages (it would be great if there were an option to spit out what content the validator actually pulled/parsed), but for now I think our problem is plugged.
Thanks,
-Sander
