icehotpix.com 2012 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither the service provider nor the domain owner maintain any relationship with the advertisers. In ...

icehotpix.com
  • Domain Name
    icehotpix.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #56084
  • Page Size
    5.8 KB
  • Ip Address
    62.116.143.17
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    icehotpix.com
  • Meta Keyword
  • Meta Description
    icehotpix.com 2012 Copyright. All Rights Reserved. The Sponsored Listings displayed above are served automatically by a third party. Neither the service provider nor the domain owner maintain any relationship with the advertisers. In case of ...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    62.116.143.17
  • Domain Age
    1 Years, 6 Months, 3 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 04 Sep 2013 15:00:00 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-check: 3c12dc4d54f8e22d666785b733b0052100c53444
  • x-language: english
  • x-template: tpl_CleanPeppermintCaf4Ads5_twoclick
  • x-buckets: bucket074
  • x-adblock-key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_Hc3zYsBExQfvFjEQKYLSxe4q13hD1xIBYzd+aKCI3OslWIk0RJatOVnvVRlsR6brtBk7YIrNKMpUXlt0hFgSSw==
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for icehotpix.com

DNS Analysis


DNS servers
ns-uk.topdns.com
ns-canada.topdns.com
ns-usa.topdns.com


DNS Records

Answer records
icehotpix.com SOA
server: ns-uk.topdns.com
email: hostmaster@topdns.com
serial: 2012081804
refresh: 172800
retry: 900
expire: 1209600
minimum ttl: 3600
7200s
icehotpix.com NS  ns-uk.topdns.com 3600s
icehotpix.com NS  ns-canada.topdns.com 3600s
icehotpix.com NS  ns-usa.topdns.com 3600s
icehotpix.com A 69.60.116.111 3600s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 13 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.29630249288940935
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <HTML><HEAD><base target=_blank>

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

  • Error Line 3, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Warning Line 12, Column 17: NET-enabling start-tag requires SHORTTAG YES
    <STYLE type=text/css>BODY {

    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 58, Column 28: 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 67, Column 57: an attribute value must be a literal unless it contains only name characters
    <TABLE cellSpacing=0 cellPadding=0 width="100%" bgColor=#222222 border=0>

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

  • Error Line 72, Column 17: there is no attribute "BORDER"
    		<TBODY border=1>

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

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

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

  • Error Line 76, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=MOST_VIEW…

    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 77, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=TOP_RATED…

    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 78, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=CATEGORIE…

    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 79, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=CHANNELS"…

    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 80, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=MY_FAVORI…

    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 81, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=LIVE SEX"…

    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 82, Column 142: document type does not allow element "TD" here
    …olorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=TEEN_PHOT…

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

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

  • Info Line 82, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=TEEN_PHOTO…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 81, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=LIVE SEX">…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 80, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=MY_FAVORIT…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 79, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=CHANNELS">…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 78, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=CATEGORIES…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 77, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=TOP_RATED"…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 76, Column 143: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=MOST_VIEWE…
  • Error Line 83, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    		  </TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 75, Column 149: start tag was here
    …lorstr='#777777',gradientType='0'); "><center><a href="../out.php?l=HOME"><fon…
  • Error Line 91, Column 58: an attribute value must be a literal unless it contains only name characters
     <TABLE cellSpacing=0 cellPadding=0 width="100%" bgColor=#333333 border=0>

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

  • Error Line 98, Column 17: an attribute value must be a literal unless it contains only name characters
    				<td width=20% style=" filter:progid:DXImageTransform.Microsoft.Gradient(end…

    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 100, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 101, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 102, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 103, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 104, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 105, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 106, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 107, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 108, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 109, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 110, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 111, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 112, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 113, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 114, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 115, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 116, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 117, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 118, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 119, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 120, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 121, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 122, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 123, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 124, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 125, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 126, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 127, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 128, Column 18: required attribute "ALT" not specified
    <img src=logo.gif>

    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 129, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 130, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 131, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 132, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 133, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 134, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 135, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 136, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 137, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 138, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 139, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 140, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 141, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 142, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 143, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 144, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 145, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 146, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 147, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 148, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 149, Column 89: an attribute value must be a literal unless it contains only name characters
    …teenfgalleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A>

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

  • Error Line 150, Column 89: an attribute value must be a literal unless it contains only name characters
    …galleriesx.com/school/index.html"><font size=-5 color=#333333>.</font></A></td>

    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 154, Column 19: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
            <TR align=middle>

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

  • Error Line 158, Column 4: document type does not allow element "TD" here; assuming missing "TR" start-tag
    <td><font size=1>1</font></td>
  • Warning Line 159, Column 46: cannot generate system identifier for general entity "l"
    …<a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='http…

    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 159, Column 46: general entity "l" not defined and no default entity
    …<a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='http…

    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 159, Column 47: reference to entity "l" for which no system identifier could be generated
    …a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 161, Column 49: reference to entity "l" for which no system identifier could be generated
    …href='out.php?perm=sexystarstube.com&l=top2' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 163, Column 43: reference to entity "l" for which no system identifier could be generated
    …<b><a href='out.php?perm=pornska.com&l=top3' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 166, Column 45: reference to entity "l" for which no system identifier could be generated
    …><a href='out.php?perm=armedtube.com&l=top4' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 168, Column 43: reference to entity "l" for which no system identifier could be generated
    …<b><a href='out.php?perm=wetsolo.com&l=top5' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 170, Column 47: reference to entity "l" for which no system identifier could be generated
    …a href='out.php?perm=diamond-tgp.com&l=top6' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 173, Column 43: reference to entity "l" for which no system identifier could be generated
    …<b><a href='out.php?perm=pornteen.us&l=top7' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 175, Column 49: reference to entity "l" for which no system identifier could be generated
    …href='out.php?perm=goldhomevideo.com&l=top8' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 177, Column 42: reference to entity "l" for which no system identifier could be generated
    …><b><a href='out.php?perm=sexgaz.com&l=top9' ONMOUSEOVER="window.status='http:…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 180, Column 42: reference to entity "l" for which no system identifier could be generated
    …><b><a href='out.php?perm=mary18.net&l=top10' ONMOUSEOVER="window.status='http…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 182, Column 55: reference to entity "l" for which no system identifier could be generated
    …out.php?perm=prettyamateursgirls.com&l=top11' ONMOUSEOVER="window.status='http…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 184, Column 48: reference to entity "l" for which no system identifier could be generated
    … href='out.php?perm=gargonaxtube.net&l=top12' ONMOUSEOVER="window.status='http…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 187, Column 46: reference to entity "l" for which no system identifier could be generated
    …<a href='out.php?perm=secret-xxx.com&l=top13' ONMOUSEOVER="window.status='http…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 189, Column 48: reference to entity "l" for which no system identifier could be generated
    … href='out.php?perm=galleries100.com&l=top14' ONMOUSEOVER="window.status='http…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 191, Column 47: reference to entity "l" for which no system identifier could be generated
    …a href='out.php?perm=youcamehere.com&l=top15' ONMOUSEOVER="window.status='http…

    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 159, Column 45: entity was defined here
    …><a href='out.php?perm=teenofalbum.com&l=top1' ONMOUSEOVER="window.status='htt…
  • Error Line 205, Column 36: there is no attribute "BORDERCOLOR"
    			<TABLE width="100%" borderColor=#222222 align=center bgColor=#000000 cellSpa…

    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 205, Column 36: an attribute value must be a literal unless it contains only name characters
    			<TABLE width="100%" borderColor=#222222 align=center bgColor=#000000 cellSpa…

    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 205, Column 65: an attribute value must be a literal unless it contains only name characters
    …" borderColor=#222222 align=center bgColor=#000000 cellSpacing=0 cellPadding=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 207, Column 177: an attribute value must be a literal unless it contains only name characters
    …Span=3><FONT face=Verdana size=4 color=#ffffff>Videos Being Watched</FONT></TD>

    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 214, Column 23: an attribute value must be a literal unless it contains only name characters
    			<TABLE borderColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellP…

    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 214, Column 52: an attribute value must be a literal unless it contains only name characters
    …derColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellPadding=5 bor…

    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 216, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…

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

  • Warning Line 216, Column 61: cannot generate system identifier for general entity "link"
    …00><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http:…

    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 216, Column 61: general entity "link" not defined and no default entity
    …00><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http:…

    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 216, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Warning Line 216, Column 71: cannot generate system identifier for general entity "gr"
    …><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.…

    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 216, Column 71: general entity "gr" not defined and no default entity
    …><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.…

    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 216, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Warning Line 216, Column 76: cannot generate system identifier for general entity "id"
    …ref="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.3…

    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 216, Column 76: general entity "id" not defined and no default entity
    …ref="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.3…

    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 216, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 216, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.34/sxs/tube_2/507.jpeg wid…

    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 216, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.34/sxs/tube_2/507.jpeg wid…

    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 216, Column 165: document type does not allow element "A" here
    …2/507.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 216, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">11:59</td><td><img …

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

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

  • Error Line 216, Column 247: required attribute "ALT" not specified
    …"60%">11:59</td><td><img src=small.gif></td></tr><tr><td>1 year ago</td><td>45…

    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 216, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>1 year ago</td><td>4534 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 216, Column 163: start tag was here
    …e_2/507.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 216, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>1 year ago</td><td>4534 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 216, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 216, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>1 year ago</td><td>4534 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 216, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 217, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…

    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 217, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=ee3eac"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 217, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=ee3eac"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 217, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=ee3eac"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 217, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=ee3eac"><img src=http://190.120.228.34/sxs/tube_2/732.jpeg wid…

    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 217, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=ee3eac"><img src=http://190.120.228.34/sxs/tube_2/732.jpeg wid…

    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 217, Column 165: document type does not allow element "A" here
    …2/732.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 217, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">10:38</td><td><img …

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

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

  • Error Line 217, Column 247: required attribute "ALT" not specified
    …"60%">10:38</td><td><img src=small.gif></td></tr><tr><td>2 weeks ago</td><td>4…

    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 217, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>2 weeks ago</td><td>4334 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 217, Column 163: start tag was here
    …e_2/732.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 217, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>2 weeks ago</td><td>4334 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 217, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 217, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>2 weeks ago</td><td>4334 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 217, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 218, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…

    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 218, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=e43008"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 218, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=e43008"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 218, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=e43008"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 218, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=e43008"><img src=http://190.120.228.34/sxs/tube_2/968.jpeg wid…

    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 218, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=e43008"><img src=http://190.120.228.34/sxs/tube_2/968.jpeg wid…

    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 218, Column 165: document type does not allow element "A" here
    …2/968.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 218, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:38</td><td><img …

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

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

  • Error Line 218, Column 247: required attribute "ALT" not specified
    …"60%">09:38</td><td><img src=small.gif></td></tr><tr><td>6 months ago</td><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 218, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>6 months ago</td><td>563 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 218, Column 163: start tag was here
    …e_2/968.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 218, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>6 months ago</td><td>563 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 218, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 218, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>6 months ago</td><td>563 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 218, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 219, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…

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

  • Error Line 219, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=de47ae"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 219, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=de47ae"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 219, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=de47ae"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 219, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=de47ae"><img src=http://190.120.228.34/sxs/tube_2/568.jpeg wid…

    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 219, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=de47ae"><img src=http://190.120.228.34/sxs/tube_2/568.jpeg wid…

    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 219, Column 165: document type does not allow element "A" here
    …2/568.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 219, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">07:29</td><td><img …

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

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

  • Error Line 219, Column 248: required attribute "ALT" not specified
    …60%">07:29</td><td><img src=small2.gif></td></tr><tr><td>1 year ago</td><td>74…

    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 219, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>745 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 219, Column 163: start tag was here
    …e_2/568.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 219, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>745 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 219, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 219, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>745 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 219, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 220, Column 10: end tag for "TABLE" omitted, but its declaration does not permit this
    					</TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 214, Column 4: start tag was here
    			<TABLE borderColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellP…
  • Error Line 223, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…

    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 223, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=bd72d5"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 223, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=bd72d5"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 223, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=bd72d5"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 223, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=bd72d5"><img src=http://190.120.228.34/sxs/tube_2/812.jpeg wid…

    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 223, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=bd72d5"><img src=http://190.120.228.34/sxs/tube_2/812.jpeg wid…

    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 223, Column 165: document type does not allow element "A" here
    …2/812.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 223, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">04:24</td><td><img …

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

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

  • Error Line 223, Column 247: required attribute "ALT" not specified
    …"60%">04:24</td><td><img src=small.gif></td></tr><tr><td>1 weeks ago</td><td>3…

    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 223, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>1 weeks ago</td><td>3567 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 223, Column 163: start tag was here
    …e_2/812.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 223, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>1 weeks ago</td><td>3567 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 223, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 223, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>1 weeks ago</td><td>3567 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 223, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 224, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…

    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 224, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=b4442d"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 224, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=b4442d"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 224, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=b4442d"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 224, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=b4442d"><img src=http://190.120.228.34/sxs/tube_2/683.jpeg wid…

    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 224, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=b4442d"><img src=http://190.120.228.34/sxs/tube_2/683.jpeg wid…

    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 224, Column 165: document type does not allow element "A" here
    …2/683.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 224, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:36</td><td><img …

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

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

  • Error Line 224, Column 248: required attribute "ALT" not specified
    …60%">09:36</td><td><img src=small2.gif></td></tr><tr><td>1 months ago</td><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 224, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>1 months ago</td><td>357 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 224, Column 163: start tag was here
    …e_2/683.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 224, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>1 months ago</td><td>357 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 224, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 224, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>1 months ago</td><td>357 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 224, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 225, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…

    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 225, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=4fbd74"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 225, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=4fbd74"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 225, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=4fbd74"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 225, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=4fbd74"><img src=http://190.120.228.34/sxs/tube_2/725.jpeg wid…

    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 225, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=4fbd74"><img src=http://190.120.228.34/sxs/tube_2/725.jpeg wid…

    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 225, Column 165: document type does not allow element "A" here
    …2/725.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 225, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:35</td><td><img …

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

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

  • Error Line 225, Column 248: required attribute "ALT" not specified
    …60%">02:35</td><td><img src=small2.gif></td></tr><tr><td>1 year ago</td><td>68…

    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 225, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>684 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 225, Column 163: start tag was here
    …e_2/725.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 225, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>684 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 225, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…
  • Error Line 225, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>684 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 225, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…
  • Error Line 226, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…

    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 226, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=d11b16"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 226, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=d11b16"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 226, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=d11b16"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 226, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=d11b16"><img src=http://190.120.228.34/sxs/tube_2/598.jpeg wid…

    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 226, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=d11b16"><img src=http://190.120.228.34/sxs/tube_2/598.jpeg wid…

    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 226, Column 165: document type does not allow element "A" here
    …2/598.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 226, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">08:18</td><td><img …

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

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

  • Error Line 226, Column 247: required attribute "ALT" not specified
    …"60%">08:18</td><td><img src=small.gif></td></tr><tr><td>9 minutes ago</td><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 226, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>9 minutes ago</td><td>3457 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 226, Column 163: start tag was here
    …e_2/598.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 226, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>9 minutes ago</td><td>3457 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 226, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 226, Column 320: end tag for "CENTER" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>9 minutes ago</td><td>3457 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 226, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 229, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…

    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 229, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=37faa7"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 229, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=37faa7"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 229, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=37faa7"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 229, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=37faa7"><img src=http://190.120.228.34/sxs/tube_2/658.jpeg wid…

    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 229, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=37faa7"><img src=http://190.120.228.34/sxs/tube_2/658.jpeg wid…

    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 229, Column 165: document type does not allow element "A" here
    …2/658.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 229, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">11:05</td><td><img …

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

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

  • Error Line 229, Column 248: required attribute "ALT" not specified
    …60%">11:05</td><td><img src=small2.gif></td></tr><tr><td>1 year ago</td><td>34…

    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 229, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>347 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 229, Column 163: start tag was here
    …e_2/658.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 229, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>347 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 229, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 229, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall2.gif></td></tr><tr><td>1 year ago</td><td>347 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 229, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 230, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…

    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 230, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=b940b7"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 230, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=b940b7"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 230, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=b940b7"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 230, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=b940b7"><img src=http://190.120.228.34/sxs/tube_2/1060.jpeg wi…

    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 230, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=b940b7"><img src=http://190.120.228.34/sxs/tube_2/1060.jpeg wi…

    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 230, Column 166: document type does not allow element "A" here
    …/1060.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 230, Column 195: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">13:35</td><td><img …

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

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

  • Error Line 230, Column 248: required attribute "ALT" not specified
    …"60%">13:35</td><td><img src=small.gif></td></tr><tr><td>6 minutes ago</td><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 230, Column 321: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>6 minutes ago</td><td>8545 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 230, Column 164: start tag was here
    …_2/1060.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 230, Column 321: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>6 minutes ago</td><td>8545 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 230, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 230, Column 321: end tag for "CENTER" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>6 minutes ago</td><td>8545 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 230, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 231, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…

    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 231, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=33aa10"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 231, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=33aa10"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 231, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=33aa10"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 231, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=33aa10"><img src=http://190.120.228.34/sxs/tube_2/643.jpeg wid…

    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 231, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=33aa10"><img src=http://190.120.228.34/sxs/tube_2/643.jpeg wid…

    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 231, Column 165: document type does not allow element "A" here
    …2/643.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 231, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:51</td><td><img …

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

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

  • Error Line 231, Column 247: required attribute "ALT" not specified
    …"60%">09:51</td><td><img src=small.gif></td></tr><tr><td>2 months ago</td><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 231, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll.gif></td></tr><tr><td>2 months ago</td><td>9345 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 231, Column 163: start tag was here
    …e_2/643.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 231, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll.gif></td></tr><tr><td>2 months ago</td><td>9345 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 231, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 231, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll.gif></td></tr><tr><td>2 months ago</td><td>9345 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 231, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 232, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=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 232, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=22c02e"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 232, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=22c02e"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 232, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=22c02e"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 232, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=22c02e"><img src=http://190.120.228.34/sxs/tube_2/804.jpeg wid…

    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 232, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=22c02e"><img src=http://190.120.228.34/sxs/tube_2/804.jpeg wid…

    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 232, Column 165: document type does not allow element "A" here
    …2/804.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 232, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">08:17</td><td><img …

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

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

  • Error Line 232, Column 248: required attribute "ALT" not specified
    …60%">08:17</td><td><img src=small3.gif></td></tr><tr><td>3 weeks ago</td><td>3…

    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 232, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>3 weeks ago</td><td>3245 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 232, Column 163: start tag was here
    …e_2/804.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 232, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>3 weeks ago</td><td>3245 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 232, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 232, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>3 weeks ago</td><td>3245 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 232, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 235, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…

    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 235, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=f8243d"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 235, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=f8243d"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 235, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=f8243d"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 235, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=f8243d"><img src=http://190.120.228.34/sxs/tube_2/822.jpeg wid…

    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 235, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=f8243d"><img src=http://190.120.228.34/sxs/tube_2/822.jpeg wid…

    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 235, Column 165: document type does not allow element "A" here
    …2/822.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 235, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">04:29</td><td><img …

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

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

  • Error Line 235, Column 248: required attribute "ALT" not specified
    …60%">04:29</td><td><img src=small3.gif></td></tr><tr><td>3 weeks ago</td><td>9…

    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 235, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>3 weeks ago</td><td>9154 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 235, Column 163: start tag was here
    …e_2/822.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 235, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>3 weeks ago</td><td>9154 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 235, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 235, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>3 weeks ago</td><td>9154 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 235, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 236, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=6…

    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 236, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=67301b"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 236, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=67301b"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 236, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=67301b"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 236, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=67301b"><img src=http://190.120.228.34/sxs/tube_2/1008.jpeg wi…

    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 236, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=67301b"><img src=http://190.120.228.34/sxs/tube_2/1008.jpeg wi…

    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 236, Column 166: document type does not allow element "A" here
    …/1008.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 236, Column 195: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:09</td><td><img …

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

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

  • Error Line 236, Column 248: required attribute "ALT" not specified
    …"60%">02:09</td><td><img src=small.gif></td></tr><tr><td>11 months ago</td><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 236, Column 321: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>11 months ago</td><td>1734 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 236, Column 164: start tag was here
    …_2/1008.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 236, Column 321: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>11 months ago</td><td>1734 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 236, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=6…
  • Error Line 236, Column 321: end tag for "CENTER" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>11 months ago</td><td>1734 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 236, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=6…
  • Error Line 237, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=6…

    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 237, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=69662a"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 237, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=69662a"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 237, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=69662a"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 237, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=69662a"><img src=http://190.120.228.34/sxs/tube_2/820.jpeg wid…

    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 237, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=69662a"><img src=http://190.120.228.34/sxs/tube_2/820.jpeg wid…

    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 237, Column 165: document type does not allow element "A" here
    …2/820.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 237, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:16</td><td><img …

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

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

  • Error Line 237, Column 248: required attribute "ALT" not specified
    …60%">09:16</td><td><img src=small2.gif></td></tr><tr><td>1 year ago</td><td>34…

    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 237, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>1 year ago</td><td>3458 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 237, Column 163: start tag was here
    …e_2/820.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 237, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>1 year ago</td><td>3458 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 237, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=6…
  • Error Line 237, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>1 year ago</td><td>3458 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 237, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=6…
  • Error Line 238, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=9…

    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 238, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=979857"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 238, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=979857"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 238, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=979857"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 238, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=979857"><img src=http://190.120.228.34/sxs/tube_2/1129.jpeg wi…

    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 238, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=979857"><img src=http://190.120.228.34/sxs/tube_2/1129.jpeg wi…

    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 238, Column 166: document type does not allow element "A" here
    …/1129.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 238, Column 195: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">06:19</td><td><img …

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

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

  • Error Line 238, Column 249: required attribute "ALT" not specified
    …60%">06:19</td><td><img src=small2.gif></td></tr><tr><td>6 months ago</td><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 238, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>6 months ago</td><td>289 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 238, Column 164: start tag was here
    …_2/1129.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 238, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>6 months ago</td><td>289 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 238, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=9…
  • Error Line 238, Column 320: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>6 months ago</td><td>289 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 238, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=9…
  • Error Line 239, Column 10: end tag for element "TD" which is not open
    					</TD>

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

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

  • Error Line 242, Column 7: end tag for element "TD" which is not open
    		</TD>

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

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

  • Error Line 243, Column 6: end tag for element "TR" which is not open
    	</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 244, Column 8: end tag for element "TABLE" which is not open
    </TABLE>

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

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

  • Error Line 249, Column 36: an attribute value must be a literal unless it contains only name characters
    			<TABLE width="100%" borderColor=#222222 align=center bgColor=#000000 cellSpa…

    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 249, Column 65: an attribute value must be a literal unless it contains only name characters
    …" borderColor=#222222 align=center bgColor=#000000 cellSpacing=0 cellPadding=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 251, Column 177: an attribute value must be a literal unless it contains only name characters
    …'); " colSpan=3><FONT face=Verdana size=4 color=#ffffff>Our Friends</FONT></TD>

    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 258, Column 23: an attribute value must be a literal unless it contains only name characters
    			<TABLE borderColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellP…

    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 258, Column 52: an attribute value must be a literal unless it contains only name characters
    …derColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellPadding=5 bor…

    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 260, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=c…

    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 260, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=c796e5"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 260, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=c796e5"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 260, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=c796e5"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 260, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=c796e5"><img src=http://190.120.228.34/sxs/tube_2/747.jpeg wid…

    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 260, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=c796e5"><img src=http://190.120.228.34/sxs/tube_2/747.jpeg wid…

    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 260, Column 165: document type does not allow element "A" here
    …2/747.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 260, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">08:10</td><td><img …

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

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

  • Error Line 260, Column 247: required attribute "ALT" not specified
    …"60%">08:10</td><td><img src=small.gif></td></tr><tr><td>3 weeks ago</td><td>8…

    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 260, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>3 weeks ago</td><td>845 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 260, Column 163: start tag was here
    …e_2/747.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 260, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>3 weeks ago</td><td>845 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 260, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=c…
  • Error Line 260, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>3 weeks ago</td><td>845 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 260, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=c…
  • Error Line 261, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…

    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 261, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=434ff7"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 261, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=434ff7"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 261, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=434ff7"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 261, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=434ff7"><img src=http://190.120.228.34/sxs/tube_2/880.jpeg wid…

    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 261, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=434ff7"><img src=http://190.120.228.34/sxs/tube_2/880.jpeg wid…

    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 261, Column 165: document type does not allow element "A" here
    …2/880.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 261, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">05:25</td><td><img …

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

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

  • Error Line 261, Column 248: required attribute "ALT" not specified
    …60%">05:25</td><td><img src=small2.gif></td></tr><tr><td>2 minutes ago</td><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 261, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …l2.gif></td></tr><tr><td>2 minutes ago</td><td>674 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 261, Column 163: start tag was here
    …e_2/880.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 261, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …l2.gif></td></tr><tr><td>2 minutes ago</td><td>674 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 261, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…
  • Error Line 261, Column 320: end tag for "CENTER" omitted, but its declaration does not permit this
    …l2.gif></td></tr><tr><td>2 minutes ago</td><td>674 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 261, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…
  • Error Line 262, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…

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

  • Error Line 262, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=010c39"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 262, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=010c39"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 262, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=010c39"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 262, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=010c39"><img src=http://190.120.228.34/sxs/tube_2/552.jpeg wid…

    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 262, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=010c39"><img src=http://190.120.228.34/sxs/tube_2/552.jpeg wid…

    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 262, Column 165: document type does not allow element "A" here
    …2/552.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 262, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">13:25</td><td><img …

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

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

  • Error Line 262, Column 247: required attribute "ALT" not specified
    …"60%">13:25</td><td><img src=small.gif></td></tr><tr><td>1 year ago</td><td>65…

    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 262, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>1 year ago</td><td>6537 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 262, Column 163: start tag was here
    …e_2/552.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 262, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>1 year ago</td><td>6537 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 262, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 262, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>1 year ago</td><td>6537 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 262, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 263, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…

    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 263, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=83235d"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 263, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=83235d"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 263, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=83235d"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 263, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=83235d"><img src=http://190.120.228.34/sxs/tube_2/666.jpeg wid…

    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 263, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=83235d"><img src=http://190.120.228.34/sxs/tube_2/666.jpeg wid…

    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 263, Column 165: document type does not allow element "A" here
    …2/666.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 263, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">03:34</td><td><img …

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

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

  • Error Line 263, Column 248: required attribute "ALT" not specified
    …60%">03:34</td><td><img src=small2.gif></td></tr><tr><td>1 weeks ago</td><td>8…

    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 263, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>1 weeks ago</td><td>836 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 263, Column 163: start tag was here
    …e_2/666.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 263, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>1 weeks ago</td><td>836 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 263, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 263, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>1 weeks ago</td><td>836 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 263, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 266, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…

    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 266, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=47c284"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 266, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=47c284"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 266, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=47c284"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 266, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=47c284"><img src=http://190.120.228.34/sxs/tube_2/592.jpeg wid…

    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 266, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=47c284"><img src=http://190.120.228.34/sxs/tube_2/592.jpeg wid…

    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 266, Column 165: document type does not allow element "A" here
    …2/592.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 266, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">10:48</td><td><img …

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

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

  • Error Line 266, Column 247: required attribute "ALT" not specified
    …"60%">10:48</td><td><img src=small.gif></td></tr><tr><td>3 months ago</td><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 266, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>3 months ago</td><td>346 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 266, Column 163: start tag was here
    …e_2/592.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 266, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>3 months ago</td><td>346 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 266, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…
  • Error Line 266, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>3 months ago</td><td>346 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 266, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=4…
  • Error Line 267, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…

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

  • Error Line 267, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=a684d5"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 267, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=a684d5"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 267, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=a684d5"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 267, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=a684d5"><img src=http://190.120.228.34/sxs/tube_2/1062.jpeg wi…

    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 267, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=a684d5"><img src=http://190.120.228.34/sxs/tube_2/1062.jpeg wi…

    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 267, Column 166: document type does not allow element "A" here
    …/1062.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 267, Column 195: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">07:27</td><td><img …

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

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

  • Error Line 267, Column 249: required attribute "ALT" not specified
    …60%">07:27</td><td><img src=small3.gif></td></tr><tr><td>17 minutes ago</td><t…

    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 267, Column 322: end tag for "A" omitted, but its declaration does not permit this
    …3.gif></td></tr><tr><td>17 minutes ago</td><td>856 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 267, Column 164: start tag was here
    …_2/1062.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 267, Column 322: end tag for "A" omitted, but its declaration does not permit this
    …3.gif></td></tr><tr><td>17 minutes ago</td><td>856 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 267, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…
  • Error Line 267, Column 322: end tag for "CENTER" omitted, but its declaration does not permit this
    …3.gif></td></tr><tr><td>17 minutes ago</td><td>856 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 267, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…
  • Error Line 268, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…

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

  • Error Line 268, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=0aa69e"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 268, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=0aa69e"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 268, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=0aa69e"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 268, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=0aa69e"><img src=http://190.120.228.34/sxs/tube_2/782.jpeg wid…

    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 268, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=0aa69e"><img src=http://190.120.228.34/sxs/tube_2/782.jpeg wid…

    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 268, Column 165: document type does not allow element "A" here
    …2/782.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 268, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">01:52</td><td><img …

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

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

  • Error Line 268, Column 247: required attribute "ALT" not specified
    …"60%">01:52</td><td><img src=small.gif></td></tr><tr><td>1 year ago</td><td>95…

    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 268, Column 316: end tag for "A" omitted, but its declaration does not permit this
    …small.gif></td></tr><tr><td>1 year ago</td><td>953 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 268, Column 163: start tag was here
    …e_2/782.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 268, Column 316: end tag for "A" omitted, but its declaration does not permit this
    …small.gif></td></tr><tr><td>1 year ago</td><td>953 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 268, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 268, Column 316: end tag for "CENTER" omitted, but its declaration does not permit this
    …small.gif></td></tr><tr><td>1 year ago</td><td>953 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 268, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 269, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…

    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 269, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=d337b5"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 269, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=d337b5"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 269, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=d337b5"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 269, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=d337b5"><img src=http://190.120.228.34/sxs/tube_2/639.jpeg wid…

    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 269, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=d337b5"><img src=http://190.120.228.34/sxs/tube_2/639.jpeg wid…

    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 269, Column 165: document type does not allow element "A" here
    …2/639.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 269, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">08:25</td><td><img …

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

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

  • Error Line 269, Column 248: required attribute "ALT" not specified
    …60%">08:25</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 269, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>348 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 269, Column 163: start tag was here
    …e_2/639.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 269, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>348 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 269, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 269, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>348 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 269, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 272, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=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 272, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=2c417a"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 272, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=2c417a"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 272, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=2c417a"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 272, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=2c417a"><img src=http://190.120.228.34/sxs/tube_2/878.jpeg wid…

    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 272, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=2c417a"><img src=http://190.120.228.34/sxs/tube_2/878.jpeg wid…

    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 272, Column 165: document type does not allow element "A" here
    …2/878.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 272, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">12:27</td><td><img …

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

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

  • Error Line 272, Column 248: required attribute "ALT" not specified
    …60%">12:27</td><td><img src=small3.gif></td></tr><tr><td>4 months ago</td><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 272, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 months ago</td><td>875 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 272, Column 163: start tag was here
    …e_2/878.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 272, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 months ago</td><td>875 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 272, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 272, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 months ago</td><td>875 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 272, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 273, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=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 273, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=2212ca"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 273, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=2212ca"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 273, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=2212ca"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 273, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=2212ca"><img src=http://190.120.228.34/sxs/tube_2/1050.jpeg wi…

    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 273, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=2212ca"><img src=http://190.120.228.34/sxs/tube_2/1050.jpeg wi…

    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 273, Column 166: document type does not allow element "A" here
    …/1050.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 273, Column 195: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">07:26</td><td><img …

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

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

  • Error Line 273, Column 248: required attribute "ALT" not specified
    …"60%">07:26</td><td><img src=small.gif></td></tr><tr><td>2 years ago </td><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 273, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>2 years ago </td><td>654 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 273, Column 164: start tag was here
    …_2/1050.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 273, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>2 years ago </td><td>654 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 273, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 273, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …all.gif></td></tr><tr><td>2 years ago </td><td>654 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 273, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 274, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…

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

  • Error Line 274, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=8112a7"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 274, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=8112a7"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 274, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=8112a7"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 274, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=8112a7"><img src=http://190.120.228.34/sxs/tube_2/810.jpeg wid…

    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 274, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=8112a7"><img src=http://190.120.228.34/sxs/tube_2/810.jpeg wid…

    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 274, Column 165: document type does not allow element "A" here
    …2/810.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 274, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">11:15</td><td><img …

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

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

  • Error Line 274, Column 248: required attribute "ALT" not specified
    …60%">11:15</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 274, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>256 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 274, Column 163: start tag was here
    …e_2/810.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 274, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>256 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 274, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 274, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>256 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 274, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 275, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…

    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 275, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=33d720"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 275, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=33d720"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 275, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=33d720"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 275, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=33d720"><img src=http://190.120.228.34/sxs/tube_2/691.jpeg wid…

    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 275, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=33d720"><img src=http://190.120.228.34/sxs/tube_2/691.jpeg wid…

    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 275, Column 165: document type does not allow element "A" here
    …2/691.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 275, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">04:36</td><td><img …

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

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

  • Error Line 275, Column 248: required attribute "ALT" not specified
    …60%">04:36</td><td><img src=small2.gif></td></tr><tr><td>3 weeks ago</td><td>9…

    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 275, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>3 weeks ago</td><td>945 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 275, Column 163: start tag was here
    …e_2/691.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 275, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>3 weeks ago</td><td>945 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 275, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 275, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all2.gif></td></tr><tr><td>3 weeks ago</td><td>945 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 275, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 276, Column 10: end tag for "TABLE" omitted, but its declaration does not permit this
    					</TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 258, Column 4: start tag was here
    			<TABLE borderColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellP…
  • Error Line 279, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…

    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 279, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=8b02f7"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 279, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=8b02f7"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 279, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=8b02f7"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 279, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=8b02f7"><img src=http://190.120.228.34/sxs/tube_2/601.jpeg wid…

    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 279, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=8b02f7"><img src=http://190.120.228.34/sxs/tube_2/601.jpeg wid…

    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 279, Column 165: document type does not allow element "A" here
    …2/601.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 279, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">10:43</td><td><img …

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

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

  • Error Line 279, Column 248: required attribute "ALT" not specified
    …60%">10:43</td><td><img src=small3.gif></td></tr><tr><td>37 minutes ago</td><t…

    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 279, Column 321: end tag for "A" omitted, but its declaration does not permit this
    …3.gif></td></tr><tr><td>37 minutes ago</td><td>283 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 279, Column 163: start tag was here
    …e_2/601.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 279, Column 321: end tag for "A" omitted, but its declaration does not permit this
    …3.gif></td></tr><tr><td>37 minutes ago</td><td>283 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 279, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 279, Column 321: end tag for "CENTER" omitted, but its declaration does not permit this
    …3.gif></td></tr><tr><td>37 minutes ago</td><td>283 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 279, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 280, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…

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

  • Error Line 280, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=0f779f"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 280, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=0f779f"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 280, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=0f779f"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 280, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=0f779f"><img src=http://190.120.228.34/sxs/tube_2/984.jpeg wid…

    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 280, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=0f779f"><img src=http://190.120.228.34/sxs/tube_2/984.jpeg wid…

    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 280, Column 165: document type does not allow element "A" here
    …2/984.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 280, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:34</td><td><img …

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

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

  • Error Line 280, Column 248: required attribute "ALT" not specified
    …60%">02:34</td><td><img src=small2.gif></td></tr><tr><td>1 weeks ago</td><td>8…

    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 280, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>1 weeks ago</td><td>8545 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 280, Column 163: start tag was here
    …e_2/984.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 280, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>1 weeks ago</td><td>8545 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 280, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 280, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>1 weeks ago</td><td>8545 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 280, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 281, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=1…

    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 281, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=1cee3c"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 281, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=1cee3c"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 281, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=1cee3c"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 281, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=1cee3c"><img src=http://190.120.228.34/sxs/tube_2/593.jpeg wid…

    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 281, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=1cee3c"><img src=http://190.120.228.34/sxs/tube_2/593.jpeg wid…

    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 281, Column 165: document type does not allow element "A" here
    …2/593.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 281, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">05:28</td><td><img …

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

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

  • Error Line 281, Column 248: required attribute "ALT" not specified
    …60%">05:28</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 281, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>843 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 281, Column 163: start tag was here
    …e_2/593.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 281, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>843 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 281, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=1…
  • Error Line 281, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>843 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 281, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=1…
  • Error Line 282, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…

    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 282, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=bb4aaf"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 282, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=bb4aaf"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 282, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=bb4aaf"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 282, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=bb4aaf"><img src=http://190.120.228.34/sxs/tube_2/674.jpeg wid…

    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 282, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=bb4aaf"><img src=http://190.120.228.34/sxs/tube_2/674.jpeg wid…

    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 282, Column 165: document type does not allow element "A" here
    …2/674.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 282, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">04:48</td><td><img …

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

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

  • Error Line 282, Column 247: required attribute "ALT" not specified
    …"60%">04:48</td><td><img src=small.gif></td></tr><tr><td>37 minutes ago</td><t…

    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 282, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>37 minutes ago</td><td>956 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 282, Column 163: start tag was here
    …e_2/674.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 282, Column 320: end tag for "A" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>37 minutes ago</td><td>956 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 282, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 282, Column 320: end tag for "CENTER" omitted, but its declaration does not permit this
    …l.gif></td></tr><tr><td>37 minutes ago</td><td>956 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 282, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 285, Column 7: end tag for element "TD" which is not open
    		</TD>

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

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

  • Error Line 286, Column 6: end tag for element "TR" which is not open
    	</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 287, Column 8: end tag for element "TABLE" which is not open
    </TABLE>

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

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

  • Error Line 292, Column 36: an attribute value must be a literal unless it contains only name characters
    			<TABLE width="100%" borderColor=#222222 align=center bgColor=#000000 cellSpa…

    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 292, Column 65: an attribute value must be a literal unless it contains only name characters
    …" borderColor=#222222 align=center bgColor=#000000 cellSpacing=0 cellPadding=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 294, Column 177: an attribute value must be a literal unless it contains only name characters
    …e='0'); " colSpan=3><FONT face=Verdana size=4 color=#ffffff>ARCHIVE</FONT></TD>

    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 301, Column 23: an attribute value must be a literal unless it contains only name characters
    			<TABLE borderColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellP…

    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 301, Column 52: an attribute value must be a literal unless it contains only name characters
    …derColor=#222222 align=center bgColor=#000000 cellSpacing=10 cellPadding=5 bor…

    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 303, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…

    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 303, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=ec3482"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 303, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=ec3482"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 303, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=ec3482"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 303, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=ec3482"><img src=http://190.120.228.34/sxs/tube_2/721.jpeg wid…

    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 303, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=ec3482"><img src=http://190.120.228.34/sxs/tube_2/721.jpeg wid…

    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 303, Column 165: document type does not allow element "A" here
    …2/721.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 303, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:41</td><td><img …

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

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

  • Error Line 303, Column 248: required attribute "ALT" not specified
    …60%">09:41</td><td><img src=small3.gif></td></tr><tr><td>1 year ago</td><td>74…

    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 303, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 303, Column 163: start tag was here
    …e_2/721.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 303, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 303, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 303, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 303, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 304, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…

    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 304, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=e76280"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 304, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=e76280"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 304, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=e76280"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 304, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=e76280"><img src=http://190.120.228.34/sxs/tube_2/621.jpeg wid…

    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 304, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=e76280"><img src=http://190.120.228.34/sxs/tube_2/621.jpeg wid…

    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 304, Column 165: document type does not allow element "A" here
    …2/621.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 304, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">05:27</td><td><img …

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

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

  • Error Line 304, Column 247: required attribute "ALT" not specified
    …"60%">05:27</td><td><img src=small.gif></td></tr><tr><td>2 years ago</td><td>2…

    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 304, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 304, Column 163: start tag was here
    …e_2/621.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 304, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 304, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 304, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 304, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=e…
  • Error Line 305, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…

    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 305, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=ffa2b9"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 305, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=ffa2b9"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 305, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=ffa2b9"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 305, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=ffa2b9"><img src=http://190.120.228.34/sxs/tube_2/793.jpeg wid…

    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 305, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=ffa2b9"><img src=http://190.120.228.34/sxs/tube_2/793.jpeg wid…

    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 305, Column 165: document type does not allow element "A" here
    …2/793.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 305, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:52</td><td><img …

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

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

  • Error Line 305, Column 248: required attribute "ALT" not specified
    …60%">09:52</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 305, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 305, Column 163: start tag was here
    …e_2/793.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 305, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 305, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 305, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 305, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 306, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…

    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 306, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=8a8e9a"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 306, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=8a8e9a"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 306, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=8a8e9a"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 306, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=8a8e9a"><img src=http://190.120.228.34/sxs/tube_2/720.jpeg wid…

    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 306, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=8a8e9a"><img src=http://190.120.228.34/sxs/tube_2/720.jpeg wid…

    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 306, Column 165: document type does not allow element "A" here
    …2/720.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 306, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:24</td><td><img …

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

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

  • Error Line 306, Column 248: required attribute "ALT" not specified
    …60%">02:24</td><td><img src=small3.gif></td></tr><tr><td>4 weeks ago</td><td>8…

    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 306, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 306, Column 163: start tag was here
    …e_2/720.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 306, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 306, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 306, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 306, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=8…
  • Error Line 309, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…

    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 309, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=f51151"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 309, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=f51151"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 309, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=f51151"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 309, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=f51151"><img src=http://190.120.228.34/sxs/tube_2/571.jpeg wid…

    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 309, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=f51151"><img src=http://190.120.228.34/sxs/tube_2/571.jpeg wid…

    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 309, Column 165: document type does not allow element "A" here
    …2/571.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 309, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:41</td><td><img …

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

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

  • Error Line 309, Column 248: required attribute "ALT" not specified
    …60%">09:41</td><td><img src=small3.gif></td></tr><tr><td>1 year ago</td><td>74…

    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 309, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 309, Column 163: start tag was here
    …e_2/571.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 309, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 309, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 309, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 309, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 310, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=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 310, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=2c08a2"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 310, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=2c08a2"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 310, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=2c08a2"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 310, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=2c08a2"><img src=http://190.120.228.34/sxs/tube_2/842.jpeg wid…

    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 310, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=2c08a2"><img src=http://190.120.228.34/sxs/tube_2/842.jpeg wid…

    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 165: document type does not allow element "A" here
    …2/842.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 310, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">05:27</td><td><img …

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

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

  • Error Line 310, Column 247: required attribute "ALT" not specified
    …"60%">05:27</td><td><img src=small.gif></td></tr><tr><td>2 years ago</td><td>2…

    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 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 310, Column 163: start tag was here
    …e_2/842.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 310, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 310, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 310, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 310, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=2…
  • Error Line 311, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…

    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 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=337c81"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 311, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=337c81"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 311, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=337c81"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 311, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=337c81"><img src=http://190.120.228.34/sxs/tube_2/541.jpeg wid…

    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 311, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=337c81"><img src=http://190.120.228.34/sxs/tube_2/541.jpeg wid…

    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 311, Column 165: document type does not allow element "A" here
    …2/541.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 311, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:52</td><td><img …

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

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

  • Error Line 311, Column 248: required attribute "ALT" not specified
    …60%">09:52</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 311, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 311, Column 163: start tag was here
    …e_2/541.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 311, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 311, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 311, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 311, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=3…
  • Error Line 312, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=5…

    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 312, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=5113b4"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 312, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=5113b4"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 312, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=5113b4"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 312, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=5113b4"><img src=http://190.120.228.34/sxs/tube_2/856.jpeg wid…

    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 312, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=5113b4"><img src=http://190.120.228.34/sxs/tube_2/856.jpeg wid…

    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 312, Column 165: document type does not allow element "A" here
    …2/856.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 312, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:24</td><td><img …

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

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

  • Error Line 312, Column 248: required attribute "ALT" not specified
    …60%">02:24</td><td><img src=small3.gif></td></tr><tr><td>4 weeks ago</td><td>8…

    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 312, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 312, Column 163: start tag was here
    …e_2/856.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 312, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 312, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=5…
  • Error Line 312, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 312, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=5…
  • Error Line 315, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…

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

  • Error Line 315, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=a415b9"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 315, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=a415b9"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 315, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=a415b9"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 315, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=a415b9"><img src=http://190.120.228.34/sxs/tube_2/830.jpeg wid…

    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 315, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=a415b9"><img src=http://190.120.228.34/sxs/tube_2/830.jpeg wid…

    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 315, Column 165: document type does not allow element "A" here
    …2/830.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 315, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:41</td><td><img …

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

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

  • Error Line 315, Column 248: required attribute "ALT" not specified
    …60%">09:41</td><td><img src=small3.gif></td></tr><tr><td>1 year ago</td><td>74…

    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 315, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 315, Column 163: start tag was here
    …e_2/830.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 315, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 315, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…
  • Error Line 315, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 315, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…
  • Error Line 316, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…

    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 316, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=f73c40"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 316, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=f73c40"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 316, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=f73c40"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 316, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=f73c40"><img src=http://190.120.228.34/sxs/tube_2/670.jpeg wid…

    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 316, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=f73c40"><img src=http://190.120.228.34/sxs/tube_2/670.jpeg wid…

    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 316, Column 165: document type does not allow element "A" here
    …2/670.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 316, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">05:27</td><td><img …

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

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

  • Error Line 316, Column 247: required attribute "ALT" not specified
    …"60%">05:27</td><td><img src=small.gif></td></tr><tr><td>2 years ago</td><td>2…

    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 316, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 316, Column 163: start tag was here
    …e_2/670.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 316, Column 317: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 316, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 316, Column 317: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 316, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=f…
  • Error Line 317, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…

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

  • Error Line 317, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=0d6cfa"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 317, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=0d6cfa"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 317, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=0d6cfa"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 317, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=0d6cfa"><img src=http://190.120.228.34/sxs/tube_2/857.jpeg wid…

    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 317, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=0d6cfa"><img src=http://190.120.228.34/sxs/tube_2/857.jpeg wid…

    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 317, Column 165: document type does not allow element "A" here
    …2/857.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 317, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:52</td><td><img …

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

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

  • Error Line 317, Column 248: required attribute "ALT" not specified
    …60%">09:52</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 317, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 317, Column 163: start tag was here
    …e_2/857.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 317, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 317, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 317, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 317, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 318, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…

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

  • Error Line 318, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=a5b16e"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 318, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=a5b16e"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 318, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=a5b16e"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 318, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=a5b16e"><img src=http://190.120.228.34/sxs/tube_2/540.jpeg wid…

    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 318, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=a5b16e"><img src=http://190.120.228.34/sxs/tube_2/540.jpeg wid…

    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 318, Column 165: document type does not allow element "A" here
    …2/540.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 318, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:24</td><td><img …

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

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

  • Error Line 318, Column 248: required attribute "ALT" not specified
    …60%">02:24</td><td><img src=small3.gif></td></tr><tr><td>4 weeks ago</td><td>8…

    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 318, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 318, Column 163: start tag was here
    …e_2/540.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 318, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 318, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…
  • Error Line 318, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 318, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=a…
  • Error Line 321, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…

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

  • Error Line 321, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=02749d"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 321, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=02749d"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 321, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=02749d"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 321, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=02749d"><img src=http://190.120.228.34/sxs/tube_2/596.jpeg wid…

    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 321, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=02749d"><img src=http://190.120.228.34/sxs/tube_2/596.jpeg wid…

    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 321, Column 165: document type does not allow element "A" here
    …2/596.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 321, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:41</td><td><img …

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

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

  • Error Line 321, Column 248: required attribute "ALT" not specified
    …60%">09:41</td><td><img src=small3.gif></td></tr><tr><td>1 year ago</td><td>74…

    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 321, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 321, Column 163: start tag was here
    …e_2/596.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 321, Column 318: end tag for "A" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 321, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 321, Column 318: end tag for "CENTER" omitted, but its declaration does not permit this
    …all3.gif></td></tr><tr><td>1 year ago</td><td>7483 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 321, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0…
  • Error Line 322, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…

    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 322, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=ded480"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 322, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=ded480"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 322, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=ded480"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 322, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=ded480"><img src=http://190.120.228.34/sxs/tube_2/91.jpeg widt…

    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 322, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=ded480"><img src=http://190.120.228.34/sxs/tube_2/91.jpeg widt…

    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 322, Column 164: document type does not allow element "A" here
    …_2/91.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 322, Column 193: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">05:27</td><td><img …

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

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

  • Error Line 322, Column 246: required attribute "ALT" not specified
    …"60%">05:27</td><td><img src=small.gif></td></tr><tr><td>2 years ago</td><td>2…

    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 322, Column 316: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 322, Column 162: start tag was here
    …be_2/91.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 322, Column 316: end tag for "A" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 322, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 322, Column 316: end tag for "CENTER" omitted, but its declaration does not permit this
    …mall.gif></td></tr><tr><td>2 years ago</td><td>286 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 322, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=d…
  • Error Line 323, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…

    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 323, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=b02a88"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 323, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=b02a88"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 323, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=b02a88"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 323, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=b02a88"><img src=http://190.120.228.34/sxs/tube_2/667.jpeg wid…

    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 323, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=b02a88"><img src=http://190.120.228.34/sxs/tube_2/667.jpeg wid…

    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 323, Column 165: document type does not allow element "A" here
    …2/667.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 323, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">09:52</td><td><img …

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

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

  • Error Line 323, Column 248: required attribute "ALT" not specified
    …60%">09:52</td><td><img src=small2.gif></td></tr><tr><td>2 months ago</td><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 323, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 323, Column 163: start tag was here
    …e_2/667.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 323, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 323, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 323, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll2.gif></td></tr><tr><td>2 months ago</td><td>768 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 323, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=b…
  • Error Line 324, Column 18: an attribute value must be a literal unless it contains only name characters
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=7…

    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 324, Column 65: reference to entity "link" for which no system identifier could be generated
    …center><a href="dtr/link.php?url=&link=tube&gr=4&id=7b68a2"><img src=http://19…

    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 216, Column 60: entity was defined here
    …000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http…
  • Error Line 324, Column 73: reference to entity "gr" for which no system identifier could be generated
    …a href="dtr/link.php?url=&link=tube&gr=4&id=7b68a2"><img src=http://190.120.22…

    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 216, Column 70: entity was defined here
    …r><a href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120…
  • Error Line 324, Column 78: reference to entity "id" for which no system identifier could be generated
    …f="dtr/link.php?url=&link=tube&gr=4&id=7b68a2"><img src=http://190.120.228.34/…

    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 216, Column 75: entity was defined here
    …href="dtr/link.php?url=&link=tube&gr=4&id=0a1fc3"><img src=http://190.120.228.…
  • Warning Line 324, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …nk=tube&gr=4&id=7b68a2"><img src=http://190.120.228.34/sxs/tube_2/603.jpeg wid…

    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 324, Column 101: required attribute "ALT" not specified
    …nk=tube&gr=4&id=7b68a2"><img src=http://190.120.228.34/sxs/tube_2/603.jpeg wid…

    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 324, Column 165: document type does not allow element "A" here
    …2/603.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td wi…

    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 324, Column 194: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …80><br><a><table width="100%" border=0><tr><td width="60%">02:24</td><td><img …

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

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

  • Error Line 324, Column 248: required attribute "ALT" not specified
    …60%">02:24</td><td><img src=small3.gif></td></tr><tr><td>4 weeks ago</td><td>8…

    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 324, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 324, Column 163: start tag was here
    …e_2/603.jpeg width=240 height=180><br><a><table width="100%" border=0><tr><td …
  • Error Line 324, Column 319: end tag for "A" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 324, Column 34: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=7…
  • Error Line 324, Column 319: end tag for "CENTER" omitted, but its declaration does not permit this
    …ll3.gif></td></tr><tr><td>4 weeks ago</td><td>8754 views</td></tr></table></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 324, Column 26: start tag was here
    					<TD bgColor=#000000><center><a href="dtr/link.php?url=&link=tube&gr=4&id=7…
  • Error Line 329, Column 52: required attribute "TYPE" not specified
    </TABLE>  <BR><BR> <script src="dtr/count.php?gr=4"></script>

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

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

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

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

  • Info Line 201, Column 1: start tag was here
    <center>
  • Error Line 340, Column 17: end tag for "CENTER" omitted, but its declaration does not permit this
     </CENTER></BODY></HTML>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 89, Column 1: start tag was here
    <center>
  • Error Line 340, Column 17: end tag for "CENTER" omitted, but its declaration does not permit this
     </CENTER></BODY></HTML>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 66, Column 1: start tag was here
    <CENTER>

Visitor Analysis

Daily Visitor
  • 9 visits