Daily Media, Humor, Shocking Videos, Rape Videos, slaughter, disturbing videos adult content please be aware. ...

theync.com
  • Domain Name
    theync.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #7005
  • Page Size
    77.2 KB
  • Ip Address
    66.55.146.75
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    30 GIF, 0 JPG, 5 PNG

Website Meta Analysis

  • Title
    Daily Media, Humor, Shocking, News Videos | theYNC.com
  • Meta Keyword
  • Meta Description
    Daily Media, Humor, Shocking Videos, Rape Videos, slaughter, disturbing videos adult content please be aware.

Technical Analysis

  • Webserver
    nginx/1.4.1
  • Ip Address
    66.55.146.75
  • Domain Age
    7 Years, 10 Months, 9 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.4.1
  • date: Tue, 13 Aug 2013 00:58:03 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 11965
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: private, no-cache, no-store, proxy-revalidate, no-transform
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
Domain Domain Name: THEYNC.COM
Created: 14-Oct-05
Expires: 14-Oct-14
Updated: 03-Aug-10
Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax - (480) 624-2598
Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax - (480) 624-2598
Name Servers:
NS31.DOMAINCONTROL.COM
NS32.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns31.domaincontrol.com [216.69.185.16]
ns32.domaincontrol.com [208.109.255.16]

DNS Records

