Facebook Like Button Html Validation Error DOWNLOAD (Mirror #1)
5a02188284 That bypasses the w3c parser and facebook still recognizes the meta tags, cause it ignores the comment. So the very thing you do to build traffic may produce the opposite effect. a u 404 Error !. When Validator referring to my page, using PHP, I don't render the content that is not recognized by W3C Validator. In other words, if you build to a standard, your site will look and function pretty much the same no matter what browser you use. I simply do this by extracting headers' information that is sent by W3C Validator, which is user-agent and which is W3CValidator/version. It's that simple—start using Genesis now!Click here to download The Genesis Guide for Absolute Beginners (PDF - 1.4 MB)Comments frankzeffi saysJune 25, 2013 at 6:22 amWhat is the basis for validating the document if it does not work the OpenGraph?Reply Fred C saysJune 20, 2013 at 12:12 pmHi Victor. The beauty of this fix is that Facebook's Open Graph Protocol doesn't really care where on the page the meta tags are located. nerdramblings.tumblr.com/post/3213578636/… J. Das ist nicht nur unntig kompliziert, sondern erfordert auch eine Anmeldung und langweilt mit vielen technischen Details, die oft nur Experten verstehen. Join Stack Overflow to learn, share knowledge, and build your career. Create PHP function and assign it to Smarty: function UserAgentCheck($useragent) { $useragentcheck = strpos($SERVER['HTTPUSERAGENT'], $useragent); if ($useragentcheck === false) { return false; } else { return true; } } Then let's check the user agent: if (UserAgentCheck("W3CValidator")) { $smarty->assign('W3C', "1"); } else { $smarty->assign('W3C', "0"); } Then in Smarty template you use (if you don't use Smarty just 'echo' the content with PHP): {if $W3C == 0} {/if} When Validator tries to check your page those meta tags are just not output to the page! When any other user agent is seeing your page then those codes are just output as usual! You can do this for Facebook Like Button or for any OG Metatags - actually for anything else. Im interested in understanding how validation effects the search engine algorithm since they dont validate. So that was the point and my solution. Bei normalen Webseiten einfach die genderte HTML-Datei per FTP hochladen. Either you want to pass W3C validation or the Facebook debugger. Which to use?2146How can I know which radio button is selected via jQuery?1545HTML 5: Is it , , or ?1175How to create an HTML button that acts like a link?711What's the shebang/hashbang (#!) in Facebook and new Twitter URLs for?1235Redirect from an HTML page0changing the appearence of an facebook like button (XFBML)6116Why does HTML think chucknorris is a color?1493How does Facebook disable the browser's integrated Developer Tools? Hot Network Questions Can you use Ready an action with "receive a buff from an ally" as the trigger? How to measure small, spiky amounts of current? Why was there a robot in Rocky IV? How can I make a beveled edge with bump mapping? Is it accurate to compare the nuclearization of North Korea with that of Pakistan and India? Why or why not? How to prove a non-provable statement? That is weird. Falls du ein Content-Management-System wie z.B. I've included it below so you can compare the difference from the original source code above to the meta data the SEO plugin produces. stating that google does not validate. An alternative is to use the HTML5 doctype which isn't quite as picky. This code is perfectly valid to integrate with Facebook. –user1137834 Feb 10 '11 at 8:17 add a comment 15 Answers 15 active oldest votes up vote 43 down vote accepted Here is a solution for not swapping doctype: As zerkms suggested, adding the "fb" namespace only applies for the "fb:" attributes. shareimprove this answer answered Jan 25 '11 at 11:32 jsims281 1,76712346 add a comment up vote 0 down vote Ok, after going over literally hundreds of these posts, I finally found a quick and easy way to get a valid page with a Like button (or any other facebook widget) on it. The head area is a container that can include scripts, instruct the browser where to find style sheets, provide meta information, and more. Not perfect though - but there is no perfect decision here, I think! –Ilia Rostovtsev Jul 4 '12 at 8:07 But why do you want to validate if the page everyone really sees is not valid? The only reason I'd care about valid HTML is if I'm worrying about a browser switching to quirks mode or something, and they're going to do it with this. On our last project my friend Jason and I knew two things for certain: We were going to validate XHTML Strict 1.0 using Facebook's Like Button We were not going to add Technical Debt by fudging our DOCTYPE or xmlns The solution is to use a flexible, asynchronous JavaScript module. Do you think that FB has changed how they find the meta tags and excludes this one?Reply Victor Font saysMarch 22, 2012 at 5:34 pmFacebook doesnt look for meta tags on your site. The Open Graph Protocol meta tags take the form of: ‹meta property='og:type' content='blog' /›This is where the problem is with W3C Validation. About The Author Gabriel Harper Gabe is the owner and founder of Intavant, and contributes to Intavant Blog regularly with his expertise in design, development & business. Your page will show up in the same places that Facebook pages show up around the site (e.g