heavy-r.com

heavy-r.com has Alexa Rank 2.977 and Google Page Rank is 3

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 08:54:06  (update).

Overview Info

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

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.206.46
  • Domain Age
    3 Years, 5 Months, 28 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

  • server: cloudflare-nginx
  • date: Tue, 17 Sep 2013 08:54:02 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze14
  • last-modified: Tue, 17 Sep 2013 08:54:02 GMT
  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • vary: Accept-Encoding
  • cf-ray: af491c686c8059d
  • 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 108.162.206.46 Analysis

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

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

    NetRange: 108.162.192.0 - 108.162.255.255
    CIDR: 108.162.192.0/18
    OriginAS: AS13335
    NetName: CLOUDFLARENET
    NetHandle: NET-108-162-192-0-1
    Parent: NET-108-0-0-0-0
    NetType: Direct Assignment
    Comment: http://www.cloudflare.com
    RegDate: 2011-10-28
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-108-162-192-0-1

    OrgName: CloudFlare, Inc.
    OrgId: CLOUD14
    Address: 665 Third Street #207
    City: San Francisco
    StateProv: CA
    PostalCode: 94107
    Country: US
    RegDate: 2010-07-09
    Updated: 2013-01-04
    Comment: http://www.cloudflare.com/
    Ref: http://whois.arin.net/rest/org/CLOUD14

    OrgTechHandle: ADMIN2521-ARIN
    OrgTechName: Admin
    OrgTechPhone: +1-650-319-8930
    OrgTechEmail: admin@cloudflare.com
    OrgTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    OrgNOCHandle: NOC11962-ARIN
    OrgNOCName: NOC
    OrgNOCPhone: +1-650-319-8930
    OrgNOCEmail: noc@cloudflare.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    OrgAbuseHandle: ABUSE2916-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-650-319-8930
    OrgAbuseEmail: abuse@cloudflare.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    RAbuseHandle: ABUSE2916-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-650-319-8930
    RAbuseEmail: abuse@cloudflare.com
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    RNOCHandle: NOC11962-ARIN
    RNOCName: NOC
    RNOCPhone: +1-650-319-8930
    RNOCEmail: noc@cloudflare.com
    RNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    RTechHandle: ADMIN2521-ARIN
    RTechName: Admin
    RTechPhone: +1-650-319-8930
    RTechEmail: admin@cloudflare.com
    RTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 382 Errors
  • 78 Warnings
