itemvn.com

Listen to free music. Search and listen to free songs online. Search songs, artists, and albums, create playlists and share them with your friends and family. Free MP3 Streaming. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 03-09-2013 03:35:02  (update).

Overview Info

  • Domain Name
    itemvn.com
  • Favicon
  • Alexa Rank
    #27853
  • Google Page Rank
    PR 2
  • Ip Address
    192.211.54.202
  • Page Size
    68.5 KB
  • Images
    5 GIF, 6 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    3 3 0 0 0 0

Website Meta Analysis



  • Title
    Itemvn - Listen to Free Music Online - Free MP3 Streaming - Search music, find music, listen to music, share music online
  • Meta Keyword
    listen to music, play music online, discover music, music search engine, online music, music search, search music, music playlist, free mp3, itemvn
  • Meta Description
    Listen to free music. Search and listen to free songs online. Search songs, artists, and albums, create playlists and share them with your friends and family. Free MP3 Streaming.

Technical Analysis



  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    192.211.54.202
  • Domain Age
    8 Years, 1 Months, 13 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache
  • pragma: no-cache
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • expires: -1
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-powered-by: UrlRewriter.NET 2.0.0
  • x-aspnet-version: 2.0.50727
  • date: Tue, 03 Sep 2013 15:35:02 GMT
  • content-length: 14042
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC

Domain Name: ITEMVN.COM

Domain servers in listed order:
NS47.DOMAINCONTROL.COM
NS48.DOMAINCONTROL.COM

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?domain=ITEMVN.COM

DNS Analysis


DNS servers
ns47.domaincontrol.com [216.69.185.24]
ns48.domaincontrol.com [208.109.255.24]


DNS Records

Answer records
itemvn.com A 192.211.54.202 3600s
itemvn.com MX
preference: 0
exchange: mail.itemvn.com
86400s
itemvn.com NS  ns47.domaincontrol.com 3600s
itemvn.com NS  ns48.domaincontrol.com 3600s
itemvn.com TXT v=spf1 mx ip4:192.211.54.202 -all 3600s
itemvn.com SOA
server: ns47.domaincontrol.com
email: dns@jomax.net
serial: 2012111500
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 192.211.54.202 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 192.211.54.202"
    #
    # Use "?" to get help.
    #

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

    NetRange: 192.211.48.0 - 192.211.63.255
    CIDR: 192.211.48.0/20
    OriginAS: AS174, AS13354
    NetName: INCERO-LLC
    NetHandle: NET-192-211-48-0-1
    Parent: NET-192-0-0-0-0
    NetType: Direct Allocation
    Comment: http://www.Incero.com
    RegDate: 2012-09-27
    Updated: 2012-09-27
    Ref: http://whois.arin.net/rest/net/NET-192-211-48-0-1

    OrgName: Incero LLC
    OrgId: IL-38
    Address: 5555 N LAMAR, STE L-121
    City: AUSTIN
    StateProv: TX
    PostalCode: 78751
    Country: US
    RegDate: 2012-02-16
    Updated: 2012-03-20
    Ref: http://whois.arin.net/rest/org/IL-38

    OrgTechHandle: NONO-ARIN
    OrgTechName: Network Operations, Network Operations
    OrgTechPhone: +1-512-394-8803
    OrgTechEmail: abuse@inceronetwork.com
    OrgTechRef: http://whois.arin.net/rest/poc/NONO-ARIN

    OrgNOCHandle: NONO-ARIN
    OrgNOCName: Network Operations, Network Operations
    OrgNOCPhone: +1-512-394-8803
    OrgNOCEmail: abuse@inceronetwork.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NONO-ARIN

    OrgAbuseHandle: NONO-ARIN
    OrgAbuseName: Network Operations, Network Operations
    OrgAbusePhone: +1-512-394-8803
    OrgAbuseEmail: abuse@inceronetwork.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/NONO-ARIN

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 166 Errors
  • 37 Warnings
Ratio Text/Html
  • 0.5507889405655263
