newpornfantasy.net has Alexa Rank 217.096 and Google Page Rank is 0

newpornfantasy.net
  • Domain Name
    newpornfantasy.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #217096
  • Page Size
    18.4 KB
  • Ip Address
    95.211.198.11
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 84 JPG, 0 PNG

Website Meta Analysis

  • Title
    HD-PORN VIDEOS
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    nginx/1.2.5
  • Ip Address
    95.211.198.11
  • Domain Age
    6 Months, 3 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from newpornfantasy.net.

HTML Analysis

  • server: nginx/1.2.5
  • date: Sat, 09 Mar 2013 21:24:23 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for newpornfantasy.net

IP 95.211.198.11 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 95.211.198.11

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 376 Errors
  • 181 Warnings
Ratio Text/Html
  • 0.9110191960971471
Message Error
  • Warning Line 6, Column 34: NET-enabling start-tag requires SHORTTAG YES
    <meta name="keywords" content="" />

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

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

  • Warning Line 7, Column 37: NET-enabling start-tag requires SHORTTAG YES
    <meta name="description" content="" />

    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 7, Column 37: document type does not allow element "META" here
    <meta name="description" content="" />

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

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

  • Warning Line 8, Column 66: NET-enabling start-tag requires SHORTTAG YES
    <meta name="prVerify" content="ec4c560870adecc1b8a6acde82a03eef" />

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

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

  • Error Line 8, Column 66: document type does not allow element "META" here
    <meta name="prVerify" content="ec4c560870adecc1b8a6acde82a03eef" />

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

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

  • Error Line 11, Column 56: document type does not allow element "LINK" here
    <link rel="stylesheet" type="text/css" href="style.css">

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

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

  • Error Line 14, Column 20: document type does not allow element "BASE" here
    <base target=_blank>

    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 16, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 17, Column 6: document type does not allow element "BODY" here
    <body>

    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 39, Column 27: there is no attribute "ALLOWTRANSPARENCY"
    <iframe allowtransparency="1" frameborder="0" height="156" id="plwpr56062511a83…

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

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

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

  • Warning Line 40, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

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

  • Warning Line 40, Column 32: cannot generate system identifier for general entity "gr"
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 40, Column 32: general entity "gr" not defined and no default entity
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    This is usually a cascading error caused by 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 40, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 40, Column 37: cannot generate system identifier for general entity "url"
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 40, Column 37: general entity "url" not defined and no default entity
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    This is usually a cascading error caused by 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 40, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 40, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img177.imagevenue.com/loc414/th_417455…

    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 40, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img177.imagevenue.com/loc414/th_417455…

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

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

  • Error Line 40, Column 148: end tag for element "A" which is not open
    …=http://img177.imagevenue.com/loc414/th_417455839_aEviKcieMN_123_414lo.jpg></a>

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

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

  • Warning Line 41, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=32eb6a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 41, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=32eb6a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 41, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=32eb6a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 41, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img159.imagevenue.com/loc513/th_417453…

    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 41, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img159.imagevenue.com/loc513/th_417453…

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

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

  • Error Line 41, Column 148: end tag for element "A" which is not open
    …=http://img159.imagevenue.com/loc513/th_417453206_aelcwnUjNj_123_513lo.jpg></a>

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

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

  • Warning Line 42, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=1a9907&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 42, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=1a9907&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 42, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=1a9907&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 42, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img42.imagevenue.com/loc378/th_4173412…

    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 42, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img42.imagevenue.com/loc378/th_4173412…

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

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

  • Error Line 42, Column 147: end tag for element "A" which is not open
    …c=http://img42.imagevenue.com/loc378/th_417341287_0603196850_123_378lo.jpg></a>

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

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

  • Warning Line 43, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=2fa42f&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 43, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=2fa42f&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 43, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=2fa42f&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 43, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img237.imagevenue.com/loc356/th_417395…

    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 43, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img237.imagevenue.com/loc356/th_417395…

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

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

  • Error Line 43, Column 148: end tag for element "A" which is not open
    …=http://img237.imagevenue.com/loc356/th_417395117_1132130962_123_356lo.jpg></a>

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

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

  • Warning Line 44, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=f47282&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 44, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=f47282&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 44, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=f47282&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 44, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img259.imagevenue.com/loc139/th_417690…

    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 44, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img259.imagevenue.com/loc139/th_417690…

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

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

  • Error Line 44, Column 148: end tag for element "A" which is not open
    …=http://img259.imagevenue.com/loc139/th_417690884_kMv7kTMqyZ_123_139lo.jpg></a>

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

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

  • Warning Line 45, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=4c7ea2&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 45, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=4c7ea2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 45, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=4c7ea2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 45, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img40.imagevenue.com/loc96/th_41710668…

    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 45, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img40.imagevenue.com/loc96/th_41710668…

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

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

  • Error Line 45, Column 145: end tag for element "A" which is not open
    …src=http://img40.imagevenue.com/loc96/th_417106682_4JePKHblMz_123_96lo.jpg></a>

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

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

  • Warning Line 46, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b73501&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 46, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b73501&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 46, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b73501&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 46, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img175.imagevenue.com/loc461/th_417078…

    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 46, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img175.imagevenue.com/loc461/th_417078…

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

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

  • Error Line 46, Column 148: end tag for element "A" which is not open
    …=http://img175.imagevenue.com/loc461/th_417078312_3oph4SKVNt_123_461lo.jpg></a>

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

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

  • Warning Line 47, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=72ab81&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 47, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=72ab81&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 47, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=72ab81&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 47, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img176.imagevenue.com/loc25/th_4170765…

    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 47, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img176.imagevenue.com/loc25/th_4170765…

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

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

  • Error Line 47, Column 146: end tag for element "A" which is not open
    …rc=http://img176.imagevenue.com/loc25/th_417076561_1LsSalGTpg_123_25lo.jpg></a>

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

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

  • Warning Line 48, Column 13: NET-enabling start-tag requires SHORTTAG YES
    <img src=dtr/count.php?gr=2 width=1 height=1>

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

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

  • Error Line 48, Column 13: required attribute "ALT" not specified
    <img src=dtr/count.php?gr=2 width=1 height=1>

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

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

  • Error Line 49, Column 64: ID "PLWPR56062511A83F922BB48.87575403" already defined
    …="1" frameborder="0" height="156" id="plwpr56062511a83f922bb48.87575403" scrol…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 39, Column 64: ID "PLWPR56062511A83F922BB48.87575403" first defined here
    …="1" frameborder="0" height="156" id="plwpr56062511a83f922bb48.87575403" scrol…
  • Warning Line 49, Column 204: NET-enabling start-tag requires SHORTTAG YES
    …473" width="1271"></iframe><a href=dtr/link.php?id=5c80e9&gr=2&url=/tp/out.php…

    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 49, Column 226: reference to entity "gr" for which no system identifier could be generated
    …rame><a href=dtr/link.php?id=5c80e9&gr=2&url=/tp/out.php class=lm><img src=htt…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 49, Column 232: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=5c80e9&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 49, Column 268: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img101.imagevenue.com/loc254/th_417081…

    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 49, Column 268: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img101.imagevenue.com/loc254/th_417081…

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

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

  • Error Line 49, Column 340: end tag for element "A" which is not open
    …=http://img101.imagevenue.com/loc254/th_417081662_3t0nk0K0oN_123_254lo.jpg></a>

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

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

  • Warning Line 50, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=4decea&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

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

  • Error Line 50, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=4decea&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 50, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=4decea&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 50, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img264.imagevenue.com/loc544/th_417088…

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

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

  • Error Line 50, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img264.imagevenue.com/loc544/th_417088…

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

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

  • Error Line 50, Column 148: end tag for element "A" which is not open
    …=http://img264.imagevenue.com/loc544/th_417088487_4bUxcqSWuk_123_544lo.jpg></a>

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

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

  • Warning Line 51, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=70e34f&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 51, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=70e34f&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 51, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=70e34f&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 51, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img12.imagevenue.com/loc69/th_41709168…

    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 51, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img12.imagevenue.com/loc69/th_41709168…

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

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

  • Error Line 51, Column 145: end tag for element "A" which is not open
    …src=http://img12.imagevenue.com/loc69/th_417091680_4h82WYGn12_123_69lo.jpg></a>

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

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

  • Warning Line 52, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=f7f590&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 52, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=f7f590&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 52, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=f7f590&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 52, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img21.imagevenue.com/loc33/th_41755627…

    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 52, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img21.imagevenue.com/loc33/th_41755627…

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

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

  • Error Line 52, Column 145: end tag for element "A" which is not open
    …src=http://img21.imagevenue.com/loc33/th_417556278_gGFLo6azzO_123_33lo.jpg></a>

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

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

  • Warning Line 53, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=52be8b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 53, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=52be8b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 53, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=52be8b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 53, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img242.imagevenue.com/loc161/th_417503…

    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 53, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img242.imagevenue.com/loc161/th_417503…

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

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

  • Error Line 53, Column 148: end tag for element "A" which is not open
    …=http://img242.imagevenue.com/loc161/th_417503668_dIhVmTtjmS_123_161lo.jpg></a>

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

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

  • Warning Line 54, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=4c3e1a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 54, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=4c3e1a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 54, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=4c3e1a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 54, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img266.imagevenue.com/loc246/th_417481…

    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 54, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img266.imagevenue.com/loc246/th_417481…

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

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

  • Error Line 54, Column 148: end tag for element "A" which is not open
    …=http://img266.imagevenue.com/loc246/th_417481338_chqdXSYq4w_123_246lo.jpg></a>

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

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

  • Warning Line 55, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b1b847&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 55, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b1b847&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 55, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b1b847&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 55, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img262.imagevenue.com/loc480/th_418074…

    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 55, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img262.imagevenue.com/loc480/th_418074…

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

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

  • Error Line 55, Column 148: end tag for element "A" which is not open
    …=http://img262.imagevenue.com/loc480/th_418074857_R4pe2gsVfN_123_480lo.jpg></a>

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

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

  • Warning Line 56, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=2534f1&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 56, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=2534f1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 56, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=2534f1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 56, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img21.imagevenue.com/loc454/th_4174904…

    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 56, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img21.imagevenue.com/loc454/th_4174904…

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

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

  • Error Line 56, Column 147: end tag for element "A" which is not open
    …c=http://img21.imagevenue.com/loc454/th_417490459_cMe4eYguKt_123_454lo.jpg></a>

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

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

  • Warning Line 57, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=77d862&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 57, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=77d862&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 57, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=77d862&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 57, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img173.imagevenue.com/loc563/th_417131…

    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 57, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img173.imagevenue.com/loc563/th_417131…

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

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

  • Error Line 57, Column 148: end tag for element "A" which is not open
    …=http://img173.imagevenue.com/loc563/th_417131298_5OYtQKTVck_123_563lo.jpg></a>

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

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

  • Warning Line 58, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=d5eef5&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=d5eef5&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 58, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=d5eef5&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 58, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img159.imagevenue.com/loc225/th_418102…

    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 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img159.imagevenue.com/loc225/th_418102…

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

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

  • Error Line 58, Column 148: end tag for element "A" which is not open
    …=http://img159.imagevenue.com/loc225/th_418102932_Rlt8N0YgFP_123_225lo.jpg></a>

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

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

  • Warning Line 59, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=8caab1&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 59, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=8caab1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 59, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=8caab1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 59, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img262.imagevenue.com/loc467/th_417560…

    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 59, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img262.imagevenue.com/loc467/th_417560…

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

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

  • Error Line 59, Column 148: end tag for element "A" which is not open
    …=http://img262.imagevenue.com/loc467/th_417560743_gGgyImgZyV_123_467lo.jpg></a>

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

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

  • Warning Line 60, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=9ae13d&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 60, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=9ae13d&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 60, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=9ae13d&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 60, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img237.imagevenue.com/loc437/th_417108…

    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 60, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img237.imagevenue.com/loc437/th_417108…

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

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

  • Error Line 60, Column 148: end tag for element "A" which is not open
    …=http://img237.imagevenue.com/loc437/th_417108665_4kwQLRLxk1_123_437lo.jpg></a>

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

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

  • Warning Line 61, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=4d9172&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 61, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=4d9172&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 61, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=4d9172&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 61, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img205.imagevenue.com/loc360/th_418156…

    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 61, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img205.imagevenue.com/loc360/th_418156…

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

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

  • Error Line 61, Column 148: end tag for element "A" which is not open
    …=http://img205.imagevenue.com/loc360/th_418156510_RqlvnWV7mi_123_360lo.jpg></a>

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

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

  • Warning Line 62, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=713007&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 62, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=713007&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 62, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=713007&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 62, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img188.imagevenue.com/loc258/th_417569…

    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 62, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img188.imagevenue.com/loc258/th_417569…

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

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

  • Error Line 62, Column 148: end tag for element "A" which is not open
    …=http://img188.imagevenue.com/loc258/th_417569570_gSUhELhUJn_123_258lo.jpg></a>

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

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

  • Warning Line 63, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b5eb97&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 63, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b5eb97&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 63, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b5eb97&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 63, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img102.imagevenue.com/loc570/th_417069…

    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 63, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img102.imagevenue.com/loc570/th_417069…

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

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

  • Error Line 63, Column 148: end tag for element "A" which is not open
    …=http://img102.imagevenue.com/loc570/th_417069464_0N3zOYPav1_123_570lo.jpg></a>

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

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

  • Warning Line 64, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=258450&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 64, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=258450&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 64, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=258450&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 64, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img177.imagevenue.com/loc591/th_417643…

    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 64, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img177.imagevenue.com/loc591/th_417643…

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

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

  • Error Line 64, Column 148: end tag for element "A" which is not open
    …=http://img177.imagevenue.com/loc591/th_417643391_jR3qiY8Yqn_123_591lo.jpg></a>

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

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

  • Warning Line 65, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=736cd0&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 65, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=736cd0&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 65, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=736cd0&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 65, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img260.imagevenue.com/loc360/th_417648…

    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 65, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img260.imagevenue.com/loc360/th_417648…

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

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

  • Error Line 65, Column 148: end tag for element "A" which is not open
    …=http://img260.imagevenue.com/loc360/th_417648672_JXypfu6Teo_123_360lo.jpg></a>

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

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

  • Warning Line 66, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=728b56&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 66, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=728b56&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 66, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=728b56&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 66, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img251.imagevenue.com/loc19/th_4176207…

    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 66, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img251.imagevenue.com/loc19/th_4176207…

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

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

  • Error Line 66, Column 146: end tag for element "A" which is not open
    …rc=http://img251.imagevenue.com/loc19/th_417620788_ir67aX6J2g_123_19lo.jpg></a>

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

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

  • Warning Line 67, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=1330fb&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

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

  • Error Line 67, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=1330fb&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 67, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=1330fb&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 67, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img216.imagevenue.com/loc60/th_4177644…

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

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

  • Error Line 67, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img216.imagevenue.com/loc60/th_4177644…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute 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 146: end tag for element "A" which is not open
    …rc=http://img216.imagevenue.com/loc60/th_417764412_MSG7snOrcx_123_60lo.jpg></a>

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

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

  • Warning Line 68, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=69693a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 68, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=69693a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 68, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=69693a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 68, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img148.imagevenue.com/loc573/th_418246…

    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 68, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img148.imagevenue.com/loc573/th_418246…

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

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

  • Error Line 68, Column 148: end tag for element "A" which is not open
    …=http://img148.imagevenue.com/loc573/th_418246531_TvxzJtLNyk_123_573lo.jpg></a>

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

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

  • Warning Line 69, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=a73325&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 69, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=a73325&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 69, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=a73325&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 69, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img223.imagevenue.com/loc1062/th_41833…

    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 69, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img223.imagevenue.com/loc1062/th_41833…

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

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

  • Error Line 69, Column 150: end tag for element "A" which is not open
    …ttp://img223.imagevenue.com/loc1062/th_418332984_uaHuEL2X2r_123_1062lo.jpg></a>

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

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

  • Warning Line 70, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=57f5b8&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 70, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=57f5b8&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 70, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=57f5b8&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 70, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img146.imagevenue.com/loc573/th_418344…

    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 70, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img146.imagevenue.com/loc573/th_418344…

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

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

  • Error Line 70, Column 148: end tag for element "A" which is not open
    …=http://img146.imagevenue.com/loc573/th_418344823_UV2whTXiVw_123_573lo.jpg></a>

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

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

  • Warning Line 71, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=93a50e&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 71, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=93a50e&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 71, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=93a50e&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 71, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img208.imagevenue.com/loc96/th_4182429…

    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 71, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img208.imagevenue.com/loc96/th_4182429…

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

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

  • Error Line 71, Column 146: end tag for element "A" which is not open
    …rc=http://img208.imagevenue.com/loc96/th_418242928_SyS93qMnPT_123_96lo.jpg></a>

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

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

  • Warning Line 72, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=5e7071&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 72, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=5e7071&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 72, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=5e7071&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 72, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img169.imagevenue.com/loc1067/th_34182…

    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 72, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img169.imagevenue.com/loc1067/th_34182…

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

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

  • Error Line 72, Column 150: end tag for element "A" which is not open
    …ttp://img169.imagevenue.com/loc1067/th_341823385_SYnbvzbOuf_123_1067lo.jpg></a>

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

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

  • Warning Line 73, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b9a14a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 73, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b9a14a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 73, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b9a14a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 73, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img159.imagevenue.com/loc73/th_4176853…

    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 73, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img159.imagevenue.com/loc73/th_4176853…

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

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

  • Error Line 73, Column 146: end tag for element "A" which is not open
    …rc=http://img159.imagevenue.com/loc73/th_417685323_KkxOQy72jH_123_73lo.jpg></a>

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

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

  • Warning Line 74, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=5e98ec&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 74, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=5e98ec&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 74, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=5e98ec&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 74, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img151.imagevenue.com/loc80/th_4176949…

    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 74, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img151.imagevenue.com/loc80/th_4176949…

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

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

  • Error Line 74, Column 146: end tag for element "A" which is not open
    …rc=http://img151.imagevenue.com/loc80/th_417694910_KTGlWsK3FL_123_80lo.jpg></a>

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

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

  • Warning Line 75, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=41a8ed&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 75, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=41a8ed&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 75, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=41a8ed&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 75, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img177.imagevenue.com/loc175/th_417753…

    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 75, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img177.imagevenue.com/loc175/th_417753…

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

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

  • Error Line 75, Column 148: end tag for element "A" which is not open
    …=http://img177.imagevenue.com/loc175/th_417753336_MSeTsbxI3k_123_175lo.jpg></a>

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

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

  • Warning Line 76, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=96e153&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 76, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=96e153&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 76, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=96e153&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 76, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img147.imagevenue.com/loc600/th_341765…

    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 76, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img147.imagevenue.com/loc600/th_341765…

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

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

  • Error Line 76, Column 148: end tag for element "A" which is not open
    …=http://img147.imagevenue.com/loc600/th_341765299_K1huzgfSQI_123_600lo.jpg></a>

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

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

  • Warning Line 77, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=414402&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 77, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=414402&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 77, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=414402&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 77, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img246.imagevenue.com/loc31/th_4176398…

    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 77, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img246.imagevenue.com/loc31/th_4176398…

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

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

  • Error Line 77, Column 146: end tag for element "A" which is not open
    …rc=http://img246.imagevenue.com/loc31/th_417639846_iYmvEOQ1dF_123_31lo.jpg></a>

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

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

  • Warning Line 78, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=d4b930&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 78, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=d4b930&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 78, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=d4b930&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 78, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img175.imagevenue.com/loc247/th_417112…

    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 78, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img175.imagevenue.com/loc247/th_417112…

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

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

  • Error Line 78, Column 148: end tag for element "A" which is not open
    …=http://img175.imagevenue.com/loc247/th_417112171_5czsnXL84S_123_247lo.jpg></a>

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

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

  • Warning Line 79, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=7edc35&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 79, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=7edc35&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 79, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=7edc35&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 79, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img7.imagevenue.com/loc553/th_41733514…

    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 79, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img7.imagevenue.com/loc553/th_41733514…

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

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

  • Error Line 79, Column 146: end tag for element "A" which is not open
    …rc=http://img7.imagevenue.com/loc553/th_417335149_0228771686_123_553lo.jpg></a>

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

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

  • Warning Line 80, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=eb3f81&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 80, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=eb3f81&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 80, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=eb3f81&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 80, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img173.imagevenue.com/loc513/th_417117…

    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 80, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img173.imagevenue.com/loc513/th_417117…

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

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

  • Error Line 80, Column 148: end tag for element "A" which is not open
    …=http://img173.imagevenue.com/loc513/th_417117272_5hI0dEVK5G_123_513lo.jpg></a>

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

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

  • Warning Line 81, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=7dc996&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 81, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=7dc996&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 81, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=7dc996&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 81, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img107.imagevenue.com/loc252/th_417474…

    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 81, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img107.imagevenue.com/loc252/th_417474…

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

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

  • Error Line 81, Column 148: end tag for element "A" which is not open
    …=http://img107.imagevenue.com/loc252/th_417474906_cH8VXhIThP_123_252lo.jpg></a>

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

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

  • Warning Line 82, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=72b0b4&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 82, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=72b0b4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 82, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=72b0b4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 82, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img220.imagevenue.com/loc685/th_417126…

    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 82, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img220.imagevenue.com/loc685/th_417126…

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

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

  • Error Line 82, Column 148: end tag for element "A" which is not open
    …=http://img220.imagevenue.com/loc685/th_417126265_5mtt2FzUgl_123_685lo.jpg></a>

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

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

  • Warning Line 83, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b2fd59&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 83, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b2fd59&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 83, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b2fd59&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 83, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img270.imagevenue.com/loc490/th_417160…

    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 83, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img270.imagevenue.com/loc490/th_417160…

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

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

  • Error Line 83, Column 148: end tag for element "A" which is not open
    …=http://img270.imagevenue.com/loc490/th_417160711_7pguw0ESPI_123_490lo.jpg></a>

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

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

  • Warning Line 84, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=500b09&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 84, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=500b09&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 84, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=500b09&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 84, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img178.imagevenue.com/loc249/th_417391…

    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 84, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img178.imagevenue.com/loc249/th_417391…

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

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

  • Error Line 84, Column 148: end tag for element "A" which is not open
    …=http://img178.imagevenue.com/loc249/th_417391211_0760053067_123_249lo.jpg></a>

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

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

  • Warning Line 85, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b3aed9&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 85, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b3aed9&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 85, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b3aed9&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 85, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img167.imagevenue.com/loc1074/th_41805…

    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 85, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img167.imagevenue.com/loc1074/th_41805…

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

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

  • Error Line 85, Column 150: end tag for element "A" which is not open
    …ttp://img167.imagevenue.com/loc1074/th_418057851_qIYK7xGMyg_123_1074lo.jpg></a>

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

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

  • Warning Line 86, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=081c0a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 86, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=081c0a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 86, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=081c0a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 86, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img217.imagevenue.com/loc1068/th_41820…

    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 86, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img217.imagevenue.com/loc1068/th_41820…

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

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

  • Error Line 86, Column 150: end tag for element "A" which is not open
    …ttp://img217.imagevenue.com/loc1068/th_418208620_sjIzTmNgU2_123_1068lo.jpg></a>

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

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

  • Warning Line 87, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=7d07c2&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 87, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=7d07c2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 87, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=7d07c2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 87, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img229.imagevenue.com/loc431/th_341801…

    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 87, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img229.imagevenue.com/loc431/th_341801…

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

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

  • Error Line 87, Column 148: end tag for element "A" which is not open
    …=http://img229.imagevenue.com/loc431/th_341801966_qEVrssUaxg_123_431lo.jpg></a>

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

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

  • Warning Line 88, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=13e6be&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 88, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=13e6be&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 88, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=13e6be&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 88, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img210.imagevenue.com/loc96/th_4182129…

    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 88, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img210.imagevenue.com/loc96/th_4182129…

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

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

  • Error Line 88, Column 146: end tag for element "A" which is not open
    …rc=http://img210.imagevenue.com/loc96/th_418212922_SRaLtTvU4k_123_96lo.jpg></a>

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

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

  • Warning Line 89, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=49a038&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 89, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=49a038&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 89, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=49a038&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 89, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img172.imagevenue.com/loc338/th_418070…

    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 89, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img172.imagevenue.com/loc338/th_418070…

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

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

  • Error Line 89, Column 148: end tag for element "A" which is not open
    …=http://img172.imagevenue.com/loc338/th_418070471_qN1zRw6GXu_123_338lo.jpg></a>

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

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

  • Warning Line 90, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=8eaac1&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 90, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=8eaac1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 90, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=8eaac1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 90, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img40.imagevenue.com/loc175/th_4173258…

    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 90, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img40.imagevenue.com/loc175/th_4173258…

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

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

  • Error Line 90, Column 147: end tag for element "A" which is not open
    …c=http://img40.imagevenue.com/loc175/th_417325875_18wTYyZdP2_123_175lo.jpg></a>

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

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

  • Warning Line 91, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=5d8fee&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 91, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=5d8fee&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 91, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=5d8fee&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 91, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img201.imagevenue.com/loc391/th_418215…

    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 91, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img201.imagevenue.com/loc391/th_418215…

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

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

  • Error Line 91, Column 148: end tag for element "A" which is not open
    …=http://img201.imagevenue.com/loc391/th_418215977_sX5mwNe7QQ_123_391lo.jpg></a>

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

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

  • Warning Line 92, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=f3ffa4&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 92, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=f3ffa4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 92, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=f3ffa4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 92, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img254.imagevenue.com/loc246/th_418158…

    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 92, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img254.imagevenue.com/loc246/th_418158…

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

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

  • Error Line 92, Column 148: end tag for element "A" which is not open
    …=http://img254.imagevenue.com/loc246/th_418158243_RVRrwZ4Wo2_123_246lo.jpg></a>

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

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

  • Warning Line 93, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=afacf4&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 93, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=afacf4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 93, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=afacf4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 93, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img269.imagevenue.com/loc76/th_3418162…

    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 93, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img269.imagevenue.com/loc76/th_3418162…

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

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

  • Error Line 93, Column 146: end tag for element "A" which is not open
    …rc=http://img269.imagevenue.com/loc76/th_341816277_rvypri9hjj_123_76lo.jpg></a>

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

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

  • Warning Line 94, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=4cd1a1&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 94, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=4cd1a1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 94, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=4cd1a1&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 94, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img178.imagevenue.com/loc406/th_418189…

    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 94, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img178.imagevenue.com/loc406/th_418189…

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

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

  • Error Line 94, Column 148: end tag for element "A" which is not open
    …=http://img178.imagevenue.com/loc406/th_418189969_sH8jl5dmxv_123_406lo.jpg></a>

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

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

  • Warning Line 95, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=73afe3&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 95, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=73afe3&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 95, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=73afe3&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 95, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img9.imagevenue.com/loc592/th_41732330…

    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 95, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img9.imagevenue.com/loc592/th_41732330…

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

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

  • Error Line 95, Column 145: end tag for element "A" which is not open
    …src=http://img9.imagevenue.com/loc592/th_417323300_7wgboychi_123_592lo.jpg></a>

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

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

  • Warning Line 96, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=d700f6&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 96, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=d700f6&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 96, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=d700f6&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 96, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img232.imagevenue.com/loc523/th_417122…

    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 96, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img232.imagevenue.com/loc523/th_417122…

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

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

  • Error Line 96, Column 148: end tag for element "A" which is not open
    …=http://img232.imagevenue.com/loc523/th_417122234_5IOFMG0HfN_123_523lo.jpg></a>

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

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

  • Warning Line 97, Column 13: NET-enabling start-tag requires SHORTTAG YES
    <img src=dtr/count.php?gr=2 width=1 height=1>

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

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

  • Error Line 97, Column 13: required attribute "ALT" not specified
    <img src=dtr/count.php?gr=2 width=1 height=1>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 98, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=f4f24b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 98, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=f4f24b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 98, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=f4f24b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 98, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img258.imagevenue.com/loc103/th_418419…

    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 98, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img258.imagevenue.com/loc103/th_418419…

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

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

  • Error Line 98, Column 148: end tag for element "A" which is not open
    …=http://img258.imagevenue.com/loc103/th_418419903_yPdelemisy_123_103lo.jpg></a>

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

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

  • Warning Line 99, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=12c627&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 99, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=12c627&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 99, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=12c627&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 99, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img221.imagevenue.com/loc1170/th_41841…

    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 99, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img221.imagevenue.com/loc1170/th_41841…

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

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

  • Error Line 99, Column 150: end tag for element "A" which is not open
    …ttp://img221.imagevenue.com/loc1170/th_418415528_wgnZcP4lj1_123_1170lo.jpg></a>

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

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

  • Warning Line 100, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=f790b6&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 100, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=f790b6&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 100, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=f790b6&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 100, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img225.imagevenue.com/loc1128/th_41842…

    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 100, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img225.imagevenue.com/loc1128/th_41842…

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

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

  • Error Line 100, Column 150: end tag for element "A" which is not open
    …ttp://img225.imagevenue.com/loc1128/th_418421506_yZlO9rb78p_123_1128lo.jpg></a>

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

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

  • Warning Line 101, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=58845e&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 101, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=58845e&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 101, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=58845e&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 101, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img165.imagevenue.com/loc211/th_418430…

    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 101, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img165.imagevenue.com/loc211/th_418430…

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

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

  • Error Line 101, Column 148: end tag for element "A" which is not open
    …=http://img165.imagevenue.com/loc211/th_418430988_Z4hLfp7aEs_123_211lo.jpg></a>

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

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

  • Warning Line 102, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=9050a9&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 102, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=9050a9&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 102, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=9050a9&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 102, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img232.imagevenue.com/loc164/th_418435…

    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 102, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img232.imagevenue.com/loc164/th_418435…

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

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

  • Error Line 102, Column 148: end tag for element "A" which is not open
    …=http://img232.imagevenue.com/loc164/th_418435616_zmbPmaV8Kw_123_164lo.jpg></a>

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

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

  • Warning Line 103, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=d12054&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 103, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=d12054&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 103, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=d12054&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 103, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img239.imagevenue.com/loc17/th_4183931…

    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 103, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img239.imagevenue.com/loc17/th_4183931…

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

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

  • Error Line 103, Column 146: end tag for element "A" which is not open
    …rc=http://img239.imagevenue.com/loc17/th_418393138_VQJftVr0b9_123_17lo.jpg></a>

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

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

  • Warning Line 104, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=3dda22&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 104, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=3dda22&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 104, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=3dda22&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 104, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img18.imagevenue.com/loc232/th_3418391…

    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 104, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img18.imagevenue.com/loc232/th_3418391…

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

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

  • Error Line 104, Column 147: end tag for element "A" which is not open
    …c=http://img18.imagevenue.com/loc232/th_341839126_VIHujI7WJh_123_232lo.jpg></a>

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

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

  • Warning Line 105, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=6b82f2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

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

  • Error Line 105, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=6b82f2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 105, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=6b82f2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 105, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img256.imagevenue.com/loc439/th_341835…

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

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

  • Error Line 105, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img256.imagevenue.com/loc439/th_341835…

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

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

  • Error Line 105, Column 148: end tag for element "A" which is not open
    …=http://img256.imagevenue.com/loc439/th_341835225_v0qJ6219SJ_123_439lo.jpg></a>

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

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

  • Warning Line 106, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=9026c6&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 106, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=9026c6&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 106, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=9026c6&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 106, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img267.imagevenue.com/loc483/th_418004…

    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 106, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img267.imagevenue.com/loc483/th_418004…

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

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

  • Error Line 106, Column 148: end tag for element "A" which is not open
    …=http://img267.imagevenue.com/loc483/th_418004675_pFNOpVHPas_123_483lo.jpg></a>

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

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

  • Warning Line 107, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=518306&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 107, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=518306&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 107, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=518306&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 107, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img163.imagevenue.com/loc391/th_434183…

    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 107, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img163.imagevenue.com/loc391/th_434183…

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

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

  • Error Line 107, Column 148: end tag for element "A" which is not open
    …=http://img163.imagevenue.com/loc391/th_434183602_v2d9i5zH54_123_391lo.jpg></a>

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

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

  • Warning Line 108, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=8dd46e&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 108, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=8dd46e&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 108, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=8dd46e&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 108, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img228.imagevenue.com/loc113/th_418376…

    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 108, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img228.imagevenue.com/loc113/th_418376…

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

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

  • Error Line 108, Column 148: end tag for element "A" which is not open
    …=http://img228.imagevenue.com/loc113/th_418376273_vfTcnfkJc5_123_113lo.jpg></a>

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

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

  • Warning Line 109, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=a47612&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 109, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=a47612&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 109, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=a47612&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 109, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img106.imagevenue.com/loc142/th_418386…

    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 109, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img106.imagevenue.com/loc142/th_418386…

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

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

  • Error Line 109, Column 148: end tag for element "A" which is not open
    …=http://img106.imagevenue.com/loc142/th_418386827_vHiyfZwMRQ_123_142lo.jpg></a>

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

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

  • Warning Line 110, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=391d6a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 110, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=391d6a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 110, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=391d6a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 110, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img175.imagevenue.com/loc400/th_417140…

    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 110, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img175.imagevenue.com/loc400/th_417140…

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

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

  • Error Line 110, Column 148: end tag for element "A" which is not open
    …=http://img175.imagevenue.com/loc400/th_417140281_7Jvj0E3kQc_123_400lo.jpg></a>

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

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

  • Warning Line 111, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=b4c2bd&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 111, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=b4c2bd&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 111, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=b4c2bd&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 111, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img34.imagevenue.com/loc575/th_4179874…

    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 111, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img34.imagevenue.com/loc575/th_4179874…

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

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

  • Error Line 111, Column 147: end tag for element "A" which is not open
    …c=http://img34.imagevenue.com/loc575/th_417987404_oajJa9ysi9_123_575lo.jpg></a>

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

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

  • Warning Line 112, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=9f2f01&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 112, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=9f2f01&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 112, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=9f2f01&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 112, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img228.imagevenue.com/loc24/th_4176114…

    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 112, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img228.imagevenue.com/loc24/th_4176114…

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

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

  • Error Line 112, Column 146: end tag for element "A" which is not open
    …rc=http://img228.imagevenue.com/loc24/th_417611410_i6k7mgOSMj_123_24lo.jpg></a>

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

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

  • Warning Line 113, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=3fe88a&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 113, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=3fe88a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 113, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=3fe88a&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 113, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img161.imagevenue.com/loc523/th_417607…

    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 113, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img161.imagevenue.com/loc523/th_417607…

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

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

  • Error Line 113, Column 148: end tag for element "A" which is not open
    …=http://img161.imagevenue.com/loc523/th_417607962_hvXvtersyS_123_523lo.jpg></a>

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

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

  • Warning Line 114, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=3dac5c&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 114, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=3dac5c&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 114, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=3dac5c&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 114, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img34.imagevenue.com/loc202/th_4176155…

    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 114, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img34.imagevenue.com/loc202/th_4176155…

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

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

  • Error Line 114, Column 147: end tag for element "A" which is not open
    …c=http://img34.imagevenue.com/loc202/th_417615534_I224GcmsLK_123_202lo.jpg></a>

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

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

  • Warning Line 115, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=78b5b7&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 115, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=78b5b7&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 115, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=78b5b7&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 115, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img34.imagevenue.com/loc234/th_4175275…

    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 115, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img34.imagevenue.com/loc234/th_4175275…

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

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

  • Error Line 115, Column 147: end tag for element "A" which is not open
    …c=http://img34.imagevenue.com/loc234/th_417527520_eLHcvl2WnW_123_234lo.jpg></a>

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

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

  • Warning Line 116, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=907f5b&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 116, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=907f5b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 116, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=907f5b&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 116, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img14.imagevenue.com/loc458/th_4175082…

    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 116, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img14.imagevenue.com/loc458/th_4175082…

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

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

  • Error Line 116, Column 147: end tag for element "A" which is not open
    …c=http://img14.imagevenue.com/loc458/th_417508290_ecWE1djmUr_123_458lo.jpg></a>

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

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

  • Warning Line 117, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=068e47&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

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

  • Error Line 117, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=068e47&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 117, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=068e47&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 117, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img232.imagevenue.com/loc158/th_341752…

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

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

  • Error Line 117, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img232.imagevenue.com/loc158/th_341752…

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

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

  • Error Line 117, Column 148: end tag for element "A" which is not open
    …=http://img232.imagevenue.com/loc158/th_341752542_EG00NR2EL0_123_158lo.jpg></a>

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

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

  • Warning Line 118, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=f53d14&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 118, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=f53d14&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 118, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=f53d14&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 118, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img251.imagevenue.com/loc568/th_417605…

    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 118, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img251.imagevenue.com/loc568/th_417605…

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

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

  • Error Line 118, Column 148: end tag for element "A" which is not open
    …=http://img251.imagevenue.com/loc568/th_417605915_hQQPJPaPJg_123_568lo.jpg></a>

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

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

  • Warning Line 119, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=d49333&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 119, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=d49333&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 119, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=d49333&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 119, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img12.imagevenue.com/loc197/th_4175879…

    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 119, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img12.imagevenue.com/loc197/th_4175879…

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

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

  • Error Line 119, Column 147: end tag for element "A" which is not open
    …c=http://img12.imagevenue.com/loc197/th_417587935_HkHzzw9sdQ_123_197lo.jpg></a>

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

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

  • Warning Line 120, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=2b18bf&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 120, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=2b18bf&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 120, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=2b18bf&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 120, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img218.imagevenue.com/loc789/th_417544…

    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 120, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img218.imagevenue.com/loc789/th_417544…

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

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

  • Error Line 120, Column 148: end tag for element "A" which is not open
    …=http://img218.imagevenue.com/loc789/th_417544101_F1GiJa07vE_123_789lo.jpg></a>

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

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

  • Warning Line 121, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=5a6fb2&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 121, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=5a6fb2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 121, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=5a6fb2&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 121, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img229.imagevenue.com/loc480/th_417547…

    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 121, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img229.imagevenue.com/loc480/th_417547…

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

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

  • Error Line 121, Column 148: end tag for element "A" which is not open
    …=http://img229.imagevenue.com/loc480/th_417547387_FQKrV32GZ1_123_480lo.jpg></a>

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

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

  • Warning Line 122, Column 13: NET-enabling start-tag requires SHORTTAG YES
    <img src=dtr/count.php?gr=2 width=1 height=1>

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

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

  • Error Line 122, Column 13: required attribute "ALT" not specified
    <img src=dtr/count.php?gr=2 width=1 height=1>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 124, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=2cb9f5&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 124, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=2cb9f5&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 124, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=2cb9f5&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 124, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img268.imagevenue.com/loc586/th_417564…

    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 124, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img268.imagevenue.com/loc586/th_417564…

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

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

  • Error Line 124, Column 148: end tag for element "A" which is not open
    …=http://img268.imagevenue.com/loc586/th_417564113_gNYSo1h6NY_123_586lo.jpg></a>

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

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

  • Warning Line 125, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=e1f2f4&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 125, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=e1f2f4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 125, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=e1f2f4&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 125, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img25.imagevenue.com/loc60/th_41753445…

    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 125, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img25.imagevenue.com/loc60/th_41753445…

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

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

  • Error Line 125, Column 145: end tag for element "A" which is not open
    …src=http://img25.imagevenue.com/loc60/th_417534453_eoKZyt1cu3_123_60lo.jpg></a>

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

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

  • Warning Line 126, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=2c3199&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 126, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=2c3199&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 126, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=2c3199&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 126, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img102.imagevenue.com/loc434/th_417573…

    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 126, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img102.imagevenue.com/loc434/th_417573…

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

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

  • Error Line 126, Column 148: end tag for element "A" which is not open
    …=http://img102.imagevenue.com/loc434/th_417573176_GwyUZGt3WI_123_434lo.jpg></a>

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

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

  • Warning Line 127, Column 12: NET-enabling start-tag requires SHORTTAG YES
    <a href=dtr/link.php?id=7717ca&gr=2&url=/tp/out.php class=lm><img src=http://im…

    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 127, Column 34: reference to entity "gr" for which no system identifier could be generated
    <a href=dtr/link.php?id=7717ca&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 31: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Error Line 127, Column 40: reference to entity "url" for which no system identifier could be generated
    …a href=dtr/link.php?id=7717ca&gr=2&url=/tp/out.php class=lm><img src=http://im…

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

  • Info Line 40, Column 36: entity was defined here
    <a href=dtr/link.php?id=46d05b&gr=2&url=/tp/out.php class=lm><img src=http://im…
  • Warning Line 127, Column 76: NET-enabling start-tag requires SHORTTAG YES
    …rl=/tp/out.php class=lm><img src=http://img146.imagevenue.com/loc83/th_4174694…

    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 127, Column 76: required attribute "ALT" not specified
    …rl=/tp/out.php class=lm><img src=http://img146.imagevenue.com/loc83/th_4174694…

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

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

  • Error Line 127, Column 146: end tag for element "A" which is not open
    …rc=http://img146.imagevenue.com/loc83/th_417469479_c3W5KpgLwr_123_83lo.jpg></a>

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

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

  • Warning Line 128, Column 13: NET-enabling start-tag requires SHORTTAG YES
    <img src=dtr/count.php?gr=2 width=1 height=1>

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

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

  • Error Line 128, Column 13: required attribute "ALT" not specified
    <img src=dtr/count.php?gr=2 width=1 height=1>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 138, Column 36: cannot generate system identifier for general entity "link"
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>

    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 138, Column 36: general entity "link" not defined and no default entity
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>

    This is usually a cascading error caused by 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 138, Column 40: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 139, Column 46: reference to entity "link" for which no system identifier could be generated
    …='tp/out.php?to=goldhomevideo.com&link=top' class="line">2. Gold Home Video  <…

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 140, Column 43: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=bluffyporn.com&link=top' class="line">3. bluffyporn  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 141, Column 39: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=61tube.com&link=top' class="line">4. 61tube  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 142, Column 42: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=sweettube.net&link=top' class="line">5. sweettube  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 143, Column 43: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=hdteenvids.com&link=top' class="line">6. hdteenvids  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 144, Column 45: reference to entity "link" for which no system identifier could be generated
    …ef='tp/out.php?to=x-files-tube.org&link=top' class="line">7. x-files-tube  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 145, Column 48: reference to entity "link" for which no system identifier could be generated
    …tp/out.php?to=tubelovelygirls.com&link=top' class="line">8. tubelovelygirls  <…

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 146, Column 39: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=cwtube.com&link=top' class="line">9. cwtube  </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 147, Column 42: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=6teentube.com&link=top' class="line">10. 6teentube </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 150, Column 40: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=pornska.com&link=top' class="line">11. pornska </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 151, Column 52: reference to entity "link" for which no system identifier could be generated
    …/out.php?to=xvideosamateurstube.com&link=top' class="line">12. xvideosamat </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 152, Column 41: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=amokporn.com&link=top' class="line">13. Amok Porn </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 153, Column 42: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=exteensex.com&link=top' class="line">14. exteensex </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 154, Column 50: reference to entity "link" for which no system identifier could be generated
    …/out.php?to=yourporntubeclips.com&link=top' class="line">15. yourporntubeclips…

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 155, Column 43: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=amateur1st.com&link=top' class="line">16. amateur1st </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 156, Column 44: reference to entity "link" for which no system identifier could be generated
    …href='tp/out.php?to=family-tube.com&link=top' class="line">17. family-tube </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 157, Column 45: reference to entity "link" for which no system identifier could be generated
    …f='tp/out.php?to=teenbestvids.com&link=top' class="line">18. Teen Best Vids </…

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 158, Column 45: reference to entity "link" for which no system identifier could be generated
    …ef='tp/out.php?to=teensexplace.com&link=top' class="line">19. teensexplace </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 159, Column 44: reference to entity "link" for which no system identifier could be generated
    …href='tp/out.php?to=incest-news.com&link=top' class="line">20. incest-news </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 162, Column 42: reference to entity "link" for which no system identifier could be generated
    <a href='tp/out.php?to=teenfuckr.com&link=top' class="line">21. teenfuckr </a>

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

  • Info Line 138, Column 35: entity was defined here
    <a href='tp/out.php?to=ohteeny.com&link=top' class="line">1. ohteeny  </a>
  • Error Line 211, Column 6: end tag for element "DIV" which is not open
    </div>

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

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

  • Warning Line 226, Column 13: NET-enabling start-tag requires SHORTTAG YES
    		<a href=tp/trade.php class=trade>Webmasters</a>

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

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

Visitor Analysis

Daily Visitor
  • 3.500 visits
Daily Visitor