Ratio Text/Html
  • 0.6978857113214119
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 17, 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 17, 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 17, 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 22, 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 22, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/themes/default/gfx/style/style.cs…
  • Error Line 32, 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 38, 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 48, 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 53, 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 53, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Recently Adde…
  • Error Line 54, 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 54, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Most Viewed" …
  • Error Line 55, 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 55, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Most Discusse…
  • Error Line 56, 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 56, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" title="Heavy-R - Top Favorites…
  • Error Line 79, 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 83, 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 87, 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 87, 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 87, 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 87, 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 87, 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 99, 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 17, Column 1: start tag was here
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 99, 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 100, 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 118, 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 118, 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 121, 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 133, 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 133, 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 133, 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 133, 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 133, 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 133, 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 133, 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 133, 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 133, Column 241: entity was defined here
    …<li><a  href="/./index.php?page=videos&section=upload_general" target="">Uploa…
  • Error Line 133, 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 136, 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 136, Column 1: start tag was here
    <input type="hidden" name="handler" value="search">
  • Error Line 137, 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 137, Column 1: start tag was here
    <input type="hidden" name="action" value="do_search">
  • Error Line 139, 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 139, Column 25: start tag was here
                            <input class="textfield" type="text" size='' name="keyw…
  • Error Line 142, 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 142, 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 154, 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 154, Column 9: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <DIV id=wrap>
  • Error Line 154, 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 155, 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 155, 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 155, 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 155, 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 155, 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 156, 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 157, 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 158, 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 158, 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 158, 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 158, 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 159, 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 159, 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 159, 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 159, 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 159, 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 159, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 159, 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 159, 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 159, 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 159, 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 159, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 160, 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 160, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>AMATEUR</A></TD>
  • Error Line 160, 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 161, 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 161, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 162, 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 162, 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 162, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 162, 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 162, 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 162, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 163, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>ANAL</A></TD>
  • Error Line 163, 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 164, 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 164, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 165, 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 165, 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 165, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 165, 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 165, 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 165, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 166, 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 166, 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 167, 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 167, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 168, 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 168, 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 168, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 168, 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 168, 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 168, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 169, 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 169, 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 170, 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 170, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <TR vAlign=top>
  • Error Line 170, 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 171, 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 171, 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 172, 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 172, 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 172, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 172, 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 172, 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 172, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 173, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>LESBIAN</A></TD>
  • Error Line 173, 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 174, 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 174, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 175, 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 175, 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 175, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 175, 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 175, 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 175, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 176, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>HARDCORE</A></TD>
  • Error Line 176, 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 177, 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 177, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 178, 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 178, 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 178, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 178, 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 178, 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 178, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 179, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          target=_blank>OUTDOOR</A></TD>
  • Error Line 179, 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 180, 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 180, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <TD><A class=linkph 
  • Warning Line 181, 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 181, 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 181, 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 159, Column 65: entity was defined here
    …nhub.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheav…
  • Warning Line 181, 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 181, 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 181, 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 159, Column 79: entity was defined here
    …b.com/categories?utm_source=Paulzzz&utm_medium=PT&utm_campaign=Pauluzzzheavyr" 
  • Error Line 182, 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 182, 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 183, 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 183, 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 184, 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 156, Column 3: start tag was here
      <TBODY>
  • Error Line 184, 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 155, Column 1: start tag was here
    <TABLE border="0" cellSpacing="0" cellPadding="0" width="450">
  • Error Line 184, 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 154, Column 1: start tag was here
    <DIV id=wrap>
  • Error Line 210, 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 210, Column 1: start tag was here
    <input type="hidden" name="handler" value="login">
  • Error Line 211, 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 211, Column 1: start tag was here
    <input type="hidden" name="action" value="do_login">
  • Error Line 214, 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 214, Column 41: start tag was here
    …label for="username" >Username</label><input class="textfield" type="text" siz…
  • Error Line 217, 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 217, Column 41: start tag was here
    …label for="password" >Password</label><input class="textfield" type="password"…
  • Error Line 220, 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 220, Column 44: start tag was here
    …el for="remember" >Remember me</label><input class="checkbox" type="checkbox" …
  • Error Line 222, 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 222, 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 222, Column 30: start tag was here
    				<div class="loginButton"><input name="login_0" id="login_0" class="button" …
  • Error Line 250, Column 192: there is no attribute "onMouseOver"
    …d9cbd20_1.jpg" border="0" onMouseOver="CH_StartRotateThumbnails(129913,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 250, Column 274: there is no attribute "onMouseOut"
    …//cluster1a.heavy-r.com')" onMouseOut="CH_StopRotateThumbnails( 129913,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 285, 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 282, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.animedgirl.com">animedgirl.co…
  • Error Line 307, 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 304, Column 7: start tag was here
    						<span class="label">By: <a href="http://ufym.net">ufym.net</a><br />
  • Error Line 350, 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 347, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.humoron.com">humoron.com</a><…
  • Error Line 372, 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 369, Column 7: start tag was here
    						<span class="label">By: <a href="http://freecams5.com">freecams5.com</a><…
  • Error Line 394, 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 391, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.interlust.com">interlust.com<…
  • Error Line 479, 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 476, Column 7: start tag was here
    						<span class="label">By: <a href="http://v.gd/voyeur">v.gd</a><br />
  • Error Line 522, 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 519, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.superzooi.com">superzooi.com<…
  • Error Line 586, 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 583, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.superzooi.com">superzooi.com<…
  • Error Line 608, 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 605, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.sangrento.com">sangrento.com<…
  • Error Line 651, 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 648, Column 7: start tag was here
    						<span class="label">By: <a href="http://v.gd/voyeur">v.gd</a><br />
  • Error Line 673, 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 670, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.sangrento.com">sangrento.com<…
  • Error Line 695, 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 692, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.amatvideos.org/">amatvideos.o…
  • Error Line 717, 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 714, Column 7: start tag was here
    						<span class="label">By: <a href="http://www.amatvideos.org/">amatvideos.o…
  • Error Line 770, Column 176: required attribute "alt" not specified
    …_blank"><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 780, Column 148: syntax of attribute value does not conform to declared value
    …ww.heavy-r.com/user/bharakat" 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 780, 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 789, Column 203: required attribute "alt" not specified
    …"/./avt/7a/ec/57/7aec57bda75142f.gif" 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 799, Column 150: syntax of attribute value does not conform to declared value
    ….heavy-r.com/user/colcaperss" 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 799, 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 808, Column 151: syntax of attribute value does not conform to declared value
    …heavy-r.com/user/babaloobaba" 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 808, 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 817, Column 152: syntax of attribute value does not conform to declared value
    …eavy-r.com/user/johnryan1951" 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 817, Column 196: 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 826, Column 150: syntax of attribute value does not conform to declared value
    ….heavy-r.com/user/hisfsthomo" 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 826, 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 835, Column 150: syntax of attribute value does not conform to declared value
    ….heavy-r.com/user/rickyblack" 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 835, 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 844, Column 148: syntax of attribute value does not conform to declared value
    …ww.heavy-r.com/user/john1987" 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 844, 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 853, Column 146: syntax of attribute value does not conform to declared value
    …/www.heavy-r.com/user/123456" 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 853, Column 190: 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 903, 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 903, 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 903, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 903, 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 903, 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 903, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 903, 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 903, 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 903, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 903, 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 903, 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 903, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 903, 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 903, 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 903, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 940, 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 940, 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 940, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 940, 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 940, 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 940, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 940, 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 940, 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 940, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 940, 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 940, 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 940, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 940, 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 940, 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 940, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 977, 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 977, 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 977, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 977, 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 977, 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 977, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 977, 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 977, 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 977, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 977, 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 977, 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 977, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 977, 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 977, 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 977, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1014, 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 1014, 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 1014, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1014, 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 1014, 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 1014, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1014, 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 1014, 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 1014, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1014, 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 1014, 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 1014, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1014, 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 1014, 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 1014, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1051, Column 89: 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 1051, Column 90: 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 1051, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_off.gif" width="11" height="11" b…
  • Error Line 1051, Column 178: 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 1051, Column 179: 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 1051, Column 90: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1051, Column 267: 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 1051, Column 268: 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 1051, Column 179: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1051, 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 1051, 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 1051, Column 268: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1051, 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 1051, 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 1051, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1088, 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 1088, 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 1088, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1088, 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 1088, 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 1088, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1088, 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 1088, 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 1088, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1088, 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 1088, 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 1088, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1088, 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 1088, 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 1088, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1125, 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 1125, 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 1125, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1125, 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 1125, 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 1125, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1125, 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 1125, 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 1125, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1125, 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 1125, 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 1125, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1125, 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 1125, 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 1125, Column 354: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1162, 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 1162, 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 1162, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1162, 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 1162, 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 1162, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1162, 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 1162, 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 1162, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1162, 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 1162, 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 1162, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1162, 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 1162, 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 1162, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1199, 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 1199, 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 1199, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1199, 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 1199, 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 1199, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1199, 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 1199, 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 1199, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1199, 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 1199, 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 1199, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1199, 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 1199, 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 1199, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1236, 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 1236, 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 1236, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1236, 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 1236, 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 1236, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1236, 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 1236, 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 1236, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1236, 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 1236, 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 1236, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1236, 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 1236, 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 1236, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1273, 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 1273, 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 1273, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1273, 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 1273, 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 1273, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1273, 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 1273, 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 1273, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1273, 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 1273, 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 1273, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1273, 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 1273, 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 1273, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1310, 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 1310, 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 1310, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1310, 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 1310, 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 1310, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1310, 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 1310, 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 1310, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1310, 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 1310, 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 1310, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1310, 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 1310, 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 1310, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1347, 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 1347, 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 1347, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1347, 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 1347, 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 1347, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1347, 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 1347, 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 1347, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1347, 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 1347, 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 1347, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1347, 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 1347, 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 1347, Column 357: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1384, 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 1384, 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 1384, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1384, 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 1384, 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 1384, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1384, 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 1384, 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 1384, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1384, 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 1384, 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 1384, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1384, 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 1384, 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 1384, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1421, 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 1421, 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 1421, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1421, 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 1421, 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 1421, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1421, 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 1421, 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 1421, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1421, 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 1421, 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 1421, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1421, 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 1421, 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 1421, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1458, 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 1458, 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 1458, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1458, 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 1458, 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 1458, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1458, 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 1458, 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 1458, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1458, 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 1458, 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 1458, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1458, 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 1458, 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 1458, Column 354: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1495, 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 1495, 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 1495, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1495, 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 1495, 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 1495, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1495, 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 1495, 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 1495, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1495, 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 1495, 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 1495, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1495, 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 1495, 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 1495, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1532, 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 1532, 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 1532, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1532, 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 1532, 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 1532, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1532, 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 1532, 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 1532, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1532, 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 1532, 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 1532, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1532, 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 1532, 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 1532, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1569, 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 1569, 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 1569, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1569, 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 1569, 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 1569, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1569, 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 1569, 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 1569, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1569, 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 1569, 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 1569, Column 265: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1569, 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 1569, 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 1569, Column 353: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1606, 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 1606, 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 1606, Column 1: start tag was here
    <img src="themes/default/gfx/icons/star_small_on.gif" width="11" height="11" bo…
  • Error Line 1606, 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 1606, 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 1606, Column 89: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1606, 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 1606, 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 1606, Column 177: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1606, 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 1606, 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 1606, Column 269: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Error Line 1606, 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 1606, 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 1606, Column 358: start tag was here
    …if" width="11" height="11" border="0"><img src="themes/default/gfx/icons/star_…
  • Warning Line 1626, 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 1626, 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 1626, 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 1626, 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 1626, 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 1626, Column 73: entity was defined here
    …Text"><a href="./index.php?page=videos&type=featured">View More &raquo;</a></d…
  • Error Line 1655, 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 1655, 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 1655, 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 1655, 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 1655, 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 1655, 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 1655, 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 1655, 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 1663, 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 1671, 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 1698, Column 279: required attribute "alt" not specified
    … height="105" title="Drunk Public Sex"><br><p class="plugtitle">Drunk Public S…

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

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

  • Error Line 1698, Column 280: end tag for "img" omitted, but OMITTAG NO was specified
    …height="105" title="Drunk Public Sex"><br><p class="plugtitle">Drunk Public Se…

    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 1698, Column 174: start tag was here
    …ublic_sex/drunk.html" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1698, Column 284: end tag for "br" omitted, but OMITTAG NO was specified
    …ht="105" title="Drunk Public Sex"><br><p class="plugtitle">Drunk Public Sex</p…

    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 1698, Column 280: start tag was here
    …height="105" title="Drunk Public Sex"><br><p class="plugtitle">Drunk Public Se…
  • Error Line 1698, Column 304: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …k Public Sex"><br><p class="plugtitle">Drunk Public Sex</p></a></div><div clas…

    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 1698, Column 606: 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 1698, Column 607: 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 1698, Column 490: start tag was here
    …/out.php?group=hprod" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1698, Column 611: 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 1698, Column 607: start tag was here
    …105" title="No Wonder It Didn't Fit!"><br><p class="plugtitle">No Wonder It Di…
  • Error Line 1698, Column 631: 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 1698, Column 794: 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 1698, Column 794: 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 1698, Column 797: 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 1698, Column 797: 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 1698, Column 797: 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 1698, Column 793: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Error Line 1698, Column 986: 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 1698, Column 987: 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 1698, Column 867: start tag was here
    …p%3Dplay%26Id%3D1433" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1698, Column 991: 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 1698, Column 987: start tag was here
    …105" title="Girl Abused By In School"><br><p class="plugtitle">Girl Abused By …
  • Error Line 1698, Column 1011: 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 1698, Column 1327: 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 1698, Column 1328: 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 1698, Column 1214: start tag was here
    …/out.php?group=hprod" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1698, Column 1332: 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 1698, Column 1328: start tag was here
    …t="105" title="Crazy Sorority Ritual"><br><p class="plugtitle">Crazy Sorority …
  • Error Line 1698, Column 1352: 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><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 1698, Column 1518: 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 1698, Column 1518: 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 1698, Column 1518: 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 1698, Column 793: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Error Line 1698, Column 1753: 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 1698, Column 1754: 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 1698, Column 1639: start tag was here
    …-of-camera%2C346.php" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1698, Column 1758: 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 1698, Column 1754: start tag was here
    …t="105" title="Tight Pussy Destroyed"><br><p class="plugtitle">Tight Pussy Des…
  • Error Line 1698, Column 1778: 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 1698, Column 2080: 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 1698, Column 2081: 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 1698, Column 1969: start tag was here
    …/out.php?group=hprod" target="_blank"><img src="http://www.heavy-r.com/scr/plu…
  • Error Line 1698, Column 2085: 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 1698, Column 2081: start tag was here
    …105" title="Boy Shows Dick To Sister"><br><p class="plugtitle">Boy Shows Dick …
  • Error Line 1698, Column 2105: 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>").

  • Error Line 1714, 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 1722, 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 1722, 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 1722, 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 1722, 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 1722, 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 1722, Column 176: entity was defined here
    …w.heavy-r.com/index.php?handler=report&action=show_report_form" style="color: …
  • Error Line 1757, 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 1757, 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 1758, 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 1758, 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 1758, 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 1760, 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 1760, 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 1760, 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 1698, Column 793: entity was defined here
    …nk" href="/out.php?member=daftporn.com&url=http%3A%2F%2Fdaftporn.com%2F%3Fp%3D…
  • Warning Line 1760, 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 1760, 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 1760, 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 1760, 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 1760, 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 1760, 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 1761, 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 1761, 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 1761, 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 1761, 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 1761, 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 1761, 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 1762, 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 1762, 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 1762, 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 1760, 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 1763, 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 1763, 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 1763, 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 1760, 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 1764, 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 1764, 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 1764, 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 1764, 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 1764, 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 1764, 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 1764, 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 1764, 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 1764, 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 1760, 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 1765, 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 1765, 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 1765, 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 1765, 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 1765, 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 1765, Column 122: entity was defined here
    …ookmarklet?t=Hardcore+Videos+-+Heavy-R&u=http%3A%2F%2Fwww.heavy-r.com%2F',1)" …
  • Warning Line 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1767, 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 1796, 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 1798, 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 1798, 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 1798, 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 1798, 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 1798, Column 85: entity was defined here
    …cking01.com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWid…
  • Warning Line 1798, 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 1798, 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 1798, 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 1798, 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 1798, Column 92: entity was defined here
    ….com/aff/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100…
  • Warning Line 1798, 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 1798, 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 1798, 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 1798, 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 1798, Column 100: entity was defined here
    …/ep.php?act=200268:pops&prog=2&site=90&skin=c4";var popunderWidth=1100;var pop…
  • Warning Line 1809, 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 1809, 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 1809, 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 1809, 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 1809, 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 1809, Column 82: entity was defined here
    …/imad/imad-san-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="te…
  • Warning Line 1809, 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 1809, 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 1809, 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 1809, 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 1809, 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 1809, Column 96: entity was defined here
    …-v1.js?domain=streev.com&AFNO=1-525252&p=heavyrnetwork" type="text/javascript"…
  • Error Line 1814, 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 1819, 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 1823, Column 17: no document element
    //--> </script> 
  • Warning Line 214, 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 220, 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 217, 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

In Page Analysis