Facebook Like Box issues - my patience ended - html

I'm trying to set up a Like Box in this website: http://filmefilmes.com/breu
The Facebook Page of the site is: http://www.facebook.com/pages/BREU/278537375497440
I have tried all methods. iFrame, FBML, etc.
When you click the "like" button it returns a Error that says the page can't be reached.
When I pass the site on the debugger the error is:
You have < meta> tags ouside of your < head>. This is either because
your < head> was malformed and they fell lower in the parse tree, or
you accidentally put your Open Graph tags in the wrong place. Either
way you need to fix it before the tags are usable.
Which is incorrect because the tags are obviously inside the page's head.
And i get this warning too:
The og:locale property should be explicitly provided, even if a value
can be inferred from other tags.
I have to deliver this website very soon and I've spent some hours trying to correct this and to find solutions in forums etc.
As I have changed methods I believe the error is somewhere in the markup of my page but I don't really have a clue.
Help will be heavily appreciated, thanks.

Having a quick look at the site I can see you DO have <meta> tags outside of the <head> element, these are inside a second <head> tag further down the page.
Check your facetek div.

few of your meta tags are unclosed. ("/>")
thus, closing within them is parser error.
fix it and it should go fine

Related

Facebook Instant Articles error "The HTML element does not contain any text: Avoid including empty HTML elements"

In many of the articles imported from my development feed to Facebook Instant Articles I get the error "The HTML element does not contain any text: Avoid including empty HTML elements." It seems to be related to images in figures with no other content. Can anybody tell me what it is Facebook's complaining about? My markup seems to conform to Facebook's own example of a simple image inside a figure tag, so what's the problem?
Turns out the Facebook parser doesn't like a <p> tag wrapping an element if there's no text in it. When I edit one of the articles highlighted with the yellow warning icon in the Facebook code editor, there's an empty <p></p>:
When I delete the empty element the error warning remains in the code view. But this is just a glitch in the code editor. You can't always rely on the error highlighting in that. (That explains why there's a code error warning in the pic in my question even though I'd deleted the <p>.) In the article list the warning icon disappears:
And FB publishes the Instant Article.
You will also get this error if your markup contains stuff like <p><img src="..."></p>. FB expects all <p> tags to contain text.
Maybe try closing the <img > tag:
<figure>
<img src="https://test.files.wordpress.com/2015/07/selleck1.jpg?quality=60&strip=all />
</figure>
It could be that Facebook simply strips invalid XML (!), resulting in observed error message.
In the example at
https://developers.facebook.com/docs/instant-articles/reference/image
the - yet self-enclosing - <img> tag is closed (as in XHTML, rather than less restrictive HTML5).
PIA for wordpress sites, all it's content comes between tags and this eventually generates one <p> empty <\p>. For this you need to go through your post content and remove all these empty tags.
Just open the warning marked article in edit mode in and update. It will fix.

Verifying my HTML syntax

I can't figure out what's going on, here is my HTML. The validator gives me errors, but I'm completely new to this so I have no clue how to fix it. Been trying for hours now. I don't get what most of the validators message implies, some say open elements or errors - but I can't find them.
This all stems from your unclosed <class="contact"> "element" which should be an attribute of another element, not its own element. Most likely what you want is:
<div class="contact">Prime Properties</div>
In the future please post your code as text, not as an image.
The error messages are self explanatory. #Doelleri already spotted the <class="contact"> wierd tag...
In addition, your tag is missing a .
Ex:email

W3C HTML5 validator error: An body start tag seen but an element of the same type was already open

I post this question because I'm having some errors with the w3c validator in my page (Link to validation).
It outputs me a lot of strange errors related with my HTML 5 markup, being this the main error I can't get out of my head:
Line 15, Column 6: An body start tag seen but an element of the same type was already open
I have looked a lot into this problem and I'm not able to find any solutions.
Although there are more strange errors, such as
Line 14, Column 7: Stray end tag head
I'm specially interested in the first exposed one, which I would like you to help me solving this.
Thanks in advance!
Problem solved:
Conclusions:
Never display data into the <head> tag, otherwise, a body tag will be automatically opened.
The <noscript> tag content is considered by the validator as displayable, so It's convenient to take care of what we write into the tag.
The noscript element in the head element contains text output. This is not allowed in the head element; noscript in the head element may contain only link, style, and meta elements (see the spec). Any displayable content implicitly closes the head element and opens the body element (because of their content models and the fact that both opening and closing tags for them are optional).

Is it possible to use an <a> tag within a <pre> tag?

Im working with some legacy code that generates a given message on a webpage but surrounds it with a <pre> tag - I was hoping to put a link (anchor tags) within it like this:
<pre>User created successfully - <a href='/View/User/17'>click here</a> to view the users profile</pre>
But I think because its a <pre> tag it ignores tags within it. Is there any way around this?
APOLOGIES
Im really sorry to have wasted everyone's time - the reason why it was happening was due to the fact that I was using ModelState.AddModelError (in ASP.NET MVC) to set the error message, which automatically HTML encodes the message you give it (I used Chrome's element inspector which shows the HTML decoded version, hence the confusion)
Phrasing content (such as <a>) is allowed in <pre>.
References:
W3C: The <pre> element

Facebook like buttons erroneously handled as one

I've implemented the like button on my WP blog, but for some reason some of them (not all of them) are interpreted as being the same button. If I press like, I will also like the ones that is interpreted as the same. I can't figure out why. There are several other problems with what is shared on Facebook, but I think those problems are connected to this one.
It worked great for a few days, then I started getting an error each time I pressed the like button. After fiddling with the og:type value the error disappeared, but instead now I get this strange behaviour.
My implementation is so simple, I can't really think of any causes:
<div class="fb-like"><fb:like href="<?php the_permalink();?>" show_faces="true" width="600" font="arial"></fb:like></div>
I've found that the behaviour changes depending on what og:type I define in the header section, but with no value producing the correct result.
the blog can be seen at http://blog.parkov.dk/ (in Danish, though).
Anyone has experience with this?
Remove the href parameter and instead use the Open Graph meta tags. I see that you are using them but some required tags are missing:
og:title
og:url
IMPORTANT NOTE:
For the homepage use blog as og:type!