amofilmes.net

Amo Filmes grátis Amo Filmes Download Avi DVDRip Completo grátis Adrive Putlocker ONLINE Amo Filmes - Download de Filmes Grátis Baixar filmes lançamentos de graça filmes 2013 ...

This data was last updated from 23-10-2013 01:43:14  (update).

Overview Info



  • Domain Name
    amofilmes.net
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    93.115.82.80
  • Page Size
    41.4 KB
  • Images
    0 GIF, 6 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 7 6 0 0 0

Website Meta Analysis



  • Title
    Amo Filmes - Download de Filmes Grátis
  • Meta Keyword
    filmes grátis, dvdrip, rmvb, avi, xvid, dublado, dual audio, legendado, serie rmvb, series, baixar filmes, baixar filmes grátis, download filmes, download filmes grátis, filmes dvdrip, filmes novos, filmes para downloa, baixar filmes avi, 2013 filmes, filmes lançamentos baixar
  • Meta Description
    Amo Filmes grátis Amo Filmes Download Avi DVDRip Completo grátis Adrive Putlocker ONLINE Amo Filmes - Download de Filmes Grátis Baixar filmes lançamentos de graça filmes 2013

Technical Analysis



  • Webserver
    nginx/1.2.8
  • Ip Address
    93.115.82.80
  • Domain Age
    8 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from amofilmes.net.

HTML Analysis

  • server: nginx/1.2.8
  • date: Sun, 22 Sep 2013 04:40:33 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • x-pingback: http://amofilmes.net/xmlrpc.php
  • nextdns-eu-01: HIT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for amofilmes.net

IP 93.115.82.80 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 93.115.82.80

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 108 Errors
  • 65 Warnings
Ratio Text/Html
  • 0.6614007745348068
