sweepsadvantage.com

Sweepstakes Where You Really Win Cash Prizes Every Day. Sweepstakes and Instant Win Games with Free Sweepstakes Membership. See our Winner's Circle! ...

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

Overview Info

  • Domain Name
    sweepsadvantage.com
  • Favicon
  • Alexa Rank
    #25927
  • Google Page Rank
    PR 5
  • Ip Address
    184.106.55.27
  • Page Size
    40.6 KB
  • Images
    25 GIF, 17 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 1 0 0 0

Website Meta Analysis



  • Title
    Sweepstakes Advantage - Real Daily Winners and Sweepstakes Prizes
  • Meta Keyword
    sweepstakes, contests, online sweepstakes, sweeps, prizes, giveaways, prize, instant win, win, enter to win
  • Meta Description
    Sweepstakes Where You Really Win Cash Prizes Every Day. Sweepstakes and Instant Win Games with Free Sweepstakes Membership. See our Winner's Circle!

Technical Analysis



  • Webserver
    Apache/2.2
  • Ip Address
    184.106.55.27
  • Domain Age
    15 Years, 6 Months, 23 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache/2.2
  • vary: Accept-Encoding
  • content-type: text/html; charset=UTF-8
  • content-encoding: gzip
  • date: Wed, 18 Sep 2013 20:54:56 GMT
  • content-language: en-US
  • connection: Keep-Alive
  • content-length: 7779
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Diane & Ken Carlos
2965 Dana Lane
Kissimmee, FL 34744
US
Domain Domain Name: SWEEPSADVANTAGE.COM
-

-
Administrative Contact, Technical Contact:
Carlos, Ken email
Sweepstakes Advantage
4178 Quail Wood Drive
Saint Cloud, FL 34772
US
407-791-5964

Expires: 17-Mar-2013.
Created: 18-Mar-1998.
Database Updated: 30-Oct-2011 01:33:38 EDT.
Name Servers:
NS1.WORLDNIC.COM 205.178.190.1
NS2.WORLDNIC.COM 206.188.198.1

DNS Analysis


DNS servers
dns1.stabletransit.com [69.20.95.4]
dns2.stabletransit.com [65.61.188.4]


DNS Records

Answer records
sweepsadvantage.com A 184.106.55.27 300s
sweepsadvantage.com NS  dns2.stabletransit.com 3600s
sweepsadvantage.com NS  dns1.stabletransit.com 3600s
sweepsadvantage.com MX
preference: 10
exchange: mx1.emailsrvr.com
3600s
sweepsadvantage.com MX
preference: 20
exchange: mx2.emailsrvr.com
3600s
sweepsadvantage.com TXT v=spf1 ip4:64.49.217.116 ip4:64.49.217.117 ip4:64.49.217.118 ip4:64.49.217.119 mx include:emailsrvr.com ~all 3600s
sweepsadvantage.com SOA
server: dns1.stabletransit.com
email: ipadmin@stabletransit.com
serial: 1326728845
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
3600s

Authority records

Additional records

IP 184.106.55.27 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Antonio
  • Continent Code
    78218
  • Latitude
    210
  • Longitude
    641
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 184.106.55.27"
    #
    # Use "?" to get help.
    #

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

    NetRange: 184.106.0.0 - 184.106.255.255
    CIDR: 184.106.0.0/16
    OriginAS:
    NetName: RACKS-8-NET-4
    NetHandle: NET-184-106-0-0-1
    Parent: NET-184-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2010-05-21
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-184-106-0-0-1

    OrgName: Rackspace Hosting
    OrgId: RACKS-8
    Address: 5000 Walzem Road
    City: San Antonio
    StateProv: TX
    PostalCode: 78218
    Country: US
    RegDate: 2010-03-29
    Updated: 2011-11-30
    Ref: http://whois.arin.net/rest/org/RACKS-8

    OrgTechHandle: IPADM17-ARIN
    OrgTechName: IPADMIN
    OrgTechPhone: +1-210-892-4000
    OrgTechEmail: hostmaster@rackspace.com
    OrgTechRef: http://whois.arin.net/rest/poc/IPADM17-ARIN

    OrgAbuseHandle: ABUSE45-ARIN
    OrgAbuseName: Abuse Desk
    OrgAbusePhone: +1-210-892-4000
    OrgAbuseEmail: abuse@rackspace.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE45-ARIN

    RTechHandle: IPADM17-ARIN
    RTechName: IPADMIN
    RTechPhone: +1-210-892-4000
    RTechEmail: hostmaster@rackspace.com
    RTechRef: http://whois.arin.net/rest/poc/IPADM17-ARIN

    RAbuseHandle: ABUSE45-ARIN
    RAbuseName: Abuse Desk
    RAbusePhone: +1-210-892-4000
    RAbuseEmail: abuse@rackspace.com
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE45-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
  • 300 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.705506131281558