Message Error
  • Warning Line 9, Column 70: NET-enabling start-tag requires SHORTTAG YES
    						<link rel="shortcut icon" href="//s.itncdn.com/img/itemvn.ico" />

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

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

  • Error Line 10, Column 95: document type does not allow element "LINK" here
    …="text/css" rel="stylesheet" href="//s.itncdn.com/css/itemvn_v3.3.011.min.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 11, Column 12: end tag for element "HEAD" which is not open
    					</head>

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

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

  • Error Line 12, Column 108: document type does not allow element "BODY" here
    …image: url(//s.itncdn.com/img/v3_bg_74984.jpg); background-repeat: no-repeat;">

    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 14, Column 16: there is no attribute "NAME"
    				<form name="MainForm" method="post" action="/default.aspx" id="MainForm">

    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 15, Column 45: value of attribute "ID" invalid: "_" cannot start a name
    … type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTQ0OTI4Mzkw…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 15, Column 191: NET-enabling start-tag requires SHORTTAG YES
    …mVQb3N0QmFja0tleV9fFgEFEV9jdGwxOmNtZEZpbmRTb25nNhoYlwOTuiy81/z5gicpaGh/4KA=" />

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

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

  • Error Line 29, Column 44: value of attribute "ID" invalid: "_" cannot start a name
    …	<a href="http://www.itemvn.com/" id="_ctl1_lnkHome1" title="Home"><img src="/…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 29, Column 124: value of attribute "ID" invalid: "_" cannot start a name
    ….itncdn.com/img/itemvn2_logo.png" id="_ctl1_imgLogo" alt="Itemvn Music Online"…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 29, Column 176: NET-enabling start-tag requires SHORTTAG YES
    …temvn2_logo.png" id="_ctl1_imgLogo" alt="Itemvn Music Online" border="0" /></a>

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

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

  • Error Line 35, Column 22: value of attribute "ID" invalid: "_" cannot start a name
    								    <div id="_ctl1_Panel1">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 37, Column 88: value of attribute "ID" invalid: "_" cannot start a name
    …      <input name="_ctl1:hiddenUserID" type="hidden" id="_ctl1_hiddenUserID" />

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 37, Column 108: NET-enabling start-tag requires SHORTTAG YES
    …      <input name="_ctl1:hiddenUserID" type="hidden" id="_ctl1_hiddenUserID" />

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

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

  • Error Line 38, Column 88: value of attribute "ID" invalid: "_" cannot start a name
    …hiddenSessionToken" type="hidden" id="_ctl1_hiddenSessionToken" value="354F186…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 38, Column 163: NET-enabling start-tag requires SHORTTAG YES
    …="_ctl1_hiddenSessionToken" value="354F1868C6BC895A6598869EA0B1A84CA6F2142E" />

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

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

  • Error Line 39, Column 85: value of attribute "ID" invalid: "_" cannot start a name
    …l1:hiddenSeparator" type="hidden" id="_ctl1_hiddenSeparator" value="___itemvnp…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 39, Column 133: NET-enabling start-tag requires SHORTTAG YES
    …Separator" type="hidden" id="_ctl1_hiddenSeparator" value="___itemvnpara___" />

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

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

  • Warning Line 40, Column 76: NET-enabling start-tag requires SHORTTAG YES
    		                            <input type=hidden id="hiddenCurrentKeyword" />

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

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

  • Error Line 50, Column 89: value of attribute "ID" invalid: "_" cannot start a name
    …="_ctl1:txtSearchKey" type="text" id="_ctl1_txtSearchKey" class="txtsearch" au…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 50, Column 140: there is no attribute "AUTOCOMPLETE"
    …chKey" class="txtsearch" autocomplete="off" onkeyup="OnAutoSuggest(event);" on…

    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 50, Column 450: NET-enabling start-tag requires SHORTTAG YES
    … = 'cbosearch'; document.getElementById('divSuggest').className = 'hidden';" />

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

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

  • Error Line 67, Column 62: value of attribute "ID" invalid: "_" cannot start a name
    …                            <span id="_ctl1_spanSearchTypeHolder"><span id="lb…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 76, Column 95: value of attribute "ID" invalid: "_" cannot start a name
    …"_ctl1:hiddenSearchType" type="hidden" id="_ctl1_hiddenSearchType" value="1" />

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 76, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …"_ctl1:hiddenSearchType" type="hidden" id="_ctl1_hiddenSearchType" value="1" />

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

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

  • Warning Line 104, Column 92: NET-enabling start-tag requires SHORTTAG YES
    …                         <input type=submit class="cmdsearch" value="Search" />

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

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

  • Error Line 105, Column 89: value of attribute "ID" invalid: "_" cannot start a name
    …="image" name="_ctl1:cmdFindSong" id="_ctl1_cmdFindSong" class="hidden" alt="S…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 105, Column 152: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …"hidden" alt="Search" align="absmiddle" border="0" onclick="return OnCheckSear…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 105, Column 161: there is no attribute "BORDER"
    …alt="Search" align="absmiddle" border="0" onclick="return OnCheckSearchKey();"…

    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 105, Column 211: there is no attribute "LANGUAGE"
    …iddle" border="0" onclick="return OnCheckSearchKey();" language="javascript" />

    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 105, Column 224: NET-enabling start-tag requires SHORTTAG YES
    …iddle" border="0" onclick="return OnCheckSearchKey();" language="javascript" />

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

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

  • Error Line 117, Column 23: value of attribute "ID" invalid: "_" cannot start a name
    												<span id="_ctl1_lblWarning" class="warning" style="font-size:XX-Sma…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 134, Column 89: value of attribute "ID" invalid: "_" cannot start a name
    …n.com/login/?returnURL=___upload" id="_ctl1_lnkUpload" class="topmenu">Upload<…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 140, Column 95: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/register/?returnURL=" id="_ctl1_lnkRegister" class="topmenu">Creat…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 180, Column 80: value of attribute "ID" invalid: "_" cannot start a name
    …www.itemvn.com/login/?returnURL=" id="_ctl1_lnkLogin" class="topmenu">Sign In<…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 206, Column 105: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …d align=center height="30px"><a class="menu" href="#"><div>Genre</div></a></td>

    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 213, Column 99: value of attribute "ID" invalid: "_" cannot start a name
    …itemvn.com/justadded/Genre/Pop/1" id="_ctl1_lnkMenuGenrePop" class="menu_genre…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 213, Column 150: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …p/1" id="_ctl1_lnkMenuGenrePop" class="menu_genre_item"><div>Pop</div></a></td>

    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 214, Column 101: value of attribute "ID" invalid: "_" cannot start a name
    …emvn.com/justadded/Genre/Latin/1" id="_ctl1_lnkMenuGenreLatin" class="menu_gen…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 214, Column 154: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … id="_ctl1_lnkMenuGenreLatin" class="menu_genre_item"><div>Latin</div></a></td>

    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 215, Column 103: value of attribute "ID" invalid: "_" cannot start a name
    …vn.com/justadded/Genre/Country/1" id="_ctl1_lnkMenuGenreCountry" class="menu_g…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 215, Column 158: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …"_ctl1_lnkMenuGenreCountry" class="menu_genre_item"><div>Country</div></a></td>

    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 216, Column 105: value of attribute "ID" invalid: "_" cannot start a name
    ….com/justadded/Genre/Classical/1" id="_ctl1_lnkMenuGenreClassical" class="menu…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 216, Column 162: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l1_lnkMenuGenreClassical" class="menu_genre_item"><div>Classical</div></a></td>

    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 219, Column 100: value of attribute "ID" invalid: "_" cannot start a name
    …temvn.com/justadded/Genre/Rock/1" id="_ctl1_lnkMenuGenreRock" class="menu_genr…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 219, Column 152: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …1" id="_ctl1_lnkMenuGenreRock" class="menu_genre_item"><div>Rock</div></a></td>

    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 220, Column 106: value of attribute "ID" invalid: "_" cannot start a name
    …com/justadded/Genre/Electronic/1" id="_ctl1_lnkMenuGenreElectronica" class="me…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 220, Column 165: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …lnkMenuGenreElectronica" class="menu_genre_item"><div>Electronic</div></a></td>

    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 221, Column 100: value of attribute "ID" invalid: "_" cannot start a name
    …temvn.com/justadded/Genre/Jazz/1" id="_ctl1_lnkMenuGenreJazz" class="menu_genr…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 221, Column 152: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …1" id="_ctl1_lnkMenuGenreJazz" class="menu_genre_item"><div>Jazz</div></a></td>

    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 222, Column 103: value of attribute "ID" invalid: "_" cannot start a name
    …vn.com/justadded/Genre/New Age/1" id="_ctl1_lnkMenuGenreNewAge" class="menu_ge…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 222, Column 157: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …="_ctl1_lnkMenuGenreNewAge" class="menu_genre_item"><div>New Age</div></a></td>

    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 225, Column 99: value of attribute "ID" invalid: "_" cannot start a name
    …itemvn.com/justadded/Genre/R-B/1" id="_ctl1_lnkMenuGenreRB" class="menu_genre_…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 225, Column 149: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …" id="_ctl1_lnkMenuGenreRB" class="menu_genre_item"><div>R&amp;B</div></a></td>

    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 226, Column 107: value of attribute "ID" invalid: "_" cannot start a name
    …om/justadded/Genre/Alternative/1" id="_ctl1_lnkMenuGenreAlternative" class="me…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 226, Column 166: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …nkMenuGenreAlternative" class="menu_genre_item"><div>Alternative</div></a></td>

    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 227, Column 101: value of attribute "ID" invalid: "_" cannot start a name
    …emvn.com/justadded/Genre/Blues/1" id="_ctl1_lnkMenuGenreBlues" class="menu_gen…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 227, Column 154: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … id="_ctl1_lnkMenuGenreBlues" class="menu_genre_item"><div>Blues</div></a></td>

    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 228, Column 106: value of attribute "ID" invalid: "_" cannot start a name
    …com/justadded/Genre/Soundtrack/1" id="_ctl1_lnkMenuGenreSoundtrack" class="men…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 228, Column 164: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …_lnkMenuGenreSoundtrack" class="menu_genre_item"><div>Soundtrack</div></a></td>

    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 231, Column 103: value of attribute "ID" invalid: "_" cannot start a name
    …vn.com/justadded/Genre/Hip Hop/1" id="_ctl1_lnkMenuGenreHipHop" class="menu_ge…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 231, Column 157: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …="_ctl1_lnkMenuGenreHipHop" class="menu_genre_item"><div>Hip Hop</div></a></td>

    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 232, Column 101: value of attribute "ID" invalid: "_" cannot start a name
    …emvn.com/justadded/Genre/Metal/1" id="_ctl1_lnkMenuGenreMetal" class="menu_gen…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 232, Column 154: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … id="_ctl1_lnkMenuGenreMetal" class="menu_genre_item"><div>Metal</div></a></td>

    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 233, Column 100: value of attribute "ID" invalid: "_" cannot start a name
    …temvn.com/justadded/Genre/Soul/1" id="_ctl1_lnkMenuGenreSoul" class="menu_genr…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 233, Column 152: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …1" id="_ctl1_lnkMenuGenreSoul" class="menu_genre_item"><div>Soul</div></a></td>

    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 234, Column 105: value of attribute "ID" invalid: "_" cannot start a name
    ….com/justadded/Genre/Christmas/1" id="_ctl1_lnkMenuGenreChristmas" class="menu…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 234, Column 162: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …l1_lnkMenuGenreChristmas" class="menu_genre_item"><div>Christmas</div></a></td>

    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 237, Column 99: value of attribute "ID" invalid: "_" cannot start a name
    …itemvn.com/justadded/Genre/Rap/1" id="_ctl1_lnkMenuGenreRap" class="menu_genre…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 237, Column 150: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …p/1" id="_ctl1_lnkMenuGenreRap" class="menu_genre_item"><div>Rap</div></a></td>

    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 238, Column 101: value of attribute "ID" invalid: "_" cannot start a name
    …emvn.com/justadded/Genre/Indie/1" id="_ctl1_lnkMenuGenreIndie" class="menu_gen…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 238, Column 154: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … id="_ctl1_lnkMenuGenreIndie" class="menu_genre_item"><div>Indie</div></a></td>

    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 239, Column 100: value of attribute "ID" invalid: "_" cannot start a name
    …temvn.com/justadded/Genre/Folk/1" id="_ctl1_lnkMenuGenreFolk" class="menu_genr…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 239, Column 152: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …1" id="_ctl1_lnkMenuGenreFolk" class="menu_genre_item"><div>Folk</div></a></td>

    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 240, Column 100: value of attribute "ID" invalid: "_" cannot start a name
    …temvn.com/justadded/Genre/Teen/1" id="_ctl1_lnkMenuGenreTeen" class="menu_genr…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 240, Column 152: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …1" id="_ctl1_lnkMenuGenreTeen" class="menu_genre_item"><div>Teen</div></a></td>

    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 243, Column 101: value of attribute "ID" invalid: "_" cannot start a name
    …emvn.com/justadded/Genre/Dance/1" id="_ctl1_lnkMenuGenreDance" class="menu_gen…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 243, Column 154: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … id="_ctl1_lnkMenuGenreDance" class="menu_genre_item"><div>Dance</div></a></td>

    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 244, Column 100: value of attribute "ID" invalid: "_" cannot start a name
    …temvn.com/justadded/Genre/Punk/1" id="_ctl1_lnkMenuGenrePunk" class="menu_genr…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 244, Column 152: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …1" id="_ctl1_lnkMenuGenrePunk" class="menu_genre_item"><div>Punk</div></a></td>

    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 254, Column 146: value of attribute "ID" invalid: "_" cannot start a name
    …href="http://www.itemvn.com/news" id="_ctl1_lnkMenuNews" class="menu"><div sty…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 254, Column 211: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …lnkMenuNews" class="menu"><div style="padding:7px 0 8px 0;">News</div></a></td>

    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 255, Column 156: value of attribute "ID" invalid: "_" cannot start a name
    …://www.itemvn.com/featuredartist" id="_ctl1_lnkMenuFeaturedArtist" class="menu…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 255, Column 231: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …dArtist" class="menu"><div style="padding:7px 0 8px 0;">Features</div></a></td>

    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 256, Column 152: value of attribute "ID" invalid: "_" cannot start a name
    …http://www.itemvn.com/topartists" id="_ctl1_lnkMenuHotArtist" class="menu"><di…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 256, Column 222: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …tist" class="menu"><div style="padding:7px 0 8px 0;">Hot Artists</div></a></td>

    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 257, Column 154: value of attribute "ID" invalid: "_" cannot start a name
    …tp://www.itemvn.com/browse_songs" id="_ctl1_lnkMenuBrowseSongs" class="menu"><…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 257, Column 226: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …ngs" class="menu"><div style="padding:7px 0 8px 0;">Browse Songs</div></a></td>

    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 258, Column 148: value of attribute "ID" invalid: "_" cannot start a name
    …ef="http://www.itemvn.com/hot100" id="_ctl1_lnkMenuBillboardHot100" class="men…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 258, Column 224: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …class="menu"><div style="padding:7px 0 8px 0;">Billboard Hot 100</div></a></td>

    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 259, Column 153: value of attribute "ID" invalid: "_" cannot start a name
    …ttp://www.itemvn.com/bestsellers" id="_ctl1_lnkMenuBestsellers" class="menu"><…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 259, Column 225: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …lers" class="menu"><div style="padding:7px 0 8px 0;">Bestsellers</div></a></td>

    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 260, Column 151: value of attribute "ID" invalid: "_" cannot start a name
    …"http://www.itemvn.com/justadded" id="_ctl1_lnkMenuJustAdded" class="menu"><di…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 260, Column 221: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …Added" class="menu"><div style="padding:7px 0 8px 0;">Just Added</div></a></td>

    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 275, Column 15: value of attribute "ID" invalid: "_" cannot start a name
    			<table id="_ctl1_tblQuickSearch" class="body_content" cellpadding="0" cellsp…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 284, Column 32: value of attribute "ID" invalid: "_" cannot start a name
    									            <span id="_ctl1_labelQuickSearch" class="search">Browse Ar…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 289, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=A" id="_ctl1_lnkQuickSearchA" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 290, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=B" id="_ctl1_lnkQuickSearchB" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 291, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=C" id="_ctl1_lnkQuickSearchC" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 292, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=D" id="_ctl1_lnkQuickSearchD" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 293, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=E" id="_ctl1_lnkQuickSearchE" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 294, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=F" id="_ctl1_lnkQuickSearchF" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 295, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=G" id="_ctl1_lnkQuickSearchG" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 296, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=H" id="_ctl1_lnkQuickSearchH" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 297, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=I" id="_ctl1_lnkQuickSearchI" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 298, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=J" id="_ctl1_lnkQuickSearchJ" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 299, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=K" id="_ctl1_lnkQuickSearchK" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 300, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=L" id="_ctl1_lnkQuickSearchL" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 301, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=M" id="_ctl1_lnkQuickSearchM" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 302, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=N" id="_ctl1_lnkQuickSearchN" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 303, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=O" id="_ctl1_lnkQuickSearchO" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 304, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=P" id="_ctl1_lnkQuickSearchP" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 305, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=Q" id="_ctl1_lnkQuickSearchQ" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 306, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=R" id="_ctl1_lnkQuickSearchR" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 307, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=S" id="_ctl1_lnkQuickSearchS" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 308, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=T" id="_ctl1_lnkQuickSearchT" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 309, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=U" id="_ctl1_lnkQuickSearchU" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 310, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=V" id="_ctl1_lnkQuickSearchV" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 311, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=W" id="_ctl1_lnkQuickSearchW" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 312, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=X" id="_ctl1_lnkQuickSearchX" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 313, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=Y" id="_ctl1_lnkQuickSearchY" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 314, Column 79: value of attribute "ID" invalid: "_" cannot start a name
    ….itemvn.com/listartist/?letter=Z" id="_ctl1_lnkQuickSearchZ" class="search_let…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 315, Column 82: value of attribute "ID" invalid: "_" cannot start a name
    …emvn.com/listartist/?letter=0..9" id="_ctl1_lnkQuickSearchNo" class="search_le…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 321, Column 160: there is no attribute "ALLOWTRANSPARENCY"
    … overflow:hidden; width:200px; height:62px;" allowTransparency="true"></iframe>

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

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

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

  • Error Line 327, Column 15: value of attribute "ID" invalid: "_" cannot start a name
    						<h2 id="_ctl1_h2RightHeader"></h2>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 339, Column 6: document type does not allow element "HTML" here
    <HTML>

    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 341, Column 8: end tag for "HEAD" which is not finished
    	</HEAD>

    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 376, Column 207: NET-enabling start-tag requires SHORTTAG YES
    …l0_Img11" class="artist_image_larger" /><img id='addicon_222547' class="hidden…

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

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

  • Error Line 376, Column 207: required attribute "ALT" not specified
    …l0_Img11" class="artist_image_larger" /><img id='addicon_222547' class="hidden…

    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 376, Column 441: NET-enabling start-tag requires SHORTTAG YES
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

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

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

  • Error Line 376, Column 441: required attribute "ALT" not specified
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

    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 376, Column 500: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …n();" /><span class="added"><div class="hidden" id='added_222547'></div></span>

    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 384, Column 133: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …le id='paneladd_222547' cellpadding=5 cellspacing=0 width="200" class="hidden">

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

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

  • Error Line 392, Column 124: character ";" not allowed in attribute specification list
    … onclick="SaveFavoriteSong('222547');"; onmouseover="this.className='graybackg…
  • Warning Line 404, Column 252: NET-enabling start-tag requires SHORTTAG YES
    …idth:180px;" onkeypress="AddSongToNewPlaylist('222547', this.value, event);" />

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

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

  • Error Line 430, Column 29: end tag for "SPAN" omitted, but its declaration does not permit this
    												            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 429, Column 26: start tag was here
    													            <span id="listMostPopular__ctl0_lblCreator"><span clas…
  • Warning Line 445, Column 186: NET-enabling start-tag requires SHORTTAG YES
    …l1_Img11" class="artist_image_larger" /><img id='addicon_188075' class="hidden…

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

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

  • Error Line 445, Column 186: required attribute "ALT" not specified
    …l1_Img11" class="artist_image_larger" /><img id='addicon_188075' class="hidden…

    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 445, Column 420: NET-enabling start-tag requires SHORTTAG YES
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

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

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

  • Error Line 445, Column 420: required attribute "ALT" not specified
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

    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 445, Column 479: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …n();" /><span class="added"><div class="hidden" id='added_188075'></div></span>

    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 453, Column 133: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …le id='paneladd_188075' cellpadding=5 cellspacing=0 width="200" class="hidden">

    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 461, Column 124: character ";" not allowed in attribute specification list
    … onclick="SaveFavoriteSong('188075');"; onmouseover="this.className='graybackg…
  • Warning Line 473, Column 252: NET-enabling start-tag requires SHORTTAG YES
    …idth:180px;" onkeypress="AddSongToNewPlaylist('188075', this.value, event);" />

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

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

  • Error Line 499, Column 29: end tag for "SPAN" omitted, but its declaration does not permit this
    												            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 498, Column 26: start tag was here
    													            <span id="listMostPopular__ctl1_lblCreator"><span clas…
  • Warning Line 514, Column 188: NET-enabling start-tag requires SHORTTAG YES
    …l2_Img11" class="artist_image_larger" /><img id='addicon_184360' class="hidden…

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

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

  • Error Line 514, Column 188: required attribute "ALT" not specified
    …l2_Img11" class="artist_image_larger" /><img id='addicon_184360' class="hidden…

    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 514, Column 422: NET-enabling start-tag requires SHORTTAG YES
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

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

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

  • Error Line 514, Column 422: required attribute "ALT" not specified
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

    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 514, Column 481: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …n();" /><span class="added"><div class="hidden" id='added_184360'></div></span>

    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 522, Column 133: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …le id='paneladd_184360' cellpadding=5 cellspacing=0 width="200" class="hidden">

    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 530, Column 124: character ";" not allowed in attribute specification list
    … onclick="SaveFavoriteSong('184360');"; onmouseover="this.className='graybackg…
  • Warning Line 542, Column 252: NET-enabling start-tag requires SHORTTAG YES
    …idth:180px;" onkeypress="AddSongToNewPlaylist('184360', this.value, event);" />

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

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

  • Error Line 568, Column 29: end tag for "SPAN" omitted, but its declaration does not permit this
    												            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 567, Column 26: start tag was here
    													            <span id="listMostPopular__ctl2_lblCreator"><span clas…
  • Warning Line 583, Column 204: NET-enabling start-tag requires SHORTTAG YES
    …l3_Img11" class="artist_image_larger" /><img id='addicon_233622' class="hidden…

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

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

  • Error Line 583, Column 204: required attribute "ALT" not specified
    …l3_Img11" class="artist_image_larger" /><img id='addicon_233622' class="hidden…

    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 583, Column 438: NET-enabling start-tag requires SHORTTAG YES
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

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

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

  • Error Line 583, Column 438: required attribute "ALT" not specified
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

    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 583, Column 497: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …n();" /><span class="added"><div class="hidden" id='added_233622'></div></span>

    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 591, Column 133: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …le id='paneladd_233622' cellpadding=5 cellspacing=0 width="200" class="hidden">

    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 599, Column 124: character ";" not allowed in attribute specification list
    … onclick="SaveFavoriteSong('233622');"; onmouseover="this.className='graybackg…
  • Warning Line 611, Column 252: NET-enabling start-tag requires SHORTTAG YES
    …idth:180px;" onkeypress="AddSongToNewPlaylist('233622', this.value, event);" />

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

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

  • Error Line 637, Column 29: end tag for "SPAN" omitted, but its declaration does not permit this
    												            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 636, Column 26: start tag was here
    													            <span id="listMostPopular__ctl3_lblCreator"><span clas…
  • Warning Line 652, Column 218: NET-enabling start-tag requires SHORTTAG YES
    …l4_Img11" class="artist_image_larger" /><img id='addicon_232363' class="hidden…

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

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

  • Error Line 652, Column 218: required attribute "ALT" not specified
    …l4_Img11" class="artist_image_larger" /><img id='addicon_232363' class="hidden…

    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 652, Column 452: NET-enabling start-tag requires SHORTTAG YES
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

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

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

  • Error Line 652, Column 452: required attribute "ALT" not specified
    …);" onmouseout="OnMouseOutAddIcon();" /><span class="added"><div class="hidden…

    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 652, Column 511: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …n();" /><span class="added"><div class="hidden" id='added_232363'></div></span>

    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 660, Column 133: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …le id='paneladd_232363' cellpadding=5 cellspacing=0 width="200" class="hidden">

    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 668, Column 124: character ";" not allowed in attribute specification list
    … onclick="SaveFavoriteSong('232363');"; onmouseover="this.className='graybackg…
  • Warning Line 680, Column 252: NET-enabling start-tag requires SHORTTAG YES
    …idth:180px;" onkeypress="AddSongToNewPlaylist('232363', this.value, event);" />

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

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

  • Error Line 706, Column 29: end tag for "SPAN" omitted, but its declaration does not permit this
    												            </td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 705, Column 26: start tag was here
    													            <span id="listMostPopular__ctl4_lblCreator"><span clas…
  • Warning Line 716, Column 140: NET-enabling start-tag requires SHORTTAG YES
    …"" onclick="return false;" language="javascript" id="cmdBodi" class="hidden" />

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

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

  • Warning Line 719, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …						            <input name="hiddenUserID" type="hidden" id="hiddenUserID" />

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

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

  • Warning Line 720, Column 104: NET-enabling start-tag requires SHORTTAG YES
    …      <input name="hiddenSessionToken" type="hidden" id="hiddenSessionToken" />

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

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

  • Warning Line 721, Column 98: NET-enabling start-tag requires SHORTTAG YES
    …            <input name="hiddenSeparator" type="hidden" id="hiddenSeparator" />

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

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

  • Warning Line 774, Column 366: NET-enabling start-tag requires SHORTTAG YES
    …igerian Singer Goldie Harvey Dead Following Trip to Grammy Awards Photo" /></a>

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

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

  • Warning Line 825, Column 31: NET-enabling start-tag requires SHORTTAG YES
    														            <br />

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

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

  • Warning Line 846, Column 376: NET-enabling start-tag requires SHORTTAG YES
    …lt="Sound City Players: Opposites Attract (And Don’t) in New York Photo" /></a>

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

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

  • Warning Line 897, Column 31: NET-enabling start-tag requires SHORTTAG YES
    														            <br />

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

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

  • Error Line 916, Column 7: end tag for "TABLE" omitted, but its declaration does not permit this
    </HTML>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 16, Column 1: start tag was here
    <table cellspacing="0" cellpadding="0" border="0" style="border-width:0px;width…
  • Error Line 916, Column 7: end tag for "FORM" omitted, but its declaration does not permit this
    </HTML>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 14, Column 5: start tag was here
    				<form name="MainForm" method="post" action="/default.aspx" id="MainForm">
  • Error Line 916, Column 7: end tag for "DIV" omitted, but its declaration does not permit this
    </HTML>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 13, Column 7: start tag was here
    						<div>
  • Error Line 917, Column 5: end tag for element "TD" which is not open
    </td>

    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 918, Column 6: end tag for element "TR" which is not open
    	</tr><tr>

    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 918, Column 10: document type does not allow element "TR" here
    	</tr><tr>

    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 925, Column 14: value of attribute "ID" invalid: "_" cannot start a name
    			<span id="_ctl2_lblCopyRight" class="copyright">Itemvn &copy; 2013</span>

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 932, Column 54: value of attribute "ID" invalid: "_" cannot start a name
    …f="http://www.itemvn.com/privacy" id="_ctl2_lnkMenuPrivacy" class="menu_footer…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 933, Column 49: value of attribute "ID" invalid: "_" cannot start a name
    …ref="http://www.itemvn.com/terms" id="_ctl2_lnkMenuTerms" class="menu_footer">…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 934, Column 51: value of attribute "ID" invalid: "_" cannot start a name
    …f="http://www.itemvn.com/contact" id="_ctl2_lnkMenuContactUs" class="menu_foot…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 942, Column 10: value of attribute "ID" invalid: "_" cannot start a name
    <div id="_ctl2_divNormalJS">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 961, Column 8: end tag for element "TABLE" which is not open
    </table>

    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 962, Column 51: value of attribute "ID" invalid: "_" cannot start a name
    …"hidden" name="__EVENTVALIDATION" id="__EVENTVALIDATION" value="/wEWCwL+tNiXDQ…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 962, Column 199: NET-enabling start-tag requires SHORTTAG YES
    …AgLdlqvXCQKFoc/rAwL4hq7JBgKkwKrWCwLU4tCGDK/zOWffecuBNcACiuG4za6CC7i6" /></form>

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

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

  • Error Line 962, Column 199: document type does not allow element "INPUT" here
    …AgLdlqvXCQKFoc/rAwL4hq7JBgKkwKrWCwLU4tCGDK/zOWffecuBNcACiuG4za6CC7i6" /></form>

    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 962, Column 200: character data is not allowed here
    …AgLdlqvXCQKFoc/rAwL4hq7JBgKkwKrWCwLU4tCGDK/zOWffecuBNcACiuG4za6CC7i6" /></form>

    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 962, Column 207: end tag for element "FORM" which is not open
    …AgLdlqvXCQKFoc/rAwL4hq7JBgKkwKrWCwLU4tCGDK/zOWffecuBNcACiuG4za6CC7i6" /></form>

    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 963, Column 12: 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 964, Column 12: end tag for element "BODY" which is not open
    					</body>

    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 965, Column 11: end tag for element "HTML" which is not open
    				</html>

    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.

Visitor Analysis

Daily Visitor
  • 3.617 visits

In Page Analysis