miniinthebox.com

MiniInTheBox offers wide selection of Cool Gadgets, electronic gadgets at cheap price; find new and cool gadgets for time limit of 50% discount and enjoy free shipping now! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 31-07-2013 01:23:05  (update).

Overview Info

  • Domain Name
    miniinthebox.com
  • Favicon
  • Alexa Rank
    #2815
  • Google Page Rank
    PR 4
  • Ip Address
    216.146.46.10
  • Page Size
    317.5 KB
  • Images
    0 GIF, 11 JPG, 37 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 21 9 13 0 0

Website Meta Analysis



  • Title
    Cool Gadgets, Electronic Gadgets on Sale, Free Shipping for all New and Cool Gadgets at MiniInTheBox
  • Meta Keyword
    Cool Gadgets, New Gadgets, Electronic Gadgets
  • Meta Description
    MiniInTheBox offers wide selection of Cool Gadgets, electronic gadgets at cheap price; find new and cool gadgets for time limit of 50% discount and enjoy free shipping now!

Technical Analysis



  • Webserver
    litb-webserver
  • Ip Address
    216.146.46.10
  • Domain Age
    3 Years, 8 Months, 0 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: litb-webserver
  • content-type: text/html; charset=utf-8
  • p3p: CP="CAO PSA OUR"
  • content-encoding: gzip
  • expires: Wed, 31 Jul 2013 13:22:59 GMT
  • cache-control: max-age=0, no-cache, no-store
  • pragma: no-cache
  • date: Wed, 31 Jul 2013 13:22:59 GMT
  • content-length: 58900
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Light In The Box Limited
ATTN MINIINTHEBOX.COM
care of Network Solutions
PO Box 459
Drums, PA. US 18222

Domain Name: MINIINTHEBOX.COM
-

-
Administrative Contact, Technical Contact:
Light In The Box email
ATTN MINIINTHEBOX.COM
care of Network Solutions
PO Box 459
Drums, PA 18222
US
570-708-8780

Expires: 19-Nov-2013.
Created: 12-Sep-2010.
Database Updated: 17-Sep-2011 13:08:15 EDT.
Name Servers:
PDNS1.ULTRADNS.NET 204.74.108.1
PDNS2.ULTRADNS.NET 204.74.109.1
PDNS3.ULTRADNS.ORG 199.7.68.1
PDNS4.ULTRADNS.ORG 199.7.69.1
PDNS5.ULTRADNS.INFO 204.74.114.1
PDNS6.ULTRADNS.CO.UK

DNS Analysis


DNS servers
ns1.p20.dynect.net [208.78.70.20]
ns3.p20.dynect.net [208.78.71.20]
ns2.p20.dynect.net [204.13.250.20]
ns4.p20.dynect.net [204.13.251.20]

DNS Records

Answer records
miniinthebox.com SOA
server: ns1.p20.dynect.net
email: zengyu@lightinthebox.com
serial: 2012122000
refresh: 3600
retry: 600
expire: 604800
minimum ttl: 60
3600s
miniinthebox.com NS  ns4.p20.dynect.net 86400s
miniinthebox.com NS  ns1.p20.dynect.net 86400s
miniinthebox.com NS  ns3.p20.dynect.net 86400s
miniinthebox.com NS  ns2.p20.dynect.net 86400s
miniinthebox.com A 216.146.46.11 60s
miniinthebox.com A 216.146.46.10 60s
miniinthebox.com MX
preference: 30
exchange: aspmx3.googlemail.com
86400s
miniinthebox.com MX
preference: 30
exchange: aspmx4.googlemail.com
86400s
miniinthebox.com MX
preference: 30
exchange: aspmx5.googlemail.com
86400s
miniinthebox.com MX
preference: 10
exchange: aspmx.l.google.com
86400s
miniinthebox.com MX
preference: 20
exchange: alt1.aspmx.l.google.com
86400s
miniinthebox.com MX
preference: 20
exchange: alt2.aspmx.l.google.com
86400s
miniinthebox.com MX
preference: 30
exchange: aspmx2.googlemail.com
86400s
miniinthebox.com TXT v=spf1 ip4:174.36.249.66 ~all 86400s

Authority records

Additional records

IP 216.146.46.10 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Manchester
  • Continent Code
    03101
  • Latitude
    603
  • Longitude
    506
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.146.46.10"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=216.146.46.10?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 216.146.32.0 - 216.146.47.255
    CIDR: 216.146.32.0/20
    OriginAS: AS33517
    NetName: DNSINC-3
    NetHandle: NET-216-146-32-0-1
    Parent: NET-216-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2008-07-16
    Updated: 2012-12-03
    Ref: http://whois.arin.net/rest/net/NET-216-146-32-0-1

    OrgName: Dynamic Network Services, Inc.
    OrgId: DNS-33
    Address: 150 Dow St.
    City: Manchester
    StateProv: NH
    PostalCode: 03101
    Country: US
    RegDate: 2004-01-06
    Updated: 2012-12-03
    Ref: http://whois.arin.net/rest/org/DNS-33

    OrgNOCHandle: NOC1473-ARIN
    OrgNOCName: Network Operations Center
    OrgNOCPhone: +1-603-668-4998
    OrgNOCEmail:
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC1473-ARIN

    OrgAbuseHandle: ABUSE514-ARIN
    OrgAbuseName: Abuse Department
    OrgAbusePhone: +1-603-668-4998
    OrgAbuseEmail:
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE514-ARIN

    OrgTechHandle: IAA29-ARIN
    OrgTechName: IP Address Administator
    OrgTechPhone: +1-603-296-1598
    OrgTechEmail:
    OrgTechRef: http://whois.arin.net/rest/poc/IAA29-ARIN

    RTechHandle: IAA29-ARIN
    RTechName: IP Address Administator
    RTechPhone: +1-603-296-1598
    RTechEmail:
    RTechRef: http://whois.arin.net/rest/poc/IAA29-ARIN

    RAbuseHandle: EMAIL66-ARIN
    RAbuseName: Email Deliverability
    RAbusePhone: +1-603-668-4998
    RAbuseEmail:
    RAbuseRef: http://whois.arin.net/rest/poc/EMAIL66-ARIN

    RNOCHandle: NOC1473-ARIN
    RNOCName: Network Operations Center
    RNOCPhone: +1-603-668-4998
    RNOCEmail:
    RNOCRef: http://whois.arin.net/rest/poc/NOC1473-ARIN

    RAbuseHandle: ABUSE514-ARIN
    RAbuseName: Abuse Department
    RAbusePhone: +1-603-668-4998
    RAbuseEmail:
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE514-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 354 Errors
  • 217 Warnings
Ratio Text/Html
  • 0.36302930944859846
