Tsontes και sex video με πορνο βιντεος και greek porn μαζι με tsonta απο Youporn. Σεξ βιντεος με πολλα σεχ πορνο και γκει ελληνικες τσοντες. Τσοντες μονο απο το YouHot! ...

youhot.gr
  • Domain Name
    youhot.gr
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #64505
  • Page Size
    77.9 KB
  • Ip Address
    5.63.151.132
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 62 JPG, 27 PNG

Website Meta Analysis

  • Title
    TSONTES | GREEK PORN | SEX VIDEO | GAY PORN | ΠΟΡΝΟ ΒΙΝΤΕΟΣ | ΣΕΧ ΠΟΡΝΟ | TSONTA | YOUHOT | YOUPORN
  • Meta Keyword
    TSONTES, TSONTA, GAY PORN, ΕΛΛΗΝΙΚΕΣ ΤΣΟΝΤΕΣ, ΣΕΧ ΒΙΝΤΕΟ, SEX VIDEO, ΠΟΡΝΟ ΒΙΝΤΕΟΣ, GREEK PORN, YOUPORN, ΧΧΧ, Greek sex videos, tsontes ellinikes, youhot, kafto, escort tubes
  • Meta Description
    Tsontes και sex video με πορνο βιντεος και greek porn μαζι με tsonta απο Youporn. Σεξ βιντεος με πολλα σεχ πορνο και γκει ελληνικες τσοντες. Τσοντες μονο απο το YouHot!

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    5.63.151.132
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from youhot.gr.

HTML Analysis

  • server: nginx
  • date: Thu, 27 Jun 2013 08:59:59 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Thu, 27 Jun 2013 08:59:59 GMT
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for youhot.gr

DNS Analysis


DNS servers
ns04.iphost.gr
ns05.iphost.gr


DNS Records

Answer records
youhot.gr SOA
server: ns04.iphost.gr
email: admin@iphost.gr
serial: 2012120565
refresh: 14400
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
youhot.gr NS  ns04.iphost.gr 86400s
youhot.gr NS  ns05.iphost.gr 86400s
youhot.gr A 5.63.151.132 86400s
youhot.gr MX
preference: 1
exchange: ASPMX.L.GOOGLE.COM
86400s
youhot.gr MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.COM
86400s
youhot.gr MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.COM
86400s
youhot.gr MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.COM
86400s
youhot.gr MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.COM
86400s

Authority records

Additional records
ALT1.ASPMX.L.GOOGLE.COM A 93.174.121.39 86400s
ns04.iphost.gr A 93.174.121.39 86400s

IP 5.63.151.132 Analysis

  • Country Code
    EU
  • Country Code3
    EU
  • Country Name
    Europe
  • City
    EU
  • Continent Code
    47° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 5.63.151.132

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 341 Errors
  • 192 Warnings
Ratio Text/Html
  • 0.8195645092585633