Answer records
theync.com A 66.55.146.69 3600s
theync.com MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.com
3600s
theync.com MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.com
3600s
theync.com MX
preference: 10
exchange: ASPMX.L.GOOGLE.com
3600s
theync.com MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.com
3600s
theync.com MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.com
3600s
theync.com MX
preference: 30
exchange: ASPMX4.GOOGLEMAIL.com
3600s
theync.com MX
preference: 30
exchange: ASPMX5.GOOGLEMAIL.com
3600s
theync.com NS  ns32.domaincontrol.com 3600s
theync.com NS  ns31.domaincontrol.com 3600s
theync.com TXT google-site-verification=s85DaSIGRLVdA1e_2PRj3FEl1co6MImHLJQqzL62eKI 3600s
theync.com SOA
server: ns31.domaincontrol.com
email: dns@jomax.net
serial: 2012121000
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 66.55.146.75 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 56 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.6726840314235474
Message Error
  • Error Line 8, Column 72: required attribute "type" not specified
    …cript src="http://cdn.jquerytools.org/1.2.7/full/jquery.tools.min.js"></script>

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

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

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

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

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

  • Error Line 28, Column 146: end tag for "meta" omitted, but OMITTAG NO was specified
    …eos, Rape Videos, slaughter, disturbing videos adult content please be aware.">

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

  • Info Line 28, Column 1: start tag was here
    <meta name="description" content="Daily Media, Humor, Shocking Videos, Rape Vid…
  • Error Line 29, Column 348: end tag for "meta" omitted, but OMITTAG NO was specified
    …, rape, suicide, murder, suicide, fight, hand chopped off, rapist, dead girls">

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

  • Info Line 29, Column 1: start tag was here
    <meta name="keywords" content="extreme content, shocking content, shocking vide…
  • Error Line 41, Column 103: there is no attribute "allowtransparency"
    …90" frameborder="0" allowtransparency="true" marginheight="0" marginwidth="0" …

    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 44, Column 67: there is no attribute "onMouseDown"
    …or:#FFFFFF;"><a  href="#" onMouseDown="addBookmark('www.theync.com','http://ww…

    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 49, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 106, Column 8: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li><a href="/out.php?url=extremefuse.com" target="_blank" rel="nofollow">E…

    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 107, Column 5: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
     <li><a href="http://www.iloveinterracial.com" target="_blank" rel="nofollow">I…

    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 108, Column 5: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
     <li><a href="http://bit.ly/yDwMiT" target="_new"  rel="nofollow">Dating</a></l…

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

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

  • Error Line 110, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
       <li><a href="#" 

    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 122, Column 27: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li style="height: 28px;"><a href="/uploads.php">Upload</a></li>

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

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

  • Error Line 123, Column 39: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="hed" style="height: 28px;"><a href="/underground-options.php">Under…

    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 124, Column 18: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	<li class="last"><a href="/forum/">Forums</a></li>

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

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

  • Error Line 126, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 98, Column 1: start tag was here
    <li><a href="#" 
  • Error Line 132, Column 54: required attribute "alt" not specified
    <img src="/images/banner_ync.jpg" style="float:left;">

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

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

  • Error Line 132, Column 55: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="/images/banner_ync.jpg" style="float:left;">

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

  • Info Line 132, Column 1: start tag was here
    <img src="/images/banner_ync.jpg" style="float:left;">
  • Error Line 135, Column 38: required attribute "type" not specified
            <script language="javascript">

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

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

  • Error Line 177, Column 25: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    		<td width="100" nowrap></td>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 178, Column 60: cannot generate system identifier for general entity "totalRows_objects"
    …<a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fon…

    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 178, Column 60: general entity "totalRows_objects" not defined and no default entity
    …<a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fon…

    This is usually a cascading error caused by 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 178, Column 77: reference not terminated by REFC delimiter
    …hp?pageNum_objects=0&totalRows_objects=12094" class="fs"><font color="red"><em…

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

  • Warning Line 178, Column 77: reference to external entity in attribute value
    …hp?pageNum_objects=0&totalRows_objects=12094" class="fs"><font color="red"><em…

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

  • Error Line 178, Column 77: reference to entity "totalRows_objects" for which no system identifier could be generated
    …hp?pageNum_objects=0&totalRows_objects=12094" class="fs"><font color="red"><em…

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 180, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=1&totalRows_objects=12094" class="f"><em>2</em></a>

    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 180, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=1&totalRows_objects=12094" class="f"><em>2</em></a>

    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 180, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=1&totalRows_objects=12094" class="f"><em>2</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 182, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=2&totalRows_objects=12094" class="f"><em>3</em></a>

    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 182, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=2&totalRows_objects=12094" class="f"><em>3</em></a>

    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 182, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=2&totalRows_objects=12094" class="f"><em>3</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 184, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=3&totalRows_objects=12094" class="f"><em>4</em></a>

    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 184, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=3&totalRows_objects=12094" class="f"><em>4</em></a>

    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 184, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=3&totalRows_objects=12094" class="f"><em>4</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 186, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=4&totalRows_objects=12094" class="f"><em>5</em></a>

    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 186, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=4&totalRows_objects=12094" class="f"><em>5</em></a>

    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 186, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=4&totalRows_objects=12094" class="f"><em>5</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 188, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=5&totalRows_objects=12094" class="f"><em>6</em></a>

    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 188, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=5&totalRows_objects=12094" class="f"><em>6</em></a>

    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 188, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=5&totalRows_objects=12094" class="f"><em>6</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 190, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=6&totalRows_objects=12094" class="f"><em>7</em></a>

    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 190, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=6&totalRows_objects=12094" class="f"><em>7</em></a>

    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 190, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=6&totalRows_objects=12094" class="f"><em>7</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 192, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=7&totalRows_objects=12094" class="f"><em>8</em></a>

    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 192, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=7&totalRows_objects=12094" class="f"><em>8</em></a>

    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 192, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=7&totalRows_objects=12094" class="f"><em>8</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 194, Column 62: reference not terminated by REFC delimiter
    ….php?pageNum_objects=8&totalRows_objects=12094' class='f'><em>...</em></a></td>

    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 194, Column 62: reference to external entity in attribute value
    ….php?pageNum_objects=8&totalRows_objects=12094' class='f'><em>...</em></a></td>

    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 194, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    ….php?pageNum_objects=8&totalRows_objects=12094' class='f'><em>...</em></a></td>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Error Line 195, Column 39: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    		<td width="100" align="right" nowrap>          <a href="/index.php?pageNum_ob…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 195, Column 105: reference not terminated by REFC delimiter
    …hp?pageNum_objects=1&totalRows_objects=12094" class="fr"><em>next &raquo;</em>…

    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 195, Column 105: reference to external entity in attribute value
    …hp?pageNum_objects=1&totalRows_objects=12094" class="fr"><em>next &raquo;</em>…

    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 195, Column 105: reference to entity "totalRows_objects" for which no system identifier could be generated
    …hp?pageNum_objects=1&totalRows_objects=12094" class="fr"><em>next &raquo;</em>…

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Error Line 199, Column 813: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 934: cannot generate system identifier for general entity "time"
    …f-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");</…

    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 199, Column 934: general entity "time" not defined and no default entity
    …f-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");</…

    This is usually a cascading error caused by 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 199, Column 938: reference not terminated by REFC delimiter
    …man-dressed-for-her-final-viewing&time=1361689115","commentcount32187");</scri…

    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 199, Column 938: reference to entity "time" for which no system identifier could be generated
    …man-dressed-for-her-final-viewing&time=1361689115","commentcount32187");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 1856: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 1977: reference not terminated by REFC delimiter
    …e-is-dressed-up-for-final-viewing&time=1361689115","commentcount32188");</scri…

    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 199, Column 1977: reference to entity "time" for which no system identifier could be generated
    …e-is-dressed-up-for-final-viewing&time=1361689115","commentcount32188");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 2756: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 2852: reference not terminated by REFC delimiter
    …?name=teenagers-beheaded-by-zetas&time=1361689115","commentcount32193");</scri…

    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 199, Column 2852: reference to entity "time" for which no system identifier could be generated
    …?name=teenagers-beheaded-by-zetas&time=1361689115","commentcount32193");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 3753: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 3870: reference not terminated by REFC delimiter
    …-fingers-chopped-n-then-beheaded-&time=1361689115","commentcount32183");</scri…

    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 199, Column 3870: reference to entity "time" for which no system identifier could be generated
    …-fingers-chopped-n-then-beheaded-&time=1361689115","commentcount32183");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 4659: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 4760: reference not terminated by REFC delimiter
    …=how-to-curl-your-hair-gone-wrong&time=1361689115","commentcount32184");</scri…

    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 199, Column 4760: reference to entity "time" for which no system identifier could be generated
    …=how-to-curl-your-hair-gone-wrong&time=1361689115","commentcount32184");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 6390: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 6487: reference not terminated by REFC delimiter
    …name=subway-sex-caught-on-cameraa&time=1361689115","commentcount32168");</scri…

    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 199, Column 6487: reference to entity "time" for which no system identifier could be generated
    …name=subway-sex-caught-on-cameraa&time=1361689115","commentcount32168");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 8064: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 8159: reference not terminated by REFC delimiter
    …p?name=dead-fubar-horrid-accident&time=1361689115","commentcount32181");</scri…

    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 199, Column 8159: reference to entity "time" for which no system identifier could be generated
    …p?name=dead-fubar-horrid-accident&time=1361689115","commentcount32181");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 10765: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 10872: reference not terminated by REFC delimiter
    …ese-girl-invents-a-sexier-bikini-&time=1361689115","commentcount32045");</scri…

    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 199, Column 10872: reference to entity "time" for which no system identifier could be generated
    …ese-girl-invents-a-sexier-bikini-&time=1361689115","commentcount32045");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 12454: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 12543: reference not terminated by REFC delimiter
    …jax.php?name=bomb-blast-sends-him&time=1361689115","commentcount32182");</scri…

    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 199, Column 12543: reference to entity "time" for which no system identifier could be generated
    …jax.php?name=bomb-blast-sends-him&time=1361689115","commentcount32182");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 14760: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 14863: reference not terminated by REFC delimiter
    …unatic-husband-runs-over-attacker&time=1361689115","commentcount32152");</scri…

    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 199, Column 14863: reference to entity "time" for which no system identifier could be generated
    …unatic-husband-runs-over-attacker&time=1361689115","commentcount32152");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 15698: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 15799: reference not terminated by REFC delimiter
    …=burned-to-a-crisp-motorcycle-acc&time=1361689115","commentcount32163");</scri…

    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 199, Column 15799: reference to entity "time" for which no system identifier could be generated
    …=burned-to-a-crisp-motorcycle-acc&time=1361689115","commentcount32163");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 16640: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 16733: reference not terminated by REFC delimiter
    …php?name=kid-falls-off-a-ski-lift&time=1361689115","commentcount32157");</scri…

    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 199, Column 16733: reference to entity "time" for which no system identifier could be generated
    …php?name=kid-falls-off-a-ski-lift&time=1361689115","commentcount32157");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 17507: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 17607: reference not terminated by REFC delimiter
    …e=first-ride-on-a-bike-gone-wrong&time=1361689115","commentcount32154");</scri…

    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 199, Column 17607: reference to entity "time" for which no system identifier could be generated
    …e=first-ride-on-a-bike-gone-wrong&time=1361689115","commentcount32154");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 18421: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 18519: reference not terminated by REFC delimiter
    …ame=train-hits-idiot-truck-driver&time=1361689115","commentcount32159");</scri…

    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 199, Column 18519: reference to entity "time" for which no system identifier could be generated
    …ame=train-hits-idiot-truck-driver&time=1361689115","commentcount32159");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 19409: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 19514: reference not terminated by REFC delimiter
    …b-loves-his-teen-prostitute-whore&time=1361689115","commentcount32167");</scri…

    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 199, Column 19514: reference to entity "time" for which no system identifier could be generated
    …b-loves-his-teen-prostitute-whore&time=1361689115","commentcount32167");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 20287: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 20398: reference not terminated by REFC delimiter
    …ican-special-forces-own-gangsters&time=1361689115","commentcount32151");</scri…

    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 199, Column 20398: reference to entity "time" for which no system identifier could be generated
    …ican-special-forces-own-gangsters&time=1361689115","commentcount32151");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 199, Column 21877: required attribute "type" not specified
    …</strong><script language="javascript">document.onload = getDataReturnInner("/…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "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 199, Column 21971: reference not terminated by REFC delimiter
    …hp?name=woman-struck-by-lightning&time=1361689115","commentcount32158");</scri…

    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 199, Column 21971: reference to entity "time" for which no system identifier could be generated
    …hp?name=woman-struck-by-lightning&time=1361689115","commentcount32158");</scri…

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

  • Info Line 199, Column 933: entity was defined here
    …of-woman-dressed-for-her-final-viewing&time=1361689115","commentcount32187");<…
  • Error Line 202, Column 25: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    		<td width="100" nowrap></td>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 203, Column 77: reference not terminated by REFC delimiter
    …hp?pageNum_objects=0&totalRows_objects=12094" class="fs"><font color="red"><em…

    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 203, Column 77: reference to external entity in attribute value
    …hp?pageNum_objects=0&totalRows_objects=12094" class="fs"><font color="red"><em…

    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 203, Column 77: reference to entity "totalRows_objects" for which no system identifier could be generated
    …hp?pageNum_objects=0&totalRows_objects=12094" class="fs"><font color="red"><em…

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 205, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=1&totalRows_objects=12094" class="f"><em>2</em></a>

    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 205, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=1&totalRows_objects=12094" class="f"><em>2</em></a>

    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 205, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=1&totalRows_objects=12094" class="f"><em>2</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 207, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=2&totalRows_objects=12094" class="f"><em>3</em></a>

    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 207, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=2&totalRows_objects=12094" class="f"><em>3</em></a>

    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 207, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=2&totalRows_objects=12094" class="f"><em>3</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 209, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=3&totalRows_objects=12094" class="f"><em>4</em></a>

    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 209, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=3&totalRows_objects=12094" class="f"><em>4</em></a>

    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 209, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=3&totalRows_objects=12094" class="f"><em>4</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 211, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=4&totalRows_objects=12094" class="f"><em>5</em></a>

    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 211, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=4&totalRows_objects=12094" class="f"><em>5</em></a>

    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 211, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=4&totalRows_objects=12094" class="f"><em>5</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 213, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=5&totalRows_objects=12094" class="f"><em>6</em></a>

    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 213, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=5&totalRows_objects=12094" class="f"><em>6</em></a>

    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 213, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=5&totalRows_objects=12094" class="f"><em>6</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 215, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=6&totalRows_objects=12094" class="f"><em>7</em></a>

    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 215, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=6&totalRows_objects=12094" class="f"><em>7</em></a>

    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 215, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=6&totalRows_objects=12094" class="f"><em>7</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 217, Column 62: reference not terminated by REFC delimiter
    …"/index.php?pageNum_objects=7&totalRows_objects=12094" class="f"><em>8</em></a>

    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 217, Column 62: reference to external entity in attribute value
    …"/index.php?pageNum_objects=7&totalRows_objects=12094" class="f"><em>8</em></a>

    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 217, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    …"/index.php?pageNum_objects=7&totalRows_objects=12094" class="f"><em>8</em></a>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Warning Line 219, Column 62: reference not terminated by REFC delimiter
    ….php?pageNum_objects=8&totalRows_objects=12094' class='f'><em>...</em></a></td>

    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 219, Column 62: reference to external entity in attribute value
    ….php?pageNum_objects=8&totalRows_objects=12094' class='f'><em>...</em></a></td>

    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 219, Column 62: reference to entity "totalRows_objects" for which no system identifier could be generated
    ….php?pageNum_objects=8&totalRows_objects=12094' class='f'><em>...</em></a></td>

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Error Line 220, Column 39: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    		<td width="100" align="right" nowrap>          <a href="/index.php?pageNum_ob…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 220, Column 105: reference not terminated by REFC delimiter
    …hp?pageNum_objects=1&totalRows_objects=12094" class="fr"><em>next &raquo;</em>…

    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 220, Column 105: reference to external entity in attribute value
    …hp?pageNum_objects=1&totalRows_objects=12094" class="fr"><em>next &raquo;</em>…

    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 220, Column 105: reference to entity "totalRows_objects" for which no system identifier could be generated
    …hp?pageNum_objects=1&totalRows_objects=12094" class="fr"><em>next &raquo;</em>…

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

  • Info Line 178, Column 59: entity was defined here
    …><a href="/index.php?pageNum_objects=0&totalRows_objects=12094" class="fs"><fo…
  • Error Line 224, Column 24: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<font color="red"><h2>Underground Videos </h2></font>

    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 227, Column 33: required attribute "type" not specified
    			<script language="javascript">

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

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

  • Error Line 243, Column 60: value of attribute "id" invalid: "1" cannot start a name
    …ww.porndaddy.us/" target="_blank" id="174532" rel="nofollow" >Sick Daddy Porn …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 245, Column 60: value of attribute "id" invalid: "1" cannot start a name
    …ww.surenews.com/" target="_blank" id="107174" rel="nofollow" >***FUCKED UP NEW…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 247, Column 62: value of attribute "id" invalid: "1" cannot start a name
    ….newsfilter.org/" target="_blank" id="11564" rel="nofollow" >SLEEPING 18+</a><…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 249, Column 58: value of attribute "id" invalid: "1" cannot start a name
    …/www.humoron.com" target="_blank" id="100006" rel="nofollow" >Sick Videos 18+<…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 251, Column 62: value of attribute "id" invalid: "1" cannot start a name
    ….extremefuse.com" target="_blank" id="100057" rel="nofollow" >Suicide 18+ Only…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 253, Column 61: value of attribute "id" invalid: "4" cannot start a name
    …w.machovideo.com" target="_blank" id="4316" rel="nofollow" >Shocking Vids</a><…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 255, Column 61: value of attribute "id" invalid: "1" cannot start a name
    …w.cumlouder.com/" target="_blank" id="174531" rel="nofollow" >Cumlouder</a></l…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 257, Column 58: value of attribute "id" invalid: "1" cannot start a name
    …/www.heavy-r.com" target="_blank" id="137127" rel="nofollow" >Hardcore Porn </…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 259, Column 61: value of attribute "id" invalid: "1" cannot start a name
    …w.mentalzero.com" target="_blank" id="127145" rel="nofollow" >Murder Videos 18…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 261, Column 67: value of attribute "id" invalid: "1" cannot start a name
    …made-voyeur.com/" target="_blank" id="174101" rel="nofollow" >FREE VOYEUR</a><…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 263, Column 60: value of attribute "id" invalid: "1" cannot start a name
    …ww.epicfail.com/" target="_blank" id="174525" rel="nofollow" >EPIC FAIL</a></l…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 265, Column 62: value of attribute "id" invalid: "1" cannot start a name
    ….m90.org/1/rape/" target="_blank" id="120281" rel="nofollow" >Fucked Up Sex </…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 267, Column 60: value of attribute "id" invalid: "1" cannot start a name
    …ww.holyjugs.com/" target="_blank" id="111505" rel="nofollow" >MILF Videos 18+<…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 269, Column 61: value of attribute "id" invalid: "1" cannot start a name
    …w.angryduck.com/" target="_blank" id="144306" rel="nofollow" >Dead Girls</a></…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 279, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                    	<li><a href=ads.php?id=567 target="_blank"><img src=http://med…
  • Error Line 279, Column 37: an attribute value must be a literal unless it contains only name characters
                    	<li><a href=ads.php?id=567 target="_blank"><img src=http://med…

    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 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.php?id=567 target="_blank"><img src=http://media.theync.com/banners/585181pl…
  • Error Line 279, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …id=567 target="_blank"><img src=http://media.theync.com/banners/585181plug4.jp…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 279, Column 76: required attribute "alt" not specified
    …id=567 target="_blank"><img src=http://media.theync.com/banners/585181plug4.jp…

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

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

  • Error Line 279, Column 76: end tag for "img" omitted, but OMITTAG NO was specified
    …id=567 target="_blank"><img src=http://media.theync.com/banners/585181plug4.jp…

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

  • Info Line 279, Column 61: start tag was here
    …a href=ads.php?id=567 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 279, Column 125: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …rget="_blank"><img src=http://media.theync.com/banners/585181plug4.jpg></a><li>

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

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

  • Error Line 280, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="/ads.php?id=506" target="_blank" rel="nofollow"><img src=http://me…

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

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

  • Error Line 280, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/51.jpg><…
  • Error Line 280, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/51.jpg></a><li…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 280, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/51.jpg></a><li…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute 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 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/51.jpg></a><li…

    You may 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 62: start tag was here
    …d=506" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 280, Column 117: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/51.jpg></a><li>

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

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

  • Error Line 281, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="/ads.php?id=504" target="_blank" rel="nofollow"><img src=http://me…

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

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

  • Error Line 281, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/171.jpg>…
  • Error Line 281, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/171.jpg></a><l…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 281, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/171.jpg></a><l…

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

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

  • Error Line 281, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/171.jpg></a><l…

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

  • Info Line 281, Column 62: start tag was here
    …d=504" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 281, Column 118: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …blank" rel="nofollow"><img src=http://media.theync.com/banners/171.jpg></a><li>

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

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

  • Error Line 282, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="/ads.php?id=505" target="_blank" rel="nofollow"><img src=http://me…

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

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

  • Error Line 282, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/982.jpg>…
  • Error Line 282, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/982.jpg></a><l…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 282, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/982.jpg></a><l…

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

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

  • Error Line 282, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/982.jpg></a><l…

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

  • Info Line 282, Column 62: start tag was here
    …d=505" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 282, Column 118: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …blank" rel="nofollow"><img src=http://media.theync.com/banners/982.jpg></a><li>

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

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

  • Error Line 283, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="/ads.php?id=508" target="_blank" rel="nofollow"><img src=http://me…

    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 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/466.jpg>…
  • Error Line 283, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/466.jpg></a><l…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 283, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/466.jpg></a><l…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute 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 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/466.jpg></a><l…

    You may 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 62: start tag was here
    …d=508" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 283, Column 118: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …blank" rel="nofollow"><img src=http://media.theync.com/banners/466.jpg></a><li>

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

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

  • Error Line 284, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a href="/ads.php?id=509" target="_blank" rel="nofollow"><img src=http://me…

    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 284, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/302.jpg>…
  • Error Line 284, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/302.jpg></a><l…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 284, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/302.jpg></a><l…

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

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

  • Error Line 284, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/302.jpg></a><l…

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

  • Info Line 284, Column 62: start tag was here
    …d=509" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 284, Column 118: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

    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 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 284, Column 115: start tag was here
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 284, Column 1: start tag was here
    <li><a href="/ads.php?id=509" target="_blank" rel="nofollow"><img src=http://me…
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

    You may 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 115: start tag was here
    …blank" rel="nofollow"><img src=http://media.theync.com/banners/466.jpg></a><li>
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

    You may 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
    <li><a href="/ads.php?id=508" target="_blank" rel="nofollow"><img src=http://me…
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 282, Column 115: start tag was here
    …blank" rel="nofollow"><img src=http://media.theync.com/banners/982.jpg></a><li>
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 282, Column 1: start tag was here
    <li><a href="/ads.php?id=505" target="_blank" rel="nofollow"><img src=http://me…
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 281, Column 115: start tag was here
    …blank" rel="nofollow"><img src=http://media.theync.com/banners/171.jpg></a><li>
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 281, Column 1: start tag was here
    <li><a href="/ads.php?id=504" target="_blank" rel="nofollow"><img src=http://me…
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

    You may 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 114: start tag was here
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/51.jpg></a><li>
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

    You may 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
    <li><a href="/ads.php?id=506" target="_blank" rel="nofollow"><img src=http://me…
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 279, Column 122: start tag was here
    …rget="_blank"><img src=http://media.theync.com/banners/585181plug4.jpg></a><li>
  • Error Line 284, Column 144: end tag for "li" omitted, but OMITTAG NO was specified
    … src=http://media.theync.com/banners/302.jpg></a><li>					                </ul>

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

  • Info Line 279, Column 18: start tag was here
                    	<li><a href=ads.php?id=567 target="_blank"><img src=http://med…
  • Error Line 288, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/69gg.jpg…
  • Error Line 288, Column 106: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/69gg.jpg></a><…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 288, Column 106: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/69gg.jpg></a><…

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

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

  • Error Line 288, Column 106: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/69gg.jpg></a><…

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

  • Info Line 288, Column 91: start tag was here
    …d=450" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 290, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/56dd.jpe…
  • Error Line 290, Column 106: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/56dd.jpeg></a>…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 290, Column 106: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/56dd.jpeg></a>…

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

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

  • Error Line 290, Column 106: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/56dd.jpeg></a>…

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

  • Info Line 290, Column 91: start tag was here
    …d=488" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Warning Line 299, Column 100: cannot generate system identifier for general entity "p"
    …ion.traffichaus.com/adserve.php?z=176&p=32" frameborder="0" scrolling="no" wid…

    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 299, Column 100: general entity "p" not defined and no default entity
    …ion.traffichaus.com/adserve.php?z=176&p=32" frameborder="0" scrolling="no" wid…

    This is usually a cascading error caused by 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 299, Column 101: reference not terminated by REFC delimiter
    …on.traffichaus.com/adserve.php?z=176&p=32" frameborder="0" scrolling="no" widt…

    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 299, Column 101: reference to external entity in attribute value
    …on.traffichaus.com/adserve.php?z=176&p=32" frameborder="0" scrolling="no" widt…

    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 299, Column 101: reference to entity "p" for which no system identifier could be generated
    …on.traffichaus.com/adserve.php?z=176&p=32" frameborder="0" scrolling="no" widt…

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

  • Info Line 299, Column 99: entity was defined here
    …tion.traffichaus.com/adserve.php?z=176&p=32" frameborder="0" scrolling="no" wi…
  • Error Line 309, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 309, Column 30: document type does not allow element "script" here; assuming missing "li" start-tag
    <script language="javascript">
  • Warning Line 310, Column 61: cannot generate system identifier for general entity "id"
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

    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 310, Column 61: general entity "id" not defined and no default entity
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

    This is usually a cascading error caused by 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 310, Column 63: reference not terminated by REFC delimiter
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

    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 310, Column 63: reference to entity "id" for which no system identifier could be generated
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

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

  • Info Line 310, Column 60: entity was defined here
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')
  • Warning Line 310, Column 65: cannot generate system identifier for general entity "t"
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

    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 310, Column 65: general entity "t" not defined and no default entity
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

    This is usually a cascading error caused by 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 310, Column 66: reference not terminated by REFC delimiter
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

    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 310, Column 66: reference to entity "t" for which no system identifier could be generated
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')

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

  • Info Line 310, Column 64: entity was defined here
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')
  • Error Line 314, Column 22: end tag for "li" omitted, but OMITTAG NO was specified
                    	</ul>

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

  • Info Line 309, Column 1: start tag was here
    <script language="javascript">
  • Error Line 319, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 319, Column 30: document type does not allow element "script" here; assuming missing "li" start-tag
    <script language="javascript">
  • Warning Line 320, Column 75: reference not terminated by REFC delimiter
    …turnInner('/top_media_underground.php?nsfw=0&id=&t=01:58:35','top-underground')

    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 320, Column 75: reference to entity "id" for which no system identifier could be generated
    …turnInner('/top_media_underground.php?nsfw=0&id=&t=01:58:35','top-underground')

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

  • Info Line 310, Column 60: entity was defined here
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')
  • Warning Line 320, Column 78: reference not terminated by REFC delimiter
    …turnInner('/top_media_underground.php?nsfw=0&id=&t=01:58:35','top-underground')

    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 320, Column 78: reference to entity "t" for which no system identifier could be generated
    …turnInner('/top_media_underground.php?nsfw=0&id=&t=01:58:35','top-underground')

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

  • Info Line 310, Column 64: entity was defined here
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')
  • Error Line 324, Column 22: end tag for "li" omitted, but OMITTAG NO was specified
                    	</ul>

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

  • Info Line 319, Column 1: start tag was here
    <script language="javascript">
  • Error Line 330, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 330, Column 30: document type does not allow element "script" here; assuming missing "li" start-tag
    <script language="javascript">
  • Warning Line 331, Column 60: reference not terminated by REFC delimiter
    …onload = getDataReturnInner('/random.php?nsfw=0&id=&t=01:58:35','randomvideos')

    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 331, Column 60: reference to entity "id" for which no system identifier could be generated
    …onload = getDataReturnInner('/random.php?nsfw=0&id=&t=01:58:35','randomvideos')

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

  • Info Line 310, Column 60: entity was defined here
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')
  • Warning Line 331, Column 63: reference not terminated by REFC delimiter
    …onload = getDataReturnInner('/random.php?nsfw=0&id=&t=01:58:35','randomvideos')

    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 331, Column 63: reference to entity "t" for which no system identifier could be generated
    …onload = getDataReturnInner('/random.php?nsfw=0&id=&t=01:58:35','randomvideos')

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

  • Info Line 310, Column 64: entity was defined here
    …onload = getDataReturnInner('/top_media.php?nsfw=0&id=&t=01:58:35','topvideos')
  • Error Line 335, Column 22: end tag for "li" omitted, but OMITTAG NO was specified
                    	</ul>

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

  • Info Line 330, Column 1: start tag was here
    <script language="javascript">
  • Error Line 342, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/824.jpg>…
  • Error Line 342, Column 84: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/824.jpg></a></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 342, Column 84: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/824.jpg></a></…

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

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

  • Error Line 342, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/824.jpg></a></…

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

  • Info Line 342, Column 69: start tag was here
    …d=514" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 343, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/121.jpg>…
  • Error Line 343, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/121.jpg></a></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 343, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/121.jpg></a></…

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

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

  • Error Line 343, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/121.jpg></a></…

    You may 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 62: start tag was here
    …d=510" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 344, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/241.jpg>…
  • Error Line 344, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/241.jpg></a></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 344, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/241.jpg></a></…

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

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

  • Error Line 344, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/241.jpg></a></…

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

  • Info Line 344, Column 62: start tag was here
    …d=512" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 345, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/792.jpg>…
  • Error Line 345, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/792.jpg></a></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 345, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/792.jpg></a></…

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

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

  • Error Line 345, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/792.jpg></a></…

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

  • Info Line 345, Column 62: start tag was here
    …d=516" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 346, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/631.jpg>…
  • Error Line 346, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/631.jpg></a></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 346, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/631.jpg></a></…

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

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

  • Error Line 346, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/631.jpg></a></…

    You may 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 62: start tag was here
    …d=515" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 347, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/882.JPG>…
  • Error Line 347, Column 77: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/882.JPG></a></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 347, Column 77: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/882.JPG></a></…

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

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

  • Error Line 347, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/882.JPG></a></…

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

  • Info Line 347, Column 62: start tag was here
    …d=511" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 351, Column 464: there is no attribute "allowTransparency"
    …verflow:hidden; width:300px; height:180px;" allowTransparency="false"></iframe>

    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 356, 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 356, Column 7: 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 365, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<div class="pt5 pb5"><a href=ads.php?id=566 target="_blank"><img src=http://m…
  • Error Line 365, Column 39: an attribute value must be a literal unless it contains only name characters
    		<div class="pt5 pb5"><a href=ads.php?id=566 target="_blank"><img src=http://m…

    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 365, Column 72: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.php?id=566 target="_blank"><img src=http://media.theync.com/banners/56girlsn…
  • Error Line 365, Column 78: NET-enabling start-tag not immediately followed by null end-tag
    …id=566 target="_blank"><img src=http://media.theync.com/banners/56girlsnowboar…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 365, Column 78: required attribute "alt" not specified
    …id=566 target="_blank"><img src=http://media.theync.com/banners/56girlsnowboar…

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

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

  • Error Line 365, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
    …id=566 target="_blank"><img src=http://media.theync.com/banners/56girlsnowboar…

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

  • Info Line 365, Column 63: start tag was here
    …a href=ads.php?id=566 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 367, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/ads.php?id=565 target="_blank"><img src=http://media.theync.com/banner…

    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 367, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.php?id=565 target="_blank"><img src=http://media.theync.com/banners/4677efdb…
  • Error Line 367, Column 56: NET-enabling start-tag not immediately followed by null end-tag
    …id=565 target="_blank"><img src=http://media.theync.com/banners/4677efdb97bd30…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 367, Column 56: required attribute "alt" not specified
    …id=565 target="_blank"><img src=http://media.theync.com/banners/4677efdb97bd30…

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

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

  • Error Line 367, Column 56: end tag for "img" omitted, but OMITTAG NO was specified
    …id=565 target="_blank"><img src=http://media.theync.com/banners/4677efdb97bd30…

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

  • Info Line 367, Column 41: start tag was here
    … href=/ads.php?id=565 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 368, Column 9: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <a href=ads.php?id=563 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 368, Column 16: an attribute value must be a literal unless it contains only name characters
    <a href=ads.php?id=563 target="_blank"><img src=http://media.theync.com/banners…

    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 368, Column 49: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.php?id=563 target="_blank"><img src=http://media.theync.com/banners/35621b9c…
  • Error Line 368, Column 55: NET-enabling start-tag not immediately followed by null end-tag
    …id=563 target="_blank"><img src=http://media.theync.com/banners/35621b9c19bfb7…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 368, Column 55: required attribute "alt" not specified
    …id=563 target="_blank"><img src=http://media.theync.com/banners/35621b9c19bfb7…

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

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

  • Error Line 368, Column 55: end tag for "img" omitted, but OMITTAG NO was specified
    …id=563 target="_blank"><img src=http://media.theync.com/banners/35621b9c19bfb7…

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

  • Info Line 368, Column 40: start tag was here
    …a href=ads.php?id=563 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 369, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/ads.php?id=562 target="_blank"><img src=http://media.theync.com/banner…

    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 369, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.php?id=562 target="_blank"><img src=http://media.theync.com/banners/60fgg.jp…
  • Error Line 369, Column 56: NET-enabling start-tag not immediately followed by null end-tag
    …?id=562 target="_blank"><img src=http://media.theync.com/banners/60fgg.jpg></a>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 369, Column 56: required attribute "alt" not specified
    …?id=562 target="_blank"><img src=http://media.theync.com/banners/60fgg.jpg></a>

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

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

  • Error Line 369, Column 56: end tag for "img" omitted, but OMITTAG NO was specified
    …?id=562 target="_blank"><img src=http://media.theync.com/banners/60fgg.jpg></a>

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

  • Info Line 369, Column 41: start tag was here
    … href=/ads.php?id=562 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 370, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=/ads.php?id=557 target="_blank"><img src=http://media.theync.com/banner…

    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 370, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …s.php?id=557 target="_blank"><img src=http://media.theync.com/banners/401a23d2…
  • Error Line 370, Column 56: NET-enabling start-tag not immediately followed by null end-tag
    …id=557 target="_blank"><img src=http://media.theync.com/banners/401a23d27ddd93…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 370, Column 56: required attribute "alt" not specified
    …id=557 target="_blank"><img src=http://media.theync.com/banners/401a23d27ddd93…

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

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

  • Error Line 370, Column 56: end tag for "img" omitted, but OMITTAG NO was specified
    …id=557 target="_blank"><img src=http://media.theync.com/banners/401a23d27ddd93…

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

  • Info Line 370, Column 41: start tag was here
    … href=/ads.php?id=557 target="_blank"><img src=http://media.theync.com/banners…
  • Error Line 371, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rget="_blank" rel="nofollow"><img src=http://media.theync.com/banners/7988.jpg…
  • Error Line 371, Column 73: NET-enabling start-tag not immediately followed by null end-tag
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/7988.jpg></a><…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 371, Column 73: required attribute "alt" not specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/7988.jpg></a><…

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

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

  • Error Line 371, Column 73: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" rel="nofollow"><img src=http://media.theync.com/banners/7988.jpg></a><…

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

  • Info Line 371, Column 58: start tag was here
    …d=471" target="_blank" rel="nofollow"><img src=http://media.theync.com/banners…
  • Error Line 391, Column 95: value of attribute "id" invalid: "1" cannot start a name
    …/Funny+T-Shirts/" target="_blank" id="174528" rel="nofollow" >Funny T Shirts</…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 393, Column 59: value of attribute "id" invalid: "1" cannot start a name
    …www.surenews.com" target="_blank" id="174529" rel="nofollow" >Sure News</a></l…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 410, Column 21: character ";" not allowed in attribute specification list
    	for(i=0; i<a.length; i++)
  • Error Line 410, Column 21: element "a.length" undefined
    	for(i=0; i<a.length; i++)

    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 424, Column 9: end tag for "a.length" omitted, but OMITTAG NO was specified
    </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 410, Column 12: start tag was here
    	for(i=0; i<a.length; i++)
  • Error Line 434, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 436, Column 96: cannot generate system identifier for general entity "utm_medium"
    …com/video-categories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync"…

    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 436, Column 96: general entity "utm_medium" not defined and no default entity
    …com/video-categories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync"…

    This is usually a cascading error caused by 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 436, Column 106: reference not terminated by REFC delimiter
    …categories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync";var popun…

    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 436, Column 106: reference to entity "utm_medium" for which no system identifier could be generated
    …categories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync";var popun…

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

  • Info Line 436, Column 95: entity was defined here
    ….com/video-categories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync…
  • Warning Line 436, Column 110: cannot generate system identifier for general entity "utm_campaign"
    …gories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync";var popunderW…

    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 436, Column 110: general entity "utm_campaign" not defined and no default entity
    …gories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync";var popunderW…

    This is usually a cascading error caused by 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 436, Column 122: reference not terminated by REFC delimiter
    …ource=stile&utm_medium=PT&utm_campaign=stile-theync";var popunderWidth=1100;va…

    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 436, Column 122: reference to entity "utm_campaign" for which no system identifier could be generated
    …ource=stile&utm_medium=PT&utm_campaign=stile-theync";var popunderWidth=1100;va…

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

  • Info Line 436, Column 109: entity was defined here
    …egories?utm_source=stile&utm_medium=PT&utm_campaign=stile-theync";var popunder…

Visitor Analysis

Daily Visitor
  • 17.500 visits