burmeseclassic.com

 The Best Myanmar Website  Home  BurmeseClassic Bookshelf  Music Training Corner  Kitchen Corner  Sports Section  Monastery Directory  Myanmar Karaoke  English Version  Myanmar Calendar  Myanmar Photo Gallery  Contact Us Copyright © Burmese ... ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    burmeseclassic.com
  • Favicon
  • Alexa Rank
    #4140
  • Google Page Rank
    PR 3
  • Ip Address
    208.53.158.68
  • Page Size
    29.9 KB
  • Images
    10 GIF, 35 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    The Best Myanmar Website
  • Meta Keyword
    Myanmar Songs, Myanmar Song, Burmese Songs, Burmese Song, Myanmar Movies, Myanmar Movie, Myanmar Videos, Myanmar Video, Myanmar Tranditional Song, Free Myanmar Music, Free Myanmar Video, Burmese Classic , Myanmar Classic Song, Free Video, Burma Classic Song, Myanmar Cartoon, Dhamma Articles, Myanmar Daily News, Burmese Baydin, Free Myanmar Music VCDs, Free Myanmar Books
  • Meta Description
     The Best Myanmar Website  Home  BurmeseClassic Bookshelf  Music Training Corner  Kitchen Corner  Sports Section  Monastery Directory  Myanmar Karaoke  English Version  Myanmar Calendar  Myanmar Photo Gallery  Contact Us Copyright © Burmese ...

Technical Analysis



  • Webserver
    Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    208.53.158.68
  • Domain Age
    7 Years, 7 Months, 14 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 19 Sep 2013 06:56:37 GMT
  • server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.3.19
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for burmeseclassic.com

IP 208.53.158.68 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Bronx
  • Continent Code
    718
  • Latitude
    501
  • Longitude
    501
  • %rwhois V-1.5:003eff:00 rwhois.fdcservers.net (by Network Solutions, Inc. V-1.5.10-pre6)
    network:Auth-Area:208.53.128.0/18
    network:Class-Name:network
    network:OrgName:Burmeseclassic
    network:OrgID;I:FDC-4266
    network:Address:6612 Convict Hill
    network:City:Austin
    network:StateProv:TX
    network:PostalCode:78749
    network:Country:US
    network:NetRange:208.53.158.68 - 208.53.158.68
    network:CIDR:208.53.158.68/32
    network:NetName:FDC-4266-208.53.158.68
    network:OrgAbuseHandle:ABUSE438-ARIN
    network:OrgAbuseName:Abuse Department
    network:OrgAbusePhone:+1-312-423-6675
    network:OrgAbuseEmail:abuse@fdcservers.net
    network:OrgNOCHandle:TECHS72-ARIN
    network:OrgNOCName:Tech Support
    network:OrgNOCPhone:+1-312-423-6675
    network:OrgNOCEmail:support@fdcservers.net
    network:OrgTechHandle:TECHS72-ARIN
    network:OrgTechName:Tech Support
    network:OrgTechPhone:+1-312-423-6675
    network:OrgTechEmail:support@fdcservers.net

    %ok

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 105 Errors
  • 29 Warnings
Ratio Text/Html
  • 0.6552241728121125
