Apne Tv- Hindi Serials Online .Watch Hindi Punjabi Movies Online, Hindi punjabi Songs online.Latest Bollywood News and Much More ...

apne.tv
  • Domain Name
    apne.tv
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #7789
  • Page Size
    46.6 KB
  • Ip Address
    50.57.180.18
  • Heading
    H1: 0, H2: 10, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 34 JPG, 2 PNG

Website Meta Analysis

  • Title
    Apne TV Hindi Serials Online | Punjabi Movies | Songs | Radio | News | Watch Bollywood Videos
  • Meta Keyword
    Apne tv , Hindi Serials , Hindi Serials Online , Hindi movies , Hindi drama , Hindi dramas ,apne.tv,punjabi songs,punjabi movies
  • Meta Description
    Apne Tv- Hindi Serials Online .Watch Hindi Punjabi Movies Online, Hindi punjabi Songs online.Latest Bollywood News and Much More

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    50.57.180.18
  • Domain Age
    3 Years, 2 Months, 21 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from apne.tv.

HTML Analysis

  • date: Tue, 30 Jul 2013 15:27:41 GMT
  • server: Apache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 11354
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Whois Server Version 1.0

Domain names can now be registered with many different competing registrars.
Go to http://registrar.verisign-grs.com/whois/ for detailed information.

Domain Name: APNE.TV
Registrar: GODADDY.COM, LLC
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com
Name Server: DNS2.STABLETRANSIT.COM
Name Server: DNS1.STABLETRANSIT.COM
Status: CLIENT-RENEW-PROHIBITED
Status: CLIENT-XFER-PROHIBITED
Status: CLIENT-UPDATE-PROHIBITED
Status: CLIENT-DELETE-PROHIBITED
Updated Date: 10-may-2012
Creation Date: 26-may-2010
Expiration Date: 26-may-2013


>>> Last update of whois database: Thu, 24 May 2012 07:38:38 EDT

DNS Analysis


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

DNS Records

Answer records
apne.tv NS  dns1.stabletransit.com 3600s
apne.tv NS  dns2.stabletransit.com 3600s
apne.tv MX
preference: 20
exchange: mx2.emailsrvr.com
3600s
apne.tv MX
preference: 10
exchange: mx1.emailsrvr.com
3600s
apne.tv A 98.129.229.64 3600s
apne.tv SOA
server: dns1.stabletransit.com
email: ipadmin@stabletransit.com
serial: 1343344804
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
3600s

Authority records

Additional records

IP 50.57.180.18 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 104 Errors
  • 56 Warnings
Ratio Text/Html
  • 0.6343612334801763
