Heavy-R.com is a free porn tube. Updated with the best free porn videos every day! ...

heavy-r.com
  • Domain Name
    heavy-r.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #2588
  • Page Size
    135.4 KB
  • Ip Address
    141.101.120.204
  • Heading
    H1: 1, H2: 3, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    104 GIF, 58 JPG, 8 PNG

Website Meta Analysis

  • Title
    Free Porn Videos - Heavy-R.com
  • Meta Keyword
    porn, porn tube, porno, shocking videos, hardcore porn, sex, bizarre videos, free porn, free sex, videos
  • Meta Description
    Heavy-R.com is a free porn tube. Updated with the best free porn videos every day!

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.120.204
  • Domain Age
    3 Years, 5 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from heavy-r.com.

HTML Analysis

  • date: Wed, 08 Oct 2014 00:00:07 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze19
  • last-modified: Wed, 08 Oct 2014 00:00:07 GMT
  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • server: cloudflare-nginx
  • cf-ray: 175e0e59813610e7-ORD
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: HEAVY-R.COM
Created on: 08-Apr-10
Expires on: 08-Apr-13
Last Updated on: 16-Feb-11

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS33.DOMAINCONTROL.COM
NS34.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns33.domaincontrol.com [216.69.185.17]
ns34.domaincontrol.com [208.109.255.17]

DNS Records

Answer records
heavy-r.com A 95.211.192.86 3600s
heavy-r.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
heavy-r.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
heavy-r.com NS  ns33.domaincontrol.com 3600s
heavy-r.com NS  ns34.domaincontrol.com 3600s
heavy-r.com SOA
server: ns33.domaincontrol.com
email: dns@jomax.net
serial: 2012121400
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 141.101.120.204 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 402 Errors
  • 102 Warnings
Ratio Text/Html
  • 0.6944733044733045