Message Error
  • Error Line 13, Column 16: there is no attribute "property"
    <meta property="og:title" content=""/><meta property="og:type" content="product…

    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 13, Column 530: required attribute "type" not specified
    …http://www.miniinthebox.com/" /><style>.widget-dfp div{display:inline;}.widget…

    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 16, Column 7: required attribute "type" not specified
    <style>section {display:block;} #mainNav .cateWrap .subCate dt a:link, #mainNav…

    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 19, Column 7: required attribute "type" not specified
    <style>#wrapper{width:992px;margin:0 auto;}#wrapper-t-l, .w-content-wrap .side-…

    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 25, Column 118: required attribute "type" not specified
    …/1.3.1/jquery.min.js"></script><script>!window.jQuery && document.write('<scri…

    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 25, Column 134: character "&" is the first character of a delimiter but occurred as data
    …n.js"></script><script>!window.jQuery && document.write('<script src="'+litb.r…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 25, Column 135: character "&" is the first character of a delimiter but occurred as data
    ….js"></script><script>!window.jQuery && document.write('<script src="'+litb.re…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 25, Column 199: required attribute "type" not specified
    …nt.write('<script src="'+litb.resouceURL+'jquery.min.js"><\/script>');</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 25, Column 199: document type does not allow element "script" here
    …nt.write('<script src="'+litb.resouceURL+'jquery.min.js"><\/script>');</script>

    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 25, Column 200: character "<" is the first character of a delimiter but occurred as data
    …nt.write('<script src="'+litb.resouceURL+'jquery.min.js"><\/script>');</script>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 26, Column 98: document type does not allow element "script" here
    …t" src="http://partner.googleadservices.com/gampad/google_service.js"></script>

    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 27, Column 110: document type does not allow element "script" here
    …e_90355/dev_v2/jquery.lazyload.min.js"></script><script type="text/javascript"…

    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 27, Column 233: document type does not allow element "script" here
    …ww.miniinthebox.com/resource_90355/miniinthebox/jscript_global_en.js"></script>

    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 32, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 46, Column 145: document type does not allow element "link" here
    …iniinthebox.com/statics/ria/dev_v2/pagelet/litb-cate-menu/litb-cate-menu.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).

  • Error Line 47, Column 110: document type does not allow element "link" here
    …xt/css" href="http://www.miniinthebox.com/statics/ria/theme/newblue/skin.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).

  • Error Line 48, Column 7: end tag for "script" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 25, Column 111: start tag was here
    …/jquery/1.3.1/jquery.min.js"></script><script>!window.jQuery && document.write…
  • Error Line 87, Column 44: end tag for "ul" which is not finished
              			<ul class="dropdown-menu"></ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 96, Column 14: end tag for "ul" which is not finished
    					<ul></ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 113, Column 96: cannot generate system identifier for general entity "src"
    …nthebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign …

    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 113, Column 96: general entity "src" not defined and no default entity
    …nthebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign …

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

  • Warning Line 113, Column 99: reference not terminated by REFC delimiter
    …ebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign In<…

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

  • Warning Line 113, Column 99: reference to external entity in attribute value
    …ebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign In<…

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

  • Error Line 113, Column 99: reference to entity "src" for which no system identifier could be generated
    …ebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign In<…

    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 113, Column 95: entity was defined here
    …inthebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign…
  • Warning Line 116, Column 78: reference not terminated by REFC delimiter
    …iinthebox.com/index.php?main_page=login&src=mainLoginLink">My Account</a>&nbsp;

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

  • Warning Line 116, Column 78: reference to external entity in attribute value
    …iinthebox.com/index.php?main_page=login&src=mainLoginLink">My Account</a>&nbsp;

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

  • Error Line 116, Column 78: reference to entity "src" for which no system identifier could be generated
    …iinthebox.com/index.php?main_page=login&src=mainLoginLink">My Account</a>&nbsp;

    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 113, Column 95: entity was defined here
    …inthebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign…
  • Error Line 124, Column 16: there is no attribute "ref"
    				<dt><a ref="nofollow" href="http://www.miniinthebox.com/knowledge-base/">He…

    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 142, Column 7: required attribute "type" not specified
    <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 142, Column 7: document type does not allow element "style" here
    <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 154, 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 168, Column 58: document type does not allow element "em" here
    …ass="'+obj.find('em').attr('class')+'"></em>'+_s+'</a><span class="caret"></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 168, Column 73: end tag for element "a" which is not open
    …"'+obj.find('em').attr('class')+'"></em>'+_s+'</a><span class="caret"></span>';

    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 168, Column 93: document type does not allow element "span" here
    …"'+obj.find('em').attr('class')+'"></em>'+_s+'</a><span class="caret"></span>';

    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 176, Column 16: document type does not allow element "li" here
    			html += '<li><a href=""><em class="flag '+i+'"></em>'+options.tecoData[i]+'<…

    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 178, Column 31: document type does not allow element "li" here
    		html += '<li class="divider"></li>';

    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 180, Column 16: document type does not allow element "li" here
    			html += '<li><a href=""><em class="flag '+i+'"></em>'+options.data[i]+'</a><…

    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 190, Column 58: cannot generate system identifier for general entity "action"
    …URL + 'index.php?main_page=info_check&action=change_country&country_code='+_cu…

    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 190, Column 58: general entity "action" not defined and no default entity
    …URL + 'index.php?main_page=info_check&action=change_country&country_code='+_cu…

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

  • Warning Line 190, Column 64: reference not terminated by REFC delimiter
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,

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

  • Error Line 190, Column 64: reference to entity "action" for which no system identifier could be generated
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,

    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 190, Column 57: entity was defined here
    …eURL + 'index.php?main_page=info_check&action=change_country&country_code='+_c…
  • Warning Line 190, Column 80: cannot generate system identifier for general entity "country_code"
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,

    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 190, Column 80: general entity "country_code" not defined and no default entity
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,

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

  • Warning Line 190, Column 92: reference not terminated by REFC delimiter
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,

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

  • Error Line 190, Column 92: reference to entity "country_code" for which no system identifier could be generated
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,

    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 190, Column 79: entity was defined here
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,
  • Warning Line 194, Column 18: character "&" is the first character of a delimiter but occurred as data
    						if(data!=''&&data==1){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 194, Column 20: cannot generate system identifier for general entity "data"
    						if(data!=''&&data==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 194, Column 20: general entity "data" not defined and no default entity
    						if(data!=''&&data==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.

  • Warning Line 194, Column 24: reference not terminated by REFC delimiter
    						if(data!=''&&data==1){

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

  • Error Line 194, Column 24: reference to entity "data" for which no system identifier could be generated
    						if(data!=''&&data==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 194, Column 19: entity was defined here
    						if(data!=''&&data==1){
  • Warning Line 241, Column 10: character "<" is the first character of a delimiter but occurred as data
    			//if(n<20) $(this).remove();

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 248, Column 14: cannot generate system identifier for general entity "t"
    			if(n==20&&t==0){

    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 248, Column 14: general entity "t" not defined and no default entity
    			if(n==20&&t==0){

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

  • Warning Line 248, Column 15: reference not terminated by REFC delimiter
    			if(n==20&&t==0){

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

  • Error Line 248, Column 15: reference to entity "t" for which no system identifier could be generated
    			if(n==20&&t==0){

    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 248, Column 13: entity was defined here
    			if(n==20&&t==0){
  • Error Line 253, Column 58: document type does not allow element "li" here
    …u ul',$this).html('<li class="noResul">'+litb.langs["noResultMatch"]+'"'+$inpu…

    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 257, Column 31: character "&" is the first character of a delimiter but occurred as data
    			if((lastKeyPressCode >= 33 && lastKeyPressCode <= 45) 

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 259, Column 33: character "&" is the first character of a delimiter but occurred as data
    				|| (lastKeyPressCode >= 112 && lastKeyPressCode <= 135)) 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 259, Column 34: character "&" is the first character of a delimiter but occurred as data
    				|| (lastKeyPressCode >= 112 && lastKeyPressCode <= 135)) 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 259, Column 53: character "<" is the first character of a delimiter but occurred as data
    				|| (lastKeyPressCode >= 112 && lastKeyPressCode <= 135)) 

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 297, Column 29: character "&" is the first character of a delimiter but occurred as data
    							if($(this).text()!=''&&$(this).text()==$input.val()) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 297, Column 30: character "&" is the first character of a delimiter but occurred as data
    							if($(this).text()!=''&&$(this).text()==$input.val()) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 349, 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>.

  • Warning Line 354, Column 92: cannot generate system identifier for general entity "currency"
    …thebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.miniin…

    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 354, Column 92: general entity "currency" not defined and no default entity
    …thebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.miniin…

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

  • Warning Line 354, Column 100: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 100: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 178: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=DKK","NOK":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 178: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=DKK","NOK":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 256: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=NOK","BRL":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 256: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=NOK","BRL":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 334: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=BRL","RUB":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 334: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=BRL","RUB":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 412: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=RUB","EUR":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 412: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=RUB","EUR":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 490: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=EUR","GBP":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 490: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=EUR","GBP":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 568: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=GBP","CAD":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 568: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=GBP","CAD":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 646: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=CAD","AUD":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 646: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=CAD","AUD":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 724: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=AUD","CHF":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 724: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=AUD","CHF":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 802: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=CHF","HKD":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 802: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=CHF","HKD":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 880: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=HKD","KRW":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 880: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=HKD","KRW":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 958: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=KRW","SEK":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 958: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=KRW","SEK":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 1036: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=SEK","CLP":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 1036: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=SEK","CLP":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 1114: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=CLP","JPY":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 1114: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=CLP","JPY":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 1192: reference not terminated by REFC delimiter
    …om\/index.php?main_page=index&currency=JPY","ILS":"http:\/\/www.miniinthebox.c…

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

  • Error Line 354, Column 1192: reference to entity "currency" for which no system identifier could be generated
    …om\/index.php?main_page=index&currency=JPY","ILS":"http:\/\/www.miniinthebox.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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 354, Column 1270: reference not terminated by REFC delimiter
    …"ILS":"http:\/\/www.miniinthebox.com\/index.php?main_page=index&currency=ILS"};

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

  • Error Line 354, Column 1270: reference to entity "currency" for which no system identifier could be generated
    …"ILS":"http:\/\/www.miniinthebox.com\/index.php?main_page=index&currency=ILS"};

    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 354, Column 91: entity was defined here
    …nthebox.com\/index.php?main_page=index&currency=USD","DKK":"http:\/\/www.minii…
  • Warning Line 357, Column 58: reference not terminated by REFC delimiter
    //main_page=info_check?action=change_country&country_code=us

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

  • Error Line 357, Column 58: reference to entity "country_code" for which no system identifier could be generated
    //main_page=info_check?action=change_country&country_code=us

    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 190, Column 79: entity was defined here
    …RL + 'index.php?main_page=info_check&action=change_country&country_code='+_cut,
  • Error Line 380, 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>.

  • Warning Line 384, Column 53: cannot generate system identifier for general entity "get_frame"
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

    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 384, Column 53: general entity "get_frame" not defined and no default entity
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

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

  • Warning Line 384, Column 62: reference not terminated by REFC delimiter
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

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

  • Error Line 384, Column 62: reference to entity "get_frame" for which no system identifier could be generated
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

    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 384, Column 52: entity was defined here
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,
  • Warning Line 384, Column 65: cannot generate system identifier for general entity "language"
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

    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 384, Column 65: general entity "language" not defined and no default entity
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

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

  • Warning Line 384, Column 73: reference not terminated by REFC delimiter
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

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

  • Error Line 384, Column 73: reference to entity "language" for which no system identifier could be generated
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

    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 384, Column 64: entity was defined here
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,
  • Warning Line 384, Column 80: reference not terminated by REFC delimiter
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

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

  • Error Line 384, Column 80: reference to entity "src" for which no system identifier could be generated
    …litb.baseURL + 'index.php?main_page=login&get_frame=1&language=en&src='+source,

    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 113, Column 95: entity was defined here
    …inthebox.com/index.php?main_page=login&src=mainLoginLink" title="Sign In">Sign…
  • Error Line 396, Column 126: document type does not allow element "link" here
    …href="http://www.miniinthebox.com/resource_90355/miniinthebox/chosen.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).

  • Error Line 431, Column 73: there is no attribute "ctr"
    …fo ctrTrackA" id="litb-cate-menu" ctr="{area:'category_menu'}" page="index" st…

    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 431, Column 103: there is no attribute "page"
    …tb-cate-menu" ctr="{area:'category_menu'}" page="index" style="display:block;">

    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 434, Column 17: there is no attribute "ctr"
    				<h2><a  ctr="{seat:''}" href="http://www.miniinthebox.com/new-year-deals-20…

    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 548, Column 31: document type does not allow element "script" here; missing one of "dt", "dd" start-tag
    <script type="text/javascript">litb['category_menu']={"menu":[{"text":"New Year…

    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>").

  • Warning Line 548, Column 739: character "&" is the first character of a delimiter but occurred as data
    …al","nofollow":false},{"text":"iPad 2 & the New iPad","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 3000: character "&" is the first character of a delimiter but occurred as data
    …llow":false,"children":[{"text":"Mice & Keyboards","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 3535: character "&" is the first character of a delimiter but occurred as data
    …"position":"right"},{"text":"Speakers & Earphones","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 5357: character "&" is the first character of a delimiter but occurred as data
    …e,"position":"left"},{"text":"Charger & Adapters","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 5853: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Cables & Chargers","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 6512: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Stylus & Touch Gloves","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 7040: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Cables & Adapters","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 7703: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Stylus & Touch Gloves","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 8219: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Cables & Adapters","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 8882: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Stylus & Touch Gloves","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 9404: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Cables & Adapters","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 10060: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Stylus & Touch Gloves","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 13550: cannot generate system identifier for general entity "inc_subcat"
    ….php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&key…

    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 548, Column 13550: general entity "inc_subcat" not defined and no default entity
    ….php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&key…

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

  • Warning Line 548, Column 13560: reference not terminated by REFC delimiter
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unise…

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

  • Error Line 548, Column 13560: reference to entity "inc_subcat" for which no system identifier could be generated
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unise…

    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 548, Column 13549: entity was defined here
    …x.php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&ke…
  • Warning Line 548, Column 13563: cannot generate system identifier for general entity "search_in_description"
    …e=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&l…

    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 548, Column 13563: general entity "search_in_description" not defined and no default entity
    …e=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&l…

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

  • Warning Line 548, Column 13584: reference not terminated by REFC delimiter
    …ult&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","po…

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

  • Error Line 548, Column 13584: reference to entity "search_in_description" for which no system identifier could be generated
    …ult&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","po…

    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 548, Column 13562: entity was defined here
    …ge=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&…
  • Warning Line 548, Column 13587: cannot generate system identifier for general entity "keyword"
    …&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","point…

    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 548, Column 13587: general entity "keyword" not defined and no default entity
    …&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","point…

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

  • Warning Line 548, Column 13594: reference not terminated by REFC delimiter
    …bcat=1&search_in_description=0&keyword=unisex&light_select=3175","point":false…

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

  • Error Line 548, Column 13594: reference to entity "keyword" for which no system identifier could be generated
    …bcat=1&search_in_description=0&keyword=unisex&light_select=3175","point":false…

    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 548, Column 13586: entity was defined here
    …t&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","poin…
  • Warning Line 548, Column 13602: cannot generate system identifier for general entity "light_select"
    …earch_in_description=0&keyword=unisex&light_select=3175","point":false,"type":…

    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 548, Column 13602: general entity "light_select" not defined and no default entity
    …earch_in_description=0&keyword=unisex&light_select=3175","point":false,"type":…

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

  • Warning Line 548, Column 13614: reference not terminated by REFC delimiter
    …cription=0&keyword=unisex&light_select=3175","point":false,"type":"nomal","nof…

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

  • Error Line 548, Column 13614: reference to entity "light_select" for which no system identifier could be generated
    …cription=0&keyword=unisex&light_select=3175","point":false,"type":"nomal","nof…

    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 548, Column 13601: entity was defined here
    …search_in_description=0&keyword=unisex&light_select=3175","point":false,"type"…
  • Warning Line 548, Column 19097: reference not terminated by REFC delimiter
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=Repai…

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

  • Error Line 548, Column 19097: reference to entity "inc_subcat" for which no system identifier could be generated
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=Repai…

    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 548, Column 13549: entity was defined here
    …x.php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&ke…
  • Warning Line 548, Column 19121: reference not terminated by REFC delimiter
    …ult&inc_subcat=1&search_in_description=0&keyword=Repair+Tool&light_select=3175…

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

  • Error Line 548, Column 19121: reference to entity "search_in_description" for which no system identifier could be generated
    …ult&inc_subcat=1&search_in_description=0&keyword=Repair+Tool&light_select=3175…

    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 548, Column 13562: entity was defined here
    …ge=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&…
  • Warning Line 548, Column 19131: reference not terminated by REFC delimiter
    …bcat=1&search_in_description=0&keyword=Repair+Tool&light_select=3175","point":…

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

  • Error Line 548, Column 19131: reference to entity "keyword" for which no system identifier could be generated
    …bcat=1&search_in_description=0&keyword=Repair+Tool&light_select=3175","point":…

    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 548, Column 13586: entity was defined here
    …t&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","poin…
  • Warning Line 548, Column 19156: reference not terminated by REFC delimiter
    …ion=0&keyword=Repair+Tool&light_select=3175","point":false,"type":"nomal","nof…

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

  • Error Line 548, Column 19156: reference to entity "light_select" for which no system identifier could be generated
    …ion=0&keyword=Repair+Tool&light_select=3175","point":false,"type":"nomal","nof…

    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 548, Column 13601: entity was defined here
    …search_in_description=0&keyword=unisex&light_select=3175","point":false,"type"…
  • Warning Line 548, Column 19360: reference not terminated by REFC delimiter
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=watch…

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

  • Error Line 548, Column 19360: reference to entity "inc_subcat" for which no system identifier could be generated
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=watch…

    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 548, Column 13549: entity was defined here
    …x.php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&ke…
  • Warning Line 548, Column 19384: reference not terminated by REFC delimiter
    …ult&inc_subcat=1&search_in_description=0&keyword=watch+box&light_select=3175",…

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

  • Error Line 548, Column 19384: reference to entity "search_in_description" for which no system identifier could be generated
    …ult&inc_subcat=1&search_in_description=0&keyword=watch+box&light_select=3175",…

    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 548, Column 13562: entity was defined here
    …ge=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&…
  • Warning Line 548, Column 19394: reference not terminated by REFC delimiter
    …bcat=1&search_in_description=0&keyword=watch+box&light_select=3175","point":fa…

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

  • Error Line 548, Column 19394: reference to entity "keyword" for which no system identifier could be generated
    …bcat=1&search_in_description=0&keyword=watch+box&light_select=3175","point":fa…

    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 548, Column 13586: entity was defined here
    …t&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","poin…
  • Warning Line 548, Column 19417: reference not terminated by REFC delimiter
    …ption=0&keyword=watch+box&light_select=3175","point":false,"type":"nomal","nof…

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

  • Error Line 548, Column 19417: reference to entity "light_select" for which no system identifier could be generated
    …ption=0&keyword=watch+box&light_select=3175","point":false,"type":"nomal","nof…

    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 548, Column 13601: entity was defined here
    …search_in_description=0&keyword=unisex&light_select=3175","point":false,"type"…
  • Warning Line 548, Column 19622: reference not terminated by REFC delimiter
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=Case+…

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

  • Error Line 548, Column 19622: reference to entity "inc_subcat" for which no system identifier could be generated
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=Case+…

    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 548, Column 13549: entity was defined here
    …x.php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&ke…
  • Warning Line 548, Column 19646: reference not terminated by REFC delimiter
    …ult&inc_subcat=1&search_in_description=0&keyword=Case+Opener&light_select=3175…

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

  • Error Line 548, Column 19646: reference to entity "search_in_description" for which no system identifier could be generated
    …ult&inc_subcat=1&search_in_description=0&keyword=Case+Opener&light_select=3175…

    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 548, Column 13562: entity was defined here
    …ge=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&…
  • Warning Line 548, Column 19656: reference not terminated by REFC delimiter
    …bcat=1&search_in_description=0&keyword=Case+Opener&light_select=3175","point":…

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

  • Error Line 548, Column 19656: reference to entity "keyword" for which no system identifier could be generated
    …bcat=1&search_in_description=0&keyword=Case+Opener&light_select=3175","point":…

    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 548, Column 13586: entity was defined here
    …t&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","poin…
  • Warning Line 548, Column 19681: reference not terminated by REFC delimiter
    …ion=0&keyword=Case+Opener&light_select=3175","point":false,"type":"nomal","nof…

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

  • Error Line 548, Column 19681: reference to entity "light_select" for which no system identifier could be generated
    …ion=0&keyword=Case+Opener&light_select=3175","point":false,"type":"nomal","nof…

    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 548, Column 13601: entity was defined here
    …search_in_description=0&keyword=unisex&light_select=3175","point":false,"type"…
  • Warning Line 548, Column 29717: character "&" is the first character of a delimiter but occurred as data
    …"position":"left"},{"text":"Wii Cable & Adapter","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 30066: character "&" is the first character of a delimiter but occurred as data
    …,"position":"left"},{"text":"Wii Bags & Cases","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 31161: character "&" is the first character of a delimiter but occurred as data
    …tion":"left"},{"text":"Xbox 360 Cable & Adapter","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 32073: character "&" is the first character of a delimiter but occurred as data
    …osition":"left"},{"text":"PS3 Charger & Cable","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 32951: character "&" is the first character of a delimiter but occurred as data
    …"children":[{"text":"Nintendo DS Case & Bag","url":"http:\/\/www.miniinthebox.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 33137: character "&" is the first character of a delimiter but occurred as data
    …:"left"},{"text":"Nintendo DS Charger & Battery","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 34268: character "&" is the first character of a delimiter but occurred as data
    …":false,"children":[{"text":"PSP Case & Bag","url":"http:\/\/www.miniinthebox.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 34438: character "&" is the first character of a delimiter but occurred as data
    …osition":"left"},{"text":"PSP Charger & Battery","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 35699: character "&" is the first character of a delimiter but occurred as data
    …"left"},{"text":"Nintendo 3DS Charger & Battery","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 39763: character "&" is the first character of a delimiter but occurred as data
    …osition":"left"},{"text":"Microscopes & Magnifiers","url":"http:\/\/www.miniin…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 41225: character "&" is the first character of a delimiter but occurred as data
    …lse,"position":"left"},{"text":"Flash & Accessories","url":"http:\/\/www.minii…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 41414: character "&" is the first character of a delimiter but occurred as data
    …n":"left"},{"text":"Screen Protectors & Cleaners","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 42271: character "&" is the first character of a delimiter but occurred as data
    …"position":"left"},{"text":"Airplanes & Accessories","url":"http:\/\/www.minii…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 42454: character "&" is the first character of a delimiter but occurred as data
    …e,"position":"left"},{"text":"Engines & Motors","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 43628: character "&" is the first character of a delimiter but occurred as data
    …":false,"children":[{"text":"Speakers & Earphones","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 43803: character "&" is the first character of a delimiter but occurred as data
    …alse,"position":"left"},{"text":"Mice & Keyboards","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 44141: character "&" is the first character of a delimiter but occurred as data
    …"position":"left"},{"text":"Bluetooth & IrDA","url":"http:\/\/www.miniinthebox…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 45031: character "&" is the first character of a delimiter but occurred as data
    …sition":"left"},{"text":"Memory Stick & M2 Memory Cards","url":"http:\/\/www.m…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 47241: character "&" is the first character of a delimiter but occurred as data
    …n":"left"}]},{"text":"Computer Cables & Adapters","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 47438: character "&" is the first character of a delimiter but occurred as data
    …false,"children":[{"text":"Converters & Adapters","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 62114: character "&" is the first character of a delimiter but occurred as data
    …ow":false},{"text":"Android HD Player & Mini PC","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 62316: character "&" is the first character of a delimiter but occurred as data
    …e}]}],"has_child":true},{"text":"Home & Office Gadget...","url":"http:\/\/www.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 62649: character "&" is the first character of a delimiter but occurred as data
    …target":false,"left":[{"text":"Health & Beauty","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 62832: character "&" is the first character of a delimiter but occurred as data
    …:false,"children":[{"text":"Nail Care & Art","url":"http:\/\/www.miniinthebox.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 63163: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Health & Personal Care","url":"http:\/\/www.min…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 63348: character "&" is the first character of a delimiter but occurred as data
    …,"position":"left"},{"text":"Relaxers & Massagers","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 63685: character "&" is the first character of a delimiter but occurred as data
    …e,"position":"left"},{"text":"Shavers & Razors","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 63867: character "&" is the first character of a delimiter but occurred as data
    …":"left"}]},{"text":"Kitchen Utensils & Gadgets","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 64229: character "&" is the first character of a delimiter but occurred as data
    …lse,"position":"left"},{"text":"Fruit & Vegetable Tools","url":"http:\/\/www.m…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 64933: character "&" is the first character of a delimiter but occurred as data
    …false,"position":"left"},{"text":"Ice & Ice Pop Molds","url":"http:\/\/www.min…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 65297: character "&" is the first character of a delimiter but occurred as data
    …lse,"children":[{"text":"Novelty Cups & Bottles","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 66463: character "&" is the first character of a delimiter but occurred as data
    …llow":false,"children":[{"text":"Pens & Writing Instruments","url":"http:\/\/w…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 66838: character "&" is the first character of a delimiter but occurred as data
    …"position":"left"},{"text":"Memo Pads & Notebooks","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 67180: character "&" is the first character of a delimiter but occurred as data
    …osition":"left"},{"text":"Pen Holders & Cases","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 67708: character "&" is the first character of a delimiter but occurred as data
    …low":false,"children":[{"text":"Boxes & Barrels","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 67876: character "&" is the first character of a delimiter but occurred as data
    …alse,"position":"left"},{"text":"Bags & Baskets","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 68044: character "&" is the first character of a delimiter but occurred as data
    …lse,"position":"left"},{"text":"Cable & Wire Organization","url":"http:\/\/www…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 68394: character "&" is the first character of a delimiter but occurred as data
    …ion":"left"},{"text":"Clothes Hangers & Bags","url":"http:\/\/www.miniinthebox…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 69940: character "&" is the first character of a delimiter but occurred as data
    …:"left"}]}],"middle":[{"text":"Health & Beauty","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 70132: character "&" is the first character of a delimiter but occurred as data
    …"children":[{"text":"Kitchen Utensils & Gadgets","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 70644: character "&" is the first character of a delimiter but occurred as data
    …mal","nofollow":false},{"text":"Alarm &  Security","url":"http:\/\/www.miniint…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 71191: character "&" is the first character of a delimiter but occurred as data
    …ofollow":false},{"text":"Alarm Clocks & Clocks","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 78261: character "&" is the first character of a delimiter but occurred as data
    …"position":"right"},{"text":"DIY Pars & Tools","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 90023: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Stylus & Touch Gloves","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 90899: character "&" is the first character of a delimiter but occurred as data
    …hildren":[{"text":"Collars, Harnesses & Leashes","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 91524: character "&" is the first character of a delimiter but occurred as data
    …,"position":"left"},{"text":"Carriers & Travel Backpacks","url":"http:\/\/www.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 92895: character "&" is the first character of a delimiter but occurred as data
    …":"left"},{"text":"Collars, Harnesses & Leashes","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 94704: character "&" is the first character of a delimiter but occurred as data
    …alse,"position":"right"},{"text":"Paw & Boots","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 94997: reference not terminated by REFC delimiter
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=led+c…

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

  • Error Line 548, Column 94997: reference to entity "inc_subcat" for which no system identifier could be generated
    …page=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=led+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 548, Column 13549: entity was defined here
    …x.php?main_page=advanced_search_result&inc_subcat=1&search_in_description=0&ke…
  • Warning Line 548, Column 95021: reference not terminated by REFC delimiter
    …ult&inc_subcat=1&search_in_description=0&keyword=led+collar&light_select=4853"…

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

  • Error Line 548, Column 95021: reference to entity "search_in_description" for which no system identifier could be generated
    …ult&inc_subcat=1&search_in_description=0&keyword=led+collar&light_select=4853"…

    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 548, Column 13562: entity was defined here
    …ge=advanced_search_result&inc_subcat=1&search_in_description=0&keyword=unisex&…
  • Warning Line 548, Column 95031: reference not terminated by REFC delimiter
    …bcat=1&search_in_description=0&keyword=led+collar&light_select=4853","point":t…

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

  • Error Line 548, Column 95031: reference to entity "keyword" for which no system identifier could be generated
    …bcat=1&search_in_description=0&keyword=led+collar&light_select=4853","point":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 548, Column 13586: entity was defined here
    …t&inc_subcat=1&search_in_description=0&keyword=unisex&light_select=3175","poin…
  • Warning Line 548, Column 95055: reference not terminated by REFC delimiter
    …tion=0&keyword=led+collar&light_select=4853","point":true,"type":"nomal","nofo…

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

  • Error Line 548, Column 95055: reference to entity "light_select" for which no system identifier could be generated
    …tion=0&keyword=led+collar&light_select=4853","point":true,"type":"nomal","nofo…

    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 548, Column 13601: entity was defined here
    …search_in_description=0&keyword=unisex&light_select=3175","point":false,"type"…
  • Warning Line 548, Column 101733: character "&" is the first character of a delimiter but occurred as data
    …osition":"right"},{"text":"Sunglasses & Eyeglasses","url":"http:\/\/www.miniin…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 102265: character "&" is the first character of a delimiter but occurred as data
    …]}],"has_child":true},{"text":"Sports & Outdoors","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 102770: character "&" is the first character of a delimiter but occurred as data
    …ow":false,"children":[{"text":"Lights & Reflectors","url":"http:\/\/www.miniin…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 103115: character "&" is the first character of a delimiter but occurred as data
    …lse,"position":"left"},{"text":"Bells & Mirrors & Locks","url":"http:\/\/www.m…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 103125: character "&" is the first character of a delimiter but occurred as data
    …ion":"left"},{"text":"Bells & Mirrors & Locks","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 103640: character "&" is the first character of a delimiter but occurred as data
    …e,"position":"left"},{"text":"Bottles & Bottle Cages","url":"http:\/\/www.mini…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 103825: character "&" is the first character of a delimiter but occurred as data
    …"position":"left"}]},{"text":"Camping & Hiking","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 104491: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Knives & Tools","url":"http:\/\/www.miniinthebo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 104823: character "&" is the first character of a delimiter but occurred as data
    …se,"position":"left"},{"text":"Safety & Survival","url":"http:\/\/www.miniinth…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 105196: character "&" is the first character of a delimiter but occurred as data
    …w":false,"children":[{"text":"Camping & Hiking","url":"http:\/\/www.miniintheb…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 105859: character "&" is the first character of a delimiter but occurred as data
    …","nofollow":false},{"text":"Exercise & Fitness","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 108075: character "&" is the first character of a delimiter but occurred as data
    …al","nofollow":false},{"text":"Health & Hygiene","url":"http:\/\/www.miniinthe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 548, Column 108247: character "&" is the first character of a delimiter but occurred as data
    …mal","nofollow":false},{"text":"Locks & Tags","url":"http:\/\/www.miniinthebox…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 555, Column 513: there is no attribute "qs_url"
    …" name="keyword" id="keywords" qs_url="http://www.miniinthebox.com/query_sugge…

    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 555, Column 579: there is no attribute "dvalue"
    …/query_suggestion/qs_server.b" dvalue="" value=""  maxlength="120" autocomplet…

    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 555, Column 621: there is no attribute "autocomplete"
    …/qs_server.b" dvalue="" value=""  maxlength="120" autocomplete="off" lang="1"/>

    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 595, 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>.

  • Warning Line 600, Column 110: character "<" is the first character of a delimiter but occurred as data
    …navHeight,"height":newHeight-secHeight,"padding-top":secHeight<0?0:secHeight});

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 610, Column 57: character "&" is the first character of a delimiter but occurred as data
    …rowser = $.browser ,isIE9 = browser.msie === true && browser.version === '9.0';

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 610, Column 58: character "&" is the first character of a delimiter but occurred as data
    …rowser = $.browser ,isIE9 = browser.msie === true && browser.version === '9.0';

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 633, Column 42: character "&" is the first character of a delimiter but occurred as data
    …	if($('.cate_menu_hero',this).size()>0&&$('.litb-cate-menu-specialoffer',this)…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 633, Column 43: character "&" is the first character of a delimiter but occurred as data
    …if($('.cate_menu_hero',this).size()>0&&$('.litb-cate-menu-specialoffer',this).…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 644, Column 51: document type does not allow element "br" here
    					if(n==size) $(this).before('<br class="clear">'); 

    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 644, Column 52: end tag for "br" omitted, but OMITTAG NO was specified
    					if(n==size) $(this).before('<br class="clear">'); 

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

  • Info Line 644, Column 34: start tag was here
    					if(n==size) $(this).before('<br class="clear">'); 
  • Warning Line 686, Column 10: character "&" is the first character of a delimiter but occurred as data
    		if(data&&data!=''){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 686, Column 16: reference not terminated by REFC delimiter
    		if(data&&data!=''){

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

  • Error Line 686, Column 16: reference to entity "data" for which no system identifier could be generated
    		if(data&&data!=''){

    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 194, Column 19: entity was defined here
    						if(data!=''&&data==1){
  • Error Line 687, Column 32: document type does not allow element "div" here
    			_str +='<div class="'+elm+'">';

    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 688, Column 29: character ";" not allowed in attribute specification list
    			for(var t=0;t<data.length;t++){
  • Error Line 688, Column 29: element "data.length" undefined
    			for(var t=0;t<data.length;t++){

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 691, Column 17: character data is not allowed here
    				_str +='<dl>';

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 695, Column 44: character data is not allowed here
    							_str +='<dt>'+data[t]['text']+'</dt>';

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 697, Column 23: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							_str +='<dt><h3><a '+ _nofollow + _target +' ctr="{seat:\''+data[0]["pos…

    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 697, Column 27: an attribute specification must start with a name or name token
    							_str +='<dt><h3><a '+ _nofollow + _target +' ctr="{seat:\''+data[0]["pos…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 697, Column 155: character data is not allowed here
    …osition"]+'\'}" href="'+_href+'"'+_lClass+'>'+data[t]['text']+'</a></h3></dt>';

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 700, Column 27: character "&" is the first character of a delimiter but occurred as data
    				if(data[t]['children']&&data[t]['children']!=''){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 700, Column 33: reference not terminated by REFC delimiter
    				if(data[t]['children']&&data[t]['children']!=''){

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

  • Error Line 700, Column 33: reference to entity "data" for which no system identifier could be generated
    				if(data[t]['children']&&data[t]['children']!=''){

    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 194, Column 19: entity was defined here
    						if(data!=''&&data==1){
  • Error Line 702, Column 32: character ";" not allowed in attribute specification list
    					for(var p=0;p<_data.length;p++){
  • Error Line 702, Column 32: element "_data.length" undefined
    					for(var p=0;p<_data.length;p++){

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 707, Column 23: an attribute specification must start with a name or name token
    							_str +='<dd><a '+ _nofollow + _target +' ctr="{seat:\''+data[0]['positio…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 709, Column 27: an attribute specification must start with a name or name token
    							_str +='<dd><h4><a '+ _nofollow + _target +' ctr="{seat:\''+data[0]['pos…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 713, Column 17: end tag for "_data.length" omitted, but OMITTAG NO was specified
    				_str +='</dl>';

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

  • Info Line 702, Column 19: start tag was here
    					for(var p=0;p<_data.length;p++){
  • Error Line 715, Column 17: end tag for "data.length" omitted, but OMITTAG NO was specified
    			_str +='</div>';

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

  • Info Line 688, Column 17: start tag was here
    			for(var t=0;t<data.length;t++){
  • Error Line 722, Column 29: character ";" not allowed in attribute specification list
    		for(var i=0;i<_data.length;i++){
  • Error Line 722, Column 29: element "_data.length" undefined
    		for(var i=0;i<_data.length;i++){

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 788, Column 99: character data is not allowed here
    …clearfix ' + (item.attachment?' attachment':'') + (isFirst?'  first':'') + '">\

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 790, Column 230: end tag for "img" omitted, but OMITTAG NO was specified
    … (item.img ? item.img : (litb.resouceURL+'base-images/300x300.png')) + '"></a>\

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

  • Info Line 790, Column 76: start tag was here
    …le:'') + '"  href="' + item.href + '"><img alt="' + (item.title?item.title:'')…
  • Error Line 791, Column 8: character data is not allowed here
    		</dt>\

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 794, Column 23: character data is not allowed here
                    '</dd>\

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 814, Column 69: reference not terminated by REFC delimiter
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',

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

  • Error Line 814, Column 69: reference to entity "action" for which no system identifier could be generated
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',

    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 190, Column 57: entity was defined here
    …eURL + 'index.php?main_page=info_check&action=change_country&country_code='+_c…
  • Warning Line 814, Column 88: cannot generate system identifier for general entity "callback"
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',

    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 814, Column 88: general entity "callback" not defined and no default entity
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',

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

  • Warning Line 814, Column 96: reference not terminated by REFC delimiter
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',

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

  • Error Line 814, Column 96: reference to entity "callback" for which no system identifier could be generated
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',

    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 814, Column 87: entity was defined here
    …thebox.com/index.php?main_page=info_check&action=ajax_shippingcart&callback=?',
  • Warning Line 827, Column 22: character "<" is the first character of a delimiter but occurred as data
    			for (var i = 0; i < items.length; i++) {

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 882, Column 9: end tag for "_data.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 722, Column 16: start tag was here
    		for(var i=0;i<_data.length;i++){
  • Error Line 901, Column 7: required attribute "type" not specified
    <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 901, Column 7: document type does not allow element "style" here
    <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).

  • Warning Line 913, Column 3251: character "&" is the first character of a delimiter but occurred as data
    …r &amp; Battery","pos":2});' >Charger & Battery</a></dd><dd><a href='http://ww…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 917, Column 175: character "&" is the first character of a delimiter but occurred as data
    …; Flashlight","pos":0});' >LED Lights & Flashlight</a></h3><dl><dt><a href='ht…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 919, Column 163: character "&" is the first character of a delimiter but occurred as data
    …Toys &amp; Hobbies","pos":0});' >Toys & Hobbies</a></h3><dl><dt><a href='http:…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 919, Column 1192: character "&" is the first character of a delimiter but occurred as data
    …pod &amp; Holder","pos":1});' >Tripod & Holder</a></dd><dd><a href='http://www…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 919, Column 2045: character "&" is the first character of a delimiter but occurred as data
    …Bells &amp; Locks","pos":2});' >Bells & Locks</a></dd><dd><a href='http://www.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 921, Column 179: character "&" is the first character of a delimiter but occurred as data
    …p; Electronics","pos":0});' >Computer & Electronics</a></h3><dl><dt><a href='h…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 929, Column 24: there is no attribute "class"
            <section class="widget-dfp widget"><section class="widget-dfp widget" s…

    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 929, Column 43: element "section" undefined
    …    <section class="widget-dfp widget"><section class="widget-dfp widget" styl…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 929, Column 85: there is no attribute "style"
    …ction class="widget-dfp widget" style="position:relative;width:238px;height:16…

    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 929, Column 224: element "section" undefined
    …04/43991/43991_en.jpg) 0 0 no-repeat;"> <form method="post" action="http://www…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 929, Column 319: reference not terminated by REFC delimiter
    …/index.php?main_page=info_check&action=newsletter&newsletterPage=activation" i…

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

  • Warning Line 929, Column 319: reference to external entity in attribute value
    …/index.php?main_page=info_check&action=newsletter&newsletterPage=activation" i…

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

  • Error Line 929, Column 319: reference to entity "action" for which no system identifier could be generated
    …/index.php?main_page=info_check&action=newsletter&newsletterPage=activation" 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 190, Column 57: entity was defined here
    …eURL + 'index.php?main_page=info_check&action=change_country&country_code='+_c…
  • Warning Line 929, Column 331: cannot generate system identifier for general entity "newsletterPage"
    …ain_page=info_check&action=newsletter&newsletterPage=activation" id="newslette…

    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 929, Column 331: general entity "newsletterPage" not defined and no default entity
    …ain_page=info_check&action=newsletter&newsletterPage=activation" id="newslette…

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

  • Warning Line 929, Column 345: reference not terminated by REFC delimiter
    …check&action=newsletter&newsletterPage=activation" id="newsletter_sub_form_s">…

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

  • Warning Line 929, Column 345: reference to external entity in attribute value
    …check&action=newsletter&newsletterPage=activation" id="newsletter_sub_form_s">…

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

  • Error Line 929, Column 345: reference to entity "newsletterPage" for which no system identifier could be generated
    …check&action=newsletter&newsletterPage=activation" id="newsletter_sub_form_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 929, Column 330: entity was defined here
    …main_page=info_check&action=newsletter&newsletterPage=activation" id="newslett…
  • Error Line 929, Column 432: end tag for "input" omitted, but OMITTAG NO was specified
    …ype="hidden" value="index" name="url"> <input type="hidden" id="source1" name=…

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

  • Info Line 929, Column 386: start tag was here
    …tivation" id="newsletter_sub_form_s"> <input type="hidden" value="index" name=…
  • Error Line 929, Column 731: end tag for "input" omitted, but OMITTAG NO was specified
    …der:none;color:#045294;" name="email"><button id="newsletter_submit_s" style="…

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

  • Info Line 929, Column 556: start tag was here
    …"source2" name="source2" value="D" /> <input type="text" value="Your Email Add…
  • Error Line 952, Column 417: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">50</em>			</a>

    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 418: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">50</em>			</a>

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

  • Info Line 952, Column 267: start tag was here
    …-Pack)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 966, Column 463: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">60</em>			</a>

    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 966, Column 464: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">60</em>			</a>

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

  • Info Line 966, Column 313: start tag was here
    …-pack)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 979, Column 413: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 979, Column 414: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 979, Column 263: start tag was here
    … Cloth" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 992, Column 410: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">40</em>			</a>

    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 992, Column 411: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">40</em>			</a>

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

  • Info Line 992, Column 260: start tag was here
    …acelet" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1005, Column 498: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 499: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1005, Column 348: start tag was here
    … (6ft)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1018, Column 491: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">30</em>			</a>

    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 1018, Column 492: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">30</em>			</a>

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

  • Info Line 1018, Column 341: start tag was here
    …lable)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1032, Column 454: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">55</em>			</a>

    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 455: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">55</em>			</a>

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

  • Info Line 1032, Column 304: start tag was here
    …Small)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1046, Column 479: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">40</em>			</a>

    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 1046, Column 480: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">40</em>			</a>

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

  • Info Line 1046, Column 329: start tag was here
    …r Band" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1059, Column 468: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">40</em>			</a>

    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 469: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">40</em>			</a>

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

  • Info Line 1059, Column 318: start tag was here
    …A, 3W)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1072, Column 499: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1072, Column 500: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1072, Column 349: start tag was here
    …olors)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1085, Column 418: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1085, Column 419: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1085, Column 268: start tag was here
    …tainer" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1098, Column 482: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 483: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1098, Column 332: start tag was here
    …urple)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1129, Column 489: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1129, Column 490: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1129, Column 339: start tag was here
    …White)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1143, Column 425: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1143, Column 426: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1143, Column 275: start tag was here
    …and 4S" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1156, Column 464: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1156, Column 465: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1156, Column 314: start tag was here
    …diaPad" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1169, Column 555: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 556: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1169, Column 405: start tag was here
    …-30cm)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1182, Column 479: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1182, Column 480: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1182, Column 329: start tag was here
    …Muller" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1195, Column 441: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1195, Column 442: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1195, Column 291: start tag was here
    … (3 m)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1209, Column 458: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1209, Column 459: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1209, Column 308: start tag was here
    … S5570" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1223, Column 459: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1223, Column 460: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1223, Column 309: start tag was here
    …16340)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1236, Column 413: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1236, Column 414: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1236, Column 263: start tag was here
    …cklace" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1249, Column 417: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1249, Column 418: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1249, Column 267: start tag was here
    … Black" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1262, Column 412: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1262, Column 413: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1262, Column 262: start tag was here
    …k(25g)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1275, Column 410: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1275, Column 411: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1275, Column 260: start tag was here
    …Travel" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1306, Column 407: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1306, Column 408: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1306, Column 257: start tag was here
    …ration" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1320, Column 519: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1320, Column 520: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1320, Column 369: start tag was here
    …olors)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1333, Column 458: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1333, Column 459: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1333, Column 308: start tag was here
    …and 4S" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1346, Column 381: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1346, Column 382: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1346, Column 231: start tag was here
    … (3 v)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1359, Column 482: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1359, Column 483: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1359, Column 332: start tag was here
    … (12V)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1372, Column 400: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1372, Column 401: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1372, Column 250: start tag was here
    …Black)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1386, Column 356: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">50</em>			</a>

    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 1386, Column 357: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">50</em>			</a>

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

  • Info Line 1386, Column 206: start tag was here
    …arring" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1400, Column 429: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1400, Column 430: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1400, Column 279: start tag was here
    …Black)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1413, Column 428: required attribute "alt" not specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

    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 1413, Column 429: end tag for "img" omitted, but OMITTAG NO was specified
    …om/resource_90355/miniinthebox/themes/newblue/images/imageHover128.png">			</a>

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

  • Info Line 1413, Column 278: start tag was here
    …s Cats" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1426, Column 394: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">25</em>			</a>

    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 1426, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">25</em>			</a>

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

  • Info Line 1426, Column 244: start tag was here
    …dapter" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1439, Column 503: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">50</em>			</a>

    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 1439, Column 504: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">50</em>			</a>

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

  • Info Line 1439, Column 353: start tag was here
    … Black" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1452, Column 496: required attribute "alt" not specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">30</em>			</a>

    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 1452, Column 497: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/newblue/images/imageHover128.png"><em class="iconDiscount">30</em>			</a>

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

  • Info Line 1452, Column 346: start tag was here
    …1 Set)" width="128" height="128" />			<img width="128" height="128" class="ima…
  • Error Line 1469, Column 97: there is no attribute "isshow"
    …t-history"  class="widget mini-w-recentViewed ctrInfo ctrTrackA" isshow="true">

    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 1477, Column 65: there is no attribute "entity"
    …Left" href="javascript:void(0)" entity="pre_arrow" ctr="{type:'PRE_NEXT'}"></a>

    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 1483, Column 73: character "<" is the first character of a delimiter but occurred as data
    …cent-history').offset().top - $(this).scrollTop()) < $(window).height() + 500){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1487, Column 33: character "&" is the first character of a delimiter but occurred as data
    	        if(litb['recentlyView']&&litb['recentlyView']!=""){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1487, Column 35: cannot generate system identifier for general entity "litb"
    	        if(litb['recentlyView']&&litb['recentlyView']!=""){

    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 1487, Column 35: general entity "litb" not defined and no default entity
    	        if(litb['recentlyView']&&litb['recentlyView']!=""){

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

  • Warning Line 1487, Column 39: reference not terminated by REFC delimiter
    	        if(litb['recentlyView']&&litb['recentlyView']!=""){

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

  • Error Line 1487, Column 39: reference to entity "litb" for which no system identifier could be generated
    	        if(litb['recentlyView']&&litb['recentlyView']!=""){

    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 1487, Column 34: entity was defined here
    	        if(litb['recentlyView']&&litb['recentlyView']!=""){
  • Warning Line 1490, Column 86: reference not terminated by REFC delimiter
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',

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

  • Error Line 1490, Column 86: reference to entity "action" for which no system identifier could be generated
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',

    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 190, Column 57: entity was defined here
    …eURL + 'index.php?main_page=info_check&action=change_country&country_code='+_c…
  • Warning Line 1490, Column 103: cannot generate system identifier for general entity "pid"
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',

    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 1490, Column 103: general entity "pid" not defined and no default entity
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',

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

  • Warning Line 1490, Column 106: reference not terminated by REFC delimiter
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',

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

  • Error Line 1490, Column 106: reference to entity "pid" for which no system identifier could be generated
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',

    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 1490, Column 102: entity was defined here
    ….miniinthebox.com/index.php?main_page=info_check&action=recently_viewed&pid=0',
  • Warning Line 1494, Column 33: character "&" is the first character of a delimiter but occurred as data
    	            		if (data != null && typeof(data) != 'undefined' && data.info.len…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1494, Column 34: character "&" is the first character of a delimiter but occurred as data
    	            		if (data != null && typeof(data) != 'undefined' && data.info.len…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1494, Column 64: character "&" is the first character of a delimiter but occurred as data
    …   		if (data != null && typeof(data) != 'undefined' && data.info.length > 0) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1494, Column 65: character "&" is the first character of a delimiter but occurred as data
    …   		if (data != null && typeof(data) != 'undefined' && data.info.length > 0) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1516, Column 6: end tag for element "div" which is not open
    </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 1527, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <dl class=freeShipping>
  • Error Line 1538, Column 262: end tag for element "p" which is not open
    …rted is a valid email address. Start buying online and grab a gadget today!</p>

    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 1545, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <dl class=secure>
  • Error Line 1560, Column 8: required attribute "type" not specified
    	<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 1560, Column 8: document type does not allow element "style" here
    	<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 1573, Column 630: there is no attribute "allowtransparency"
    …21" frameborder="0" allowtransparency="allowtransparency" scrolling="no"></ifr…

    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 1574, Column 167: there is no attribute "data-lang"
    … us</em> on Twitter</a> 	<a data-lang="en" data-show-screen-name="false" data-…

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

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

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

  • Error Line 1574, Column 194: there is no attribute "data-show-screen-name"
    … data-lang="en" data-show-screen-name="false" data-show-count="true" class="tw…

    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 1574, Column 218: there is no attribute "data-show-count"
    …w-screen-name="false" data-show-count="true" class="twitter-follow-button" hre…

    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 1574, Column 332: required attribute "type" not specified
    …om" target="_blank">Follow</a> <script>!function(d,s,id){var js,fjs=d.getEleme…

    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 1599, Column 101: reference not terminated by REFC delimiter
    …nthebox.com/?main_page=info_check&action=newsletter&newsletterPage=activation">

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

  • Warning Line 1599, Column 101: reference to external entity in attribute value
    …nthebox.com/?main_page=info_check&action=newsletter&newsletterPage=activation">

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

  • Error Line 1599, Column 101: reference to entity "action" for which no system identifier could be generated
    …nthebox.com/?main_page=info_check&action=newsletter&newsletterPage=activation">

    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 190, Column 57: entity was defined here
    …eURL + 'index.php?main_page=info_check&action=change_country&country_code='+_c…
  • Warning Line 1599, Column 127: reference not terminated by REFC delimiter
    …nthebox.com/?main_page=info_check&action=newsletter&newsletterPage=activation">

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

  • Warning Line 1599, Column 127: reference to external entity in attribute value
    …nthebox.com/?main_page=info_check&action=newsletter&newsletterPage=activation">

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

  • Error Line 1599, Column 127: reference to entity "newsletterPage" for which no system identifier could be generated
    …nthebox.com/?main_page=info_check&action=newsletter&newsletterPage=activation">

    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 929, Column 330: entity was defined here
    …main_page=info_check&action=newsletter&newsletterPage=activation" id="newslett…
  • Error Line 1640, Column 14: end tag for "ul" which is not finished
    <li> <ul></ul> </li>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 1645, Column 1: name start character invalid: only S separators and TAGC allowed here
    n> USD<span class="caret"></span></div></button><ul class="dropdown-menu"></ul>…
  • Error Line 1645, Column 1: end tag for element "spa" which is not open
    n> USD<span class="caret"></span></div></button><ul class="dropdown-menu"></ul>…

    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 1645, Column 39: end tag for "span" omitted, but OMITTAG NO was specified
    n> USD<span class="caret"></span></div></button><ul class="dropdown-menu"></ul>…

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

  • Info Line 1644, Column 117: start tag was here
    …up curSelector"> <button class="btn btn-mini dropdown-toggle"><div><span>$</spa
  • Error Line 1645, Column 79: end tag for "ul" which is not finished
    …ass="caret"></span></div></button><ul class="dropdown-menu"></ul> </div>	</div>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

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

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

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

  • Error Line 1658, Column 37: element "section" undefined
    <section class="widget-dfp clearfix"> <script type='text/javascript'> GS_google…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1658, Column 492: element "section" undefined
    …n><section class="widget-dfp clearfix"> <script type='text/javascript'> GS_goo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1668, Column 345: there is no attribute "oncontextmenu"
    …rime." class="relative" oncontextmenu="alert('Copying Prohibited by Law - HACK…

    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 1669, Column 80: cannot generate system identifier for general entity "size"
    …etseal?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES…

    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 1669, Column 80: general entity "size" not defined and no default entity
    …etseal?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES…

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

  • Warning Line 1669, Column 84: reference not terminated by REFC delimiter
    …al?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lan…

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

  • Warning Line 1669, Column 84: reference to external entity in attribute value
    …al?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lan…

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

  • Error Line 1669, Column 84: reference to entity "size" for which no system identifier could be generated
    …al?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&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.

  • Info Line 1669, Column 79: entity was defined here
    …getseal?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YE…
  • Warning Line 1669, Column 87: cannot generate system identifier for general entity "use_flash"
    …host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=e…

    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 1669, Column 87: general entity "use_flash" not defined and no default entity
    …host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=e…

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

  • Warning Line 1669, Column 96: reference not terminated by REFC delimiter
    …=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=en" type="…

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

  • Warning Line 1669, Column 96: reference to external entity in attribute value
    …=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=en" type="…

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

  • Error Line 1669, Column 96: reference to entity "use_flash" for which no system identifier could be generated
    …=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=en" type="…

    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 1669, Column 86: entity was defined here
    …?host_name=www.miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=…
  • Warning Line 1669, Column 101: cannot generate system identifier for general entity "use_transparent"
    …miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=en" type="text/…

    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 1669, Column 101: general entity "use_transparent" not defined and no default entity
    …miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=en" type="text/…

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

  • Warning Line 1669, Column 116: reference not terminated by REFC delimiter
    …m&size=S&use_flash=YES&use_transparent=YES&lang=en" type="text/javascript"></s…

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

  • Warning Line 1669, Column 116: reference to external entity in attribute value
    …m&size=S&use_flash=YES&use_transparent=YES&lang=en" type="text/javascript"></s…

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

  • Error Line 1669, Column 116: reference to entity "use_transparent" for which no system identifier could be generated
    …m&size=S&use_flash=YES&use_transparent=YES&lang=en" type="text/javascript"></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 1669, Column 100: entity was defined here
    ….miniinthebox.com&size=S&use_flash=YES&use_transparent=YES&lang=en" type="text…
  • Warning Line 1669, Column 125: reference not terminated by REFC delimiter
    …e=S&use_flash=YES&use_transparent=YES&lang=en" type="text/javascript"></script>

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

  • Error Line 1695, Column 15: required attribute "type" not specified
            <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 1695, Column 15: document type does not allow element "style" here
            <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 1716, 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>.

  • Warning Line 1732, Column 311: character "&" is the first character of a delimiter but occurred as data
    …etElementById("cto_mg_div");if(d!=null&&d.appendChild){d.appendChild(c)}}}}ret…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1732, Column 313: cannot generate system identifier for general entity "d.appendChild"
    …ElementById("cto_mg_div");if(d!=null&&d.appendChild){d.appendChild(c)}}}}retur…

    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 1732, Column 313: general entity "d.appendChild" not defined and no default entity
    …ElementById("cto_mg_div");if(d!=null&&d.appendChild){d.appendChild(c)}}}}retur…

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

  • Warning Line 1732, Column 326: reference not terminated by REFC delimiter
    …cto_mg_div");if(d!=null&&d.appendChild){d.appendChild(c)}}}}return{Load:functi…

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

  • Error Line 1732, Column 326: reference to entity "d.appendChild" for which no system identifier could be generated
    …cto_mg_div");if(d!=null&&d.appendChild){d.appendChild(c)}}}}return{Load:functi…

    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 1732, Column 312: entity was defined here
    …tElementById("cto_mg_div");if(d!=null&&d.appendChild){d.appendChild(c)}}}}retu…
  • Error Line 1732, Column 430: document type does not allow element "div" here
    … id='cto_mg_div' style='display:none;'></div>");b.Load(function(){a(c)})}}}();…

    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 1732, Column 560: cannot generate system identifier for general entity "wi"
    …teo.com/dis/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&…

    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 1732, Column 560: general entity "wi" not defined and no default entity
    …teo.com/dis/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&…

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

  • Warning Line 1732, Column 562: reference not terminated by REFC delimiter
    …o.com/dis/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=…

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

  • Error Line 1732, Column 562: reference to entity "wi" for which no system identifier could be generated
    …o.com/dis/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&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.

  • Info Line 1732, Column 559: entity was defined here
    …iteo.com/dis/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent…
  • Warning Line 1732, Column 571: cannot generate system identifier for general entity "pt1"
    …/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&…

    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 1732, Column 571: general entity "pt1" not defined and no default entity
    …/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&…

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

  • Warning Line 1732, Column 574: reference not terminated by REFC delimiter
    …s.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb=…

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

  • Error Line 1732, Column 574: reference to entity "pt1" for which no system identifier could be generated
    …s.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb=…

    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 1732, Column 570: entity was defined here
    …s/dis.aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2…
  • Warning Line 1732, Column 577: cannot generate system identifier for general entity "pt2"
    …spx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+M…

    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 1732, Column 577: general entity "pt2" not defined and no default entity
    …spx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+M…

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

  • Warning Line 1732, Column 580: reference not terminated by REFC delimiter
    …?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math…

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

  • Error Line 1732, Column 580: reference to entity "pt2" for which no system identifier could be generated
    …?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math…

    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 1732, Column 576: entity was defined here
    …aspx?p1="+escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+…
  • Warning Line 1732, Column 587: cannot generate system identifier for general entity "t1"
    …scape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(…

    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 1732, Column 587: general entity "t1" not defined and no default entity
    …scape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(…

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

  • Warning Line 1732, Column 589: reference not terminated by REFC delimiter
    …ape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Ma…

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

  • Error Line 1732, Column 589: reference to entity "t1" for which no system identifier could be generated
    …ape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Ma…

    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 1732, Column 586: entity was defined here
    …escape("v=2&wi=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor…
  • Warning Line 1732, Column 600: cannot generate system identifier for general entity "p"
    …=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()…

    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 1732, Column 600: general entity "p" not defined and no default entity
    …=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()…

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

  • Warning Line 1732, Column 601: reference not terminated by REFC delimiter
    …7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*…

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

  • Error Line 1732, Column 601: reference to entity "p" for which no system identifier could be generated
    …7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*…

    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 1732, Column 599: entity was defined here
    …i=7713670&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random(…
  • Warning Line 1732, Column 607: cannot generate system identifier for general entity "c"
    …0&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*999999…

    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 1732, Column 607: general entity "c" not defined and no default entity
    …0&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*999999…

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

  • Warning Line 1732, Column 608: reference not terminated by REFC delimiter
    …&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*9999999…

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

  • Error Line 1732, Column 608: reference to entity "c" for which no system identifier could be generated
    …&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*9999999…

    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 1732, Column 606: entity was defined here
    …70&pt1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*99999…
  • Warning Line 1732, Column 611: cannot generate system identifier for general entity "cb"
    …1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*9999999999…

    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 1732, Column 611: general entity "cb" not defined and no default entity
    …1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*9999999999…

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

  • Warning Line 1732, Column 613: reference not terminated by REFC delimiter
    …0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*99999999999)…

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

  • Error Line 1732, Column 613: reference to entity "cb" for which no system identifier could be generated
    …0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*99999999999)…

    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 1732, Column 610: entity was defined here
    …t1=0&pt2=1")+"&t1=sendEvent&p=3003&c=2&cb="+Math.floor(Math.random()*999999999…
  • Warning Line 1733, Column 109: cannot generate system identifier for general entity "srvc"
    …dvertising.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&bet…

    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 1733, Column 109: general entity "srvc" not defined and no default entity
    …dvertising.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&bet…

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

  • Warning Line 1733, Column 113: reference not terminated by REFC delimiter
    …tising.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12…

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

  • Warning Line 1733, Column 113: reference to external entity in attribute value
    …tising.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12…

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

  • Error Line 1733, Column 113: reference to entity "srvc" for which no system identifier could be generated
    …tising.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12…

    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 1733, Column 108: entity was defined here
    …advertising.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&be…
  • Warning Line 1733, Column 116: cannot generate system identifier for general entity "betr"
    …ing.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607…

    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 1733, Column 116: general entity "betr" not defined and no default entity
    …ing.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607…

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

  • Warning Line 1733, Column 120: reference not terminated by REFC delimiter
    …com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]…

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

  • Warning Line 1733, Column 120: reference to external entity in attribute value
    …com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]…

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

  • Error Line 1733, Column 120: reference to entity "betr" for which no system identifier could be generated
    …com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]…

    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 1733, Column 115: entity was defined here
    …sing.com/adcedge/lb?site=695501&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=1260…
  • Warning Line 1733, Column 146: cannot generate system identifier for general entity "betq"
    …&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]433089" width = "1" height…

    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 1733, Column 146: general entity "betq" not defined and no default entity
    …&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]433089" width = "1" height…

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

  • Warning Line 1733, Column 150: reference not terminated by REFC delimiter
    …c=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]433089" width = "1" height = "…

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

  • Warning Line 1733, Column 150: reference to external entity in attribute value
    …c=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]433089" width = "1" height = "…

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

  • Error Line 1733, Column 150: reference to entity "betq" for which no system identifier could be generated
    …c=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]433089" width = "1" height = "…

    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 1733, Column 145: entity was defined here
    …1&srvc=1&betr=56009_NDM_cs=[+]rtminihp&betq=12607=[+]433089" width = "1" heigh…
  • Error Line 1733, Column 205: required attribute "alt" not specified
    …+]433089" width = "1" height = "1" border = "0"><script type="text/javascript">

    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 1733, Column 206: end tag for "img" omitted, but OMITTAG NO was specified
    …+]433089" width = "1" height = "1" border = "0"><script type="text/javascript">

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

  • Info Line 1733, Column 44: start tag was here
    …ript><!-- #26678-CRITEO-EN[US]-EOF --><img src="http://leadback.advertising.co…
  • Error Line 1748, Column 62: required attribute "type" not specified
    <!-- trackingcode #48272 BOF --><script language="JavaScript">

    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 1749, Column 86: an attribute specification must start with a name or name token
    … = w_rand * 1000; document.write('<scr'+'ipt type="text/javascript" src="https…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 1749, Column 86: element "scr" undefined
    … = w_rand * 1000; document.write('<scr'+'ipt type="text/javascript" src="https…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1749, Column 167: cannot generate system identifier for general entity "aid"
    …dsp-service.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:i…

    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 1749, Column 167: general entity "aid" not defined and no default entity
    …dsp-service.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type: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.

  • Warning Line 1749, Column 170: reference not terminated by REFC delimiter
    …-service.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:inde…

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

  • Error Line 1749, Column 170: reference to entity "aid" for which no system identifier could be generated
    …-service.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:inde…

    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 1749, Column 166: entity was defined here
    …/dsp-service.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:…
  • Warning Line 1749, Column 174: cannot generate system identifier for general entity "uuid"
    …vice.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$ca…

    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 1749, Column 174: general entity "uuid" not defined and no default entity
    …vice.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$ca…

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

  • Warning Line 1749, Column 178: reference not terminated by REFC delimiter
    ….adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$catego…

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

  • Error Line 1749, Column 178: reference to entity "uuid" for which no system identifier could be generated
    ….adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$catego…

    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 1749, Column 173: entity was defined here
    …rvice.adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$c…
  • Warning Line 1749, Column 180: cannot generate system identifier for general entity "seg"
    …dsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$category…

    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 1749, Column 180: general entity "seg" not defined and no default entity
    …dsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$category…

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

  • Warning Line 1749, Column 183: reference not terminated by REFC delimiter
    …ana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$category_le…

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

  • Error Line 1749, Column 183: reference to entity "seg" for which no system identifier could be generated
    …ana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$category_le…

    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 1749, Column 179: entity was defined here
    …adsvana.com/um?'+w_rand+'&aid=gM&uuid=&seg=language:en$page_type:index$categor…
  • Error Line 1749, Column 259: delimiter "'" invalid: only S separators and TAGC allowed here
    …ge:en$page_type:index$category_level:$category_id:$product_id:"></scr'+'ipt>');
  • Error Line 1783, Column 112: element "section" undefined
    …de"><section class="widget-dfp widget"><div id="dfp-home-slides"> <script type…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1783, Column 1776: element "section" undefined
    …de"><section class="widget-dfp widget"> <script type='text/javascript'> GS_goo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1783, Column 2270: element "section" undefined
    …de"><section class="widget-dfp widget"> <script type='text/javascript'> GS_goo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1783, Column 2759: element "section" undefined
    …de"><section class="widget-dfp widget"> <script type='text/javascript'> GS_goo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1783, Column 3644: element "section" undefined
    …de"><section class="widget-dfp widget"> <script type='text/javascript'> GS_goo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1783, Column 4529: element "section" undefined
    …de"><section class="widget-dfp widget"> <script type='text/javascript'> GS_goo…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1783, Column 5341: required attribute "type" not specified
    …en"); </script></section></div><script>$(function() {$('#delay-dfp-home-slides…

    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>.

Visitor Analysis

Daily Visitor
  • 39.667 visits

In Page Analysis