Message Error
  • Error Line 14, Column 40: document type does not allow element "html" here
    		<html xmlns:fb="http://ogp.me/ns/fb#">

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

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

  • Error Line 14, Column 3: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    		<html xmlns:fb="http://ogp.me/ns/fb#">

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

  • Error Line 15, Column 104: document type does not allow element "link" here; assuming missing "head" start-tag
    …" href = "/templates/frontend/default/css/style_total.css" type = "text/css" />
  • Error Line 38, Column 9: end tag for "head" which is not finished
    		</head>

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

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

  • Error Line 62, Column 375: there is no attribute "allowTransparency"
    … overflow:hidden; width:150px; height:21px;" allowTransparency="true"></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.

  • Warning Line 71, Column 89: cannot generate system identifier for general entity "login"
    …tion.exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_co…

    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 71, Column 89: general entity "login" not defined and no default entity
    …tion.exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_co…

    This is usually a cascading error caused by 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 71, Column 94: reference not terminated by REFC delimiter
    …exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0…

    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 71, Column 94: reference to external entity in attribute value
    …exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0…

    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 71, Column 94: reference to entity "login" for which no system identifier could be generated
    …exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0…

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

  • Info Line 71, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_c…
  • Warning Line 71, Column 104: cannot generate system identifier for general entity "cat"
    …om/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgco…

    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 71, Column 104: general entity "cat" not defined and no default entity
    …om/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgco…

    This is usually a cascading error caused by 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 71, Column 107: reference not terminated by REFC delimiter
    …ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 71, Column 107: reference to external entity in attribute value
    …ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 71, Column 107: reference to entity "cat" for which no system identifier could be generated
    …ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 71, Column 103: entity was defined here
    …com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 71, Column 110: cannot generate system identifier for general entity "search"
    ….php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    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 71, Column 110: general entity "search" not defined and no default entity
    ….php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FF…

    This is usually a cascading error caused by 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 71, Column 116: reference not terminated by REFC delimiter
    …ype=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 71, Column 116: reference to external entity in attribute value
    …ype=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 71, Column 116: reference to entity "search" for which no system identifier could be generated
    …ype=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 71, Column 109: entity was defined here
    …s.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 71, Column 118: cannot generate system identifier for general entity "ad_title_color"
    …e=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 71, Column 118: general entity "ad_title_color" not defined and no default entity
    …e=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    This is usually a cascading error caused by 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 71, Column 132: reference not terminated by REFC delimiter
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 71, Column 132: reference to external entity in attribute value
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 71, Column 132: reference to entity "ad_title_color" for which no system identifier could be generated
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 71, Column 117: entity was defined here
    …pe=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 71, Column 140: cannot generate system identifier for general entity "bgcolor"
    …4&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

    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 71, Column 140: general entity "bgcolor" not defined and no default entity
    …4&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

    This is usually a cascading error caused by 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 71, Column 147: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 71, Column 147: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 71, Column 147: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&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.

  • Info Line 71, Column 139: entity was defined here
    …34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 71, Column 155: cannot generate system identifier for general entity "border"
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

    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 71, Column 155: general entity "border" not defined and no default entity
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

    This is usually a cascading error caused by 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 71, Column 161: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 71, Column 161: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 71, Column 161: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 71, Column 154: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 71, Column 164: cannot generate system identifier for general entity "border_color"
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

    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 71, Column 164: general entity "border_color" not defined and no default entity
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

    This is usually a cascading error caused by 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 71, Column 176: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 71, Column 176: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 71, Column 176: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 71, Column 163: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 71, Column 184: cannot generate system identifier for general entity "font"
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 71, Column 184: general entity "font" not defined and no default entity
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    This is usually a cascading error caused by 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 71, Column 188: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 71, Column 188: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 71, Column 188: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 71, Column 183: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 71, Column 190: cannot generate system identifier for general entity "block_keywords"
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 71, Column 190: general entity "block_keywords" not defined and no default entity
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    This is usually a cascading error caused by 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 71, Column 204: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 71, Column 204: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 71, Column 204: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 71, Column 189: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 71, Column 206: cannot generate system identifier for general entity "ad_text_color"
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 71, Column 206: general entity "ad_text_color" not defined and no default entity
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    This is usually a cascading error caused by 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 71, Column 219: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 71, Column 219: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 71, Column 219: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 71, Column 205: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 71, Column 227: cannot generate system identifier for general entity "ad_durl_color"
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_…

    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 71, Column 227: general entity "ad_durl_color" not defined and no default entity
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_…

    This is usually a cascading error caused by 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 71, Column 240: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 71, Column 240: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 71, Column 240: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

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

  • Info Line 71, Column 226: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 71, Column 248: cannot generate system identifier for general entity "adult"
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&i…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 71, Column 248: general entity "adult" not defined and no default entity
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&i…

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

  • Warning Line 71, Column 253: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 71, Column 253: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 71, Column 253: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

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

  • Info Line 71, Column 247: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 71, Column 259: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=13289…

    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 71, Column 262: cannot generate system identifier for general entity "text_only"
    …00&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&i…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 71, Column 262: general entity "text_only" not defined and no default entity
    …00&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&i…

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

  • Warning Line 71, Column 271: reference not terminated by REFC delimiter
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=676…

    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 71, Column 271: reference to external entity in attribute value
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=676…

    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 71, Column 271: reference to entity "text_only" for which no system identifier could be generated
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=676…

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

  • Info Line 71, Column 261: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&…
  • Warning Line 71, Column 274: cannot generate system identifier for general entity "show_thumb"
    …olor=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"…

    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 71, Column 274: general entity "show_thumb" not defined and no default entity
    …olor=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"…

    This is usually a cascading error caused by 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 71, Column 284: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 284: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 284: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

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

  • Info Line 71, Column 273: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681…
  • Warning Line 71, Column 287: cannot generate system identifier for general entity "idzone"
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 287: general entity "idzone" not defined and no default entity
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    This is usually a cascading error caused by 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 71, Column 293: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 293: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 293: reference to entity "idzone" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

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

  • Info Line 71, Column 286: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>
  • Warning Line 71, Column 301: cannot generate system identifier for general entity "idsite"
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 301: general entity "idsite" not defined and no default entity
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    This is usually a cascading error caused by 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 71, Column 307: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 307: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

    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 71, Column 307: reference to entity "idsite" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>

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

  • Info Line 71, Column 300: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>
  • Error Line 78, Column 98: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …selector" title="Select Language"><div><img src="/templates/frontend/default/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 78, Column 162: ID "select_language" already defined
    …tend/default/images/flags/gr.gif" id="select_language" alt="gr.gif" /><img src…

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

  • Info Line 78, Column 28: ID "select_language" first defined here
    											<a href="#" id="select_language" class="languageselector" title="Sel…
  • Error Line 78, Column 253: required attribute "alt" not specified
    …r.gif" /><img src="/templates/frontend/default/images/arrowdown.gif"></div></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 78, Column 259: end tag for "img" omitted, but OMITTAG NO was specified
    …r.gif" /><img src="/templates/frontend/default/images/arrowdown.gif"></div></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 78, Column 194: start tag was here
    …" id="select_language" alt="gr.gif" /><img src="/templates/frontend/default/im…
  • Error Line 90, Column 49: there is no attribute "TARGET"
    	<li><a href="http://www.youchat.gr/all" TARGET="_blank">Ελληνίδες Φώτο</a></li>

    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 99, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=32">Hentai Manga</a>

    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 100, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=40">Interracial</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 101, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=23">Milf</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 102, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=35">Transexual</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 103, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=4">Asian</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 104, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=27">Βαθύ Λαρύγγι</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 105, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=24">Δημόσια</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 106, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=2">Ερασιτεχνικά</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 107, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=14">Ζευγάρια</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 108, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=37">Ιερόδουλες</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 109, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=25">Κοκκινομάλλες</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 110, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=7">Κωλάρες</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 111, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=21">Λατίνες</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 112, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=1">Λεσβίες</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 113, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=17">Μαύρες</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 114, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=12">Μελαχρινές</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 115, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=9">Ξανθιές</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 116, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=28">Παρτούζες</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 117, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=10">Πίπες</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 118, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=33">Πιπίνια</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 119, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=3">Πρωκτικό</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 120, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=18">Φετίχ</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 121, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=39">Χοντρές</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 122, Column 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=16">Χύσιμο</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 7: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    			<li><a href="http://www.youhot.gr/videos?c=43">Affiliate Videos</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 124, Column 7: 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 99, Column 4: start tag was here
    			<li><a href="http://www.youhot.gr/videos?c=32">Hentai Manga</a>
  • Error Line 124, Column 7: 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 4: start tag was here
    			<li><a href="http://www.youhot.gr/videos?c=31">Ελληνικά</a>
  • Error Line 140, Column 36: there is no attribute "border"
    	<li id="juicylink"><iframe border=0 frameborder=0 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 140, Column 36: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<li id="juicylink"><iframe border=0 frameborder=0 marginheight=0 marginwidth=0…
  • Error Line 140, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …icylink"><iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=178…
  • Error Line 140, Column 65: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=178 height=18 scro…
  • Error Line 140, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=178 height=18 scrolling=no allow…
  • Error Line 140, Column 87: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=178 height=18 scrolling=no allowtranspar…
  • Error Line 140, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=178 height=18 scrolling=no allowtransparency=true s…
  • Error Line 140, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=178 height=18 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 140, Column 132: there is no attribute "allowtransparency"
    …ght=18 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

    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 140, Column 132: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=18 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 140, Column 141: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 140, Column 147: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 140, Column 202: end tag for element "iframe" which is not open
    …cy=true src=http://adserver.juicyads.com/adshow.php?adzone=62180></iframe></li>

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

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

  • Error Line 240, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 263, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 283, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=2…
  • Error Line 283, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=2…
  • Error Line 283, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=299 scr…
  • Error Line 283, Column 60: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allo…
  • Error Line 283, Column 68: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allowtranspa…
  • Error Line 283, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=299 scrolling=no allowtransparency=true …
  • Error Line 283, Column 93: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=299 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 283, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 283, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 283, Column 129: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 184: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=44297></iframe>

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

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

  • Error Line 290, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 313, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 336, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 359, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 378, Column 49: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 378, Column 71: ID "scrambler_juicyad" already defined
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 379, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 379, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 379, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 379, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 379, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 379, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 379, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 379, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 379, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 379, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 379, Column 183: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=44302></iframe>

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

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

  • Error Line 386, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 409, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 432, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 455, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 478, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 498, Column 14: ID "scramble_ad" already defined
    				<div id="scramble_ad">

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 499, Column 96: required attribute "alt" not specified
    …ww.youflirt.gr" target="_blank"><img src="http://www.youhot.gr/rise8.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 500, Column 41: ID "scramble_video_title" already defined
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 500, Column 68: end tag for "span" omitted, but OMITTAG NO was specified
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>

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

  • Info Line 500, Column 5: start tag was here
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>
  • Error Line 505, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 528, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 551, Column 20: ID "hta_video_title" already defined
    									<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 647, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 673, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 696, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 715, Column 50: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 715, Column 72: ID "scrambler_juicyad" already defined
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 716, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 716, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 716, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 716, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 716, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 716, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 716, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 716, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 716, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 716, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 716, Column 183: end tag for element "iframe" which is not open
    …s.com/adshow.php?adzone=44300></iframe><!--JuicyAds END--></div><span class="f…

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

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

  • Error Line 716, Column 245: ID "scramble_video_title" already defined
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 721, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 744, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 767, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 790, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 810, Column 14: ID "scramble_ad" already defined
    				<div id="scramble_ad">

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 811, Column 94: required attribute "alt" not specified
    …/www.youflirt.gr" target="_blank"><img src="http://www.youhot.gr/301.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 812, Column 41: ID "scramble_video_title" already defined
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 812, Column 68: end tag for "span" omitted, but OMITTAG NO was specified
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>

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

  • Info Line 812, Column 5: start tag was here
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>
  • Error Line 817, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 840, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 863, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 886, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 909, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 928, Column 50: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 928, Column 72: ID "scrambler_juicyad" already defined
    …o_box"><div id="scramble_ad"><div id="scrambler_juicyad"><iframe hspace=0 vspa…

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 928, Column 106: there is no attribute "hspace"
    …id="scrambler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 margin…

    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 928, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id="scrambler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 margin…
  • Error Line 928, Column 115: there is no attribute "vspace"
    …bler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=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 928, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 …
  • Error Line 928, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …yad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwid…
  • Error Line 928, Column 138: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308…
  • Error Line 928, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=299 scr…
  • Error Line 928, Column 167: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allo…
  • Error Line 928, Column 175: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allowtranspa…
  • Error Line 928, Column 186: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=299 scrolling=no allowtransparency=true …
  • Error Line 928, Column 200: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=299 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 928, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 928, Column 230: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 928, Column 236: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 928, Column 291: end tag for element "iframe" which is not open
    …s.com/adshow.php?adzone=44302></iframe></div><span class="font-13 font-bold" i…

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

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

  • Error Line 928, Column 334: ID "scramble_video_title" already defined
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 933, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 956, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 979, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1002, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1021, Column 50: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 1021, Column 72: ID "scrambler_juicyad" already defined
    …o_box"><div id="scramble_ad"><div id="scrambler_juicyad"><iframe hspace=0 vspa…

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 1021, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id="scrambler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 margin…
  • Error Line 1021, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 …
  • Error Line 1021, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …yad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwid…
  • Error Line 1021, Column 138: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308…
  • Error Line 1021, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=299 scr…
  • Error Line 1021, Column 167: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allo…
  • Error Line 1021, Column 175: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allowtranspa…
  • Error Line 1021, Column 186: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=299 scrolling=no allowtransparency=true …
  • Error Line 1021, Column 200: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=299 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1021, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1021, Column 230: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1021, Column 236: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1021, Column 291: end tag for element "iframe" which is not open
    …s.com/adshow.php?adzone=44019></iframe></div><span class="font-13 font-bold" i…

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

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

  • Error Line 1021, Column 334: ID "scramble_video_title" already defined
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 1026, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1049, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1072, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1095, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1118, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1137, Column 50: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 1137, Column 72: ID "scrambler_juicyad" already defined
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 1138, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 1138, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 1138, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 1138, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 1138, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 1138, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 1138, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1138, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1138, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1138, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1138, Column 183: end tag for element "iframe" which is not open
    …s.com/adshow.php?adzone=44300></iframe><!--JuicyAds END--></div><span class="f…

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

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

  • Error Line 1138, Column 245: ID "scramble_video_title" already defined
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 1143, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1166, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1189, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1212, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1235, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1258, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1278, Column 14: ID "scramble_ad" already defined
    				<div id="scramble_ad">

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 1279, Column 94: required attribute "alt" not specified
    …/www.youflirt.gr" target="_blank"><img src="http://www.youhot.gr/301.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 1280, Column 41: ID "scramble_video_title" already defined
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 1280, Column 68: end tag for "span" omitted, but OMITTAG NO was specified
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>

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

  • Info Line 1280, Column 5: start tag was here
    				<span class="font-13 font-bold" id="scramble_video_title"></div></div>
  • Error Line 1285, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1308, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1331, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1354, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1377, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1403, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1426, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1445, Column 50: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 1445, Column 72: ID "scrambler_juicyad" already defined
    …o_box"><div id="scramble_ad"><div id="scrambler_juicyad"><iframe hspace=0 vspa…

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 1445, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id="scrambler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 margin…
  • Error Line 1445, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 …
  • Error Line 1445, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …yad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwid…
  • Error Line 1445, Column 138: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308…
  • Error Line 1445, Column 153: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=299 scr…
  • Error Line 1445, Column 167: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allo…
  • Error Line 1445, Column 175: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allowtranspa…
  • Error Line 1445, Column 186: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=299 scrolling=no allowtransparency=true …
  • Error Line 1445, Column 200: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=299 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1445, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1445, Column 230: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1445, Column 236: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1445, Column 291: end tag for element "iframe" which is not open
    …s.com/adshow.php?adzone=44302></iframe></div><span class="font-13 font-bold" i…

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

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

  • Error Line 1445, Column 334: ID "scramble_video_title" already defined
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 1450, Column 19: ID "hta_video_title" already defined
    								<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1479, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1502, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1525, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1544, Column 55: ID "scramble_ad" already defined
    																						<div class="video_box"><div id="scramble_ad">

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 1545, Column 21: ID "scrambler_juicyad" already defined
    											<div id="scrambler_juicyad"><!-- BEGIN ExoClick.com Ad Code -->

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Warning Line 1546, Column 107: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0…

    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 1546, Column 107: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0…

    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 1546, Column 107: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0…

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

  • Info Line 71, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_c…
  • Warning Line 1546, Column 120: reference not terminated by REFC delimiter
    …ds.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 1546, Column 120: reference to external entity in attribute value
    …ds.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 1546, Column 120: reference to entity "cat" for which no system identifier could be generated
    …ds.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 71, Column 103: entity was defined here
    …com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 1546, Column 129: reference not terminated by REFC delimiter
    …pe=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 1546, Column 129: reference to external entity in attribute value
    …pe=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 1546, Column 129: reference to entity "search" for which no system identifier could be generated
    …pe=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 71, Column 109: entity was defined here
    …s.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 1546, Column 145: reference not terminated by REFC delimiter
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 1546, Column 145: reference to external entity in attribute value
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 1546, Column 145: reference to entity "ad_title_color" for which no system identifier could be generated
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 71, Column 117: entity was defined here
    …pe=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 1546, Column 160: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 1546, Column 160: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 1546, Column 160: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&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.

  • Info Line 71, Column 139: entity was defined here
    …34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 1546, Column 174: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 1546, Column 174: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 1546, Column 174: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 71, Column 154: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 1546, Column 189: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 1546, Column 189: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 1546, Column 189: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 71, Column 163: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 1546, Column 201: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 1546, Column 201: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 1546, Column 201: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 71, Column 183: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 1546, Column 217: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 1546, Column 217: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 1546, Column 217: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 71, Column 189: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 1546, Column 232: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 1546, Column 232: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 1546, Column 232: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 71, Column 205: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 1546, Column 253: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 1546, Column 253: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    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 1546, Column 253: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

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

  • Info Line 71, Column 226: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 1546, Column 266: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 1546, Column 266: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 1546, Column 266: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

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

  • Info Line 71, Column 247: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 1546, Column 272: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=13289…

    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 1546, Column 284: reference not terminated by REFC delimiter
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=676…

    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 1546, Column 284: reference to external entity in attribute value
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=676…

    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 1546, Column 284: reference to entity "text_only" for which no system identifier could be generated
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=676…

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

  • Info Line 71, Column 261: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&…
  • Warning Line 1546, Column 297: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

    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 1546, Column 297: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

    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 1546, Column 297: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

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

  • Info Line 71, Column 273: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681…
  • Warning Line 1546, Column 306: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

    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 1546, Column 306: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

    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 1546, Column 306: reference to entity "idzone" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

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

  • Info Line 71, Column 286: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>
  • Warning Line 1546, Column 320: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

    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 1546, Column 320: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

    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 1546, Column 320: reference to entity "idsite" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132892&idsite=67681"></script>

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

  • Info Line 71, Column 300: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>
  • Error Line 1549, Column 48: ID "scramble_video_title" already defined
    …		<span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 1555, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1578, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1601, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1624, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1643, Column 53: ID "scramble_ad" already defined
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…

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

  • Info Line 282, Column 49: ID "scramble_ad" first defined here
    …						<div class="video_box"><div id="scramble_ad"><div id="scrambler_juicyad"…
  • Error Line 1643, Column 75: ID "scrambler_juicyad" already defined
    …o_box"><div id="scramble_ad"><div id="scrambler_juicyad"><iframe hspace=0 vspa…

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

  • Info Line 282, Column 71: ID "scrambler_juicyad" first defined here
    …deo_box"><div id="scramble_ad"><div id="scrambler_juicyad"><!--JuicyAds v2.0-->
  • Error Line 1643, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id="scrambler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 margin…
  • Error Line 1643, Column 118: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bler_juicyad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 …
  • Error Line 1643, Column 127: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …yad"><iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwid…
  • Error Line 1643, Column 141: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308…
  • Error Line 1643, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=299 scr…
  • Error Line 1643, Column 170: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allo…
  • Error Line 1643, Column 178: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allowtranspa…
  • Error Line 1643, Column 189: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=299 scrolling=no allowtransparency=true …
  • Error Line 1643, Column 203: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=299 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1643, Column 224: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1643, Column 233: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1643, Column 239: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1643, Column 294: end tag for element "iframe" which is not open
    …s.com/adshow.php?adzone=44298></iframe></div><span class="font-13 font-bold" i…

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

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

  • Error Line 1643, Column 337: ID "scramble_video_title" already defined
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…

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

  • Info Line 285, Column 44: ID "scramble_video_title" first defined here
    …v><span class="font-13 font-bold" id="scramble_video_title"><span class="scram…
  • Error Line 1648, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1674, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1697, Column 21: ID "hta_video_title" already defined
    										<span id="hta_video_title" class="font-13 font-bold">

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

  • Info Line 214, Column 20: ID "hta_video_title" first defined here
    									<span id="hta_video_title" class="font-13 font-bold">
  • Error Line 1717, Column 267: character data is not allowed here
    …hot.gr/videos?page=4">4</a></li>&nbsp;...&nbsp;<li><a href="http://www.youhot.…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1726, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=…
  • Error Line 1726, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=…
  • Error Line 1726, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 1726, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 1726, Column 69: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 1726, Column 80: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 1726, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1726, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1726, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1726, Column 130: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1726, Column 185: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=37290></iframe>

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

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

  • Warning Line 1732, Column 97: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0…

    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 1732, Column 97: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0…

    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 1732, Column 97: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0…

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

  • Info Line 71, Column 88: entity was defined here
    …ation.exoclick.com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_c…
  • Warning Line 1732, Column 110: reference not terminated by REFC delimiter
    …ds.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 1732, Column 110: reference to external entity in attribute value
    …ds.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

    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 1732, Column 110: reference to entity "cat" for which no system identifier could be generated
    …ds.php?type=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor…

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

  • Info Line 71, Column 103: entity was defined here
    …com/ads.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgc…
  • Warning Line 1732, Column 119: reference not terminated by REFC delimiter
    …pe=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 1732, Column 119: reference to external entity in attribute value
    …pe=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 1732, Column 119: reference to entity "search" for which no system identifier could be generated
    …pe=300x250&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

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

  • Info Line 71, Column 109: entity was defined here
    …s.php?type=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 1732, Column 135: reference not terminated by REFC delimiter
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Warning Line 1732, Column 135: reference to external entity in attribute value
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Error Line 1732, Column 135: reference to entity "ad_title_color" for which no system identifier could be generated
    …=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

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

  • Info Line 71, Column 117: entity was defined here
    …pe=728x90&login=youhot34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 1732, Column 150: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 1732, Column 150: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 1732, Column 150: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&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.

  • Info Line 71, Column 139: entity was defined here
    …34&cat=2&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 1732, Column 164: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 1732, Column 164: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 1732, Column 164: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

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

  • Info Line 71, Column 154: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 1732, Column 179: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 1732, Column 179: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 1732, Column 179: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

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

  • Info Line 71, Column 163: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 1732, Column 191: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 1732, Column 191: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 1732, Column 191: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&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 71, Column 183: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 1732, Column 207: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 1732, Column 207: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 1732, Column 207: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

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

  • Info Line 71, Column 189: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 1732, Column 222: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 1732, Column 222: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 1732, Column 222: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

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

  • Info Line 71, Column 205: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 1732, Column 243: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 1732, Column 243: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

    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 1732, Column 243: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_th…

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

  • Info Line 71, Column 226: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 1732, Column 256: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=1…

    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 1732, Column 256: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=1…

    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 1732, Column 256: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=1…

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

  • Info Line 71, Column 247: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 1732, Column 262: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&…

    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 1732, Column 273: reference not terminated by REFC delimiter
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=6768…

    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 1732, Column 273: reference to external entity in attribute value
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=6768…

    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 1732, Column 273: reference to entity "text_only" for which no system identifier could be generated
    …rl_color=008000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=6768…

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

  • Info Line 71, Column 261: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&…
  • Warning Line 1732, Column 286: reference not terminated by REFC delimiter
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

    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 1732, Column 286: reference to external entity in attribute value
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

    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 1732, Column 286: reference to entity "show_thumb" for which no system identifier could be generated
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

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

  • Info Line 71, Column 273: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681…
  • Warning Line 1732, Column 294: reference not terminated by REFC delimiter
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

    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 1732, Column 294: reference to external entity in attribute value
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

    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 1732, Column 294: reference to entity "idzone" for which no system identifier could be generated
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

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

  • Info Line 71, Column 286: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>
  • Warning Line 1732, Column 308: reference not terminated by REFC delimiter
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

    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 1732, Column 308: reference to external entity in attribute value
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

    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 1732, Column 308: reference to entity "idsite" for which no system identifier could be generated
    …8000&adult=0&sub=&text_only=0&show_thumb=&idzone=133864&idsite=67681"></script>

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

  • Info Line 71, Column 300: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=132898&idsite=67681"></script>
  • Error Line 1739, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 1739, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 1739, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 1739, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 1739, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 1739, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 1739, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 1739, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 1739, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 1739, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 1739, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=122936></iframe>

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

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

  • Warning Line 1749, Column 89: character "&" is the first character of a delimiter but occurred as data
    …e="ΟΡΟΙ ΣΥΜΜΕΤΟΧΗΣ ΣΤΙΣ ΥΠΗΡΕΣΙΕΣ SMS & ΦΩΝΗΣ">- Οροί Συμμετοχής Στις Υπηρεσίε…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1749, Column 135: character "&" is the first character of a delimiter but occurred as data
    …Σ ΣΤΙΣ ΥΠΗΡΕΣΙΕΣ SMS & ΦΩΝΗΣ">- Οροί Συμμετοχής Στις Υπηρεσίες Sms & Φωνής </a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1766, Column 8: end tag for "head" omitted, but OMITTAG NO was specified
    </html>

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

  • Info Line 4, Column 2: start tag was here
    	<head>
  • Error Line 1766, Column 8: "html" not finished but document ended
    </html>
  • Error Line 1766, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

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

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

Visitor Analysis

Daily Visitor
  • 1.633 visits
Daily Visitor