Message Error
  • Error Line 5, Column 12: there is no attribute "NAME"
    <META NAME="Description" CONTENT="Sweepstakes Where You Really Win Cash Prizes …

    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 5, Column 34: there is no attribute "CONTENT"
    <META NAME="Description" CONTENT="Sweepstakes Where You Really Win Cash Prizes …

    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 5, Column 186: element "META" undefined
    …nstant Win Games with Free Sweepstakes Membership. See our Winner's Circle!" />

    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 6, Column 44: element "META" undefined
    <META NAME="charset" CONTENT="ISO-8859-1" />

    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 7, Column 38: element "META" undefined
    <META NAME="ROBOTS" CONTENT="NOOPD" />

    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 8, Column 49: element "META" undefined
    <META NAME="GOOGLEBOT" CONTENT="INDEX, FOLLOW" />

    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 10, Column 37: element "META" undefined
    <META NAME="ROBOTS" CONTENT="NOYDIR">

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

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

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

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

  • Error Line 45, Column 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 10, Column 1: start tag was here
    <META NAME="ROBOTS" CONTENT="NOYDIR">
  • Error Line 53, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
    …"image/sweepstakes.jpg" alt="Sweepstakes Directory" border="0"></a><br><script>

    You may 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 85: start tag was here
    … class="top_menu"><a href="index.php"><img src="image/sweepstakes.jpg" alt="Sw…
  • Error Line 53, Column 165: end tag for "br" omitted, but OMITTAG NO was specified
    …"image/sweepstakes.jpg" alt="Sweepstakes Directory" border="0"></a><br><script>

    You may 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 161: start tag was here
    …"image/sweepstakes.jpg" alt="Sweepstakes Directory" border="0"></a><br><script>
  • Error Line 53, Column 172: required attribute "type" not specified
    …"image/sweepstakes.jpg" alt="Sweepstakes Directory" border="0"></a><br><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 64, Column 10: character "<" is the first character of a delimiter but occurred as data
    if (year < 1000)

    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.
  • Warning Line 74, Column 9: character "<" is the first character of a delimiter but occurred as data
    if (daym<10)

    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 82, Column 23: document type does not allow element "small" here
    document.write("<small><font color='006600' face='Arial' size='2'><b>"+dayarray…

    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 84, Column 14: end tag for element "br" which is not open
    </script></br></td>

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

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

  • Error Line 86, Column 60: required attribute "action" not specified
    				<form method="post" name="header_form" id="header_form">

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

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

  • Error Line 86, Column 60: document type does not allow element "form" here
    				<form method="post" name="header_form" id="header_form">

    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 87, Column 24: document type does not allow element "tr" here; assuming missing "table" start-tag
                        <tr>
  • Error Line 105, Column 57: end tag for "br" omitted, but OMITTAG NO was specified
    …    <td colspan="10"  height="20"><br><center><b><font face="Arial" size="2" c…

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

  • Info Line 105, Column 53: start tag was here
    …        <td colspan="10"  height="20"><br><center><b><font face="Arial" size="…
  • Error Line 105, Column 120: end tag for "font" omitted, but OMITTAG NO was specified
    …="20"><br><center><b><font face="Arial" size="2" color="#008000"></center></td>

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

  • Info Line 105, Column 68: start tag was here
    …span="10"  height="20"><br><center><b><font face="Arial" size="2" color="#0080…
  • Error Line 105, Column 120: end tag for "b" omitted, but OMITTAG NO was specified
    …="20"><br><center><b><font face="Arial" size="2" color="#008000"></center></td>

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

  • Info Line 105, Column 65: start tag was here
    …colspan="10"  height="20"><br><center><b><font face="Arial" size="2" color="#0…
  • Error Line 106, Column 32: end tag for "table" omitted, but OMITTAG NO was specified
                        </tr></form>

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

  • Info Line 87, Column 21: start tag was here
                        <tr>
  • Error Line 107, Column 26: end tag for "table" which is not finished
                      </table></td>

    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 112, Column 50: element "STRONG" undefined
    …lign="center" height="93"><div><STRONG><FONT color=#ed1212 size=5 face=Arial>T…

    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 112, Column 63: there is no attribute "color"
    … height="93"><div><STRONG><FONT color=#ed1212 size=5 face=Arial>The Largest Di…

    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 112, Column 63: an attribute value must be a literal unless it contains only name characters
    … height="93"><div><STRONG><FONT color=#ed1212 size=5 face=Arial>The Largest Di…

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

  • Error Line 112, Column 76: there is no attribute "size"
    …<div><STRONG><FONT color=#ed1212 size=5 face=Arial>The Largest Directory of Fr…

    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 112, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …<div><STRONG><FONT color=#ed1212 size=5 face=Arial>The Largest Directory of Fr…
  • Error Line 112, Column 83: there is no attribute "face"
    …TRONG><FONT color=#ed1212 size=5 face=Arial>The Largest Directory of Free Swee…

    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 112, Column 83: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …TRONG><FONT color=#ed1212 size=5 face=Arial>The Largest Directory of Free Swee…
  • Error Line 112, Column 88: element "FONT" undefined
    …><FONT color=#ed1212 size=5 face=Arial>The Largest Directory of Free Sweepstak…

    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 116, Column 56: there is no attribute "fb:like:layout"
    <a class="addthis_button_facebook_like" fb:like:layout="button_count"></a>

    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 57: there is no attribute "g:plusone:size"
    <a class="addthis_button_google_plusone" g:plusone:size="medium"></a>

    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 124, Column 108: document type does not allow element "table" here
    …" width="750" border="0" cellspacing="0" cellpadding="0" class="tablecontent1">

    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 129, Column 35: document type does not allow element "td" here; assuming missing "tr" start-tag
                        <td height="5"></td>
  • Error Line 130, Column 24: document type does not allow element "tr" here
                        <tr>

    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 131, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
                          <td><img src="image/header.jpg" alt="" border="0"></td>

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

  • Info Line 131, Column 27: start tag was here
                          <td><img src="image/header.jpg" alt="" border="0"></td>
  • Error Line 133, Column 24: document type does not allow element "tr" here
                        <tr>

    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 137, Column 43: document type does not allow element "td" here; assuming missing "tr" start-tag
    …                        <td height="0"><center><!-- ca-pub-5861183367155090/Ma…
  • Error Line 140, Column 22: document type does not allow element "tr" here; assuming missing "table" start-tag
    </script></center><tr></td>
  • Error Line 140, Column 27: "tr" not finished but containing element ended
    </script></center><tr></td>
  • Error Line 140, Column 27: end tag for "tr" omitted, but OMITTAG NO was specified
    </script></center><tr></td>

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

  • Info Line 140, Column 19: start tag was here
    </script></center><tr></td>
  • Error Line 140, Column 27: end tag for "table" omitted, but OMITTAG NO was specified
    </script></center><tr></td>

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

  • Info Line 140, Column 19: start tag was here
    </script></center><tr></td>
  • Error Line 143, Column 25: end tag for "td" omitted, but OMITTAG NO was specified
                        </tr>

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

  • Info Line 134, Column 23: start tag was here
                          <td class="left_center_bg">
  • Error Line 144, Column 24: document type does not allow element "tr" here
                        <tr>

    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 149, Column 24: document type does not allow element "tr" here
                        <tr>

    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 152, Column 24: document type does not allow element "tr" here
                        <tr>

    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 155, Column 24: document type does not allow element "tr" here
                        <tr>

    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 158, Column 24: document type does not allow element "tr" here
                        <tr>

    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 161, Column 24: document type does not allow element "tr" here
                        <tr>

    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 164, Column 24: document type does not allow element "tr" here
                        <tr>

    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 167, Column 25: document type does not allow element "tr" here
                         <tr>

    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 170, Column 24: document type does not allow element "tr" here
                        <tr>

    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 173, Column 24: document type does not allow element "tr" here
                        <tr>

    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 176, Column 24: document type does not allow element "tr" here
                        <tr>

    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 179, Column 24: document type does not allow element "tr" here
                        <tr>

    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 182, Column 24: document type does not allow element "tr" here
                        <tr>

    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 185, Column 24: document type does not allow element "tr" here
                        <tr>

    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 188, Column 24: document type does not allow element "tr" here
                        <tr>

    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 191, Column 24: document type does not allow element "tr" here
                        <tr>

    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 194, Column 24: document type does not allow element "tr" here
                        <tr>

    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 197, Column 24: document type does not allow element "tr" here
                        <tr>

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

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

  • Error Line 235, Column 56: there is no attribute "charset"
    …Form Generator 3.0 --><SCRIPT charset="utf-8" type="text/javascript" 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 235, Column 69: there is no attribute "type"
    …r 3.0 --><SCRIPT charset="utf-8" type="text/javascript" src="http://ws.amazon.…

    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 235, Column 91: there is no attribute "src"
    …et="utf-8" type="text/javascript" src="http://ws.amazon.com/widgets/q?rt=tf_sw…

    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 235, Column 132: cannot generate system identifier for general entity "ServiceVersion"
    …tp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&I…

    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 235, Column 132: general entity "ServiceVersion" not defined and no default entity
    …tp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&I…

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

  • Warning Line 235, Column 146: reference not terminated by REFC delimiter
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US…

    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 235, Column 146: reference to external entity in attribute value
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US…

    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 235, Column 146: reference to entity "ServiceVersion" for which no system identifier could be generated
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US…

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

  • Info Line 235, Column 131: entity was defined here
    …ttp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&…
  • Warning Line 235, Column 156: cannot generate system identifier for general entity "MarketPlace"
    …ts/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstak…

    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 235, Column 156: general entity "MarketPlace" not defined and no default entity
    …ts/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstak…

    This is usually a cascading error caused by 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 235, Column 167: reference not terminated by REFC delimiter
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/800…

    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 235, Column 167: reference to external entity in attribute value
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/800…

    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 235, Column 167: reference to entity "MarketPlace" for which no system identifier could be generated
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/800…

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

  • Info Line 235, Column 155: entity was defined here
    …ets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepsta…
  • Warning Line 235, Column 171: cannot generate system identifier for general entity "ID"
    …erviceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/8002/5a…

    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 235, Column 171: general entity "ID" not defined and no default entity
    …erviceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/8002/5a…

    This is usually a cascading error caused by 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 235, Column 173: reference not terminated by REFC delimiter
    …viceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/8002/5ab9…

    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 235, Column 173: reference to external entity in attribute value
    …viceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/8002/5ab9…

    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 235, Column 173: reference to entity "ID" for which no system identifier could be generated
    …viceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/8002/5ab9…

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

  • Info Line 235, Column 170: entity was defined here
    …ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/sweepstakesad-20/8002/5…
  • Error Line 235, Column 246: element "SCRIPT" undefined
    …stakesad-20/8002/5ab90bc0-094b-43f4-a157-65ffda1834fc"> </SCRIPT></center></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 237, Column 24: document type does not allow element "tr" here
                        <tr>

    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 249, Column 24: document type does not allow element "tr" here
                        <tr>

    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 252, Column 26: end tag for "tr" omitted, but OMITTAG NO was specified
                      </table></td>

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

  • Info Line 237, Column 21: start tag was here
                        <tr>
  • Error Line 252, Column 26: end tag for "tr" omitted, but OMITTAG NO was specified
                      </table></td>

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

  • Info Line 129, Column 21: start tag was here
                        <td height="5"></td>
  • Error Line 254, Column 36: document type does not allow element "td" here; assuming missing "tr" start-tag
    				<td height="210" align="center"><link href="css/style.css" rel="stylesheet"…
  • Error Line 254, Column 82: document type does not allow element "link" here
    …	<td height="210" align="center"><link href="css/style.css" rel="stylesheet" />

    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 255, Column 120: there is no attribute "background"
    …"0" class="tablecontent1"  background="image/winners_circle_2c_544x204.jpg" he…

    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 255, Column 165: there is no attribute "height"
    …winners_circle_2c_544x204.jpg" height="204" width="549" style="background-repe…

    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 255, Column 177: duplicate specification of attribute "width"
    …le_2c_544x204.jpg" height="204" width="549" style="background-repeat:no-repeat…

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

  • Error Line 260, Column 388: end tag for "br" omitted, but OMITTAG NO was specified
    …day...</font></a> | 1-26-13 <br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 260, Column 378: start tag was here
    …mple Saturday...</font></a> | 1-26-13 <br></font></b><b><font face='Arial' siz…
  • Error Line 260, Column 646: end tag for "br" omitted, but OMITTAG NO was specified
    … Win!!</font></a> | 1-26-13 <br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 260, Column 636: start tag was here
    …First Trip Win!!</font></a> | 1-26-13 <br></font></b><b><font face='Arial' siz…
  • Error Line 260, Column 974: end tag for "br" omitted, but OMITTAG NO was specified
    … Xb...</font></a> | 1-26-13 <br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 260, Column 964: start tag was here
    …n - Won an Xb...</font></a> | 1-26-13 <br></font></b><b><font face='Arial' siz…
  • Error Line 260, Column 1225: end tag for "br" omitted, but OMITTAG NO was specified
    …win...</font></a> | 1-27-13 <br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 260, Column 1215: start tag was here
    …0'>Quaker win...</font></a> | 1-27-13 <br></font></b><b><font face='Arial' siz…
  • Error Line 260, Column 1479: end tag for "br" omitted, but OMITTAG NO was specified
    …ze='2'color='#000000'>Wheels of Fire!</font></a> | 1-27-13 <br></font></b></tr>

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

  • Info Line 260, Column 1469: start tag was here
    …ze='2'color='#000000'>Wheels of Fire!</font></a> | 1-27-13 <br></font></b></tr>
  • Error Line 260, Column 1488: end tag for "td" omitted, but OMITTAG NO was specified
    …ze='2'color='#000000'>Wheels of Fire!</font></a> | 1-27-13 <br></font></b></tr>

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

  • Info Line 260, Column 29: start tag was here
                                <td class="center_heading2" align="left" style="pad…
  • Error Line 262, Column 33: required attribute "type" not specified
                              <style>

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

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

  • Error Line 262, Column 33: document type does not allow element "style" here
                              <style>

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

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

  • Error Line 267, Column 36: document type does not allow element "center" here; missing one of "th", "td" start-tag
                                <center><td align="center" valign="bottom" halign="…

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

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

  • Error Line 267, Column 79: there is no attribute "halign"
    …align="center" valign="bottom" halign="left"><a href="http://www.sweepsadvanta…

    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 267, Column 85: document type does not allow element "td" here
    …"center" valign="bottom" halign="left"><a href="http://www.sweepsadvantage.com…

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

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

  • Warning Line 267, Column 159: cannot generate system identifier for general entity "f"
    ….com/forum/newthread.php?do=newthread&f=11" target="_blank"><font face="Arial"…

    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 267, Column 159: general entity "f" not defined and no default entity
    ….com/forum/newthread.php?do=newthread&f=11" target="_blank"><font face="Arial"…

    This is usually a cascading error caused by 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 267, Column 160: reference not terminated by REFC delimiter
    …com/forum/newthread.php?do=newthread&f=11" target="_blank"><font face="Arial" …

    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 267, Column 160: reference to external entity in attribute value
    …com/forum/newthread.php?do=newthread&f=11" target="_blank"><font face="Arial" …

    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 267, Column 160: reference to entity "f" for which no system identifier could be generated
    …com/forum/newthread.php?do=newthread&f=11" target="_blank"><font face="Arial" …

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

  • Info Line 267, Column 158: entity was defined here
    …e.com/forum/newthread.php?do=newthread&f=11" target="_blank"><font face="Arial…
  • Error Line 267, Column 253: character ";" not allowed in attribute specification list
    …"#000000" style="text-decoration:none";>Post a Win</font></a></div></center><b…
  • Error Line 267, Column 281: end tag for element "div" which is not open
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

    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 267, Column 290: end tag for "td" omitted, but OMITTAG NO was specified
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

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

  • Info Line 267, Column 37: start tag was here
                                <center><td align="center" valign="bottom" halign="…
  • Error Line 267, Column 294: document type does not allow element "br" here; missing one of "th", "td" start-tag
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

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

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

  • Error Line 267, Column 298: end tag for element "a" which is not open
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

    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 267, Column 298: end tag for "br" omitted, but OMITTAG NO was specified
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

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

  • Info Line 267, Column 291: start tag was here
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>
  • Error Line 267, Column 298: character data is not allowed here
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 267, Column 303: "tr" not finished but containing element ended
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>
  • Error Line 267, Column 303: end tag for "tr" omitted, but OMITTAG NO was specified
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

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

  • Info Line 261, Column 27: start tag was here
                              <tr>
  • Error Line 267, Column 303: end tag for "table" omitted, but OMITTAG NO was specified
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

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

  • Info Line 255, Column 23: start tag was here
                          <table width="100%" border="0" cellspacing="0" cellpaddin…
  • Error Line 267, Column 312: end tag for element "center" which is not open
    …xt-decoration:none";>Post a Win</font></a></div></center><br></a></td></center>

    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 278, Column 68: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                <td class="center_table_middle"><table width=97% cellspacing=3>
  • Error Line 278, Column 70: an attribute value must be a literal unless it contains only name characters
    …                <td class="center_table_middle"><table width=97% cellspacing=3>

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

  • Error Line 278, Column 84: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                <td class="center_table_middle"><table width=97% cellspacing=3>
  • Error Line 279, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <tr><td width=50% valign=top>
  • Error Line 279, Column 17: an attribute value must be a literal unless it contains only name characters
    <tr><td width=50% valign=top>

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

  • Error Line 279, Column 26: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <tr><td width=50% valign=top>
  • Error Line 280, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="daily-sweepstakes.html" class…

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

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

  • Error Line 280, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="daily-sweepstakes.html" class=…

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

  • Info Line 280, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 280, Column 102: there is no attribute "HREF"
    …s/default/images/folder.gif'> <A HREF="daily-sweepstakes.html" class="innerlin…

    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 280, Column 133: there is no attribute "class"
    …'> <A HREF="daily-sweepstakes.html" class="innerlink" title="Daily">Daily</A>  

    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 280, Column 151: there is no attribute "title"
    …'> <A HREF="daily-sweepstakes.html" class="innerlink" title="Daily">Daily</A>  

    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 280, Column 158: element "A" undefined
    …'> <A HREF="daily-sweepstakes.html" class="innerlink" title="Daily">Daily</A>  

    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 283, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 283, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="daily-ongoing-sweepstakes.htm…

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

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

  • Error Line 283, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="daily-ongoing-sweepstakes.html…

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

  • Info Line 283, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 283, Column 174: element "A" undefined
    …g-sweepstakes.html" class="innerlink" title="Daily Ongoing">Daily Ongoing</A>  

    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 286, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 286, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="unlimited-entry-sweepstakes.h…

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

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

  • Error Line 286, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="unlimited-entry-sweepstakes.ht…

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

  • Info Line 286, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 286, Column 178: element "A" undefined
    …eepstakes.html" class="innerlink" title="Unlimited Entry">Unlimited Entry</A>  

    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 289, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 289, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="24-hour-entry-sweepstakes.htm…

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

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

  • Error Line 289, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="24-hour-entry-sweepstakes.html…

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

  • Info Line 289, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 289, Column 174: element "A" undefined
    …y-sweepstakes.html" class="innerlink" title="24 Hour Entry">24 Hour Entry</A>  

    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 292, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 292, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="instant-win-sweepstakes.html"…

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

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

  • Error Line 292, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="instant-win-sweepstakes.html" …

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

  • Info Line 292, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 292, Column 170: element "A" undefined
    …t-win-sweepstakes.html" class="innerlink" title="Instant Win">Instant Win</A>  

    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 295, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 295, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="weekly-sweepstakes.html" clas…

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

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

  • Error Line 295, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="weekly-sweepstakes.html" class…

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

  • Info Line 295, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 295, Column 160: element "A" undefined
    …<A HREF="weekly-sweepstakes.html" class="innerlink" title="Weekly">Weekly</A>  

    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 298, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 298, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="monthly-sweepstakes.html" cla…

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

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

  • Error Line 298, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="monthly-sweepstakes.html" clas…

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

  • Info Line 298, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 298, Column 162: element "A" undefined
    …HREF="monthly-sweepstakes.html" class="innerlink" title="Monthly">Monthly</A>  

    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 301, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 301, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="one-entry-sweepstakes.html" c…

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

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

  • Error Line 301, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="one-entry-sweepstakes.html" cl…

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

  • Info Line 301, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 301, Column 166: element "A" undefined
    …one-entry-sweepstakes.html" class="innerlink" title="One Entry">One Entry</A>  

    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 304, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

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

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

  • Error Line 304, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="one-entry-ongoing-sweepstakes…

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

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

  • Error Line 304, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="one-entry-ongoing-sweepstakes.…

    You may 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 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 304, Column 180: element "A" undefined
    …eepstakes.html" class="innerlink" title="1 Entry Ongoing">1 Entry Ongoing</A>  

    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 307, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 307, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="odd-entry-sweepstakes.html" c…

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

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

  • Error Line 307, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="odd-entry-sweepstakes.html" cl…

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

  • Info Line 307, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 307, Column 166: element "A" undefined
    …odd-entry-sweepstakes.html" class="innerlink" title="Odd Entry">Odd Entry</A>  

    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 310, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

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

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

  • Error Line 310, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="postal-mail-sweepstakes.html"…

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

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

  • Error Line 310, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="postal-mail-sweepstakes.html" …

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

  • Info Line 310, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 310, Column 170: element "A" undefined
    …-mail-sweepstakes.html" class="innerlink" title="Postal Mail">Postal Mail</A>  

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 313, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 313, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="uk-competitions.html" class="…

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

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

  • Error Line 313, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="uk-competitions.html" class="i…

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

  • Info Line 313, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 313, Column 166: element "A" undefined
    …petitions.html" class="innerlink" title="UK Competitions">UK Competitions</A>  

    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 316, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

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

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

  • Error Line 316, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="canada-sweepstakes.html" clas…

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

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

  • Error Line 316, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="canada-sweepstakes.html" class…

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

  • Info Line 316, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 316, Column 160: element "A" undefined
    …<A HREF="canada-sweepstakes.html" class="innerlink" title="Canada">Canada</A>  

    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 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 316, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 313, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 310, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 307, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

    You may 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 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 301, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 298, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 295, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 292, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 289, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 286, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 283, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 319, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 280, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 321, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=50% valign=top>
  • Error Line 321, Column 13: an attribute value must be a literal unless it contains only name characters
    <td width=50% valign=top>

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

  • Error Line 321, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td width=50% valign=top>
  • Error Line 322, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="dvd-giveaway.html" class="inn…

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

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

  • Error Line 322, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="dvd-giveaway.html" class="inne…

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

  • Info Line 322, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 322, Column 151: element "A" undefined
    …older.gif'> <A HREF="dvd-giveaway.html" class="innerlink" title="DVD">DVD</A>  

    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 325, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 325, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="cd-giveaway.html" class="inne…

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

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

  • Error Line 325, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="cd-giveaway.html" class="inner…

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

  • Info Line 325, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 325, Column 149: element "A" undefined
    …s/folder.gif'> <A HREF="cd-giveaway.html" class="innerlink" title="CD">CD</A>  

    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 328, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 328, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="kids-sweepstakes.html" class=…

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

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

  • Error Line 328, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="kids-sweepstakes.html" class="…

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

  • Info Line 328, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 328, Column 156: element "A" undefined
    …gif'> <A HREF="kids-sweepstakes.html" class="innerlink" title="Kids">Kids</A>  

    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 331, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 331, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="book-giveaway.html" class="in…

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

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

  • Error Line 331, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="book-giveaway.html" class="inn…

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

  • Info Line 331, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 331, Column 153: element "A" undefined
    …er.gif'> <A HREF="book-giveaway.html" class="innerlink" title="Book">Book</A>  

    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 334, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 334, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="twitter-contest.html" class="…

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

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

  • Error Line 334, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="twitter-contest.html" class="i…

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

  • Info Line 334, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 334, Column 166: element "A" undefined
    …r-contest.html" class="innerlink" title="Twitter Contest">Twitter Contest</A>  

    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 337, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 337, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="facebook-contest.html" class=…

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

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

  • Error Line 337, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="facebook-contest.html" class="…

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

  • Info Line 337, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 337, Column 160: element "A" undefined
    … HREF="facebook-contest.html" class="innerlink" title="Facebook">Facebook</A>  

    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 340, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 340, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="blog-giveaway.html" class="in…

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

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

  • Error Line 340, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="blog-giveaway.html" class="inn…

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

  • Info Line 340, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 340, Column 154: element "A" undefined
    ….gif'> <A HREF="blog-giveaway.html" class="innerlink" title="Blogs">Blogs</A>  

    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 343, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 343, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="sweepstakes-tools" class="inn…

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

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

  • Error Line 343, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="sweepstakes-tools" class="inne…

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

  • Info Line 343, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 343, Column 153: element "A" undefined
    …r.gif'> <A HREF="sweepstakes-tools" class="innerlink" title="Tools">Tools</A>  

    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 346, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 346, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="pinterest.html" class="innerl…

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

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

  • Error Line 346, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="pinterest.html" class="innerli…

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

  • Info Line 346, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 346, Column 154: element "A" undefined
    …'> <A HREF="pinterest.html" class="innerlink" title="Pinterest">Pinterest</A>  

    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 349, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 349, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="lotto-station.html" class="in…

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

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

  • Error Line 349, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="lotto-station.html" class="inn…

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

  • Info Line 349, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 349, Column 162: element "A" undefined
    …lotto-station.html" class="innerlink" title="Lotto Station">Lotto Station</A>  

    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 352, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 352, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="survey.html" class="innerlink…

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

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

  • Error Line 352, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="survey.html" class="innerlink"…

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

  • Info Line 352, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 352, Column 148: element "A" undefined
    …older.gif'> <A HREF="survey.html" class="innerlink" title="Survey">Survey</A>  

    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 355, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …='padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.…

    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 355, Column 92: required attribute "alt" not specified
    …src='themes/default/images/folder.gif'> <A HREF="coupon.html" class="innerlink…

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

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

  • Error Line 355, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …rc='themes/default/images/folder.gif'> <A HREF="coupon.html" class="innerlink"…

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

  • Info Line 355, Column 49: start tag was here
    …'padding-left:5px;' class='innerlink'><img src='themes/default/images/folder.g…
  • Error Line 355, Column 149: element "A" undefined
    …der.gif'> <A HREF="coupon.html" class="innerlink" title="Coupons">Coupons</A>  

    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 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 355, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 352, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 349, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 346, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 343, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 340, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 337, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 334, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 331, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 328, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 325, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 358, Column 5: end tag for "p" omitted, but OMITTAG NO was specified
    </td>

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

  • Info Line 322, Column 1: start tag was here
    <p  style='padding-left:5px;' class='innerlink'><img src='themes/default/images…
  • Error Line 455, Column 31: end tag for "table" omitted, but OMITTAG NO was specified
                      </table></td>

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

  • Info Line 49, Column 9: start tag was here
        <td><table width="100%" border="0" cellspacing="0" cellpadding="0" class="t…
  • Error Line 457, Column 25: end tag for element "td" which is not open
                </table></td>

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

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

  • Error Line 458, Column 13: end tag for element "tr" which is not open
            </tr>

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

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

  • Error Line 459, Column 12: document type does not allow element "tr" here; assuming missing "table" start-tag
            <tr>
  • Error Line 460, Column 83: end tag for "font" omitted, but OMITTAG NO was specified
    … <td height="2"><center><font face="Arial"><font size="2"></font></center></td>

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

  • Info Line 460, Column 34: start tag was here
              <td height="2"><center><font face="Arial"><font size="2"></font></cen…
  • Error Line 463, Column 46: document type does not allow element "link" here
    <link href="css/style.css" rel="stylesheet" />

    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 464, Column 30: document type does not allow element "center" here
                          <center><table align="center" width="100%" border="0" cel…

    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 466, Column 84: an attribute specification must start with a name or name token
    …_heading2" align="center" height="50" "float:right"><b>Latest Sweeepstakes Top…

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

  • Error Line 469, Column 72: an attribute specification must start with a name or name token
    …lass="center_heading2" align="center" "float:right"><b><font face='Arial' size…

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

  • Error Line 469, Column 338: end tag for "br" omitted, but OMITTAG NO was specified
    … Laptop Winner...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 328: start tag was here
    …weepstakes Laptop Winner...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 585: end tag for "br" omitted, but OMITTAG NO was specified
    …akes Mega Trip...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 575: start tag was here
    …ue Sweepstakes Mega Trip...</font></a><br></font></b><b><font face='Arial' siz…
  • Warning Line 469, Column 787: cannot generate system identifier for general entity "R"
    …ace='Arial' size='2'color='#000000'>H&R Block DreamFund Sweepstakes Winner and…

    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 469, Column 787: general entity "R" not defined and no default entity
    …ace='Arial' size='2'color='#000000'>H&R Block DreamFund Sweepstakes Winner and…

    This is usually a cascading error caused by 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 469, Column 788: reference not terminated by REFC delimiter
    …ce='Arial' size='2'color='#000000'>H&R Block DreamFund Sweepstakes Winner and …

    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 469, Column 788: reference to entity "R" for which no system identifier could be generated
    …ce='Arial' size='2'color='#000000'>H&R Block DreamFund Sweepstakes Winner and …

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

  • Info Line 469, Column 786: entity was defined here
    …face='Arial' size='2'color='#000000'>H&R Block DreamFund Sweepstakes Winner an…
  • Error Line 469, Column 856: end tag for "br" omitted, but OMITTAG NO was specified
    …inner and More...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 846: start tag was here
    …epstakes Winner and More...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 1107: end tag for "br" omitted, but OMITTAG NO was specified
    … 20K SA Winner...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 1097: start tag was here
    …stakes and 20K SA Winner...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 1360: end tag for "br" omitted, but OMITTAG NO was specified
    …ds Sweepstakes...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 1350: start tag was here
    …yCokeRewards Sweepstakes...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 1610: end tag for "br" omitted, but OMITTAG NO was specified
    …ewing Comments...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 1600: start tag was here
    …000000'>Viewing Comments...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 1976: end tag for "br" omitted, but OMITTAG NO was specified
    … Specified Yet...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 1966: start tag was here
    …o End Date Specified Yet...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 2270: end tag for "br" omitted, but OMITTAG NO was specified
    …me vote please...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 2260: start tag was here
    …k - One time vote please...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 2577: end tag for "br" omitted, but OMITTAG NO was specified
    …other Question...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 2567: start tag was here
    …se, and Another Question...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 2836: end tag for "br" omitted, but OMITTAG NO was specified
    …cret Win rec'd...</font></a><br></font></b><b><font face='Arial' size='2'color…

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

  • Info Line 469, Column 2826: start tag was here
    …toria's Secret Win rec'd...</font></a><br></font></b><b><font face='Arial' siz…
  • Error Line 469, Column 3142: end tag for "br" omitted, but OMITTAG NO was specified
    …d Toe Heart of Gold -- Daily (2/21/13) will RTF!</font></a><br></font></b></tr>

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

  • Info Line 469, Column 3132: start tag was here
    …d Toe Heart of Gold -- Daily (2/21/13) will RTF!</font></a><br></font></b></tr>
  • Error Line 469, Column 3151: end tag for "td" omitted, but OMITTAG NO was specified
    …d Toe Heart of Gold -- Daily (2/21/13) will RTF!</font></a><br></font></b></tr>

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

  • Info Line 469, Column 29: start tag was here
                                <td class="center_heading2" align="center" "float:r…
  • Error Line 471, Column 33: required attribute "type" not specified
                              <style>

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

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

  • Error Line 471, Column 33: document type does not allow element "style" here
                              <style>

    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 477, Column 31: end tag for "tr" which is not finished
                              </tr>

    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 478, Column 107: document type does not allow element "table" here
    …ble></center><table width="735" cellpadding="0" cellspacing="0" align="center">

    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 481, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
        <br>

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

  • Info Line 481, Column 5: start tag was here
        <br>
  • Error Line 482, Column 16: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        <h1><center><font face="Arial"><font size="2"></center></h1>

    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 482, Column 59: end tag for "font" omitted, but OMITTAG NO was specified
        <h1><center><font face="Arial"><font size="2"></center></h1>

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

  • Info Line 482, Column 36: start tag was here
        <h1><center><font face="Arial"><font size="2"></center></h1>
  • Error Line 482, Column 59: end tag for "font" omitted, but OMITTAG NO was specified
        <h1><center><font face="Arial"><font size="2"></center></h1>

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

  • Info Line 482, Column 17: start tag was here
        <h1><center><font face="Arial"><font size="2"></center></h1>
  • Error Line 487, Column 285: end tag for "br" omitted, but OMITTAG NO was specified
    …lic entry notes. Enter to Win our contests and giveaways for that Cash!<br><br>

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

  • Info Line 487, Column 281: start tag was here
    …lic entry notes. Enter to Win our contests and giveaways for that Cash!<br><br>
  • Error Line 487, Column 289: end tag for "br" omitted, but OMITTAG NO was specified
    …lic entry notes. Enter to Win our contests and giveaways for that Cash!<br><br>

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

  • Info Line 487, Column 285: start tag was here
    …lic entry notes. Enter to Win our contests and giveaways for that Cash!<br><br>
  • Error Line 488, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    	</td>

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

  • Info Line 487, Column 5: start tag was here
        <p>Speed up your entry by using our new free Sweeps Pop tool. Check off you…
  • Error Line 488, Column 6: end tag for "div" omitted, but OMITTAG NO was specified
    	</td>

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

  • Info Line 480, Column 6: start tag was here
    	<td><div align="left" style="margin-left: 5px; margin-right: 5px">
  • Error Line 491, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  • Error Line 492, Column 6: document type does not allow element "html" here
    <html><head></head><body>

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

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

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

    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 492, Column 19: end tag for "head" which is not finished
    <html><head></head><body>

    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 495, Column 28: end tag for "br" omitted, but OMITTAG NO was specified
          </center> </div> <br>

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

  • Info Line 495, Column 24: start tag was here
          </center> </div> <br>
  • Error Line 507, Column 68: there is no attribute "allign"
    …"><table class="tablecontent1" allign="center" border="0" cellpadding="0" cell…

    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 524, Column 11: end tag for "tr" which is not finished
          </tr>

    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 552, Column 39: end tag for element "font" which is not open
    } catch(err) {}</script><center></font><br>

    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 552, Column 44: end tag for "br" omitted, but OMITTAG NO was specified
    } catch(err) {}</script><center></font><br>

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

  • Info Line 552, Column 40: start tag was here
    } catch(err) {}</script><center></font><br>
  • Error Line 553, Column 89: end tag for element "script" which is not open
    …ll>Sweepstakes Advantage Copyright © 1997-2013</small></font></center></script>

    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 554, Column 15: end tag for "table" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 459, Column 9: start tag was here
            <tr>
  • Error Line 554, Column 15: end tag for "body" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 46, Column 1: start tag was here
    <body class="Main">
  • Error Line 554, Column 15: end tag for "html" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 4.433 visits

In Page Analysis