Message Error
  • Error Line 5, Column 16: there is no attribute "property"
    <meta property="og:site_name" content="Apne TV"/>

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

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

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

  • Error Line 8, Column 52: document type does not allow element "html" here
    <html xmlns:fb="https://www.facebook.com/2008/fbml">

    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 8, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html xmlns:fb="https://www.facebook.com/2008/fbml">

    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 9, Column 7: document type does not allow element "title" here; assuming missing "head" start-tag
    <title>Apne TV Watch Hindi Serials Online | Punjabi Movies | Download Songs | R…
  • Error Line 18, Column 12: there is no attribute "NAME"
    <META NAME="ROBOTS" CONTENT="INDEX, FOLLOW, ARCHIVE" /> 

    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 18, Column 29: there is no attribute "CONTENT"
    <META NAME="ROBOTS" CONTENT="INDEX, FOLLOW, ARCHIVE" /> 

    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 18, Column 55: element "META" undefined
    <META NAME="ROBOTS" CONTENT="INDEX, FOLLOW, ARCHIVE" /> 

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

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

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

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

  • Error Line 66, Column 113: there is no attribute "class"
    …version:"1.3"};</script><script class="vclk_pub_code" type="text/javascript" s…

    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 66, Column 218: cannot generate system identifier for general entity "media_type"
    …t/js/adcodes/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></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 66, Column 218: general entity "media_type" not defined and no default entity
    …t/js/adcodes/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></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 66, Column 228: reference not terminated by REFC delimiter
    …es/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript…

    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 66, Column 228: reference to external entity in attribute value
    …es/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript…

    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 66, Column 228: reference to entity "media_type" for which no system identifier could be generated
    …es/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript…

    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 66, Column 217: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></scrip…
  • Warning Line 66, Column 231: cannot generate system identifier for general entity "version"
    …pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a…

    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 66, Column 231: general entity "version" not defined and no default entity
    …pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><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.

  • Warning Line 66, Column 238: reference not terminated by REFC delimiter
    ….min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="…

    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 66, Column 238: reference to external entity in attribute value
    ….min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="…

    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 66, Column 238: reference to entity "version" for which no system identifier could be generated
    ….min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="…

    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 66, Column 230: entity was defined here
    …/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><…
  • Warning Line 66, Column 243: cannot generate system identifier for general entity "exc"
    …js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http:…

    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 66, Column 243: general entity "exc" not defined and no default entity
    …js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http:…

    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 66, Column 246: reference not terminated by REFC delimiter
    …sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 66, Column 246: reference to external entity in attribute value
    …sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 66, Column 246: reference to entity "exc" for which no system identifier could be generated
    …sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 66, Column 242: entity was defined here
    ….js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http…
  • Warning Line 66, Column 328: cannot generate system identifier for general entity "m"
    ….fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http:…

    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 66, Column 328: general entity "m" not defined and no default entity
    ….fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http:…

    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 66, Column 329: reference not terminated by REFC delimiter
    …fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http:/…

    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 66, Column 329: reference to external entity in attribute value
    …fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http:/…

    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 66, Column 329: reference to entity "m" for which no system identifier could be generated
    …fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http:/…

    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 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 66, Column 332: cannot generate system identifier for general entity "c"
    …tclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://me…

    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 66, Column 332: general entity "c" not defined and no default entity
    …tclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://me…

    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 66, Column 333: reference not terminated by REFC delimiter
    …click.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://med…

    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 66, Column 333: reference to external entity in attribute value
    …click.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://med…

    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 66, Column 333: reference to entity "c" for which no system identifier could be generated
    …click.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://med…

    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 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 66, Column 412: cannot generate system identifier for general entity "tp"
    …a.fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 heig…

    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 66, Column 412: general entity "tp" not defined and no default entity
    …a.fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 heig…

    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 66, Column 414: reference not terminated by REFC delimiter
    …fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height…

    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 66, Column 414: reference to external entity in attribute value
    …fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height…

    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 66, Column 414: reference to entity "tp" for which no system identifier could be generated
    …fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height…

    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 66, Column 411: entity was defined here
    …ia.fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 hei…
  • Warning Line 66, Column 417: cannot generate system identifier for general entity "d"
    …tclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90…

    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 66, Column 417: general entity "d" not defined and no default entity
    …tclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90…

    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 66, Column 418: reference not terminated by REFC delimiter
    …click.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 …

    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 66, Column 418: reference to external entity in attribute value
    …click.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 …

    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 66, Column 418: reference to entity "d" for which no system identifier could be generated
    …click.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 …

    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 66, Column 416: entity was defined here
    …stclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=9…
  • Warning Line 66, Column 422: reference not terminated by REFC delimiter
    …k.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 bord…

    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 66, Column 422: reference to external entity in attribute value
    …k.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 bord…

    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 66, Column 422: reference to entity "c" for which no system identifier could be generated
    …k.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 bord…

    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 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 66, Column 425: cannot generate system identifier for general entity "vcm_acv"
    …et/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=…

    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 66, Column 425: general entity "vcm_acv" not defined and no default entity
    …et/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=…

    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 66, Column 432: reference not terminated by REFC delimiter
    …t.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></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 66, Column 432: reference to external entity in attribute value
    …t.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></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 66, Column 432: reference to entity "vcm_acv" for which no system identifier could be generated
    …t.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></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 66, Column 424: entity was defined here
    …net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border…
  • Error Line 66, Column 444: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></a></noscript>
  • Error Line 66, Column 455: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></a></noscript>
  • Error Line 66, Column 465: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></a></noscript>
  • Error Line 66, Column 466: required attribute "alt" not specified
    …id=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></a></noscript>

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

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

  • Error Line 66, Column 470: end tag for "img" omitted, but OMITTAG NO was specified
    …id=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border=1></a></noscript>

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

  • Info Line 66, Column 353: start tag was here
    …re?sid=69199&m=1&c=1" target="_blank"><img src="http://media.fastclick.net/w/g…
  • Warning Line 90, Column 108: character "&" is the first character of a delimiter but occurred as data
    …"bollywood-stars.html" title="Bollywood Actors & Actresses" >Bollywood</a></li>

    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 94, Column 21: end tag for "ul" which is not finished
                    </ul>

    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 264, Column 560: "SRK" is not a member of a group specified for any attribute
    …ligious-Politics-On-Overdrive.html'SRK, Kamal Haasan: Victims Of Religious Pol…
  • Error Line 264, Column 568: "Kamal" is not a member of a group specified for any attribute
    …Politics-On-Overdrive.html'SRK, Kamal Haasan: Victims Of Religious Politics On…
  • Error Line 264, Column 576: "Haasan:" is not a member of a group specified for any attribute
    …-On-Overdrive.html'SRK, Kamal Haasan: Victims Of Religious Politics On Overdri…
  • Error Line 264, Column 584: "Victims" is not a member of a group specified for any attribute
    …drive.html'SRK, Kamal Haasan: Victims Of Religious Politics On Overdrive title…
  • Error Line 264, Column 587: "Of" is not a member of a group specified for any attribute
    …ve.html'SRK, Kamal Haasan: Victims Of Religious Politics On Overdrive title='R…
  • Error Line 264, Column 597: "Religious" is not a member of a group specified for any attribute
    …K, Kamal Haasan: Victims Of Religious Politics On Overdrive title='Read SRK, K…
  • Error Line 264, Column 606: "Politics" is not a member of a group specified for any attribute
    …Haasan: Victims Of Religious Politics On Overdrive title='Read SRK, Kamal Haas…
  • Error Line 264, Column 609: "On" is not a member of a group specified for any attribute
    …san: Victims Of Religious Politics On Overdrive title='Read SRK, Kamal Haasan:…
  • Error Line 264, Column 619: "Overdrive" is not a member of a group specified for any attribute
    …ms Of Religious Politics On Overdrive title='Read SRK, Kamal Haasan: Victims O…
  • Warning Line 272, Column 229: cannot generate system identifier for general entity "media_id"
    …t/js/adcodes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=…

    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 272, Column 229: general entity "media_id" not defined and no default entity
    …t/js/adcodes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=…

    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 272, Column 237: reference not terminated by REFC delimiter
    …odes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=1"></scr…

    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 272, Column 237: reference to external entity in attribute value
    …odes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=1"></scr…

    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 272, Column 237: reference to entity "media_id" for which no system identifier could be generated
    …odes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=1"></scr…

    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 272, Column 228: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc…
  • Warning Line 272, Column 250: reference not terminated by REFC delimiter
    …min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=1"></script><noscript…

    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 272, Column 250: reference to external entity in attribute value
    …min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=1"></script><noscript…

    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 272, Column 250: reference to entity "media_type" for which no system identifier could be generated
    …min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc=1"></script><noscript…

    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 66, Column 217: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></scrip…
  • Warning Line 272, Column 260: reference not terminated by REFC delimiter
    …=69250&media_id=1&media_type=1&version=1.3&exc=1"></script><noscript><a href="…

    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 272, Column 260: reference to external entity in attribute value
    …=69250&media_id=1&media_type=1&version=1.3&exc=1"></script><noscript><a href="…

    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 272, Column 260: reference to entity "version" for which no system identifier could be generated
    …=69250&media_id=1&media_type=1&version=1.3&exc=1"></script><noscript><a href="…

    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 66, Column 230: entity was defined here
    …/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><…
  • Warning Line 272, Column 268: reference not terminated by REFC delimiter
    …edia_id=1&media_type=1&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 272, Column 268: reference to external entity in attribute value
    …edia_id=1&media_type=1&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 272, Column 268: reference to entity "exc" for which no system identifier could be generated
    …edia_id=1&media_type=1&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 66, Column 242: entity was defined here
    ….js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http…
  • Warning Line 272, Column 351: reference not terminated by REFC delimiter
    …fastclick.net/w/click.here?sid=69250&m=1&c=1" target="_blank"><img src="http:/…

    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 272, Column 351: reference to external entity in attribute value
    …fastclick.net/w/click.here?sid=69250&m=1&c=1" target="_blank"><img src="http:/…

    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 272, Column 351: reference to entity "m" for which no system identifier could be generated
    …fastclick.net/w/click.here?sid=69250&m=1&c=1" target="_blank"><img src="http:/…

    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 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 272, Column 355: reference not terminated by REFC delimiter
    …click.net/w/click.here?sid=69250&m=1&c=1" target="_blank"><img src="http://med…

    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 272, Column 355: reference to external entity in attribute value
    …click.net/w/click.here?sid=69250&m=1&c=1" target="_blank"><img src="http://med…

    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 272, Column 355: reference to entity "c" for which no system identifier could be generated
    …click.net/w/click.here?sid=69250&m=1&c=1" target="_blank"><img src="http://med…

    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 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 272, Column 435: reference not terminated by REFC delimiter
    ….fastclick.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 h…

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

  • Warning Line 272, Column 435: reference to external entity in attribute value
    ….fastclick.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 h…

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

  • Error Line 272, Column 435: reference to entity "m" for which no system identifier could be generated
    ….fastclick.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 h…

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

  • Info Line 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 272, Column 440: reference not terminated by REFC delimiter
    …click.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height…

    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 272, Column 440: reference to external entity in attribute value
    …click.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height…

    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 272, Column 440: reference to entity "tp" for which no system identifier could be generated
    …click.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height…

    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 66, Column 411: entity was defined here
    …ia.fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 hei…
  • Warning Line 272, Column 444: reference not terminated by REFC delimiter
    …k.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 …

    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 272, Column 444: reference to external entity in attribute value
    …k.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 …

    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 272, Column 444: reference to entity "d" for which no system identifier could be generated
    …k.net/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 …

    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 66, Column 416: entity was defined here
    …stclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=9…
  • Warning Line 272, Column 448: reference not terminated by REFC delimiter
    …t/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 bord…

    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 272, Column 448: reference to external entity in attribute value
    …t/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 bord…

    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 272, Column 448: reference to entity "c" for which no system identifier could be generated
    …t/w/get.media?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 bord…

    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 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 272, Column 458: reference not terminated by REFC delimiter
    …dia?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></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 272, Column 458: reference to external entity in attribute value
    …dia?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></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 272, Column 458: reference to entity "vcm_acv" for which no system identifier could be generated
    …dia?sid=69250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></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 66, Column 424: entity was defined here
    …net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border…
  • Error Line 272, Column 470: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></a></noscript>
  • Error Line 272, Column 481: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></a></noscript>
  • Error Line 272, Column 491: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …9250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></a></noscript>
  • Error Line 272, Column 492: required attribute "alt" not specified
    …9250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></a></noscript>

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

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

  • Error Line 272, Column 496: end tag for "img" omitted, but OMITTAG NO was specified
    …9250&m=1&tp=1&d=s&c=1&vcm_acv=1.3" width=468 height=60 border=1></a></noscript>

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

  • Info Line 272, Column 375: start tag was here
    …re?sid=69250&m=1&c=1" target="_blank"><img src="http://media.fastclick.net/w/g…
  • Warning Line 428, Column 237: reference not terminated by REFC delimiter
    …odes/pubcode.min.js?sid=69199&media_id=6&media_type=8&version=1.3&exc=1"></scr…

    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 428, Column 237: reference to external entity in attribute value
    …odes/pubcode.min.js?sid=69199&media_id=6&media_type=8&version=1.3&exc=1"></scr…

    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 428, Column 237: reference to entity "media_id" for which no system identifier could be generated
    …odes/pubcode.min.js?sid=69199&media_id=6&media_type=8&version=1.3&exc=1"></scr…

    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 272, Column 228: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc…
  • Warning Line 428, Column 250: reference not terminated by REFC delimiter
    …min.js?sid=69199&media_id=6&media_type=8&version=1.3&exc=1"></script><noscript…

    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 428, Column 250: reference to external entity in attribute value
    …min.js?sid=69199&media_id=6&media_type=8&version=1.3&exc=1"></script><noscript…

    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 428, Column 250: reference to entity "media_type" for which no system identifier could be generated
    …min.js?sid=69199&media_id=6&media_type=8&version=1.3&exc=1"></script><noscript…

    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 66, Column 217: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></scrip…
  • Warning Line 428, Column 260: reference not terminated by REFC delimiter
    …=69199&media_id=6&media_type=8&version=1.3&exc=1"></script><noscript><a href="…

    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 428, Column 260: reference to external entity in attribute value
    …=69199&media_id=6&media_type=8&version=1.3&exc=1"></script><noscript><a href="…

    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 428, Column 260: reference to entity "version" for which no system identifier could be generated
    …=69199&media_id=6&media_type=8&version=1.3&exc=1"></script><noscript><a href="…

    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 66, Column 230: entity was defined here
    …/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><…
  • Warning Line 428, Column 268: reference not terminated by REFC delimiter
    …edia_id=6&media_type=8&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 428, Column 268: reference to external entity in attribute value
    …edia_id=6&media_type=8&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 428, Column 268: reference to entity "exc" for which no system identifier could be generated
    …edia_id=6&media_type=8&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 66, Column 242: entity was defined here
    ….js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http…
  • Warning Line 428, Column 351: reference not terminated by REFC delimiter
    …fastclick.net/w/click.here?sid=69199&m=6&c=1" target="_blank"><img src="http:/…

    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 428, Column 351: reference to external entity in attribute value
    …fastclick.net/w/click.here?sid=69199&m=6&c=1" target="_blank"><img src="http:/…

    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 428, Column 351: reference to entity "m" for which no system identifier could be generated
    …fastclick.net/w/click.here?sid=69199&m=6&c=1" target="_blank"><img src="http:/…

    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 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 428, Column 355: reference not terminated by REFC delimiter
    …click.net/w/click.here?sid=69199&m=6&c=1" target="_blank"><img src="http://med…

    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 428, Column 355: reference to external entity in attribute value
    …click.net/w/click.here?sid=69199&m=6&c=1" target="_blank"><img src="http://med…

    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 428, Column 355: reference to entity "c" for which no system identifier could be generated
    …click.net/w/click.here?sid=69199&m=6&c=1" target="_blank"><img src="http://med…

    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 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 428, Column 435: reference not terminated by REFC delimiter
    ….fastclick.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 h…

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

  • Warning Line 428, Column 435: reference to external entity in attribute value
    ….fastclick.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 h…

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

  • Error Line 428, Column 435: reference to entity "m" for which no system identifier could be generated
    ….fastclick.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 h…

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

  • Info Line 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 428, Column 440: reference not terminated by REFC delimiter
    …click.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height…

    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 428, Column 440: reference to external entity in attribute value
    …click.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height…

    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 428, Column 440: reference to entity "tp" for which no system identifier could be generated
    …click.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height…

    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 66, Column 411: entity was defined here
    …ia.fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 hei…
  • Warning Line 428, Column 444: reference not terminated by REFC delimiter
    …k.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250…

    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 428, Column 444: reference to external entity in attribute value
    …k.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250…

    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 428, Column 444: reference to entity "d" for which no system identifier could be generated
    …k.net/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250…

    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 66, Column 416: entity was defined here
    …stclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=9…
  • Warning Line 428, Column 448: reference not terminated by REFC delimiter
    …t/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 bor…

    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 428, Column 448: reference to external entity in attribute value
    …t/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 bor…

    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 428, Column 448: reference to entity "c" for which no system identifier could be generated
    …t/w/get.media?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 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.

  • Info Line 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 428, Column 458: reference not terminated by REFC delimiter
    …dia?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></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 428, Column 458: reference to external entity in attribute value
    …dia?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></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 428, Column 458: reference to entity "vcm_acv" for which no system identifier could be generated
    …dia?sid=69199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></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 66, Column 424: entity was defined here
    …net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border…
  • Error Line 428, Column 470: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></a></noscript>
  • Error Line 428, Column 481: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></a></noscript>
  • Error Line 428, Column 492: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></a></noscript>
  • Error Line 428, Column 493: required attribute "alt" not specified
    …199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></a></noscript>

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

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

  • Error Line 428, Column 497: end tag for "img" omitted, but OMITTAG NO was specified
    …199&m=6&tp=8&d=s&c=1&vcm_acv=1.3" width=300 height=250 border=1></a></noscript>

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

  • Info Line 428, Column 375: start tag was here
    …re?sid=69199&m=6&c=1" target="_blank"><img src="http://media.fastclick.net/w/g…
  • Error Line 453, Column 33: ID "recent-comments-2" already defined
                            <li id="recent-comments-2" class="widget widget_recent_…

    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 435, Column 31: ID "recent-comments-2" first defined here
                          <li id="recent-comments-2" class="widget widget_recent_co…
  • Error Line 455, Column 13: ID "recentcomments" already defined
        <ul id="recentcomments">

    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 437, Column 14: ID "recentcomments" first defined here
         <ul id="recentcomments">           <li class="recentcomments" ><a href="ht…
  • Error Line 473, Column 25: ID "banner300-top-right" already defined
                    <li id="banner300-top-right">

    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 426, Column 33: ID "banner300-top-right" first defined here
                            <li id="banner300-top-right">
  • Error Line 477, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…

    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 477, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 477, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…

    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 477, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 477, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 477, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 477, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…

    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 477, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 477, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…

    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 477, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 477, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…

    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 477, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Error Line 477, Column 90: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive.com/st?…

    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 477, Column 145: cannot generate system identifier for general entity "ad_size"
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=…

    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 477, Column 145: general entity "ad_size" not defined and no default entity
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=…

    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 477, Column 152: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_U…

    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 477, Column 152: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_U…

    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 477, Column 152: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_U…

    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 477, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url…
  • Warning Line 477, Column 161: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IF…

    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 477, Column 161: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IF…

    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 477, Column 168: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 168: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 168: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></I…
  • Warning Line 477, Column 177: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 177: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 184: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 184: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 184: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

    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 477, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 477, Column 196: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=300x250&section=2849466&pub_url=${PUB_URL}"></IFRAME>

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

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

    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 426, Column 33: ID "banner300-top-right" first defined here
                            <li id="banner300-top-right">
  • Warning Line 486, Column 237: reference not terminated by REFC delimiter
    …odes/pubcode.min.js?sid=69199&media_id=7&media_type=9&version=1.3&exc=1"></scr…

    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 486, Column 237: reference to external entity in attribute value
    …odes/pubcode.min.js?sid=69199&media_id=7&media_type=9&version=1.3&exc=1"></scr…

    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 486, Column 237: reference to entity "media_id" for which no system identifier could be generated
    …odes/pubcode.min.js?sid=69199&media_id=7&media_type=9&version=1.3&exc=1"></scr…

    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 272, Column 228: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69250&media_id=1&media_type=1&version=1.3&exc…
  • Warning Line 486, Column 250: reference not terminated by REFC delimiter
    …min.js?sid=69199&media_id=7&media_type=9&version=1.3&exc=1"></script><noscript…

    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 486, Column 250: reference to external entity in attribute value
    …min.js?sid=69199&media_id=7&media_type=9&version=1.3&exc=1"></script><noscript…

    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 486, Column 250: reference to entity "media_type" for which no system identifier could be generated
    …min.js?sid=69199&media_id=7&media_type=9&version=1.3&exc=1"></script><noscript…

    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 66, Column 217: entity was defined here
    …et/js/adcodes/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></scrip…
  • Warning Line 486, Column 260: reference not terminated by REFC delimiter
    …=69199&media_id=7&media_type=9&version=1.3&exc=1"></script><noscript><a href="…

    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 486, Column 260: reference to external entity in attribute value
    …=69199&media_id=7&media_type=9&version=1.3&exc=1"></script><noscript><a href="…

    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 486, Column 260: reference to entity "version" for which no system identifier could be generated
    …=69199&media_id=7&media_type=9&version=1.3&exc=1"></script><noscript><a href="…

    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 66, Column 230: entity was defined here
    …/pubcode.min.js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><…
  • Warning Line 486, Column 268: reference not terminated by REFC delimiter
    …edia_id=7&media_type=9&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 486, Column 268: reference to external entity in attribute value
    …edia_id=7&media_type=9&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 486, Column 268: reference to entity "exc" for which no system identifier could be generated
    …edia_id=7&media_type=9&version=1.3&exc=1"></script><noscript><a href="http://m…

    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 66, Column 242: entity was defined here
    ….js?sid=69199&media_type=5&version=1.3&exc=1"></script><noscript><a href="http…
  • Warning Line 486, Column 351: reference not terminated by REFC delimiter
    …fastclick.net/w/click.here?sid=69199&m=7&c=1" target="_blank"><img src="http:/…

    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 486, Column 351: reference to external entity in attribute value
    …fastclick.net/w/click.here?sid=69199&m=7&c=1" target="_blank"><img src="http:/…

    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 486, Column 351: reference to entity "m" for which no system identifier could be generated
    …fastclick.net/w/click.here?sid=69199&m=7&c=1" target="_blank"><img src="http:/…

    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 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 486, Column 355: reference not terminated by REFC delimiter
    …click.net/w/click.here?sid=69199&m=7&c=1" target="_blank"><img src="http://med…

    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 486, Column 355: reference to external entity in attribute value
    …click.net/w/click.here?sid=69199&m=7&c=1" target="_blank"><img src="http://med…

    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 486, Column 355: reference to entity "c" for which no system identifier could be generated
    …click.net/w/click.here?sid=69199&m=7&c=1" target="_blank"><img src="http://med…

    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 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 486, Column 435: reference not terminated by REFC delimiter
    ….fastclick.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 h…

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

  • Warning Line 486, Column 435: reference to external entity in attribute value
    ….fastclick.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 h…

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

  • Error Line 486, Column 435: reference to entity "m" for which no system identifier could be generated
    ….fastclick.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 h…

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

  • Info Line 66, Column 327: entity was defined here
    …a.fastclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http…
  • Warning Line 486, Column 440: reference not terminated by REFC delimiter
    …click.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height…

    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 486, Column 440: reference to external entity in attribute value
    …click.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height…

    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 486, Column 440: reference to entity "tp" for which no system identifier could be generated
    …click.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height…

    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 66, Column 411: entity was defined here
    …ia.fastclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 hei…
  • Warning Line 486, Column 444: reference not terminated by REFC delimiter
    …k.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150…

    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 486, Column 444: reference to external entity in attribute value
    …k.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150…

    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 486, Column 444: reference to entity "d" for which no system identifier could be generated
    …k.net/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150…

    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 66, Column 416: entity was defined here
    …stclick.net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=9…
  • Warning Line 486, Column 448: reference not terminated by REFC delimiter
    …t/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 bor…

    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 486, Column 448: reference to external entity in attribute value
    …t/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 bor…

    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 486, Column 448: reference to entity "c" for which no system identifier could be generated
    …t/w/get.media?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 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.

  • Info Line 66, Column 331: entity was defined here
    …stclick.net/w/click.here?sid=69199&m=1&c=1" target="_blank"><img src="http://m…
  • Warning Line 486, Column 458: reference not terminated by REFC delimiter
    …dia?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></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 486, Column 458: reference to external entity in attribute value
    …dia?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></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 486, Column 458: reference to entity "vcm_acv" for which no system identifier could be generated
    …dia?sid=69199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></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 66, Column 424: entity was defined here
    …net/w/get.media?sid=69199&tp=5&d=s&c=1&vcm_acv=1.3" width=728 height=90 border…
  • Error Line 486, Column 470: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></a></noscript>
  • Error Line 486, Column 481: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></a></noscript>
  • Error Line 486, Column 492: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></a></noscript>
  • Error Line 486, Column 493: required attribute "alt" not specified
    …199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></a></noscript>

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

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

  • Error Line 486, Column 497: end tag for "img" omitted, but OMITTAG NO was specified
    …199&m=7&tp=9&d=s&c=1&vcm_acv=1.3" width=180 height=150 border=1></a></noscript>

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

  • Info Line 486, Column 375: start tag was here
    …re?sid=69199&m=7&c=1" target="_blank"><img src="http://media.fastclick.net/w/g…
  • Warning Line 499, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1644829&101" alt="histats.com" border="0"></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 499, Column 150: end tag for "img" omitted, but OMITTAG NO was specified
    …ic1.histats.com/0.gif?1644829&101" alt="histats.com" border="0"></a></noscript>

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

  • Info Line 499, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 521, Column 17: there is no attribute "send"
    		<fb:like send="false" layout="button_count" width="50" show_faces="false" fon…

    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 521, Column 32: there is no attribute "layout"
    		<fb:like send="false" layout="button_count" width="50" show_faces="false" fon…

    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 521, Column 53: there is no attribute "width"
    …d="false" layout="button_count" width="50" show_faces="false" font="tahoma"></…

    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 521, Column 69: there is no attribute "show_faces"
    …e" layout="button_count" width="50" show_faces="false" font="tahoma"></fb:like>

    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 521, Column 82: there is no attribute "font"
    …e" layout="button_count" width="50" show_faces="false" font="tahoma"></fb:like>

    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 521, Column 90: element "fb:like" undefined
    …e" layout="button_count" width="50" show_faces="false" font="tahoma"></fb:like>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 547, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 505, Column 2: start tag was here
    	<div class="limit">
  • Error Line 547, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 501, Column 1: start tag was here
    <div id="footer" class="clearfix">
  • Error Line 547, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 103, Column 9: start tag was here
            <div id="page" class="clearfix">
  • Error Line 547, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 102, Column 5: start tag was here
        <div id="wrap">
  • Error Line 547, Column 15: "head" not finished but document ended
    </body></html>
  • Error Line 547, Column 15: end tag for "head" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 4, Column 5: start tag was here
        <head profile="http://gmpg.org/xfn/11">
  • Error Line 547, Column 15: "html" not finished but document ended
    </body></html>
  • Error Line 547, Column 15: end tag for "html" omitted, but OMITTAG NO was specified
    </body></html>

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

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

Visitor Analysis

Daily Visitor
  • 8.167 visits