Sex Shop Loja do Prazer. A Maior SexShop Da América Latina, Sexyshop Com 15 Mil Produtos Eróticos. ...

lojadoprazer.com.br
  • Domain Name
    lojadoprazer.com.br
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #51960
  • Page Size
    144.1 KB
  • Ip Address
    201.20.10.204
  • Heading
    H1: 2, H2: 3, H3: 53, H4: 6, H5: 0, H6: 0
  • Images
    14 GIF, 75 JPG, 5 PNG

Website Meta Analysis

  • Title
    Sex Shop Loja do Prazer - Sexshop - Sexyshop - Produtos Eróticos
  • Meta Keyword
    sex shop, sexshop, sex-shop virtual, sexshop internet, sex shop online, sexx chop, sexy shopping, sex toy, sextoys, produtos eróticos, produtos eroticos
  • Meta Description
    Sex Shop Loja do Prazer. A Maior SexShop Da América Latina, Sexyshop Com 15 Mil Produtos Eróticos.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    201.20.10.204
  • Domain Age
    13 Years, 12 Months, 6 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from lojadoprazer.com.br.

HTML Analysis

  • cache-control: private
  • content-length: 118803
  • content-type: text/html
  • expires: Sat, 23 Feb 2013 08:35:46 GMT
  • server: Microsoft-IIS/7.0
  • p3p: CP="CAO DSP COR CUR ADM TAI OUR STP NAV UNI" policyref="/w3c/p3p.xml"
  • x-powered-by: FastCommerce
  • date: Sat, 23 Feb 2013 08:35:45 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the terms of use (http://registro.br/termo/en.html),
% being prohibited its distribution, comercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2013-02-20 05:27:10 (BRT -03:00)

domain: lojadoprazer.com.br
owner: E Business Network Ltda
ownerid: 003.747.087/0001-53
responsible: Ger

DNS Analysis


DNS servers
buzios.rumo.com.br [201.20.10.204]
leblon.rumo.com.br [201.20.10.201]


DNS Records

Answer records
lojadoprazer.com.br A 201.20.10.204 3600s
lojadoprazer.com.br NS  angra.rumo.com.br 3600s
lojadoprazer.com.br NS  buzios.rumo.com.br 3600s
lojadoprazer.com.br NS  leblon4.rumo.com.br 3600s
lojadoprazer.com.br SOA
server: buzios
email: admin
serial: 62
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
lojadoprazer.com.br MX
preference: 10
exchange: mx.a.locaweb.com.br
3600s
lojadoprazer.com.br TXT v=spf1 include:aspmx.googlemail.com include:rumo.com.br include:_spf.locaweb.com.br include:spf.virtualtarget.com.br include:spf1.auinmeio.com.br include:spf2.auinmeio.com.br ~all 3600s

Authority records

Additional records
angra.rumo.com.br A 201.20.10.201 3600s
buzios.rumo.com.br A 201.20.10.204 1800s
leblon4.rumo.com.br A 200.158.83.49 3600s

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 305 Errors
  • 58 Warnings
Ratio Text/Html
  • 0.5913472938275285
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 6, Column 48: required attribute "TYPE" not specified
    <script language="JavaScript" src="LojaSite.js"></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 10, Column 16: there is no attribute "PROPERTY"
    <meta property="fb:app_id" content="132573280220920">

    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 12, Column 133: NET-enabling start-tag requires SHORTTAG YES
    …"Loja do Prazer Sex Shop, Sexshop Online" href="/XMLNoticias.asp?IDLoja=343" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 13, Column 155: cannot generate system identifier for general entity "NomeLoja"
    … href="XMLSearchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexs…

    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 13, Column 155: general entity "NomeLoja" not defined and no default entity
    … href="XMLSearchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexs…

    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.

  • Error Line 13, Column 163: reference to entity "NomeLoja" for which no system identifier could be generated
    …MLSearchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Onli…

    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 13, Column 154: entity was defined here
    …" href="XMLSearchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sex…
  • Warning Line 13, Column 206: cannot generate system identifier for general entity "news"
    …gine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Online&news=1">

    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 13, Column 206: general entity "news" not defined and no default entity
    …gine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Online&news=1">

    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.

  • Error Line 13, Column 210: reference to entity "news" for which no system identifier could be generated
    …gine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Online&news=1">

    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 13, Column 205: entity was defined here
    …gine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Online&news=1">
  • Error Line 13, Column 213: document type does not allow element "LINK" here
    …gine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Online&news=1">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 14, Column 68: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="content-type" content="text/html; charset=utf-8" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 14, Column 68: document type does not allow element "META" here
    <meta http-equiv="content-type" content="text/html; charset=utf-8" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 15, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="IRG-21FngvN00uApS3cpbBxnVS3pg-w78rnBNona0Kw" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 15, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="IRG-21FngvN00uApS3cpbBxnVS3pg-w78rnBNona0Kw" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 16, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="W_d-ET9r_POhgkIl4_B8-lI7J-G1m_wKL-jlsRLcbMk" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 16, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="W_d-ET9r_POhgkIl4_B8-lI7J-G1m_wKL-jlsRLcbMk" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 17, Column 46: document type does not allow element "META" here
    <META NAME="resource-type" content="document">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 18, Column 43: document type does not allow element "META" here
    <meta name="robots" content="index,follow">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 19, Column 43: document type does not allow element "META" here
    <meta name="revisit-after" content="1 day">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 20, Column 58: document type does not allow element "META" here
    <META NAME="geo.position" content="-23.636511,-46.660198">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 21, Column 67: document type does not allow element "META" here
    <META NAME="geo.placename" content="Campo Belo, São Paulo, Brazil">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 22, Column 40: document type does not allow element "META" here
    <META NAME="geo.region" content="br-sp">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 23, Column 68: document type does not allow element "LINK" here
    <link rel="shortcut icon" href="/lojas/00000343/images/favicon.swf">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 24, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="vPPmP2MlB8-FNKy0Opod2JBeHNQo2Cubv0oMrwPbAlM" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 24, Column 93: document type does not allow element "META" here
    …gle-site-verification" content="vPPmP2MlB8-FNKy0Opod2JBeHNQo2Cubv0oMrwPbAlM" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 25, Column 158: reference to entity "NomeLoja" for which no system identifier could be generated
    …MLSearchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Onli…

    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 13, Column 154: entity was defined here
    …" href="XMLSearchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sex…
  • Error Line 25, Column 201: document type does not allow element "LINK" here
    …earchEngine.asp?IDLoja=343&NomeLoja=Loja+do+Prazer+Sex+Shop%2C+Sexshop+Online">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 38, Column 7: end tag for element "HEAD" which is not open
    </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 40, Column 18: there is no attribute "LEFTMARGIN"
    <body leftmargin=0 topmargin=0 marginwidth=0 marginheight=0 bgcolor=#ffffff tex…

    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 40, Column 30: there is no attribute "TOPMARGIN"
    <body leftmargin=0 topmargin=0 marginwidth=0 marginheight=0 bgcolor=#ffffff tex…

    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 40, Column 44: there is no attribute "MARGINWIDTH"
    … leftmargin=0 topmargin=0 marginwidth=0 marginheight=0 bgcolor=#ffffff text=#4…

    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 40, Column 59: there is no attribute "MARGINHEIGHT"
    …opmargin=0 marginwidth=0 marginheight=0 bgcolor=#ffffff text=#4d4d4d link=#db0…

    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 40, Column 69: an attribute value must be a literal unless it contains only name characters
    … marginwidth=0 marginheight=0 bgcolor=#ffffff text=#4d4d4d link=#db0d33 vlink=…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 40, Column 82: an attribute value must be a literal unless it contains only name characters
    …0 marginheight=0 bgcolor=#ffffff text=#4d4d4d link=#db0d33 vlink=#4d4d4d alink…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 40, Column 95: an attribute value must be a literal unless it contains only name characters
    …t=0 bgcolor=#ffffff text=#4d4d4d link=#db0d33 vlink=#4d4d4d alink=#4f57c7 onLo…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 40, Column 109: an attribute value must be a literal unless it contains only name characters
    …fffff text=#4d4d4d link=#db0d33 vlink=#4d4d4d alink=#4f57c7 onLoad='self.focus…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 40, Column 123: an attribute value must be a literal unless it contains only name characters
    …f text=#4d4d4d link=#db0d33 vlink=#4d4d4d alink=#4f57c7 onLoad='self.focus();'>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 40, Column 153: document type does not allow element "BODY" here
    …f text=#4d4d4d link=#db0d33 vlink=#4d4d4d alink=#4f57c7 onLoad='self.focus();'>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 41, Column 62: cannot generate system identifier for general entity "t"
    ….rumo.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v…

    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 41, Column 62: general entity "t" not defined and no default entity
    ….rumo.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v…

    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.

  • Error Line 41, Column 63: reference to entity "t" for which no system identifier could be generated
    …rumo.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1…

    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 41, Column 61: entity was defined here
    …w.rumo.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&…
  • Warning Line 41, Column 66: cannot generate system identifier for general entity "n0"
    …o.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&…

    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 41, Column 66: general entity "n0" not defined and no default entity
    …o.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&…

    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.

  • Error Line 41, Column 68: reference to entity "n0" for which no system identifier could be generated
    …com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2…

    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 41, Column 65: entity was defined here
    …mo.com.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1…
  • Warning Line 41, Column 71: cannot generate system identifier for general entity "v0"
    ….br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=Qt…

    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 41, Column 71: general entity "v0" not defined and no default entity
    ….br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=Qt…

    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.

  • Error Line 41, Column 73: reference to entity "v0" for which no system identifier could be generated
    …r/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdC…

    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 41, Column 70: entity was defined here
    …m.br/SetGlobal.asp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=Q…
  • Warning Line 41, Column 87: cannot generate system identifier for general entity "n1"
    …p?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=V…

    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 41, Column 87: general entity "n1" not defined and no default entity
    …p?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=V…

    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.

  • Error Line 41, Column 89: reference to entity "n1" for which no system identifier could be generated
    …IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=Val…

    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 41, Column 86: entity was defined here
    …sp?IDLoja=343&t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=…
  • Warning Line 41, Column 101: cannot generate system identifier for general entity "v1"
    …=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1…

    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 41, Column 101: general entity "v1" not defined and no default entity
    …=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1…

    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.

  • Error Line 41, Column 103: reference to entity "v1" for which no system identifier could be generated
    …&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n…

    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 41, Column 100: entity was defined here
    …t=1&n0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=…
  • Warning Line 41, Column 106: cannot generate system identifier for general entity "n2"
    …=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=P…

    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 41, Column 106: general entity "n2" not defined and no default entity
    …=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=P…

    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.

  • Error Line 41, Column 108: reference to entity "n2" for which no system identifier could be generated
    …&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=Pes…

    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 41, Column 105: entity was defined here
    …0=Y&v0=351863223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=…
  • Warning Line 41, Column 118: cannot generate system identifier for general entity "v2"
    …223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=…

    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 41, Column 118: general entity "v2" not defined and no default entity
    …223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=…

    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.

  • Error Line 41, Column 120: reference to entity "v2" for which no system identifier could be generated
    …3537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&…

    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 41, Column 117: entity was defined here
    …3223537&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4…
  • Warning Line 41, Column 123: cannot generate system identifier for general entity "n3"
    …7&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5…

    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 41, Column 123: general entity "n3" not defined and no default entity
    …7&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5…

    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.

  • Error Line 41, Column 125: reference to entity "n3" for which no system identifier could be generated
    …n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c…

    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 41, Column 122: entity was defined here
    …37&n1=ItensCesta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=…
  • Warning Line 41, Column 137: cannot generate system identifier for general entity "v3"
    …a&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60…

    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 41, Column 137: general entity "v3" not defined and no default entity
    …a&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60…

    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.

  • Error Line 41, Column 139: reference to entity "v3" for which no system identifier could be generated
    …v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fw…

    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 41, Column 136: entity was defined here
    …ta&v1=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%6…
  • Warning Line 41, Column 142: cannot generate system identifier for general entity "n4"
    …1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s…

    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 41, Column 142: general entity "n4" not defined and no default entity
    …1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s…

    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.

  • Error Line 41, Column 144: reference to entity "n4" for which no system identifier could be generated
    …n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=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 41, Column 141: entity was defined here
    …=1&n2=QtdCesta&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&…
  • Warning Line 41, Column 155: cannot generate system identifier for general entity "v4"
    …&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></scri…

    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 41, Column 155: general entity "v4" not defined and no default entity
    …&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></scri…

    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.

  • Error Line 41, Column 157: reference to entity "v4" for which no system identifier could be generated
    …2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script…

    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 41, Column 154: entity was defined here
    …a&v2=1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></scr…
  • Warning Line 41, Column 160: cannot generate system identifier for general entity "m"
    …&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><t…

    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 41, Column 160: general entity "m" not defined and no default entity
    …&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><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.

  • Error Line 41, Column 161: reference to entity "m" for which no system identifier could be generated
    …n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><ta…

    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 41, Column 159: entity was defined here
    …1&n3=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><…
  • Warning Line 41, Column 164: cannot generate system identifier for general entity "c"
    …ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table…

    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 41, Column 164: general entity "c" not defined and no default entity
    …ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table…

    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.

  • Error Line 41, Column 165: reference to entity "c" for which no system identifier could be generated
    …alorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table …

    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 41, Column 163: entity was defined here
    …=ValorCesta&v3=1&n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><tabl…
  • Warning Line 41, Column 181: cannot generate system identifier for general entity "s"
    …4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table name=TabExterna …

    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 41, Column 181: general entity "s" not defined and no default entity
    …4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table name=TabExterna …

    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.

  • Error Line 41, Column 182: reference to entity "s" for which no system identifier could be generated
    …=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table name=TabExterna i…

    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 41, Column 180: entity was defined here
    …n4=PesoCesta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table name=TabExterna…
  • Error Line 41, Column 188: required attribute "TYPE" not specified
    …esta&v4=1&m=5&c=Z%3BOusG%60fwG&s=True'></script><table name=TabExterna id=TabE…

    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 41, Column 210: there is no attribute "NAME"
    …sG%60fwG&s=True'></script><table name=TabExterna id=TabExterna class=FundoTopo…

    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 41, Column 291: an attribute value must be a literal unless it contains only name characters
    … cellspacing=0 cellpadding=0 width=100%><tr class=EstEspacoTopoMenu><td valign…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 41, Column 490: document type does not allow element "LINK" here
    …text/css" rel="stylesheet" href="../lojas/00000343/htm/layout.css" media="all">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 42, Column 94: document type does not allow element "LINK" here
    …/css" rel="stylesheet" href="../lojas/00000343/htm/jquery_ui.css" media="all"> 

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 130, Column 282: NET-enabling start-tag requires SHORTTAG YES
    …;}" onblur="if (this.value == '') {this.value='Digite aqui o que procura';}" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 137, Column 230: NET-enabling start-tag requires SHORTTAG YES
    …3" alt="Compra segura, embalagem discreta e privacidade garantida" /></a></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 139, Column 133: NET-enabling start-tag requires SHORTTAG YES
    …ass='os_itens'>MEU CARRINHO</span><br /><span class="os_itens" id="QtdItensCes…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 139, Column 188: NET-enabling start-tag requires SHORTTAG YES
    …_itens" id="QtdItensCesta"></span><br /><span class="os_itens" id="ValorItensC…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 190, Column 419: there is no attribute "ONERROR"
    …T11041.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></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 190, Column 435: an attribute value must be a literal unless it contains only name characters
    …T11041.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 219, Column 321: an attribute value must be a literal unless it contains only name characters
    …T23058.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 274, Column 422: an attribute value must be a literal unless it contains only name characters
    …T14835.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 328, Column 353: an attribute value must be a literal unless it contains only name characters
    …455010.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 358, Column 344: an attribute value must be a literal unless it contains only name characters
    …T22637.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 400, Column 579: an attribute value must be a literal unless it contains only name characters
    …T13576.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 440, Column 380: an attribute value must be a literal unless it contains only name characters
    …T39879.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 476, Column 73: cannot generate system identifier for general entity "promocao"
    …a href="/listaprodutos.asp?idloja=343&promocao=True" class="dpromolanc">PROMO&…

    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 476, Column 73: general entity "promocao" not defined and no default entity
    …a href="/listaprodutos.asp?idloja=343&promocao=True" class="dpromolanc">PROMO&…

    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.

  • Error Line 476, Column 81: reference to entity "promocao" for which no system identifier could be generated
    …/listaprodutos.asp?idloja=343&promocao=True" class="dpromolanc">PROMO&Ccedil;&…

    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 476, Column 72: entity was defined here
    …<a href="/listaprodutos.asp?idloja=343&promocao=True" class="dpromolanc">PROMO…
  • Warning Line 477, Column 73: cannot generate system identifier for general entity "lancamento"
    …a href="/listaprodutos.asp?idloja=343&lancamento=True" class="dpromolanc">LAN&…

    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 477, Column 73: general entity "lancamento" not defined and no default entity
    …a href="/listaprodutos.asp?idloja=343&lancamento=True" class="dpromolanc">LAN&…

    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.

  • Error Line 477, Column 83: reference to entity "lancamento" for which no system identifier could be generated
    …istaprodutos.asp?idloja=343&lancamento=True" class="dpromolanc">LAN&Ccedil;AME…

    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 477, Column 72: entity was defined here
    …<a href="/listaprodutos.asp?idloja=343&lancamento=True" class="dpromolanc">LAN…
  • Warning Line 498, Column 143: NET-enabling start-tag requires SHORTTAG YES
    …0343/images/layout/bt_nf1.png" width="134" height="32" alt="Lancamentos" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 499, Column 139: NET-enabling start-tag requires SHORTTAG YES
    …000343/images/layout/bt_nf2.png" width="128" height="32" alt="Promocoes" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 500, Column 77: cannot generate system identifier for general entity "arq"
    ….com.br/sistema/Custom.asp?IDLoja=343&arq=fale_dra/fale_dra.html"><img src="..…

    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 500, Column 77: general entity "arq" not defined and no default entity
    ….com.br/sistema/Custom.asp?IDLoja=343&arq=fale_dra/fale_dra.html"><img src="..…

    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.

  • Error Line 500, Column 80: reference to entity "arq" for which no system identifier could be generated
    …m.br/sistema/Custom.asp?IDLoja=343&arq=fale_dra/fale_dra.html"><img src="../lo…

    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 500, Column 76: entity was defined here
    …r.com.br/sistema/Custom.asp?IDLoja=343&arq=fale_dra/fale_dra.html"><img src=".…
  • Warning Line 500, Column 208: NET-enabling start-tag requires SHORTTAG YES
    …ages/layout/bt_nf3.png" width="187" height="32" alt="Fale com nossa dra" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 501, Column 149: NET-enabling start-tag requires SHORTTAG YES
    …000343/images/layout/bt_nf4.png" width="194" height="32" alt="SexSquare" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 504, Column 144: NET-enabling start-tag requires SHORTTAG YES
    …out/banner/segurancan.gif" width="185" height="47" alt="Compra segura" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 507, Column 198: NET-enabling start-tag requires SHORTTAG YES
    …3/images/layout/banner/banner1.jpg" width="690" height="50" alt="" /></div>    

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 507, Column 205: end tag for "A" omitted, but its declaration does not permit this
    …3/images/layout/banner/banner1.jpg" width="690" height="50" alt="" /></div>    
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 507, Column 29: start tag was here
        <div class="fc_Banner1"><a href="http://www.lojadoprazer.com.br/page,idloja…
  • Error Line 520, Column 60: an attribute value must be a literal unless it contains only name characters
    …lign=top><table name=TabConteudoeRodape width=100% cellpadding=0 cellspacing=0>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 521, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …=EstEspacoTopoConteudo><img src=images/shim.gif width=1 height=7></td></tr><tr…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 521, Column 110: required attribute "ALT" not specified
    …=EstEspacoTopoConteudo><img src=images/shim.gif width=1 height=7></td></tr><tr…

    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 521, Column 233: NET-enabling start-tag requires SHORTTAG YES
    …EspacoEsquerdaConteudo><img src=images/shim.gif width=1 height=400></td><td va…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 521, Column 233: required attribute "ALT" not specified
    …EspacoEsquerdaConteudo><img src=images/shim.gif width=1 height=400></td><td va…

    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 521, Column 287: there is no attribute "NAME"
    …shim.gif width=1 height=400></td><td valign=top name=InicioConteudo width=100%>

    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 521, Column 311: an attribute value must be a literal unless it contains only name characters
    …shim.gif width=1 height=400></td><td valign=top name=InicioConteudo width=100%>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 522, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100% cellpadding=0 cellspacing=0>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 523, Column 17: required attribute "TYPE" not specified
      <tr><td><style>

    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 523, Column 17: document type does not allow element "STYLE" here
      <tr><td><style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 526, Column 8: 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 533, Column 79: end tag for element "FONT" which is not open
    …if(Juros[MaxParcelas-1]>0)ComSem=""; else ComSem="&nbsp;sem&nbsp;juros</font>";

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 534, Column 49: end tag for element "B" which is not open
    ….write("ou&nbsp;<b>"+MaxParcelas+"x</b>"+ComSem+" de&nbsp;<b>"+FormatPrecoReai…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 534, Column 148: end tag for element "B" which is not open
    …+FormatPrecoReais(CalculaParcelaJurosCompostos(PrecoProd,MaxParcelas))+"</b>");

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 560, Column 8: 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 562, Column 130: end tag for element "STRONG" which is not open
    …ice(PrecoOri-PrecoProd,'R$')+"</strong> ("+FormatNum(((PrecoOri-PrecoProd)/Pre…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 562, Column 191: end tag for element "FONT" which is not open
    …R$')+"</strong> ("+FormatNum(((PrecoOri-PrecoProd)/PrecoOri)*100)+"%)</font>");

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 579, Column 99: an attribute value must be a literal unless it contains only name characters
    …xaiio Pheromones" href=BannerRedir.asp?IDLoja=343&IDBanner=11237&URL=%2Fprod%2…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 579, Column 521: an attribute value must be a literal unless it contains only name characters
    …ges/slide001.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 580, Column 51: an attribute value must be a literal unless it contains only name characters
    …le="Happy Rabbit" href=BannerRedir.asp?IDLoja=343&IDBanner=10480&URL=%2FListaP…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 580, Column 308: an attribute value must be a literal unless it contains only name characters
    …ges/slide002.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 581, Column 50: an attribute value must be a literal unless it contains only name characters
    …tle="Secret Play" href=BannerRedir.asp?IDLoja=343&IDBanner=10743&URL=%2Fprod%2…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 581, Column 349: an attribute value must be a literal unless it contains only name characters
    …ges/slide003.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 592, Column 61: an attribute value must be a literal unless it contains only name characters
    …nner"><a title="" href=BannerRedir.asp?IDLoja=343&IDBanner=9638&URL=%2Fpage%2C…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 592, Column 235: an attribute value must be a literal unless it contains only name characters
    …anner5.gif' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 592, Column 243: required attribute "ALT" not specified
    …anner5.gif' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    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 594, Column 105: reference to entity "arq" for which no system identifier could be generated
    …m.br/sistema/Custom.asp?IDLoja=343&arq=pedidos.html"><img src="../lojas/000003…

    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 500, Column 76: entity was defined here
    …r.com.br/sistema/Custom.asp?IDLoja=343&arq=fale_dra/fale_dra.html"><img src=".…
  • Error Line 594, Column 189: required attribute "ALT" not specified
    …img src="../lojas/00000343/images/layout/btn_pedidos.jpg" border="0"></a></div>

    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 669, Column 10: end tag for "UL" omitted, but its declaration does not permit this
        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 599, Column 4: start tag was here
    	  <ul>
  • Error Line 695, Column 410: an attribute value must be a literal unless it contains only name characters
    …/T8054.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 698, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(85.9,0);</script><script>Mostra…

    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 698, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(85.9,0);</script><script>MostraEconomia(85.9,85.9);</script></di…

    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 704, Column 250: an attribute value must be a literal unless it contains only name characters
    …/T4652.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 707, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(99.9,0);</script><script>Mostra…

    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 707, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(99.9,0);</script><script>MostraEconomia(99.9,99.9);</script></di…

    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 713, Column 324: an attribute value must be a literal unless it contains only name characters
    …/T1580.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 716, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(19.9,0);</script><script>Mostra…

    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 716, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(19.9,0);</script><script>MostraEconomia(19.9,19.9);</script></di…

    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 722, Column 494: an attribute value must be a literal unless it contains only name characters
    …T39927.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 725, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(169.9,0);</script><script>Mostr…

    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 725, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(169.9,0);</script><script>MostraEconomia(169.9,169.9);</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 731, Column 353: an attribute value must be a literal unless it contains only name characters
    …455000.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 734, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(149.9,0);</script><script>Mostr…

    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 734, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(149.9,0);</script><script>MostraEconomia(149.9,149.9);</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 740, Column 353: an attribute value must be a literal unless it contains only name characters
    …600005.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 743, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(69.9,0);</script><script>Mostra…

    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 743, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(69.9,0);</script><script>MostraEconomia(69.9,69.9);</script></di…

    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 749, Column 362: an attribute value must be a literal unless it contains only name characters
    …455050.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 752, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(99.9,0);</script><script>Mostra…

    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 752, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(99.9,0);</script><script>MostraEconomia(99.9,99.9);</script></di…

    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 758, Column 444: an attribute value must be a literal unless it contains only name characters
    …600004.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 761, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(92.9,0);</script><script>Mostra…

    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 761, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(92.9,0);</script><script>MostraEconomia(92.9,92.9);</script></di…

    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 767, Column 381: an attribute value must be a literal unless it contains only name characters
    …T95005.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 770, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(80.0,0);</script><script>Mostra…

    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 770, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(80.0,0);</script><script>MostraEconomia(80.0,100.0);</script></d…

    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 776, Column 372: an attribute value must be a literal unless it contains only name characters
    …T39880.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 779, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(499.9,0);</script><script>Mostr…

    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 779, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(499.9,0);</script><script>MostraEconomia(499.9,499.9);</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 785, Column 408: an attribute value must be a literal unless it contains only name characters
    …/T2033.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 788, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(999.9,0);</script><script>Mostr…

    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 788, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(999.9,0);</script><script>MostraEconomia(999.9,999.9);</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 794, Column 335: an attribute value must be a literal unless it contains only name characters
    …455066.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 797, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(64.9,0);</script><script>Mostra…

    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 797, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(64.9,0);</script><script>MostraEconomia(64.9,64.9);</script></di…

    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 803, Column 350: an attribute value must be a literal unless it contains only name characters
    …T12817.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 806, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(69.9,0);</script><script>Mostra…

    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 806, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(69.9,0);</script><script>MostraEconomia(69.9,94.9);</script></di…

    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 812, Column 343: an attribute value must be a literal unless it contains only name characters
    …T14744.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 815, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(39.9,0);</script><script>Mostra…

    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 815, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(39.9,0);</script><script>MostraEconomia(39.9,39.9);</script></di…

    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 821, Column 442: an attribute value must be a literal unless it contains only name characters
    …455065.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 824, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(74.9,0);</script><script>Mostra…

    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 824, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(74.9,0);</script><script>MostraEconomia(74.9,74.9);</script></di…

    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 832, Column 404: an attribute value must be a literal unless it contains only name characters
    …T11027.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 835, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(109.9,0);</script><script>Mostr…

    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 835, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(109.9,0);</script><script>MostraEconomia(109.9,109.9);</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 841, Column 329: an attribute value must be a literal unless it contains only name characters
    …T14775.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 844, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(5.9,0);</script><script>MostraE…

    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 844, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(5.9,0);</script><script>MostraEconomia(5.9,5.9);</script></div>

    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 850, Column 277: an attribute value must be a literal unless it contains only name characters
    …T23068.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 853, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(14.9,0);</script><script>Mostra…

    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 853, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(14.9,0);</script><script>MostraEconomia(14.9,14.9);</script></di…

    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 859, Column 460: an attribute value must be a literal unless it contains only name characters
    …T14832.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 862, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(3.9,0);</script><script>MostraE…

    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 862, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(3.9,0);</script><script>MostraEconomia(3.9,9.9);</script></div>

    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 868, Column 390: an attribute value must be a literal unless it contains only name characters
    …T14956.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 871, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(19.9,0);</script><script>Mostra…

    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 871, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(19.9,0);</script><script>MostraEconomia(19.9,19.9);</script></di…

    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 877, Column 342: an attribute value must be a literal unless it contains only name characters
    …T45080.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 880, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(29.9,0);</script><script>Mostra…

    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 880, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(29.9,0);</script><script>MostraEconomia(29.9,34.9);</script></di…

    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 886, Column 364: an attribute value must be a literal unless it contains only name characters
    …T14945.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 889, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(2.5,0);</script><script>MostraE…

    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 889, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(2.5,0);</script><script>MostraEconomia(2.5,2.5);</script></div>

    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 895, Column 447: an attribute value must be a literal unless it contains only name characters
    …T14829.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 898, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(3.9,0);</script><script>MostraE…

    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 898, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(3.9,0);</script><script>MostraEconomia(3.9,9.9);</script></div>

    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 904, Column 418: an attribute value must be a literal unless it contains only name characters
    …T14716.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 907, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(19.9,0);</script><script>Mostra…

    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 907, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(19.9,0);</script><script>MostraEconomia(19.9,19.9);</script></di…

    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 913, Column 364: an attribute value must be a literal unless it contains only name characters
    …T14947.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 916, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(2.5,0);</script><script>MostraE…

    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 916, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(2.5,0);</script><script>MostraEconomia(2.5,2.5);</script></div>

    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 922, Column 420: an attribute value must be a literal unless it contains only name characters
    …T11041.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 925, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(449.9,0);</script><script>Mostr…

    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 925, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(449.9,0);</script><script>MostraEconomia(449.9,449.9);</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 931, Column 402: an attribute value must be a literal unless it contains only name characters
    …T14607.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 934, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(1.05,0);</script><script>Mostra…

    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 934, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(1.05,0);</script><script>MostraEconomia(1.05,1.5);</script></div…

    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 940, Column 398: an attribute value must be a literal unless it contains only name characters
    …T11382.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 943, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(11.95,0);</script><script>Mostr…

    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 943, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(11.95,0);</script><script>MostraEconomia(11.95,59.9);</script></d…

    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 949, Column 425: an attribute value must be a literal unless it contains only name characters
    …T15092.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 952, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(6.4,0);</script><script>MostraE…

    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 952, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(6.4,0);</script><script>MostraEconomia(6.4,6.4);</script></div>

    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 958, Column 405: an attribute value must be a literal unless it contains only name characters
    …T14817.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 961, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(19.9,0);</script><script>Mostra…

    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 961, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(19.9,0);</script><script>MostraEconomia(19.9,19.9);</script></di…

    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 969, Column 446: an attribute value must be a literal unless it contains only name characters
    …500355.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 972, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(11.45,0);</script><script>Mostr…

    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 972, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(11.45,0);</script><script>MostraEconomia(11.45,22.9);</script></d…

    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 978, Column 430: an attribute value must be a literal unless it contains only name characters
    …T11068.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 981, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(25.95,0);</script><script>Mostr…

    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 981, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(25.95,0);</script><script>MostraEconomia(25.95,129.9);</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 987, Column 459: an attribute value must be a literal unless it contains only name characters
    …T15148.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 990, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(4.5,0);</script><script>MostraE…

    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 990, Column 72: required attribute "TYPE" not specified
    …ostraMaxParcela(4.5,0);</script><script>MostraEconomia(4.5,7.9);</script></div>

    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 996, Column 339: an attribute value must be a literal unless it contains only name characters
    …T11345.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 999, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(89.9,0);</script><script>Mostra…

    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 999, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(89.9,0);</script><script>MostraEconomia(89.9,179.9);</script></d…

    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 1005, Column 395: an attribute value must be a literal unless it contains only name characters
    …T11353.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1008, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(43.9,0);</script><script>Mostra…

    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 1008, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(43.9,0);</script><script>MostraEconomia(43.9,62.8);</script></di…

    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 1014, Column 279: an attribute value must be a literal unless it contains only name characters
    …/T5803.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1017, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(20.9,0);</script><script>Mostra…

    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 1017, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(20.9,0);</script><script>MostraEconomia(20.9,29.9);</script></di…

    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 1023, Column 476: an attribute value must be a literal unless it contains only name characters
    …500399.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1026, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(11.45,0);</script><script>Mostr…

    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 1026, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(11.45,0);</script><script>MostraEconomia(11.45,22.9);</script></d…

    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 1032, Column 554: an attribute value must be a literal unless it contains only name characters
    …T14048.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1035, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(89.9,0);</script><script>Mostra…

    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 1035, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(89.9,0);</script><script>MostraEconomia(89.9,189.9);</script></d…

    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 1041, Column 472: an attribute value must be a literal unless it contains only name characters
    …T11437.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1044, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(250.0,0);</script><script>Mostr…

    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 1044, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(250.0,0);</script><script>MostraEconomia(250.0,314.9);</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 1050, Column 454: an attribute value must be a literal unless it contains only name characters
    …500326.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1053, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(11.45,0);</script><script>Mostr…

    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 1053, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(11.45,0);</script><script>MostraEconomia(11.45,22.9);</script></d…

    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 1059, Column 411: an attribute value must be a literal unless it contains only name characters
    …T40609.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1062, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(299.9,0);</script><script>Mostr…

    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 1062, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(299.9,0);</script><script>MostraEconomia(299.9,434.9);</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 1068, Column 475: an attribute value must be a literal unless it contains only name characters
    …500383.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1071, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(11.45,0);</script><script>Mostr…

    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 1071, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(11.45,0);</script><script>MostraEconomia(11.45,22.9);</script></d…

    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 1077, Column 356: an attribute value must be a literal unless it contains only name characters
    …T11215.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1080, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(119.9,0);</script><script>Mostr…

    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 1080, Column 74: required attribute "TYPE" not specified
    …raMaxParcela(119.9,0);</script><script>MostraEconomia(119.9,199.9);</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 1086, Column 334: an attribute value must be a literal unless it contains only name characters
    …T14679.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1089, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(1.99,0);</script><script>Mostra…

    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 1089, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(1.99,0);</script><script>MostraEconomia(1.99,4.9);</script></div…

    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 1095, Column 324: an attribute value must be a literal unless it contains only name characters
    …T14209.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1098, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(39.9,0);</script><script>Mostra…

    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 1098, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(39.9,0);</script><script>MostraEconomia(39.9,64.9);</script></di…

    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 1106, Column 381: an attribute value must be a literal unless it contains only name characters
    …T95005.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1109, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(80.0,0);</script><script>Mostra…

    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 1109, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(80.0,0);</script><script>MostraEconomia(80.0,100.0);</script></d…

    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 1115, Column 381: an attribute value must be a literal unless it contains only name characters
    …T95006.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1118, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(80.0,0);</script><script>Mostra…

    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 1118, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(80.0,0);</script><script>MostraEconomia(80.0,100.0);</script></d…

    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 1124, Column 381: an attribute value must be a literal unless it contains only name characters
    …T95007.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1127, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(80.0,0);</script><script>Mostra…

    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 1127, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(80.0,0);</script><script>MostraEconomia(80.0,100.0);</script></d…

    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 1133, Column 381: an attribute value must be a literal unless it contains only name characters
    …T95008.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1136, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(80.0,0);</script><script>Mostra…

    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 1136, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(80.0,0);</script><script>MostraEconomia(80.0,100.0);</script></d…

    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 1142, Column 396: an attribute value must be a literal unless it contains only name characters
    …T95001.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1145, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(50.0,0);</script><script>Mostra…

    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 1145, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(50.0,0);</script><script>MostraEconomia(50.0,60.0);</script></di…

    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 1151, Column 396: an attribute value must be a literal unless it contains only name characters
    …T95002.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1154, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(50.0,0);</script><script>Mostra…

    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 1154, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(50.0,0);</script><script>MostraEconomia(50.0,60.0);</script></di…

    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 1160, Column 396: an attribute value must be a literal unless it contains only name characters
    …T95003.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1163, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(50.0,0);</script><script>Mostra…

    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 1163, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(50.0,0);</script><script>MostraEconomia(50.0,60.0);</script></di…

    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 1169, Column 396: an attribute value must be a literal unless it contains only name characters
    …T95004.jpg' border=0 class=EstImgFC onError=MostraImgOnError(this,0)></a></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1172, Column 31: required attribute "TYPE" not specified
      <div class="parcela"><script>MostraMaxParcela(50.0,0);</script><script>Mostra…

    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 1172, Column 73: required attribute "TYPE" not specified
    …traMaxParcela(50.0,0);</script><script>MostraEconomia(50.0,60.0);</script></di…

    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 1220, Column 51: NET-enabling start-tag requires SHORTTAG YES
    … width=3 class=EstLinhaBarraExt><img src=images/shim.gif width=3 height=1></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1220, Column 51: required attribute "ALT" not specified
    … width=3 class=EstLinhaBarraExt><img src=images/shim.gif width=3 height=1></td>

    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 1221, Column 48: NET-enabling start-tag requires SHORTTAG YES
    <td width=1 class=EstLinhaBarra><img src=images/shim.gif width=1 height=1></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1221, Column 48: required attribute "ALT" not specified
    <td width=1 class=EstLinhaBarra><img src=images/shim.gif width=1 height=1></td>

    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 1222, Column 51: NET-enabling start-tag requires SHORTTAG YES
    … width=3 class=EstLinhaBarraExt><img src=images/shim.gif width=3 height=1></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1222, Column 51: required attribute "ALT" not specified
    … width=3 class=EstLinhaBarraExt><img src=images/shim.gif width=3 height=1></td>

    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 1226, Column 59: an attribute value must be a literal unless it contains only name characters
    …eExterno id=TabRodapeExterno width=100% cellspacing=0 cellpadding=0><tr><td va…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 1226, Column 198: document type does not allow element "LINK" here
    …tylesheet" href="../lojas/00000343/htm/layout.css" type="text/css" media="all">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1237, Column 87: cannot generate system identifier for general entity "style"
    …o" src="XMLPageHistory.asp?IDLoja=343&style=xsl" style="width:100%;height:250"…

    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 1237, Column 87: general entity "style" not defined and no default entity
    …o" src="XMLPageHistory.asp?IDLoja=343&style=xsl" style="width:100%;height:250"…

    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.

  • Error Line 1237, Column 92: reference to entity "style" for which no system identifier could be generated
    …c="XMLPageHistory.asp?IDLoja=343&style=xsl" style="width:100%;height:250"></if…

    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 1237, Column 86: entity was defined here
    …no" src="XMLPageHistory.asp?IDLoja=343&style=xsl" style="width:100%;height:250…
  • Warning Line 1239, Column 213: NET-enabling start-tag requires SHORTTAG YES
    …/00000343/images/slide002.jpg" width="950" height="250" alt="Sex Square" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1248, Column 117: cannot generate system identifier for general entity "scr"
    …oprazer.neoassist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' ,…

    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 1248, Column 117: general entity "scr" not defined and no default entity
    …oprazer.neoassist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' ,…

    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.

  • Error Line 1248, Column 120: reference to entity "scr" for which no system identifier could be generated
    …azer.neoassist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' , 's…

    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 1248, Column 116: entity was defined here
    …doprazer.neoassist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' …
  • Warning Line 1248, Column 129: cannot generate system identifier for general entity "ForcaAutenticar"
    …ssist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' , 'status , s…

    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 1248, Column 129: general entity "ForcaAutenticar" not defined and no default entity
    …ssist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' , 'status , s…

    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.

  • Error Line 1248, Column 144: reference to entity "ForcaAutenticar" for which no system identifier could be generated
    …on=neolive&scr=request&ForcaAutenticar=1', 'Chat' , 'status , scrollbars=no ,w…

    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 1248, Column 128: entity was defined here
    …assist.com/?action=neolive&scr=request&ForcaAutenticar=1', 'Chat' , 'status , …
  • Warning Line 1258, Column 130: NET-enabling start-tag requires SHORTTAG YES
    …out/ico_pagamento.gif" width="616" height="52" alt="formas de pagamento" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1262, Column 166: NET-enabling start-tag requires SHORTTAG YES
    …t/ico_tel.gif" width="200" height="52" alt="atendimento: (11) 5034-7444" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1278, Column 167: NET-enabling start-tag requires SHORTTAG YES
    …000343/images/layout/ico_face.gif" width="39" height="52" alt="facebook" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1279, Column 164: NET-enabling start-tag requires SHORTTAG YES
    …0343/images/layout/ico_twitter.gif" width="43" height="52" alt="twitter" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1280, Column 167: NET-enabling start-tag requires SHORTTAG YES
    …0343/images/layout/ico_youtube.gif" width="42" height="52" alt="youtube" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1281, Column 173: NET-enabling start-tag requires SHORTTAG YES
    …000343/images/layout/ico_foto.gif" width="39" height="52" alt="istagram" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1295, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …ojas/00000343/images/layout/ico_seguranca.gif" width="79" height="52" alt="" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1296, Column 152: NET-enabling start-tag requires SHORTTAG YES
    …/images/layout/ico_seguranca2.gif" width="68" height="52" alt="" /></a>        

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1300, Column 130: reference to entity "arq" for which no system identifier could be generated
    … id="news_" src="/custom.asp?idloja=343&arq=Newsletter_rod.htm&int=1"></iframe>

    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 500, Column 76: entity was defined here
    …r.com.br/sistema/Custom.asp?IDLoja=343&arq=fale_dra/fale_dra.html"><img src=".…
  • Warning Line 1304, Column 116: NET-enabling start-tag requires SHORTTAG YES
    …/00000343/images/layout/sex_rod.jpg" width="464" height="91" alt="" /></a>	    

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1306, Column 189: NET-enabling start-tag requires SHORTTAG YES
    …de CNPJ: 03.747.087/0001-53, fica sediada em S&atilde;o Paulo/SP - Brasil<br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1312, Column 13: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
          <h2><p>A Sexshop Loja Do Prazer nasceu em 1999, com o objetivo de levar o…

    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 1313, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p>A nossa loja virtual oferece serviços de entrega em até 4 horas para São Pau…

    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 1313, Column 139: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … horas para São Paulo Capital via motoboy, Serviço Exclusivo nesse segmento.<p>

    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 1314, Column 4: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
     <p>Hoje em dia um relacionamento cai na rotina e você só consegue praticar o p…

    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 1314, Column 435: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …e e descubra como um simples acessório erótico pode levar o casal à loucura.<p>

    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 1315, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p>E para as mulheres, nossa dica especial é sempre apostar no uso da lingerie …

    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 1316, Column 3: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <p>Loja do Prazer - L&iacute;der, Completa e Descomplicada</p></h2>

    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 1340, Column 8: required attribute "TYPE" not specified
    <script>MostraDadosCesta();</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 1349, Column 265: end tag for element "A" which is not open
    …184px;height:100px;">Loja do Prazer</a></h1><div class="os_tBanner1"><img src=…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1349, Column 270: end tag for element "H1" which is not open
    …;height:100px;">Loja do Prazer</a></h1><div class="os_tBanner1"><img src="../l…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1349, Column 433: end tag for element "DIV" which is not open
    …lt="Compra segura, embalagem discreta e privacidade garantida" /></div></div>';

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1349, Column 439: end tag for element "DIV" which is not open
    …lt="Compra segura, embalagem discreta e privacidade garantida" /></div></div>';

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1355, Column 168: end tag for element "A" which is not open
    …s/BotContComprando.png' border='0'></a></div><div class='os_btesp1'><input nam…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1355, Column 174: end tag for element "DIV" which is not open
    …ontComprando.png' border='0'></a></div><div class='os_btesp1'><input name='Rec…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1355, Column 373: end tag for element "DIV" which is not open
    …000343/images/BotRecalcular.png'></div><div class='os_btesp3'><input name='Com…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1355, Column 547: end tag for element "DIV" which is not open
    …0 src='../lojas/00000343/images/BotComprar.png' onclick='ComprarImg()'></div>";

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1359, Column 142: end tag for element "A" which is not open
    …s/BotContComprando.png' border='0'></a></div><div class='os_btesp1'><input nam…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1359, Column 148: end tag for element "DIV" which is not open
    …ontComprando.png' border='0'></a></div><div class='os_btesp1'><input name='Rec…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1359, Column 347: end tag for element "DIV" which is not open
    …000343/images/BotRecalcular.png'></div><div class='os_btesp3'><input name='Com…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1402, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1420, Column 200: NET-enabling start-tag requires SHORTTAG YES
    …n/1032099659/?value=0&amp;label=-C9HCIHD3AMQy66S7AM&amp;guid=ON&amp;script=0"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1424, Column 8: 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 1430, Column 40: there is no attribute "NAME"
    …/td></tr></table><div id=overlay name=overlay></div><script>DefineCatDefault(I…

    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 1430, Column 61: required attribute "TYPE" not specified
    … id=overlay name=overlay></div><script>DefineCatDefault(IDCategoriaAtualFC);</…

    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 1430, Column 172: cannot generate system identifier for general entity "IDLoja"
    …"GoogleAnalytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" …

    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 1430, Column 172: general entity "IDLoja" not defined and no default entity
    …"GoogleAnalytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" …

    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.

  • Error Line 1430, Column 178: reference to entity "IDLoja" for which no system identifier could be generated
    …eAnalytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" style=…

    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 1430, Column 171: entity was defined here
    …="GoogleAnalytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp"…
  • Warning Line 1430, Column 183: cannot generate system identifier for general entity "pag"
    …ytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" style="widt…

    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 1430, Column 183: general entity "pag" not defined and no default entity
    …ytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" style="widt…

    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.

  • Error Line 1430, Column 186: reference to entity "pag" for which no system identifier could be generated
    …cs.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" style="width:1…

    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 1430, Column 182: entity was defined here
    …lytics.asp?code=UA-618869-1&IDLoja=343&pag=%2Fsistema%2Fhome%2Easp" style="wid…

Visitor Analysis

Daily Visitor
  • 3.617 visits
Daily Visitor