Message Error
  • Error Line 4, Column 16: there is no attribute "property"
    <meta property="fb:app_id" content="459130130825121"/>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 8, Column 95: end tag for "link" omitted, but OMITTAG NO was specified
    …p://fonts.googleapis.com/css?family=Days+One' rel='stylesheet' type='text/css'>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 8, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Days+One' rel='stylesheet' t…
  • Warning Line 260, Column 25: character "&" is the first character of a delimiter but occurred as data
    	} else if(window.opera && window.print){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 260, Column 26: character "&" is the first character of a delimiter but occurred as data
    	} else if(window.opera && window.print){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 270, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 274, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=459130130825121";

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 274, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=459130130825121";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 274, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=459130130825121";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 274, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=459130130825121";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 274, Column 56: entity was defined here
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=459130130825121";
  • Error Line 288, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 292, Column 86: reference not terminated by REFC delimiter
    … 	js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=305865529459211";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 292, Column 86: reference to entity "appId" for which no system identifier could be generated
    … 	js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=305865529459211";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 274, Column 56: entity was defined here
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=459130130825121";
  • Error Line 295, Column 54: there is no attribute "data-send"
    …      	<div class="fb-like" data-send="false" data-layout="button_count" data-…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 295, Column 74: there is no attribute "data-layout"
    …b-like" data-send="false" data-layout="button_count" data-href="http://amofilm…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 295, Column 99: there is no attribute "data-href"
    … data-layout="button_count" data-href="http://amofilmes.net/" data-width="50" …

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 295, Column 134: there is no attribute "data-width"
    …ata-href="http://amofilmes.net/" data-width="50" data-show-faces="false"></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 295, Column 155: there is no attribute "data-show-faces"
    …ata-href="http://amofilmes.net/" data-width="50" data-show-faces="false"></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 317, Column 340: duplicate specification of attribute "type"
    …ue = &#39;&#39;; }' tabindex='1' type='text' value='Faça a busca por filmes e …

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 320, Column 31: ID "bt-buscar" already defined
    <input alt='Fazer Buscar' id='bt-buscar' name='s' src='http://i.imgur.com/a7RUW…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 303, Column 31: ID "bt-buscar" first defined here
    <input alt='Fazer Buscar' id='bt-buscar' name='s' src='http://i.imgur.com/a7RUW…
  • Error Line 334, Column 72: there is no attribute "target"
    …www.facebook.com/AmoFilmesNet' target='_blank' title='Curta Nossa Pagina no Fa…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 388, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-9030'><a href='http://amofilmes.net/cat/acao/' tit…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 390, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-1751'><a href='http://amofilmes.net/cat/aventura/'…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 392, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-5126'><a href='http://amofilmes.net/cat/animacao/'…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 393, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-1756'><a href='http://amofilmes.net/cat/comedia/' …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 395, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-1756'><a href='http://amofilmes.net/cat/drama/' ti…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 397, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-1749'><a href='http://amofilmes.net/cat/ficcao/' t…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 399, Column 35: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-1750'><a href='http://amofilmes.net/cat/fantasia/'…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 401, Column 33: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-11'><a href='http://amofilmes.net/cat/guerra/' tit…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 403, Column 33: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-11'><a href='http://amofilmes.net/cat/nacional/' t…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 405, Column 33: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-11'><a href='http://amofilmes.net/cat/romance/' ti…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 407, Column 33: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-11'><a href='http://amofilmes.net/cat/suspense/' t…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 409, Column 33: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class='cat-item cat-item-11'><a href='http://amofilmes.net/cat/terror/' tit…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 411, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 392, Column 1: start tag was here
    <li class='cat-item cat-item-5126'><a href='http://amofilmes.net/cat/animacao/'…
  • Error Line 411, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 387, Column 1: start tag was here
    <li class='cat-item cat-item-1748'><a href='http://amofilmes.net/cat/filmes-201…
  • Error Line 417, Column 4: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <br>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 417, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 417, Column 1: start tag was here
    <br>
  • Error Line 419, Column 8: element "center" undefined
    <center><div style="position:relative;">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 421, Column 14: there is no attribute "width"
    <embed width="728x" border="1px" height="90px" src="http://megagostoso.org/pc/7…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 421, Column 28: there is no attribute "border"
    <embed width="728x" border="1px" height="90px" src="http://megagostoso.org/pc/7…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 421, Column 41: there is no attribute "height"
    …mbed width="728x" border="1px" height="90px" src="http://megagostoso.org/pc/72…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 421, Column 52: there is no attribute "src"
    …"728x" border="1px" height="90px" src="http://megagostoso.org/pc/728.swf" type…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 421, Column 93: there is no attribute "type"
    …tp://megagostoso.org/pc/728.swf" type="application/x-shockwave-flash" wmode="o…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 421, Column 131: there is no attribute "wmode"
    …so.org/pc/728.swf" type="application/x-shockwave-flash" wmode="opaque"></embed>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 421, Column 139: element "embed" undefined
    …so.org/pc/728.swf" type="application/x-shockwave-flash" wmode="opaque"></embed>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 422, Column 19: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    </div></center><br>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 422, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    </div></center><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 422, Column 16: start tag was here
    </div></center><br>
  • Error Line 428, Column 36: document type does not allow element "div" here; assuming missing "li" start-tag
                	<div id="tptn_related"><ul><li><a href="http://amofilmes.net/baixa…
  • Warning Line 428, Column 308: cannot generate system identifier for general entity "w"
    …T0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 428, Column 308: general entity "w" not defined and no default entity
    …T0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 428, Column 309: reference not terminated by REFC delimiter
    …0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 309: reference to external entity in attribute value
    …0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 309: reference to entity "w" for which no system identifier could be generated
    …0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 314: cannot generate system identifier for general entity "h"
    …nheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um …

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 428, Column 314: general entity "h" not defined and no default entity
    …nheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 428, Column 315: reference not terminated by REFC delimiter
    …heOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Z…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 315: reference to external entity in attribute value
    …heOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Z…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 315: reference to entity "h" for which no system identifier could be generated
    …heOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Z…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 320: cannot generate system identifier for general entity "zc"
    …0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi"…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 428, Column 320: general entity "zc" not defined and no default entity
    …0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi"…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 428, Column 322: reference not terminated by REFC delimiter
    …/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 322: reference to external entity in attribute value
    …/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 322: reference to entity "zc" for which no system identifier could be generated
    …/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 325: cannot generate system identifier for general entity "q"
    …600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" titl…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 428, Column 325: general entity "q" not defined and no default entity
    …600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" titl…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 428, Column 326: reference not terminated by REFC delimiter
    …00/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" title…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 326: reference to external entity in attribute value
    …00/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" title…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 326: reference to entity "q" for which no system identifier could be generated
    …00/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" title…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Error Line 428, Column 425: there is no attribute "border"
    …umbi" width="180" height="220" border="0" class="tptn_thumb" /></a> </li><li><…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 428, Column 701: reference not terminated by REFC delimiter
    …AAAAAActk/O452LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 701: reference to external entity in attribute value
    …AAAAAActk/O452LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 701: reference to entity "w" for which no system identifier could be generated
    …AAAAAActk/O452LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 707: reference not terminated by REFC delimiter
    …ctk/O452LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 707: reference to external entity in attribute value
    …ctk/O452LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 707: reference to entity "h" for which no system identifier could be generated
    …ctk/O452LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 714: reference not terminated by REFC delimiter
    …2LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" width="…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 714: reference to external entity in attribute value
    …2LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" width="…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 714: reference to entity "zc" for which no system identifier could be generated
    …2LMRNqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" width="…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 718: reference not terminated by REFC delimiter
    …NqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" width="180"…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 718: reference to external entity in attribute value
    …NqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" width="180"…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 718: reference to entity "q" for which no system identifier could be generated
    …NqPk/s1600/Mama.jpg&w=114&h=155&zc=1&q=90" alt="Mama" title="Mama" width="180"…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Warning Line 428, Column 1083: reference not terminated by REFC delimiter
    …NXCvMl8/s320/a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do De…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1083: reference to external entity in attribute value
    …NXCvMl8/s320/a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do De…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1083: reference to entity "w" for which no system identifier could be generated
    …NXCvMl8/s320/a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do De…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 1089: reference not terminated by REFC delimiter
    …8/s320/a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio"…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1089: reference to external entity in attribute value
    …8/s320/a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio"…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1089: reference to entity "h" for which no system identifier could be generated
    …8/s320/a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio"…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 1096: reference not terminated by REFC delimiter
    …a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio" title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1096: reference to external entity in attribute value
    …a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio" title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1096: reference to entity "zc" for which no system identifier could be generated
    …a+demonio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio" title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 1100: reference not terminated by REFC delimiter
    …monio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio" title="A M…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1100: reference to external entity in attribute value
    …monio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio" title="A M…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1100: reference to entity "q" for which no system identifier could be generated
    …monio-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="A MOrte do Demonio" title="A M…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Warning Line 428, Column 1489: reference not terminated by REFC delimiter
    …CL-zbQTBI/s1600/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desa…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1489: reference to external entity in attribute value
    …CL-zbQTBI/s1600/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desa…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1489: reference to entity "w" for which no system identifier could be generated
    …CL-zbQTBI/s1600/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desa…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 1495: reference not terminated by REFC delimiter
    …TBI/s1600/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1495: reference to external entity in attribute value
    …TBI/s1600/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1495: reference to entity "h" for which no system identifier could be generated
    …TBI/s1600/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 1502: reference not terminated by REFC delimiter
    …00/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" title="O…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1502: reference to external entity in attribute value
    …00/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" title="O…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1502: reference to entity "zc" for which no system identifier could be generated
    …00/ultimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" title="O…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 1506: reference not terminated by REFC delimiter
    …ltimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" title="O Últ…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1506: reference to external entity in attribute value
    …ltimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" title="O Últ…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1506: reference to entity "q" for which no system identifier could be generated
    …ltimo-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="O Último Desafio" title="O Últ…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Warning Line 428, Column 1891: reference not terminated by REFC delimiter
    …K_wgrE/s252/miseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1891: reference to external entity in attribute value
    …K_wgrE/s252/miseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1891: reference to entity "w" for which no system identifier could be generated
    …K_wgrE/s252/miseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 1897: reference not terminated by REFC delimiter
    …/s252/miseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" titl…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1897: reference to external entity in attribute value
    …/s252/miseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" titl…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1897: reference to entity "h" for which no system identifier could be generated
    …/s252/miseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" titl…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 1904: reference not terminated by REFC delimiter
    …iseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" title="Os M…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1904: reference to external entity in attribute value
    …iseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" title="Os M…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1904: reference to entity "zc" for which no system identifier could be generated
    …iseraveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" title="Os M…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 1908: reference not terminated by REFC delimiter
    …aveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" title="Os Miser…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 1908: reference to external entity in attribute value
    …aveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" title="Os Miser…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 1908: reference to entity "q" for which no system identifier could be generated
    …aveis-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Os Miseráveis" title="Os Miser…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Warning Line 428, Column 2299: reference not terminated by REFC delimiter
    …/VIfgtHKcyjE/s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2299: reference to external entity in attribute value
    …/VIfgtHKcyjE/s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2299: reference to entity "w" for which no system identifier could be generated
    …/VIfgtHKcyjE/s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 2305: reference not terminated by REFC delimiter
    …HKcyjE/s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caça…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2305: reference to external entity in attribute value
    …HKcyjE/s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caça…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2305: reference to entity "h" for which no system identifier could be generated
    …HKcyjE/s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caça…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 2312: reference not terminated by REFC delimiter
    …s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caçadores d…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2312: reference to external entity in attribute value
    …s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caçadores d…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2312: reference to entity "zc" for which no system identifier could be generated
    …s320/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caçadores d…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 2316: reference not terminated by REFC delimiter
    …/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caçadores de Br…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2316: reference to external entity in attribute value
    …/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caçadores de Br…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2316: reference to entity "q" for which no system identifier could be generated
    …/JOAO-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="João e Maria – Caçadores de Br…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Warning Line 428, Column 2780: reference not terminated by REFC delimiter
    …_s/s1600/duro-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2780: reference to external entity in attribute value
    …_s/s1600/duro-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2780: reference to entity "w" for which no system identifier could be generated
    …_s/s1600/duro-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 307: entity was defined here
    …BT0/pXsnheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorad…
  • Warning Line 428, Column 2786: reference not terminated by REFC delimiter
    …00/duro-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um B…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2786: reference to external entity in attribute value
    …00/duro-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um B…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2786: reference to entity "h" for which no system identifier could be generated
    …00/duro-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um B…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 313: entity was defined here
    …snheOHq0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um…
  • Warning Line 428, Column 2793: reference not terminated by REFC delimiter
    …-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um Bom Dia …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2793: reference to external entity in attribute value
    …-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um Bom Dia …

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2793: reference to entity "zc" for which no system identifier could be generated
    …-de-matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um Bom Dia …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 319: entity was defined here
    …q0M/s1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi…
  • Warning Line 428, Column 2797: reference not terminated by REFC delimiter
    …matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um Bom Dia para…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 428, Column 2797: reference to external entity in attribute value
    …matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um Bom Dia para…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 428, Column 2797: reference to entity "q" for which no system identifier could be generated
    …matar-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Duro de Matar: Um Bom Dia para…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 428, Column 324: entity was defined here
    …1600/zm-Optimized.jpg&w=114&h=155&zc=1&q=90" alt="Meu Namorado É Um Zumbi" tit…
  • Error Line 428, Column 2985: end tag for "li" omitted, but OMITTAG NO was specified
    …ght="220" border="0" class="tptn_thumb" /></a></li></ul></div>            </ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 428, Column 14: start tag was here
                	<div id="tptn_related"><ul><li><a href="http://amofilmes.net/baixa…
  • Error Line 438, Column 235: there is no attribute "align"
    …1.jpg" width="166" height="236" align="left" alt="Baixar Filme Dias Melhores V…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 465, Column 23: ID "filme" already defined
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 438, Column 23: ID "filme" first defined here
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…
  • Error Line 491, Column 23: ID "filme" already defined
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 438, Column 23: ID "filme" first defined here
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…
  • Error Line 518, Column 23: ID "filme" already defined
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 438, Column 23: ID "filme" first defined here
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…
  • Error Line 545, Column 23: ID "filme" already defined
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 438, Column 23: ID "filme" first defined here
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…
  • Error Line 572, Column 23: ID "filme" already defined
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 438, Column 23: ID "filme" first defined here
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…
  • Error Line 599, Column 23: ID "filme" already defined
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 438, Column 23: ID "filme" first defined here
    	            <div id="filme"><img style="margin: 0px 10px 0px 0px; display: inl…
  • Error Line 633, Column 13: there is no attribute "src"
    <iframe src="//www.facebook.com/plugins/likebox.php?href=https%3A%2F%2Fwww.face…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 633, Column 267: there is no attribute "scrolling"
    …&amp;appId=215205991846080" scrolling="no" frameborder="0" style="border:none;…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 633, Column 284: there is no attribute "frameborder"
    …991846080" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 633, Column 294: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:300…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 633, Column 371: there is no attribute "allowTransparency"
    …overflow:hidden; width:300px; height:250px;" allowTransparency="true"></iframe>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 633, Column 377: element "iframe" undefined
    …overflow:hidden; width:300px; height:250px;" allowTransparency="true"></iframe>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 661, Column 33: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-9"><a href="http://amofilmes.net/cat/documentario…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 663, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-11"><a href="http://amofilmes.net/cat/drama/" tit…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 665, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-12"><a href="http://amofilmes.net/cat/fantasia/" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 667, Column 41: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …      <li class="cat-item cat-item-12"><a href="http://amofilmes.net/cat/faroe…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 669, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-14"><a href="http://amofilmes.net/cat/ficcao/" ti…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 672, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-14"><a href="http://amofilmes.net/cat/gospel/" ti…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 675, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-14"><a href="http://amofilmes.net/cat/guerra/" ti…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 677, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-17"><a href="http://amofilmes.net/cat/infantil/" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 679, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-18"><a href="http://amofilmes.net/cat/musical/" t…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 681, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-19"><a href="http://amofilmes.net/cat/nacional/" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 684, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-19"><a href="http://amofilmes.net/cat/policial/" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 686, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-21"><a href="http://amofilmes.net/cat/romance/" t…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 688, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-24"><a href="http://amofilmes.net/cat/suspense/" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 690, Column 34: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    	<li class="cat-item cat-item-25"><a href="http://amofilmes.net/cat/terror/" ti…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 692, Column 7: end tag for "li" omitted, but OMITTAG NO was specified
    		</ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 659, Column 2: start tag was here
    	<li class="cat-item cat-item-9"><a href="http://amofilmes.net/cat/desenhos/" t…
  • Error Line 761, Column 61: required attribute "type" not specified
    …t">AmoFilmes.net  <script id="_wauvw3">var _wau = _wau || []; _wau.push(["smal…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 768, Column 9: required attribute "type" not specified
     <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 790, Column 426: element "iframe" undefined
    …dth: 402px; height: 230px;margin-left: 8px;" allowTransparency="true"></iframe>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 796, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 758, Column 7: start tag was here
    </div><div class="footer-bg">

Visitor Analysis

Daily Visitor
  • 0 visits

In Page Analysis