Message Error
  • Warning Line 1, Column 63: no system id specified
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">

    Your document includes a DOCTYPE declaration with a public identifier (e.g. "-//W3C//DTD XHTML 1.0 Strict//EN") but no system identifier (e.g. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"). This is authorized in HTML (based on SGML), but not in XML-based languages.

    If you are using a standard XHTML document type, it is recommended to use exactly one of the DOCTYPE declarations from the recommended list on the W3C QA Website.

  • Error Line 1, Column 63: DTD did not contain element declaration for document type name
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">

    A DOCTYPE declares the version of the language used, as well as what the root (top) element of your document will be. For example, if the top element of your document is <html>, the DOCTYPE declaration will look like: "<!DOCTYPE html".

    In most cases, it is safer not to type or edit the DOCTYPE declaration at all, and preferable to let a tool include it, or copy and paste it from a trusted list of DTDs.

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

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

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

  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 8, Column 18: there is no attribute "http-equiv"
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">

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

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

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

  • Error Line 8, Column 41: there is no attribute "content"
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">

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

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

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

  • Error Line 8, Column 67: element "META" undefined
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 13, Column 83: end tag for "link" omitted, but OMITTAG NO was specified
    …nk rel="stylesheet" type="text/css" href="/themes/default/gfx/style/style.css">

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

  • Info Line 13, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/themes/default/gfx/style/style.cs…
  • Error Line 23, Column 60: required attribute "type" not specified
    <script src="http://www.heavy-r.com/js/jquery.tools.min.js"></script>

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

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

  • Error Line 29, Column 117: required attribute "type" not specified
    …/CH_HomePage.js" type="text/javascript"></script><script language='JavaScript'>

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

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

  • Error Line 39, Column 30: required attribute "type" not specified
    <script language="JavaScript">

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

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

  • Error Line 44, Column 141: end tag for "link" omitted, but OMITTAG NO was specified
    …-R - Recently Added" href="http://www.heavy-r.com/modules/rss.php?type=recent">

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

  • Info Line 44, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Recently Adde…
  • Error Line 45, Column 138: end tag for "link" omitted, but OMITTAG NO was specified
    …avy-R - Most Viewed" href="http://www.heavy-r.com/modules/rss.php?type=viewed">

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

  • Info Line 45, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Most Viewed" …
  • Error Line 46, Column 144: end tag for "link" omitted, but OMITTAG NO was specified
    …- Most Discussed" href="http://www.heavy-r.com/modules/rss.php?type=discussed">

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

  • Info Line 46, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Most Discusse…
  • Error Line 47, Column 143: end tag for "link" omitted, but OMITTAG NO was specified
    … - Top Favorites" href="http://www.heavy-r.com/modules/rss.php?type=favorites">

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

  • Info Line 47, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Top Favorites…
  • Error Line 70, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Warning Line 74, Column 13: character "<" is the first character of a delimiter but occurred as data
      for(i=0;i < 20;i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 78, Column 26: an attribute value must be a literal unless it contains only name characters
    document.write("<img src=/scj/cgi/user.php?code="+key+" width=0 height=0 style=…

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

  • Error Line 78, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=/scj/cgi/user.php?code="+key+" width=0 height=0 style='position: absolute;'/>…
  • Error Line 78, Column 72: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …scj/cgi/user.php?code="+key+" width=0 height=0 style='position: absolute;'/>");
  • Error Line 78, Column 102: required attribute "alt" not specified
    …scj/cgi/user.php?code="+key+" width=0 height=0 style='position: absolute;'/>");

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 102: document type does not allow element "img" here
    …scj/cgi/user.php?code="+key+" width=0 height=0 style='position: absolute;'/>");

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

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

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

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

  • Info Line 8, Column 1: start tag was here
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 82, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 83, Column 14: there is no attribute "onLoad"
    <body onLoad=";" style="height:100%;">

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

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

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

  • Error Line 101, Column 49: syntax of attribute value does not conform to declared value
    …href="/./index.php?page=join" target="">Sign Up</a> / <a href="index.php?page=…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 101, Column 108: end tag for element "a" which is not open
    …ef="index.php?page=join">Log In</a></a></li>			<li><a href='/directory/'>Direc…

    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 104, Column 72: required attribute "alt" not specified
    <a href="/"><img src="http://www.humoron.com/ads/logo.png" border="0" /></a> 

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

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

  • Error Line 116, Column 54: syntax of attribute value does not conform to declared value
    …rrentTab" href="/./index.php" target="">Home</a></li>		<li><a  href="/./index.…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 116, Column 119: syntax of attribute value does not conform to declared value
    …ef="/./index.php?page=videos" target="">Browse Videos</a></li>		<li><a  href="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 116, Column 180: syntax of attribute value does not conform to declared value
    …>		<li><a  href="categories/" target="">Categories</a></li>		<li><a  href="/./…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Warning Line 116, Column 242: cannot generate system identifier for general entity "section"
    …li><a  href="/./index.php?page=videos&section=upload_general" target="">Upload…

    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 116, Column 242: general entity "section" not defined and no default entity
    …li><a  href="/./index.php?page=videos&section=upload_general" target="">Upload…

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

  • Warning Line 116, Column 249: reference not terminated by REFC delimiter
    …href="/./index.php?page=videos&section=upload_general" target="">Upload</a></l…

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

  • Warning Line 116, Column 249: reference to external entity in attribute value
    …href="/./index.php?page=videos&section=upload_general" target="">Upload</a></l…

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

  • Error Line 116, Column 249: reference to entity "section" for which no system identifier could be generated
    …href="/./index.php?page=videos&section=upload_general" target="">Upload</a></l…

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

  • Info Line 116, Column 241: entity was defined here
    …<li><a  href="/./index.php?page=videos&section=upload_general" target="">Uploa…
  • Error Line 116, Column 274: syntax of attribute value does not conform to declared value
    …index.php?page=videos&section=upload_general" target="">Upload</a></li>			</ul>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 119, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="handler" value="search">

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

  • Info Line 119, Column 1: start tag was here
    <input type="hidden" name="handler" value="search">
  • Error Line 120, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="action" value="do_search">

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

  • Info Line 120, Column 1: start tag was here
    <input type="hidden" name="action" value="do_search">
  • Error Line 122, Column 256: end tag for "input" omitted, but OMITTAG NO was specified
    …'; }" onblur="if (keyword.value == '') { keyword.value = 'search for porn'; }">

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

  • Info Line 122, Column 25: start tag was here
                            <input class="textfield" type="text" size='' name="keyw…
  • Error Line 125, Column 77: there is no attribute "height"
    …src="/themes/default/gfx/search_btn.jpg" height="27" width="105"/></form></div>

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

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

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

  • Error Line 125, Column 88: there is no attribute "width"
    …src="/themes/default/gfx/search_btn.jpg" height="27" width="105"/></form></div>

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

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

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

  • Error Line 137, Column 9: there is no attribute "id"
    <DIV id=wrap>

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

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

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

  • Error Line 137, Column 9: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <DIV id=wrap>
  • Error Line 137, Column 13: element "DIV" undefined
    <DIV id=wrap>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 138, Column 15: there is no attribute "border"
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">

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

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

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

  • Error Line 138, Column 31: there is no attribute "cellSpacing"
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">

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

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

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

  • Error Line 138, Column 47: there is no attribute "cellPadding"
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">

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

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

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

  • Error Line 138, Column 57: there is no attribute "width"
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">

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

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

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

  • Error Line 138, Column 62: element "TABLE" undefined
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 139, Column 9: element "TBODY" undefined
      <TBODY>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 140, Column 6: element "TR" undefined
      <TR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 141, Column 15: there is no attribute "width"
        <TD width="1"><A class=linkph 

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

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

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

  • Error Line 141, Column 18: element "TD" undefined
        <TD width="1"><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 141, Column 28: there is no attribute "class"
        <TD width="1"><A class=linkph 

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

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

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

  • Error Line 141, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD width="1"><A class=linkph 
  • Error Line 142, Column 12: there is no attribute "href"
          href="http://www.pornhub.com/categories?utm_source=Paulzzz&utm_medium=PT&…

    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 142, Column 66: cannot generate system identifier for general entity "utm_medium"
    …hub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavy…

    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 142, Column 66: general entity "utm_medium" not defined and no default entity
    …hub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavy…

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

  • Warning Line 142, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 142, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 142, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 142, Column 80: cannot generate system identifier for general entity "utm_campaign"
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

    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 142, Column 80: general entity "utm_campaign" not defined and no default entity
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 142, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 142, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 142, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 143, Column 14: there is no attribute "target"
          target=_blank>AMATEUR</A></TD>

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

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

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

  • Error Line 143, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>AMATEUR</A></TD>
  • Error Line 143, Column 20: element "A" undefined
          target=_blank>AMATEUR</A></TD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 144, Column 8: element "TD" undefined
        <TD><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 144, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 145, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 145, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 145, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 145, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 145, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 145, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 146, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>ANAL</A></TD>
  • Error Line 146, Column 20: element "A" undefined
          target=_blank>ANAL</A></TD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 147, Column 8: element "TD" undefined
        <TD><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 147, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 148, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 148, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 148, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 148, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 148, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 148, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 149, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>BIG TITS</A></TD>
  • Error Line 149, Column 20: element "A" undefined
          target=_blank>BIG TITS</A></TD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 150, Column 8: element "TD" undefined
        <TD><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 150, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 151, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 151, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 151, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 151, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 151, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 151, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 152, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>BIG DICK</A></TD></TR>
  • Error Line 152, Column 20: element "A" undefined
          target=_blank>BIG DICK</A></TD></TR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 153, Column 14: there is no attribute "vAlign"
      <TR vAlign=top>

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

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

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

  • Error Line 153, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <TR vAlign=top>
  • Error Line 153, Column 17: element "TR" undefined
      <TR vAlign=top>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 154, Column 18: element "TD" undefined
        <TD width="1"><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 154, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD width="1"><A class=linkph 
  • Warning Line 155, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 155, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 155, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 155, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 155, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 155, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 156, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>LESBIAN</A></TD>
  • Error Line 156, Column 20: element "A" undefined
          target=_blank>LESBIAN</A></TD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 157, Column 8: element "TD" undefined
        <TD><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 157, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 158, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 158, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 158, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 158, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 158, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 158, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 159, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>HARDCORE</A></TD>
  • Error Line 159, Column 20: element "A" undefined
          target=_blank>HARDCORE</A></TD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 160, Column 8: element "TD" undefined
        <TD><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 160, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 161, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 161, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 161, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 161, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 161, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 161, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 162, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>OUTDOOR</A></TD>
  • Error Line 162, Column 20: element "A" undefined
          target=_blank>OUTDOOR</A></TD>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 163, Column 8: element "TD" undefined
        <TD><A class=linkph 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 163, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 164, Column 76: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 164, Column 76: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 164, Column 76: reference to entity "utm_medium" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 164, Column 92: reference not terminated by REFC delimiter
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Warning Line 164, Column 92: reference to external entity in attribute value
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Error Line 164, Column 92: reference to entity "utm_campaign" for which no system identifier could be generated
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 

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

  • Info Line 142, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 165, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>YOUNG</A></TD></TR>
  • Error Line 165, Column 20: element "A" undefined
          target=_blank>YOUNG</A></TD></TR>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 166, Column 8: end tag for element "tbody" which is not open
    </tbody></table>

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

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

  • Error Line 166, Column 16: end tag for element "table" which is not open
    </tbody></table>

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

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

  • Error Line 167, Column 6: end tag for "TBODY" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 139, Column 3: start tag was here
      <TBODY>
  • Error Line 167, Column 6: end tag for "TABLE" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 138, Column 1: start tag was here
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">
  • Error Line 167, Column 6: end tag for "DIV" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 137, Column 1: start tag was here
    <DIV id=wrap>
  • Error Line 193, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="handler" value="login">

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

  • Info Line 193, Column 1: start tag was here
    <input type="hidden" name="handler" value="login">
  • Error Line 194, Column 53: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="action" value="do_login">

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

  • Info Line 194, Column 1: start tag was here
    <input type="hidden" name="action" value="do_login">
  • Error Line 197, Column 134: end tag for "input" omitted, but OMITTAG NO was specified
    …textfield" type="text" size='15' name="username" value="" onfocus="" onblur="">

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

  • Info Line 197, Column 41: start tag was here
    …label for="username" >Username</label><input class="textfield" type="text" siz…
  • Error Line 200, Column 108: end tag for "input" omitted, but OMITTAG NO was specified
    …word</label><input class="textfield" type="password" size='15' name="password">

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

  • Info Line 200, Column 41: start tag was here
    …label for="password" >Password</label><input class="textfield" type="password"…
  • Error Line 203, Column 111: end tag for "input" omitted, but OMITTAG NO was specified
    …r me</label><input class="checkbox" type="checkbox" name="remember" value="1" >

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

  • Info Line 203, Column 44: start tag was here
    …el for="remember" >Remember me</label><input class="checkbox" type="checkbox" …
  • Error Line 205, Column 99: duplicate specification of attribute "name"
    …n_0" class="button" type="submit" name="submit" value="Login" onclick=""></div>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 205, Column 138: end tag for "input" omitted, but OMITTAG NO was specified
    …n_0" class="button" type="submit" name="submit" value="Login" onclick=""></div>

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

  • Info Line 205, Column 30: start tag was here
    				<div class="loginButton"><input name="login_0" id="login_0" class="button" …
  • Error Line 233, Column 197: there is no attribute "onMouseOver"
    …b931be9_1.jpg" border="0" onMouseOver="CH_StartRotateThumbnails(129346,this,'h…

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

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

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

  • Error Line 233, Column 279: there is no attribute "onMouseOut"
    …//cluster9b.heavy-r.com')" onMouseOut="CH_StopRotateThumbnails( 129346,this, '…

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

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

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

  • Error Line 289, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 286, Column 7: start tag was here
    						<span class="label">By: <a href="http://Cums.com">Cums.com</a><br />
  • Error Line 332, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 329, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.zenra.net">zenra.net</a><br />
  • Error Line 480, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 477, Column 7: start tag was here
    						<span class="label">By: <a href="http://dirty-mom.com/">dirty-mom.com</a>…
  • Error Line 502, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 499, Column 7: start tag was here
    						<span class="label">By: <a href="http://dirty-mom.com/">dirty-mom.com</a>…
  • Error Line 524, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 521, Column 7: start tag was here
    						<span class="label">By: <a href="http://dirty-mom.com/">dirty-mom.com</a>…
  • Error Line 567, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 564, Column 7: start tag was here
    						<span class="label">By: <a href="http://dirty-mom.com/">dirty-mom.com</a>…
  • Error Line 610, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 607, Column 7: start tag was here
    						<span class="label">By: <a href="http://ufym.net">ufym.net</a><br />
  • Error Line 653, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 650, Column 7: start tag was here
    						<span class="label">By: <a href="http://ufym.net">ufym.net</a><br />
  • Error Line 738, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 735, Column 7: start tag was here
    						<span class="label">By: <a href="http://ufym.net">ufym.net</a><br />
  • Error Line 749, Column 151: syntax of attribute value does not conform to declared value
    …heavy-r.com/user/dermarkus49" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 749, Column 195: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 758, Column 150: syntax of attribute value does not conform to declared value
    ….heavy-r.com/user/daniella22" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 758, Column 194: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 767, Column 150: syntax of attribute value does not conform to declared value
    ….heavy-r.com/user/dj420benny" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 767, Column 194: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 776, Column 151: syntax of attribute value does not conform to declared value
    …heavy-r.com/user/nikbarvinok" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 776, Column 195: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 785, Column 148: syntax of attribute value does not conform to declared value
    …ww.heavy-r.com/user/max250nl" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 785, Column 192: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 794, Column 145: syntax of attribute value does not conform to declared value
    …//www.heavy-r.com/user/lg911" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 794, Column 189: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 803, Column 151: syntax of attribute value does not conform to declared value
    …heavy-r.com/user/sayitaintso" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 803, Column 195: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 812, Column 147: syntax of attribute value does not conform to declared value
    …www.heavy-r.com/user/photo62" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 812, Column 191: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 821, Column 147: syntax of attribute value does not conform to declared value
    …www.heavy-r.com/user/a373516" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 821, Column 191: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 830, Column 148: syntax of attribute value does not conform to declared value
    …ww.heavy-r.com/user/buttoman" target=""><img src="/./avt/default.jpg" border="…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 830, Column 192: required attribute "alt" not specified
    …rget=""><img src="/./avt/default.jpg" border="0" /></a></div></div></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 880, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 880, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 880, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 880, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 880, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 880, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 880, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 880, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 880, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 880, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 880, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 880, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 880, Column 440: required attribute "alt" not specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 880, Column 446: end tag for "img" omitted, but OMITTAG NO was specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 880, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 917, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 917, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 917, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 917, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 917, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 917, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 917, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 917, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 917, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 917, Column 356: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 917, Column 357: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 917, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 917, Column 445: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 917, Column 451: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 917, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 954, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 954, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 954, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 954, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 954, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 954, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 954, Column 268: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 954, Column 269: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 954, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 954, Column 357: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 954, Column 358: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 954, Column 269: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 954, Column 446: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 954, Column 452: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 954, Column 358: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 991, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 991, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 991, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 991, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 991, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 991, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 991, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 991, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 991, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 991, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 991, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 991, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 991, Column 441: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 991, Column 447: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 991, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1028, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1028, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1028, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1028, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1028, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1028, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1028, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1028, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1028, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1028, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1028, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1028, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1028, Column 441: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1028, Column 447: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1028, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1065, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1065, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1065, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1065, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1065, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1065, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1065, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1065, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1065, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1065, Column 356: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1065, Column 357: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1065, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1065, Column 445: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1065, Column 451: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1065, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1102, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1102, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1102, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1102, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1102, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1102, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1102, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1102, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1102, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1102, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1102, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1102, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1102, Column 440: required attribute "alt" not specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1102, Column 446: end tag for "img" omitted, but OMITTAG NO was specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1102, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1139, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1139, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1139, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1139, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1139, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1139, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1139, Column 268: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1139, Column 269: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1139, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1139, Column 357: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1139, Column 358: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1139, Column 269: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1139, Column 446: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1139, Column 452: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1139, Column 358: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1176, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1176, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1176, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1176, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1176, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1176, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1176, Column 268: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1176, Column 269: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1176, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1176, Column 357: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1176, Column 358: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1176, Column 269: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1176, Column 446: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1176, Column 452: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1176, Column 358: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1213, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1213, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1213, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1213, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1213, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1213, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1213, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1213, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1213, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1213, Column 353: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1213, Column 354: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1213, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1213, Column 442: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1213, Column 448: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1213, Column 354: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1250, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1250, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1250, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1250, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1250, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1250, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1250, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1250, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1250, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1250, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1250, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1250, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1250, Column 444: required attribute "alt" not specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1250, Column 450: end tag for "img" omitted, but OMITTAG NO was specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1250, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1287, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1287, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1287, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1287, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1287, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1287, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1287, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1287, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1287, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1287, Column 353: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1287, Column 354: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1287, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1287, Column 442: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1287, Column 448: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1287, Column 354: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1324, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1324, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1324, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1324, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1324, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1324, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1324, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1324, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1324, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1324, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1324, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1324, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1324, Column 444: required attribute "alt" not specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1324, Column 450: end tag for "img" omitted, but OMITTAG NO was specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1324, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1361, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1361, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1361, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1361, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1361, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1361, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1361, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1361, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1361, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1361, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1361, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1361, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1361, Column 444: required attribute "alt" not specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1361, Column 450: end tag for "img" omitted, but OMITTAG NO was specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1361, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1398, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1398, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1398, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1398, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1398, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1398, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1398, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1398, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1398, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1398, Column 356: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1398, Column 357: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1398, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1398, Column 445: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1398, Column 451: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1398, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1435, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1435, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1435, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1435, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1435, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1435, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1435, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1435, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1435, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1435, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1435, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1435, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1435, Column 440: required attribute "alt" not specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1435, Column 446: end tag for "img" omitted, but OMITTAG NO was specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1435, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1472, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1472, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1472, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1472, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1472, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1472, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1472, Column 268: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1472, Column 269: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1472, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1472, Column 357: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1472, Column 358: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1472, Column 269: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1472, Column 446: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1472, Column 452: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1472, Column 358: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1509, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1509, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1509, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1509, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1509, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1509, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1509, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1509, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1509, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1509, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1509, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1509, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1509, Column 444: required attribute "alt" not specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1509, Column 450: end tag for "img" omitted, but OMITTAG NO was specified
    …gfx/icons/star_small_on_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1509, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1546, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1546, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1546, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1546, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1546, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1546, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1546, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1546, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1546, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1546, Column 352: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1546, Column 353: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1546, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1546, Column 440: required attribute "alt" not specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1546, Column 446: end tag for "img" omitted, but OMITTAG NO was specified
    …ult/gfx/icons/star_small_on.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1546, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1583, Column 88: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1583, Column 89: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1583, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1583, Column 176: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1583, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1583, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1583, Column 264: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1583, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1583, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1583, Column 353: required attribute "alt" not specified
    …gif" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1583, Column 354: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…

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

  • Info Line 1583, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1583, Column 442: required attribute "alt" not specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1583, Column 448: end tag for "img" omitted, but OMITTAG NO was specified
    …lt/gfx/icons/star_small_off.gif" width="11" height="11" border="0"></div></div>

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

  • Info Line 1583, Column 354: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Warning Line 1603, Column 74: cannot generate system identifier for general entity "type"
    …ext"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></di…

    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 1603, Column 74: general entity "type" not defined and no default entity
    …ext"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></di…

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

  • Warning Line 1603, Column 78: reference not terminated by REFC delimiter
    …xt"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></div>

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

  • Warning Line 1603, Column 78: reference to external entity in attribute value
    …xt"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></div>

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

  • Error Line 1603, Column 78: reference to entity "type" for which no system identifier could be generated
    …xt"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></div>

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

  • Info Line 1603, Column 73: entity was defined here
    …Text"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></d…
  • Error Line 1632, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="…

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

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

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

  • Error Line 1632, Column 37: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="…

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

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

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

  • Error Line 1632, Column 54: there is no attribute "MARGINHEIGHT"
    …RDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="2…

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

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

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

  • Error Line 1632, Column 68: there is no attribute "SCROLLING"
    …NWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="250" SRC="http:…

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

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

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

  • Error Line 1632, Column 79: there is no attribute "WIDTH"
    …MARGINHEIGHT="0" SCROLLING="NO" WIDTH="300" HEIGHT="250" SRC="http://a.heavy-r…

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

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

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

  • Error Line 1632, Column 92: there is no attribute "HEIGHT"
    …"0" SCROLLING="NO" WIDTH="300" HEIGHT="250" SRC="http://a.heavy-r.com/300x250-…

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

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

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

  • Error Line 1632, Column 102: there is no attribute "SRC"
    …ING="NO" WIDTH="300" HEIGHT="250" SRC="http://a.heavy-r.com/300x250-01.html"><…

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

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

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

  • Error Line 1632, Column 140: element "IFRAME" undefined
    …" WIDTH="300" HEIGHT="250" SRC="http://a.heavy-r.com/300x250-01.html"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1640, Column 140: element "IFRAME" undefined
    …" WIDTH="300" HEIGHT="250" SRC="http://a.heavy-r.com/300x250-02.html"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1648, Column 140: element "IFRAME" undefined
    …" WIDTH="300" HEIGHT="250" SRC="http://a.heavy-r.com/300x250-03.html"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1675, Column 279: required attribute "alt" not specified
    …"105" title="No Wonder It Didn't Fit!"><br><p class="plugtitle">No Wonder It D…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1675, Column 280: end tag for "img" omitted, but OMITTAG NO was specified
    …105" title="No Wonder It Didn't Fit!"><br><p class="plugtitle">No Wonder It Di…

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

  • Info Line 1675, Column 163: start tag was here
    …/out.php?group=hprod" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1675, Column 284: end tag for "br" omitted, but OMITTAG NO was specified
    … title="No Wonder It Didn't Fit!"><br><p class="plugtitle">No Wonder It Didn't…

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

  • Info Line 1675, Column 280: start tag was here
    …105" title="No Wonder It Didn't Fit!"><br><p class="plugtitle">No Wonder It Di…
  • Error Line 1675, Column 304: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … Didn't Fit!"><br><p class="plugtitle">No Wonder It Didn't Fit!</p></a></div><…

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

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

  • Warning Line 1675, Column 468: cannot generate system identifier for general entity "url"
    …k" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3Dp…

    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 1675, Column 468: general entity "url" not defined and no default entity
    …k" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3Dp…

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

  • Warning Line 1675, Column 471: reference not terminated by REFC delimiter
    …href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3Dplay…

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

  • Warning Line 1675, Column 471: reference to external entity in attribute value
    …href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3Dplay…

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

  • Error Line 1675, Column 471: reference to entity "url" for which no system identifier could be generated
    …href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3Dplay…

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

  • Info Line 1675, Column 467: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Error Line 1675, Column 660: required attribute "alt" not specified
    …"105" title="Girl Abused By In School"><br><p class="plugtitle">Girl Abused By…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1675, Column 661: end tag for "img" omitted, but OMITTAG NO was specified
    …105" title="Girl Abused By In School"><br><p class="plugtitle">Girl Abused By …

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

  • Info Line 1675, Column 541: start tag was here
    …p%3Dplay%26Id%3D1433" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1675, Column 665: end tag for "br" omitted, but OMITTAG NO was specified
    … title="Girl Abused By In School"><br><p class="plugtitle">Girl Abused By In S…

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

  • Info Line 1675, Column 661: start tag was here
    …105" title="Girl Abused By In School"><br><p class="plugtitle">Girl Abused By …
  • Error Line 1675, Column 685: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …By In School"><br><p class="plugtitle">Girl Abused By In School</p></a></div><…

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

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

  • Error Line 1675, Column 993: required attribute "alt" not specified
    …ht="105" title="Crazy Sorority Ritual"><br><p class="plugtitle">Crazy Sorority…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1675, Column 994: end tag for "img" omitted, but OMITTAG NO was specified
    …t="105" title="Crazy Sorority Ritual"><br><p class="plugtitle">Crazy Sorority …

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

  • Info Line 1675, Column 880: start tag was here
    …/out.php?group=hprod" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1675, Column 998: end tag for "br" omitted, but OMITTAG NO was specified
    …05" title="Crazy Sorority Ritual"><br><p class="plugtitle">Crazy Sorority Ritu…

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

  • Info Line 1675, Column 994: start tag was here
    …t="105" title="Crazy Sorority Ritual"><br><p class="plugtitle">Crazy Sorority …
  • Error Line 1675, Column 1018: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ority Ritual"><br><p class="plugtitle">Crazy Sorority Ritual</p></a></div></li…

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

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

  • Warning Line 1675, Column 1194: reference not terminated by REFC delimiter
    …f="/out.php?member=amateursexy.net&url=http%3A%2F%2Famateursexy.net%2Fhosted%2…

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

  • Warning Line 1675, Column 1194: reference to external entity in attribute value
    …f="/out.php?member=amateursexy.net&url=http%3A%2F%2Famateursexy.net%2Fhosted%2…

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

  • Error Line 1675, Column 1194: reference to entity "url" for which no system identifier could be generated
    …f="/out.php?member=amateursexy.net&url=http%3A%2F%2Famateursexy.net%2Fhosted%2…

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

  • Info Line 1675, Column 467: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Error Line 1675, Column 1429: required attribute "alt" not specified
    …ht="105" title="Tight Pussy Destroyed"><br><p class="plugtitle">Tight Pussy De…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1675, Column 1430: end tag for "img" omitted, but OMITTAG NO was specified
    …t="105" title="Tight Pussy Destroyed"><br><p class="plugtitle">Tight Pussy Des…

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

  • Info Line 1675, Column 1315: start tag was here
    …-of-camera%2C346.php" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1675, Column 1434: end tag for "br" omitted, but OMITTAG NO was specified
    …05" title="Tight Pussy Destroyed"><br><p class="plugtitle">Tight Pussy Destroy…

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

  • Info Line 1675, Column 1430: start tag was here
    …t="105" title="Tight Pussy Destroyed"><br><p class="plugtitle">Tight Pussy Des…
  • Error Line 1675, Column 1454: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …sy Destroyed"><br><p class="plugtitle">Tight Pussy Destroyed</p></a></div><div…

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

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

  • Error Line 1675, Column 1757: required attribute "alt" not specified
    …"105" title="Boy Shows Dick To Sister"><br><p class="plugtitle">Boy Shows Dick…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1675, Column 1758: end tag for "img" omitted, but OMITTAG NO was specified
    …105" title="Boy Shows Dick To Sister"><br><p class="plugtitle">Boy Shows Dick …

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

  • Info Line 1675, Column 1646: start tag was here
    …/out.php?group=hprod" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1675, Column 1762: end tag for "br" omitted, but OMITTAG NO was specified
    … title="Boy Shows Dick To Sister"><br><p class="plugtitle">Boy Shows Dick To S…

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

  • Info Line 1675, Column 1758: start tag was here
    …105" title="Boy Shows Dick To Sister"><br><p class="plugtitle">Boy Shows Dick …
  • Error Line 1675, Column 1782: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ck To Sister"><br><p class="plugtitle">Boy Shows Dick To Sister</p></a></div><…

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

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

  • Warning Line 1675, Column 1951: reference not terminated by REFC delimiter
    …ef="/out.php?member=motherless.com&url=http%3A%2F%2Fmotherless.com%2F2339D0D" …

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

  • Warning Line 1675, Column 1951: reference to external entity in attribute value
    …ef="/out.php?member=motherless.com&url=http%3A%2F%2Fmotherless.com%2F2339D0D" …

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

  • Error Line 1675, Column 1951: reference to entity "url" for which no system identifier could be generated
    …ef="/out.php?member=motherless.com&url=http%3A%2F%2Fmotherless.com%2F2339D0D" …

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

  • Info Line 1675, Column 467: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Error Line 1675, Column 2126: required attribute "alt" not specified
    …t="105" title="African Hooker Blowjob"><br><p class="plugtitle">African Hooker…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1675, Column 2127: end tag for "img" omitted, but OMITTAG NO was specified
    …="105" title="African Hooker Blowjob"><br><p class="plugtitle">African Hooker …

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

  • Info Line 1675, Column 2007: start tag was here
    …erless.com%2F2339D0D" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1675, Column 2131: end tag for "br" omitted, but OMITTAG NO was specified
    …5" title="African Hooker Blowjob"><br><p class="plugtitle">African Hooker Blow…

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

  • Info Line 1675, Column 2127: start tag was here
    …="105" title="African Hooker Blowjob"><br><p class="plugtitle">African Hooker …
  • Error Line 1675, Column 2151: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …oker Blowjob"><br><p class="plugtitle">African Hooker Blowjob</p></a></div></l…

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

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

  • Error Line 1691, Column 149: required attribute "alt" not specified
    …"themes/default/gfx/icons/rss.gif" border="0" width="11" height="11" /></a></p>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 1699, Column 177: cannot generate system identifier for general entity "action"
    ….heavy-r.com/index.php?handler=report&action=show_report_form" style="color: #…

    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 1699, Column 177: general entity "action" not defined and no default entity
    ….heavy-r.com/index.php?handler=report&action=show_report_form" style="color: #…

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

  • Warning Line 1699, Column 183: reference not terminated by REFC delimiter
    …-r.com/index.php?handler=report&action=show_report_form" style="color: #656565…

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

  • Warning Line 1699, Column 183: reference to external entity in attribute value
    …-r.com/index.php?handler=report&action=show_report_form" style="color: #656565…

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

  • Error Line 1699, Column 183: reference to entity "action" for which no system identifier could be generated
    …-r.com/index.php?handler=report&action=show_report_form" style="color: #656565…

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

  • Info Line 1699, Column 176: entity was defined here
    …w.heavy-r.com/index.php?handler=report&action=show_report_form" style="color: …
  • Error Line 1733, Column 34: there is no attribute "onMouseover"
    <div id="sbdropdown" onMouseover="sbStopTimer()" onMouseout="sbHide()">

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

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

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

  • Error Line 1733, Column 61: there is no attribute "onMouseout"
    <div id="sbdropdown" onMouseover="sbStopTimer()" onMouseout="sbHide()">

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

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

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

  • Error Line 1734, Column 29: there is no attribute "onClick"
    <div class="sbitem" onClick="sbAddtoFavorites(sbAddtoFavorites('http://www.heav…

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

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

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

  • Error Line 1734, Column 133: there is no attribute "onMouseOver"
    …core Videos - Heavy-R'))" onMouseOver="this.className='sbitemhighlight'" onMou…

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

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

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

  • Error Line 1734, Column 179: there is no attribute "onMouseOut"
    …assName='sbitemhighlight'" onMouseOut="this.className='sbitem'"><img src="http…

    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 1736, Column 76: reference not terminated by REFC delimiter
    …rk('http://digg.com/submit?phase=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=H…

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

  • Warning Line 1736, Column 76: reference to external entity in attribute value
    …rk('http://digg.com/submit?phase=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=H…

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

  • Error Line 1736, Column 76: reference to entity "url" for which no system identifier could be generated
    …rk('http://digg.com/submit?phase=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=H…

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

  • Info Line 1675, Column 467: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Warning Line 1736, Column 109: cannot generate system identifier for general entity "title"
    …2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onM…

    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 1736, Column 109: general entity "title" not defined and no default entity
    …2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onM…

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

  • Warning Line 1736, Column 114: reference not terminated by REFC delimiter
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Warning Line 1736, Column 114: reference to external entity in attribute value
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Error Line 1736, Column 114: reference to entity "title" for which no system identifier could be generated
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Info Line 1736, Column 108: entity was defined here
    …=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" on…
  • Warning Line 1737, Column 108: cannot generate system identifier for general entity "t"
    …jsp?u=http%3A%2F%2Fwww.heavy-r.com%2F&t=Hardcore+Videos+-+Heavy-R',1)" onMouse…

    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 1737, Column 108: general entity "t" not defined and no default entity
    …jsp?u=http%3A%2F%2Fwww.heavy-r.com%2F&t=Hardcore+Videos+-+Heavy-R',1)" onMouse…

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

  • Warning Line 1737, Column 109: reference not terminated by REFC delimiter
    …sp?u=http%3A%2F%2Fwww.heavy-r.com%2F&t=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Warning Line 1737, Column 109: reference to external entity in attribute value
    …sp?u=http%3A%2F%2Fwww.heavy-r.com%2F&t=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Error Line 1737, Column 109: reference to entity "t" for which no system identifier could be generated
    …sp?u=http%3A%2F%2Fwww.heavy-r.com%2F&t=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Info Line 1737, Column 107: entity was defined here
    ….jsp?u=http%3A%2F%2Fwww.heavy-r.com%2F&t=Hardcore+Videos+-+Heavy-R',1)" onMous…
  • Warning Line 1738, Column 120: reference not terminated by REFC delimiter
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Warning Line 1738, Column 120: reference to external entity in attribute value
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Error Line 1738, Column 120: reference to entity "title" for which no system identifier could be generated
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Info Line 1736, Column 108: entity was defined here
    …=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" on…
  • Warning Line 1739, Column 117: reference not terminated by REFC delimiter
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Warning Line 1739, Column 117: reference to external entity in attribute value
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Error Line 1739, Column 117: reference to entity "title" for which no system identifier could be generated
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Info Line 1736, Column 108: entity was defined here
    …=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" on…
  • Warning Line 1740, Column 87: cannot generate system identifier for general entity "bkmk"
    …www.google.com/bookmarks/mark?op=edit&bkmk=http%3A%2F%2Fwww.heavy-r.com%2F&tit…

    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 1740, Column 87: general entity "bkmk" not defined and no default entity
    …www.google.com/bookmarks/mark?op=edit&bkmk=http%3A%2F%2Fwww.heavy-r.com%2F&tit…

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

  • Warning Line 1740, Column 91: reference not terminated by REFC delimiter
    …google.com/bookmarks/mark?op=edit&bkmk=http%3A%2F%2Fwww.heavy-r.com%2F&title=H…

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

  • Warning Line 1740, Column 91: reference to external entity in attribute value
    …google.com/bookmarks/mark?op=edit&bkmk=http%3A%2F%2Fwww.heavy-r.com%2F&title=H…

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

  • Error Line 1740, Column 91: reference to entity "bkmk" for which no system identifier could be generated
    …google.com/bookmarks/mark?op=edit&bkmk=http%3A%2F%2Fwww.heavy-r.com%2F&title=H…

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

  • Info Line 1740, Column 86: entity was defined here
    …/www.google.com/bookmarks/mark?op=edit&bkmk=http%3A%2F%2Fwww.heavy-r.com%2F&ti…
  • Warning Line 1740, Column 129: reference not terminated by REFC delimiter
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Warning Line 1740, Column 129: reference to external entity in attribute value
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Error Line 1740, Column 129: reference to entity "title" for which no system identifier could be generated
    …=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Info Line 1736, Column 108: entity was defined here
    …=2&url=http%3A%2F%2Fwww.heavy-r.com%2F&title=Hardcore+Videos+-+Heavy-R',1)" on…
  • Warning Line 1741, Column 123: cannot generate system identifier for general entity "u"
    …okmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" o…

    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 1741, Column 123: general entity "u" not defined and no default entity
    …okmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" o…

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

  • Warning Line 1741, Column 124: reference not terminated by REFC delimiter
    …kmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" on…

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

  • Warning Line 1741, Column 124: reference to external entity in attribute value
    …kmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" on…

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

  • Error Line 1741, Column 124: reference to entity "u" for which no system identifier could be generated
    …kmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" on…

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

  • Info Line 1741, Column 122: entity was defined here
    …ookmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" …
  • Warning Line 1743, Column 103: cannot generate system identifier for general entity "Url"
    …m/index.php?Action=Blink/addblink.php&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Titl…

    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 1743, Column 103: general entity "Url" not defined and no default entity
    …m/index.php?Action=Blink/addblink.php&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Titl…

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

  • Warning Line 1743, Column 106: reference not terminated by REFC delimiter
    …ndex.php?Action=Blink/addblink.php&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Title=H…

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

  • Warning Line 1743, Column 106: reference to external entity in attribute value
    …ndex.php?Action=Blink/addblink.php&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Title=H…

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

  • Error Line 1743, Column 106: reference to entity "Url" for which no system identifier could be generated
    …ndex.php?Action=Blink/addblink.php&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Title=H…

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

  • Info Line 1743, Column 102: entity was defined here
    …om/index.php?Action=Blink/addblink.php&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Tit…
  • Warning Line 1743, Column 139: cannot generate system identifier for general entity "Title"
    …p&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Title=Hardcore+Videos+-+Heavy-R',1)" onM…

    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 1743, Column 139: general entity "Title" not defined and no default entity
    …p&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Title=Hardcore+Videos+-+Heavy-R',1)" onM…

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

  • Warning Line 1743, Column 144: reference not terminated by REFC delimiter
    …=http%3A%2F%2Fwww.heavy-r.com%2F&Title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Warning Line 1743, Column 144: reference to external entity in attribute value
    …=http%3A%2F%2Fwww.heavy-r.com%2F&Title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Error Line 1743, Column 144: reference to entity "Title" for which no system identifier could be generated
    …=http%3A%2F%2Fwww.heavy-r.com%2F&Title=Hardcore+Videos+-+Heavy-R',1)" onMouseO…

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

  • Info Line 1743, Column 138: entity was defined here
    …hp&Url=http%3A%2F%2Fwww.heavy-r.com%2F&Title=Hardcore+Videos+-+Heavy-R',1)" on…
  • Error Line 1772, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 1774, Column 86: cannot generate system identifier for general entity "prog"
    …king01.com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidt…

    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 1774, Column 86: general entity "prog" not defined and no default entity
    …king01.com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidt…

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

  • Warning Line 1774, Column 90: reference not terminated by REFC delimiter
    …01.com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=11…

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

  • Error Line 1774, Column 90: reference to entity "prog" for which no system identifier could be generated
    …01.com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=11…

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

  • Info Line 1774, Column 85: entity was defined here
    …cking01.com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWid…
  • Warning Line 1774, Column 93: cannot generate system identifier for general entity "site"
    …com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;…

    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 1774, Column 93: general entity "site" not defined and no default entity
    …com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;…

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

  • Warning Line 1774, Column 97: reference not terminated by REFC delimiter
    …aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var …

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

  • Error Line 1774, Column 97: reference to entity "site" for which no system identifier could be generated
    …aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var …

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

  • Info Line 1774, Column 92: entity was defined here
    ….com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100…
  • Warning Line 1774, Column 101: cannot generate system identifier for general entity "skin"
    …ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var popu…

    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 1774, Column 101: general entity "skin" not defined and no default entity
    …ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var popu…

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

  • Warning Line 1774, Column 105: reference not terminated by REFC delimiter
    …hp?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var popunder…

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

  • Error Line 1774, Column 105: reference to entity "skin" for which no system identifier could be generated
    …hp?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var popunder…

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

  • Info Line 1774, Column 100: entity was defined here
    …/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var pop…
  • Warning Line 1785, Column 83: cannot generate system identifier for general entity "AFNO"
    …imad/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="tex…

    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 1785, Column 83: general entity "AFNO" not defined and no default entity
    …imad/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="tex…

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

  • Warning Line 1785, Column 87: reference not terminated by REFC delimiter
    …/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/ja…

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

  • Warning Line 1785, Column 87: reference to external entity in attribute value
    …/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/ja…

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

  • Error Line 1785, Column 87: reference to entity "AFNO" for which no system identifier could be generated
    …/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/ja…

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

  • Info Line 1785, Column 82: entity was defined here
    …/imad/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="te…
  • Warning Line 1785, Column 97: cannot generate system identifier for general entity "p"
    …v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript" …

    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 1785, Column 97: general entity "p" not defined and no default entity
    …v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript" …

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

  • Warning Line 1785, Column 98: reference not terminated by REFC delimiter
    …1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript" c…

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

  • Warning Line 1785, Column 98: reference to external entity in attribute value
    …1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript" c…

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

  • Error Line 1785, Column 98: reference to entity "p" for which no system identifier could be generated
    …1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript" c…

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

  • Info Line 1785, Column 96: entity was defined here
    …-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript"…
  • Error Line 1790, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 1795, Column 53: document type does not allow element "script" here
    <script type="text/javascript" language="JavaScript"><!-- 

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

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

  • Error Line 1799, Column 17: no document element
    //--> </script> 
  • Warning Line 197, Column 14: reference to non-existent ID "username"
    	<label for="username" >Username</label><input class="textfield" type="text" si…

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 203, Column 14: reference to non-existent ID "remember"
    	<label for="remember" >Remember me</label><input class="checkbox" type="checkb…

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 200, Column 14: reference to non-existent ID "password"
    	<label for="password" >Password</label><input class="textfield" type="password…

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 65.333 visits