Message Error
  • Warning Line 7, Column 79: NET-enabling start-tag requires SHORTTAG YES
    …ETA name="verify-v1" content="X7I3Wc1JwyUjRoc2qU1wcSYkSFZX8eQjY8SRM4kgeWM=" /> 

    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 8, Column 79: NET-enabling start-tag requires SHORTTAG YES
    …nt="f/GofX5VmbS0F5hGUb8FLrNZkDA4xde6FZFTHg4aJl0=" /> <!--for webmastertools -->

    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 8, Column 79: document type does not allow element "META" here
    …nt="f/GofX5VmbS0F5hGUb8FLrNZkDA4xde6FZFTHg4aJl0=" /> <!--for webmastertools -->

    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 10, Column 392: document type does not allow element "META" here
    …ar Daily News, Burmese Baydin, Free Myanmar Music VCDs, Free Myanmar Books">		 

    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 67: document type does not allow element "META" here
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

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

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

  • Error Line 64, Column 30: required attribute "TYPE" not specified
    <SCRIPT LANGUAGE="JavaScript">

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

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

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

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

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

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

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

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

  • Error Line 142, Column 18: there is no attribute "LEFTMARGIN"
    <body leftmargin="0" topmargin="0" rightmargin="0" bottommargin="0" class="Scro…

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

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

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

  • Error Line 142, Column 32: there is no attribute "TOPMARGIN"
    <body leftmargin="0" topmargin="0" rightmargin="0" bottommargin="0" class="Scro…

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

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

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

  • Error Line 142, Column 48: there is no attribute "RIGHTMARGIN"
    …tmargin="0" topmargin="0" rightmargin="0" bottommargin="0" class="ScrollRight"…

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

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

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

  • Error Line 142, Column 65: there is no attribute "BOTTOMMARGIN"
    …rgin="0" rightmargin="0" bottommargin="0" class="ScrollRight" ondragstart="ret…

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

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

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

  • Error Line 142, Column 101: there is no attribute "ONDRAGSTART"
    …n="0" class="ScrollRight" ondragstart="return false" onselectstart="return fal…

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

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

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

  • Error Line 142, Column 130: there is no attribute "ONSELECTSTART"
    …0" class="ScrollRight" ondragstart="return false" onselectstart="return false">

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

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

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

  • Error Line 142, Column 144: document type does not allow element "BODY" here
    …0" class="ScrollRight" ondragstart="return false" onselectstart="return false">

    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 153, Column 29: there is no attribute "HEIGHT"
      <table width="770" height="100%" border="0" cellpadding="0" cellspacing="0">

    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 160, Column 140: NET-enabling start-tag requires SHORTTAG YES
    …/header_left03.gif" width="219" height="128" border="0" usemap="#Map10" /></td>

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

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

  • Error Line 160, Column 140: required attribute "ALT" not specified
    …/header_left03.gif" width="219" height="128" border="0" usemap="#Map10" /></td>

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

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

  • Warning Line 171, Column 171: NET-enabling start-tag requires SHORTTAG YES
    …t='News Section' name='Image18' width='131' height='100' border='0' /></a></td>

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

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

  • Warning Line 172, Column 197: NET-enabling start-tag requires SHORTTAG YES
    …'Youth  Section' name='Image18' width='172' height='100' border='0' /></a></td>

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

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

  • Warning Line 195, Column 144: NET-enabling start-tag requires SHORTTAG YES
    …ok.com/burmeseclassic" target="_blank" alt="BurmeseClassic Facebook Network" />

    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 195, Column 145: character data is not allowed here
    …ok.com/burmeseclassic" target="_blank" alt="BurmeseClassic Facebook Network" />

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 196, Column 139: NET-enabling start-tag requires SHORTTAG YES
    …ter.com/BurmeseClassic" target="_blank" alt="BurmeseClassic Twitter Network" />

    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 197, Column 106: NET-enabling start-tag requires SHORTTAG YES
    …"45,73,23" href="site_map.php" target="_blank" alt="BurmeseClassic Site Map" />

    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 198, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …://www.burmeseclassic.info/index.php" target="_parent" alt="English Version" />

    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 199, Column 161: NET-enabling start-tag requires SHORTTAG YES
    …" href="http://www.burmeseclassic.com/EngVersion/index.php" target="_parent" />

    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 199, Column 161: required attribute "ALT" not specified
    …" href="http://www.burmeseclassic.com/EngVersion/index.php" target="_parent" />

    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 215, Column 232: required attribute "ALT" not specified
    …sic Training Corner</a><img src='img/new-star.gif' width='45' height='20'></td>

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

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

  • Error Line 233, Column 43: there is no attribute "HEIGHT"
                </tr>              <tr height="3">

    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 255, Column 51: cannot generate system identifier for general entity "pno"
    …n="center"><a href="mtv.php?status=go&pno=1" target="_parent"><img src="img/lm…

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

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

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

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

  • Error Line 255, Column 51: general entity "pno" not defined and no default entity
    …n="center"><a href="mtv.php?status=go&pno=1" target="_parent"><img src="img/lm…

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

  • Error Line 255, Column 54: reference to entity "pno" for which no system identifier could be generated
    …center"><a href="mtv.php?status=go&pno=1" target="_parent"><img src="img/lmenu…

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

  • Info Line 255, Column 50: entity was defined here
    …gn="center"><a href="mtv.php?status=go&pno=1" target="_parent"><img src="img/l…
  • Error Line 306, Column 112: required attribute "ALT" not specified
    …"left" valign="bottom"><img src="img/adv_top.jpg" width="210" height="37"></td>

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

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

  • Error Line 310, Column 55: there is no attribute "ONMOUSEOVER"
                    <td align="left"><marquee onmouseover=this.stop() 

    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 310, Column 64: an attribute value must be a literal unless it contains only name characters
                    <td align="left"><marquee onmouseover=this.stop() 

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

  • Error Line 311, Column 44: there is no attribute "ONMOUSEOUT"
                                    onmouseout=this.start() scrollAmount=2 

    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 311, Column 54: an attribute value must be a literal unless it contains only name characters
                                    onmouseout=this.start() scrollAmount=2 

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

  • Error Line 311, Column 70: there is no attribute "SCROLLAMOUNT"
                                    onmouseout=this.start() scrollAmount=2 

    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 312, Column 45: there is no attribute "SCROLLDELAY"
    …                          scrollDelay=70 direction=up height="145" align="left…

    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 312, Column 58: there is no attribute "DIRECTION"
    …                         scrollDelay=70 direction=up height="145" align="left">

    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 312, Column 68: there is no attribute "HEIGHT"
    …                         scrollDelay=70 direction=up height="145" align="left">

    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 312, Column 80: there is no attribute "ALIGN"
    …                         scrollDelay=70 direction=up height="145" align="left">

    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 312, Column 86: element "MARQUEE" undefined
    …                         scrollDelay=70 direction=up height="145" align="left">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 313, Column 36: an attribute value must be a literal unless it contains only name characters
                        <TABLE bgcolor=#ffffff cellSpacing=0 cellPadding=0 width=20…

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

  • Error Line 329, Column 78: there is no attribute "BACKGROUND"
    …align='left' vAlign=middle background='img/dot.gif'><a href='tayar_player.php?…

    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 329, Column 126: cannot generate system identifier for general entity "FMfile"
    …if'><a href='tayar_player.php?id=1575&FMfile=UThuMingala/UThuMingala_088.xml' …

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

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

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

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

  • Error Line 329, Column 126: general entity "FMfile" not defined and no default entity
    …if'><a href='tayar_player.php?id=1575&FMfile=UThuMingala/UThuMingala_088.xml' …

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

  • Error Line 329, Column 132: reference to entity "FMfile" for which no system identifier could be generated
    … href='tayar_player.php?id=1575&FMfile=UThuMingala/UThuMingala_088.xml' target…

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

  • Info Line 329, Column 125: entity was defined here
    …gif'><a href='tayar_player.php?id=1575&FMfile=UThuMingala/UThuMingala_088.xml'…
  • Warning Line 332, Column 114: cannot generate system identifier for general entity "d"
    …ref='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2'…

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

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

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

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

  • Error Line 332, Column 114: general entity "d" not defined and no default entity
    …ref='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2'…

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

  • Error Line 332, Column 115: reference to entity "d" for which no system identifier could be generated
    …ef='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' …

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Warning Line 332, Column 141: cannot generate system identifier for general entity "s"
    …x=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cur…

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

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

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

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

  • Error Line 332, Column 141: general entity "s" not defined and no default entity
    …x=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cur…

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

  • Error Line 332, Column 142: reference to entity "s" for which no system identifier could be generated
    …=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='curs…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Warning Line 332, Column 145: cannot generate system identifier for general entity "p"
    …U5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:…

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

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

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

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

  • Error Line 332, Column 145: general entity "p" not defined and no default entity
    …U5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:…

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

  • Error Line 332, Column 146: reference to entity "p" for which no system identifier could be generated
    …5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:h…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Warning Line 332, Column 149: cannot generate system identifier for general entity "tp"
    …==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:hand…

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

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

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

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

  • Error Line 332, Column 149: general entity "tp" not defined and no default entity
    …==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:hand…

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

  • Error Line 332, Column 151: reference to entity "tp" for which no system identifier could be generated
    …&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:hand;'…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Error Line 335, Column 107: reference to entity "d" for which no system identifier could be generated
    …f'><a href='type3.php?index=OTU5NA==&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2' …

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Error Line 335, Column 134: reference to entity "s" for which no system identifier could be generated
    …=OTU5NA==&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2' target='_blank' style='curs…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Error Line 335, Column 138: reference to entity "p" for which no system identifier could be generated
    …5NA==&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2' target='_blank' style='cursor:h…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Error Line 335, Column 143: reference to entity "tp" for which no system identifier could be generated
    …&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2' target='_blank' style='cursor:hand;'…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Error Line 338, Column 107: reference to entity "d" for which no system identifier could be generated
    …f'><a href='type3.php?index=OTU5Mw==&d=aW1nL21vdmllLzk1OTMuZ2lm&s=1&p=1&tp=2' …

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Error Line 338, Column 134: reference to entity "s" for which no system identifier could be generated
    …=OTU5Mw==&d=aW1nL21vdmllLzk1OTMuZ2lm&s=1&p=1&tp=2' target='_blank' style='curs…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Error Line 338, Column 138: reference to entity "p" for which no system identifier could be generated
    …5Mw==&d=aW1nL21vdmllLzk1OTMuZ2lm&s=1&p=1&tp=2' target='_blank' style='cursor:h…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Error Line 338, Column 143: reference to entity "tp" for which no system identifier could be generated
    …&d=aW1nL21vdmllLzk1OTMuZ2lm&s=1&p=1&tp=2' target='_blank' style='cursor:hand;'…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Error Line 341, Column 145: reference to entity "d" for which no system identifier could be generated
    …com/choice_player.php?index=OTU4Nw==&d=aW1nL21vdmllLzk1ODcuZ2lm&s=9&p=1&tp=2' …

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Error Line 341, Column 172: reference to entity "s" for which no system identifier could be generated
    …=OTU4Nw==&d=aW1nL21vdmllLzk1ODcuZ2lm&s=9&p=1&tp=2' target='_blank' style='curs…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Error Line 341, Column 176: reference to entity "p" for which no system identifier could be generated
    …4Nw==&d=aW1nL21vdmllLzk1ODcuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:h…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Error Line 341, Column 181: reference to entity "tp" for which no system identifier could be generated
    …&d=aW1nL21vdmllLzk1ODcuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:hand;'…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Error Line 344, Column 145: reference to entity "d" for which no system identifier could be generated
    …com/choice_player.php?index=OTU4Ng==&d=aW1nL21vdmllLzk1ODYuZ2lm&s=6&p=1&tp=2' …

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Error Line 344, Column 172: reference to entity "s" for which no system identifier could be generated
    …=OTU4Ng==&d=aW1nL21vdmllLzk1ODYuZ2lm&s=6&p=1&tp=2' target='_blank' style='curs…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Error Line 344, Column 176: reference to entity "p" for which no system identifier could be generated
    …4Ng==&d=aW1nL21vdmllLzk1ODYuZ2lm&s=6&p=1&tp=2' target='_blank' style='cursor:h…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Error Line 344, Column 181: reference to entity "tp" for which no system identifier could be generated
    …&d=aW1nL21vdmllLzk1ODYuZ2lm&s=6&p=1&tp=2' target='_blank' style='cursor:hand;'…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Error Line 347, Column 137: reference to entity "d" for which no system identifier could be generated
    …classic.com/type3.php?index=MTIzOTA=&d=aW1nL21vdmllLzEyMzkwLmdpZg==&s=1&p=1&tp…

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Error Line 347, Column 168: reference to entity "s" for which no system identifier could be generated
    …zOTA=&d=aW1nL21vdmllLzEyMzkwLmdpZg==&s=1&p=1&tp=2' target='_blank' style='curs…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Error Line 347, Column 172: reference to entity "p" for which no system identifier could be generated
    …=&d=aW1nL21vdmllLzEyMzkwLmdpZg==&s=1&p=1&tp=2' target='_blank' style='cursor:h…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Error Line 347, Column 177: reference to entity "tp" for which no system identifier could be generated
    …W1nL21vdmllLzEyMzkwLmdpZg==&s=1&p=1&tp=2' target='_blank' style='cursor:hand;'…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Error Line 359, Column 104: required attribute "ALT" not specified
    …t" valign="bottom"><img src="img/adv_bottom.jpg" width="210" height="37"> </td>

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

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

  • Warning Line 364, Column 84: cannot generate system identifier for general entity "A.jpg"
    …target="_parent"><img src="img/dammaQ&A.jpg" alt="Dhamma Questions and Answers…

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

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

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

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

  • Error Line 364, Column 84: general entity "A.jpg" not defined and no default entity
    …target="_parent"><img src="img/dammaQ&A.jpg" alt="Dhamma Questions and Answers…

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

  • Error Line 364, Column 89: reference to entity "A.jpg" for which no system identifier could be generated
    …t="_parent"><img src="img/dammaQ&A.jpg" alt="Dhamma Questions and Answers" wid…

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

  • Info Line 364, Column 83: entity was defined here
    … target="_parent"><img src="img/dammaQ&A.jpg" alt="Dhamma Questions and Answer…
  • Error Line 425, Column 38: there is no attribute "SRC"
    				                <td><bgsound src="song/intro.wma" /></td>

    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 425, Column 55: NET-enabling start-tag requires SHORTTAG YES
    				                <td><bgsound src="song/intro.wma" /></td>

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

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

  • Error Line 425, Column 55: element "BGSOUND" undefined
    				                <td><bgsound src="song/intro.wma" /></td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 429, Column 126: NET-enabling start-tag requires SHORTTAG YES
    …"img/pn.gif" alt="Photo News" width="210" height="132" border="0"></a><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 430, Column 146: NET-enabling start-tag requires SHORTTAG YES
    …ank'><img src="img/thingyansar.gif" alt="Thingyan Sar" border="0"></a><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 437, Column 79: an attribute specification must start with a name or name token
    … valign="top" background="background="" ><table width="100%" border="0" cellpa…

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

  • Error Line 443, Column 124: there is no attribute "BORDERCOLOR"
    …border="0" cellpadding="0" cellspacing="0" bordercolor="#FFCC33" height="100%">

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

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

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

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

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

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

  • Warning Line 484, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …link rel="stylesheet" type="text/css" href="image_rotator/css/sliderman.css" />

    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 484, Column 80: document type does not allow element "LINK" here
    …link rel="stylesheet" type="text/css" href="image_rotator/css/sliderman.css" />

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

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

  • Warning Line 496, Column 74: NET-enabling start-tag requires SHORTTAG YES
                        <img src="img/HtaMaNe_1.gif" width="728" height="135"/>

    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 496, Column 74: required attribute "ALT" not specified
                        <img src="img/HtaMaNe_1.gif" width="728" height="135"/>

    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 498, Column 71: NET-enabling start-tag requires SHORTTAG YES
                    	<img src="img/htamanal2.jpg" width="728" height="135"/>

    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 498, Column 71: required attribute "ALT" not specified
                    	<img src="img/htamanal2.jpg" width="728" height="135"/>

    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 499, Column 71: NET-enabling start-tag requires SHORTTAG YES
                    	<img src="img/htamanal1.gif" width="728" height="135"/>

    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 71: required attribute "ALT" not specified
                    	<img src="img/htamanal1.gif" width="728" height="135"/>

    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 500, Column 75: NET-enabling start-tag requires SHORTTAG YES
              			<img src="img/tayar_alotawpyae1.gif" width="728" height="135"/>

    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 500, Column 75: required attribute "ALT" not specified
              			<img src="img/tayar_alotawpyae1.gif" width="728" height="135"/>

    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 559, Column 62: NET-enabling start-tag requires SHORTTAG YES
    <tr><td width="728"><img src="img/PaRaHiTa_1.jpg" border="0" /></td>

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

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

  • Error Line 559, Column 62: required attribute "ALT" not specified
    <tr><td width="728"><img src="img/PaRaHiTa_1.jpg" border="0" /></td>

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

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

  • Error Line 565, Column 96: there is no attribute "BORDER"
    …_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal - The safe…

    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 569, Column 107: NET-enabling start-tag requires SHORTTAG YES
    …list.php" target="_parent"><img src="img/PaRaHiTa_3.jpg" border="0" /></a></td>

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

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

  • Error Line 569, Column 107: required attribute "ALT" not specified
    …list.php" target="_parent"><img src="img/PaRaHiTa_3.jpg" border="0" /></a></td>

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

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

  • Error Line 579, Column 91: reference to entity "d" for which no system identifier could be generated
    …com/choice_player.php?index=OTU5NA==&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2" …

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

  • Info Line 332, Column 113: entity was defined here
    …href='choice_player.php?index=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2…
  • Error Line 579, Column 118: reference to entity "s" for which no system identifier could be generated
    …=OTU5NA==&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2" target="_blank"><img src="i…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Error Line 579, Column 122: reference to entity "p" for which no system identifier could be generated
    …5NA==&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2" target="_blank"><img src="img/m…

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

  • Info Line 332, Column 144: entity was defined here
    …TU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor…
  • Error Line 579, Column 127: reference to entity "tp" for which no system identifier could be generated
    …&d=aW1nL21vdmllLzk1OTQuZ2lm&s=6&p=1&tp=2" target="_blank"><img src="img/movie/…

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

  • Info Line 332, Column 148: entity was defined here
    …Q==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cursor:han…
  • Warning Line 579, Column 241: NET-enabling start-tag requires SHORTTAG YES
    …preview.jpg" alt="Special Film" width="280" height="280" border="0" /></a></td>

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

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

  • Warning Line 580, Column 107: NET-enabling start-tag requires SHORTTAG YES
    …p"><img src="img/more_movie.jpg" width="37" height="280" border="0" /></a></td>

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

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

  • Error Line 580, Column 107: required attribute "ALT" not specified
    …p"><img src="img/more_movie.jpg" width="37" height="280" border="0" /></a></td>

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

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

  • Error Line 606, Column 72: start tag for "TR" omitted, but its declaration does not permit this
    				        <td align="center" valign="bottom" background="img/dot.gif">
  • Error Line 614, Column 101: end tag for element "IMG" which is not open
    …gle.com/logos/Logo_25wht.gif" border="0" alt="Google" align="middle"></img></a>

    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 617, Column 77: end tag for element "INPUT" which is not open
      <input type="hidden" name="domains" value="www.burmeseclassic.com"></input>

    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 619, Column 82: end tag for element "INPUT" which is not open
    …input type="text" name="q" size="31" maxlength="255" value="" id="sbi"></input>

    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 621, Column 65: end tag for element "INPUT" which is not open
      <input type="submit" name="sa" value="Search" id="sbb"></input></td></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 628, Column 74: end tag for element "INPUT" which is not open
      <input type="radio" name="sitesearch" value="" checked id="ss0"></input>

    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 631, Column 88: end tag for element "INPUT" which is not open
    …type="radio" name="sitesearch" value="www.burmeseclassic.com" id="ss1"></input>

    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 635, Column 74: end tag for element "INPUT" which is not open
      <input type="hidden" name="client" value="pub-6632991616655797"></input>

    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 636, Column 54: end tag for element "INPUT" which is not open
      <input type="hidden" name="forid" value="1"></input>

    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 637, Column 65: end tag for element "INPUT" which is not open
      <input type="hidden" name="channel" value="9285738927"></input>

    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 638, Column 55: end tag for element "INPUT" which is not open
      <input type="hidden" name="ie" value="UTF-8"></input>

    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 639, Column 55: end tag for element "INPUT" which is not open
      <input type="hidden" name="oe" value="UTF-8"></input>

    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 640, Column 187: end tag for element "INPUT" which is not open
    …336699;ALC:0000FF;LC:0000FF;T:000000;GFNT:0000FF;GIMP:0000FF;FORID:11"></input>

    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 641, Column 52: end tag for element "INPUT" which is not open
      <input type="hidden" name="hl" value="en"></input></td></tr></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 651, Column 39: reference to entity "pno" for which no system identifier could be generated
    				    <a href="mtv.php?status=go&pno=1" target="_parent"> <img src="img/cover…

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

  • Info Line 255, Column 50: entity was defined here
    …gn="center"><a href="mtv.php?status=go&pno=1" target="_parent"><img src="img/l…
  • Error Line 651, Column 128: required attribute "ALT" not specified
    …src="img/covers/S0523.jpg" width="728" height="112" border="0"></a></span></td>

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

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

  • Error Line 669, Column 123: document type does not allow element "STYLE" here
    …"middle" background="img/bottom.jpg" bgcolor="#003366" ><style type="text/css">

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

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

  • Error Line 706, Column 66: reference to entity "s" for which no system identifier could be generated
    …218,347,325,374" href="show2.php?id=&s=&tc=&FMfile=15Nargis_UDhammaPYa.xml" ta…

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

  • Info Line 332, Column 140: entity was defined here
    …ex=OTU5NQ==&d=aW1nL21vdmllLzk1OTUuZ2lm&s=9&p=1&tp=2' target='_blank' style='cu…
  • Warning Line 706, Column 68: cannot generate system identifier for general entity "tc"
    …8,347,325,374" href="show2.php?id=&s=&tc=&FMfile=15Nargis_UDhammaPYa.xml" targ…

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

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

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

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

  • Error Line 706, Column 68: general entity "tc" not defined and no default entity
    …8,347,325,374" href="show2.php?id=&s=&tc=&FMfile=15Nargis_UDhammaPYa.xml" targ…

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

  • Error Line 706, Column 70: reference to entity "tc" for which no system identifier could be generated
    …347,325,374" href="show2.php?id=&s=&tc=&FMfile=15Nargis_UDhammaPYa.xml" target…

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

  • Info Line 706, Column 67: entity was defined here
    …18,347,325,374" href="show2.php?id=&s=&tc=&FMfile=15Nargis_UDhammaPYa.xml" tar…
  • Error Line 706, Column 78: reference to entity "FMfile" for which no system identifier could be generated
    …374" href="show2.php?id=&s=&tc=&FMfile=15Nargis_UDhammaPYa.xml" target="_paren…

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

  • Info Line 329, Column 125: entity was defined here
    …gif'><a href='tayar_player.php?id=1575&FMfile=UThuMingala/UThuMingala_088.xml'…

Visitor Analysis

Daily Visitor
  • 38.500 visits

In Page Analysis