ABEZARA.com ...

abezara.com
  • Domain Name
    abezara.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #566817
  • Page Size
    82.4 KB
  • Ip Address
    50.62.121.1
  • Heading
    H1: 0, H2: 23, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 6 JPG, 49 PNG

Website Meta Analysis

  • Title
    ABEZARA.com
  • Meta Keyword
    iumori, komedia, anegdotebi, anekdoti, prikoli, sasacilo, saxaliso
  • Meta Description
    ABEZARA.com

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    50.62.121.1
  • Domain Age
    2 Years, 4 Months, 21 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 07 Aug 2013 12:54:50 GMT
  • server: Apache
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for abezara.com

DNS Analysis


DNS servers
ns69.domaincontrol.com [216.69.185.45]
ns70.domaincontrol.com [208.109.255.45]

DNS Records

Answer records
abezara.com A 184.168.138.1 3600s
abezara.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
abezara.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
abezara.com NS  ns69.domaincontrol.com 3600s
abezara.com NS  ns70.domaincontrol.com 3600s
abezara.com SOA
server: ns69.domaincontrol.com
email: dns@jomax.net
serial: 2011032902
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 130 Errors
  • 85 Warnings
Ratio Text/Html
  • 0.5589482913882174
Message Error
  • Error Line 23, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

    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 81, Column 48: there is no attribute "height"
            <div class="top-banner"><IFRAME height=60 marginHeight=0

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

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

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

  • Error Line 81, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <div class="top-banner"><IFRAME height=60 marginHeight=0
  • Error Line 81, Column 64: there is no attribute "marginHeight"
            <div class="top-banner"><IFRAME height=60 marginHeight=0

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

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

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

  • Error Line 81, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <div class="top-banner"><IFRAME height=60 marginHeight=0
  • Error Line 82, Column 5: there is no attribute "src"
    src="http://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-49988229847221…

    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 82, Column 83: cannot generate system identifier for general entity "dt"
    …ad/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=4…

    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 82, Column 83: general entity "dt" not defined and no default entity
    …ad/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=4…

    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 82, Column 85: reference not terminated by REFC delimiter
    …/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468…

    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 82, Column 85: reference to external entity in attribute value
    …/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468…

    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 82, Column 85: reference to entity "dt" for which no system identifier could be generated
    …/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468…

    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 82, Column 82: entity was defined here
    …ead/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=…
  • Warning Line 82, Column 100: cannot generate system identifier for general entity "lmt"
    …pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=h…

    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 82, Column 100: general entity "lmt" not defined and no default entity
    …pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=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.

  • Warning Line 82, Column 103: reference not terminated by REFC delimiter
    …-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html…

    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 82, Column 103: reference to external entity in attribute value
    …-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html…

    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 82, Column 103: reference to entity "lmt" for which no system identifier could be generated
    …-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html…

    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 82, Column 99: entity was defined here
    …-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=…
  • Warning Line 82, Column 115: cannot generate system identifier for general entity "format"
    …22167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator=…

    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 82, Column 115: general entity "format" not defined and no default entity
    …22167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator=…

    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 82, Column 121: reference not terminated by REFC delimiter
    …dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator=123441…

    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 82, Column 121: reference to external entity in attribute value
    …dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator=123441…

    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 82, Column 121: reference to entity "format" for which no system identifier could be generated
    …dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator=123441…

    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 82, Column 114: entity was defined here
    …722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator…
  • Warning Line 82, Column 132: cannot generate system identifier for general entity "output"
    …18000&lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&cha…

    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 82, Column 132: general entity "output" not defined and no default entity
    …18000&lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&cha…

    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 82, Column 138: reference not terminated by REFC delimiter
    …lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&channel=7…

    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 82, Column 138: reference to external entity in attribute value
    …lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&channel=7…

    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 82, Column 138: reference to entity "output" for which no system identifier could be generated
    …lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&channel=7…

    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 82, Column 131: entity was defined here
    …618000&lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&ch…
  • Warning Line 82, Column 144: cannot generate system identifier for general entity "correlator"
    …34419618&format=468x60_as&output=html&correlator=1234419618000&channel=7516211…

    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 82, Column 144: general entity "correlator" not defined and no default entity
    …34419618&format=468x60_as&output=html&correlator=1234419618000&channel=7516211…

    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 82, Column 154: reference not terminated by REFC delimiter
    …ormat=468x60_as&output=html&correlator=1234419618000&channel=7516211662&url=ht…

    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 82, Column 154: reference to external entity in attribute value
    …ormat=468x60_as&output=html&correlator=1234419618000&channel=7516211662&url=ht…

    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 82, Column 154: reference to entity "correlator" for which no system identifier could be generated
    …ormat=468x60_as&output=html&correlator=1234419618000&channel=7516211662&url=ht…

    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 82, Column 143: entity was defined here
    …234419618&format=468x60_as&output=html&correlator=1234419618000&channel=751621…
  • Warning Line 82, Column 169: cannot generate system identifier for general entity "channel"
    …&output=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.…

    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 82, Column 169: general entity "channel" not defined and no default entity
    …&output=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.…

    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 82, Column 176: reference not terminated by REFC delimiter
    …=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality…

    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 82, Column 176: reference to external entity in attribute value
    …=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality…

    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 82, Column 176: reference to entity "channel" for which no system identifier could be generated
    …=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality…

    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 82, Column 168: entity was defined here
    …s&output=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww…
  • Warning Line 82, Column 188: cannot generate system identifier for general entity "url"
    …ator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4…

    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 82, Column 188: general entity "url" not defined and no default entity
    …ator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4…

    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 82, Column 191: reference not terminated by REFC delimiter
    …r=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4-le…

    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 82, Column 191: reference to external entity in attribute value
    …r=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4-le…

    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 82, Column 191: reference to entity "url" for which no system identifier could be generated
    …r=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4-le…

    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 82, Column 187: entity was defined here
    …lator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-…
  • Warning Line 82, Column 241: cannot generate system identifier for general entity "color_bg"
    …2Fwww.quality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_…

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

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

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

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

  • Error Line 82, Column 241: general entity "color_bg" not defined and no default entity
    …2Fwww.quality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_…

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

  • Warning Line 82, Column 249: reference not terminated by REFC delimiter
    …ality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=266…

    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 82, Column 249: reference to external entity in attribute value
    …ality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=266…

    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 82, Column 249: reference to entity "color_bg" for which no system identifier could be generated
    …ality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=266…

    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 82, Column 240: entity was defined here
    …%2Fwww.quality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color…
  • Warning Line 82, Column 257: cannot generate system identifier for general entity "color_text"
    …surance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&colo…

    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 82, Column 257: general entity "color_text" not defined and no default entity
    …surance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&colo…

    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 82, Column 267: reference not terminated by REFC delimiter
    …less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffff…

    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 82, Column 267: reference to external entity in attribute value
    …less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffff…

    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 82, Column 267: reference to entity "color_text" for which no system identifier could be generated
    …less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffff…

    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 82, Column 256: entity was defined here
    …nsurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&col…
  • Warning Line 82, Column 275: cannot generate system identifier for general entity "color_link"
    …%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color…

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

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

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

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

  • Error Line 82, Column 275: general entity "color_link" not defined and no default entity
    …%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color…

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

  • Warning Line 82, Column 285: reference not terminated by REFC delimiter
    …bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ff…

    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 82, Column 285: reference to external entity in attribute value
    …bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ff…

    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 82, Column 285: reference to entity "color_link" for which no system identifier could be generated
    …bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ff…

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

  • Info Line 82, Column 274: entity was defined here
    …m%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&colo…
  • Warning Line 82, Column 293: cannot generate system identifier for general entity "color_url"
    …f&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=…

    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 82, Column 293: general entity "color_url" not defined and no default entity
    …f&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=…

    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 82, Column 302: reference not terminated by REFC delimiter
    …ext=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=htt…

    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 82, Column 302: reference to external entity in attribute value
    …ext=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=htt…

    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 82, Column 302: reference to entity "color_url" for which no system identifier could be generated
    …ext=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=htt…

    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 82, Column 292: entity was defined here
    …ff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea…
  • Warning Line 82, Column 310: cannot generate system identifier for general entity "color_border"
    …ff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%…

    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 82, Column 310: general entity "color_border" not defined and no default entity
    …ff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%…

    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 82, Column 322: reference not terminated by REFC delimiter
    …k=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google…

    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 82, Column 322: reference to external entity in attribute value
    …k=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google…

    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 82, Column 322: reference to entity "color_border" for which no system identifier could be generated
    …k=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google…

    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 82, Column 309: entity was defined here
    …fff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F…
  • Warning Line 82, Column 330: cannot generate system identifier for general entity "ea"
    …&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fs…

    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 82, Column 330: general entity "ea" not defined and no default entity
    …&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fs…

    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 82, Column 332: reference not terminated by REFC delimiter
    …olor_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsea…

    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 82, Column 332: reference to external entity in attribute value
    …olor_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsea…

    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 82, Column 332: reference to entity "ea" for which no system identifier could be generated
    …olor_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsea…

    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 82, Column 329: entity was defined here
    …9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2F…
  • Warning Line 82, Column 335: cannot generate system identifier for general entity "ref"
    …r_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch…

    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 82, Column 335: general entity "ref" not defined and no default entity
    …r_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch…

    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 82, Column 338: reference not terminated by REFC delimiter
    …rl=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch%3F…

    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 82, Column 338: reference to external entity in attribute value
    …rl=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch%3F…

    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 82, Column 338: reference to entity "ref" for which no system identifier could be generated
    …rl=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch%3F…

    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 82, Column 334: entity was defined here
    …or_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearc…
  • Warning Line 82, Column 466: cannot generate system identifier for general entity "frm"
    …sting%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid…

    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 82, Column 466: general entity "frm" not defined and no default entity
    …sting%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid…

    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 82, Column 469: reference not terminated by REFC delimiter
    …ng%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12…

    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 82, Column 469: reference to external entity in attribute value
    …ng%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12…

    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 82, Column 469: reference to entity "frm" for which no system identifier could be generated
    …ng%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12…

    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 82, Column 465: entity was defined here
    …osting%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_si…
  • Warning Line 82, Column 472: cannot generate system identifier for general entity "ga_vid"
    …26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12344…

    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 82, Column 472: general entity "ga_vid" not defined and no default entity
    …26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12344…

    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 82, Column 478: reference not terminated by REFC delimiter
    …D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&…

    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 82, Column 478: reference to external entity in attribute value
    …D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&…

    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 82, Column 478: reference to entity "ga_vid" for which no system identifier could be generated
    …D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&…

    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 82, Column 471: entity was defined here
    …%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234…
  • Warning Line 82, Column 500: cannot generate system identifier for general entity "ga_sid"
    …g10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash…

    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 82, Column 500: general entity "ga_sid" not defined and no default entity
    …g10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash…

    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 82, Column 506: reference not terminated by REFC delimiter
    …m=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.…

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

  • Warning Line 82, Column 506: reference to external entity in attribute value
    …m=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.…

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

  • Error Line 82, Column 506: reference to entity "ga_sid" for which no system identifier could be generated
    …m=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.…

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

  • Info Line 82, Column 499: entity was defined here
    …Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flas…
  • Warning Line 82, Column 518: cannot generate system identifier for general entity "ga_hid"
    …39969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=76…

    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 82, Column 518: general entity "ga_hid" not defined and no default entity
    …39969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=76…

    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 82, Column 524: reference not terminated by REFC delimiter
    …57.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=…

    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 82, Column 524: reference to external entity in attribute value
    …57.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=…

    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 82, Column 524: reference to entity "ga_hid" for which no system identifier could be generated
    …57.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=…

    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 82, Column 517: entity was defined here
    …739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=7…
  • Warning Line 82, Column 535: cannot generate system identifier for general entity "flash"
    …18&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=7…

    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 82, Column 535: general entity "flash" not defined and no default entity
    …18&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=7…

    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 82, Column 540: reference not terminated by REFC delimiter
    …_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&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 82, Column 540: reference to external entity in attribute value
    …_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&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 82, Column 540: reference to entity "flash" for which no system identifier could be generated
    …_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&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 82, Column 534: entity was defined here
    …618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=…
  • Warning Line 82, Column 552: cannot generate system identifier for general entity "u_h"
    …618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd…

    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 82, Column 552: general entity "u_h" not defined and no default entity
    …618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd…

    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 82, Column 555: reference not terminated by REFC delimiter
    …&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32…

    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 82, Column 555: reference to external entity in attribute value
    …&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32…

    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 82, Column 555: reference to entity "u_h" for which no system identifier could be generated
    …&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32…

    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 82, Column 551: entity was defined here
    …9618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_c…
  • Warning Line 82, Column 560: cannot generate system identifier for general entity "u_w"
    …id=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz…

    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 82, Column 560: general entity "u_w" not defined and no default entity
    …id=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz…

    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 82, Column 563: reference not terminated by REFC delimiter
    …805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-3…

    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 82, Column 563: reference to external entity in attribute value
    …805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-3…

    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 82, Column 563: reference to entity "u_w" for which no system identifier could be generated
    …805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-3…

    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 82, Column 559: entity was defined here
    …hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_t…
  • Warning Line 82, Column 569: cannot generate system identifier for general entity "u_ah"
    …676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_h…

    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 82, Column 569: general entity "u_ah" not defined and no default entity
    …676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_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.

  • Warning Line 82, Column 573: reference not terminated by REFC delimiter
    …flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7…

    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 82, Column 573: reference to external entity in attribute value
    …flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7…

    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 82, Column 573: reference to entity "u_ah" for which no system identifier could be generated
    …flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7…

    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 82, Column 568: entity was defined here
    …1676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_…
  • Warning Line 82, Column 578: cannot generate system identifier for general entity "u_aw"
    …=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_ja…

    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 82, Column 578: general entity "u_aw" not defined and no default entity
    …=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_ja…

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

  • Warning Line 82, Column 582: reference not terminated by REFC delimiter
    …0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=t…

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

  • Warning Line 82, Column 582: reference to external entity in attribute value
    …0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=t…

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

  • Error Line 82, Column 582: reference to entity "u_aw" for which no system identifier could be generated
    …0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=t…

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

  • Info Line 82, Column 577: entity was defined here
    …h=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_j…
  • Warning Line 82, Column 588: cannot generate system identifier for general entity "u_cd"
    …6&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dt…

    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 82, Column 588: general entity "u_cd" not defined and no default entity
    …6&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dt…

    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 82, Column 592: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28…

    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 82, Column 592: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28…

    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 82, Column 592: reference to entity "u_cd" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28…

    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 82, Column 587: entity was defined here
    …36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&d…
  • Warning Line 82, Column 596: cannot generate system identifier for general entity "u_tz"
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 596: general entity "u_tz" not defined and no default entity
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 600: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 600: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 600: reference to entity "u_tz" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 595: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Warning Line 82, Column 606: cannot generate system identifier for general entity "u_his"
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 606: general entity "u_his" not defined and no default entity
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 611: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 611: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 611: reference to entity "u_his" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 605: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Warning Line 82, Column 614: cannot generate system identifier for general entity "u_java"
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 614: general entity "u_java" not defined and no default entity
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 620: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 620: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 620: reference to entity "u_java" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 613: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Warning Line 82, Column 626: cannot generate system identifier for general entity "dtd"
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 626: general entity "dtd" not defined and no default entity
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 629: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 629: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 629: reference to entity "dtd" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 625: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Error Line 83, Column 13: there is no attribute "frameBorder"
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0

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

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

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

  • Error Line 83, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 83, Column 21: there is no attribute "width"
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0

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

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

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

  • Error Line 83, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 83, Column 43: "allowTransparency" is not a member of a group specified for any attribute
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 83, Column 48: there is no attribute "name"
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0

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

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

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

  • Error Line 83, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 83, Column 77: there is no attribute "marginWidth"
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0

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

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

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

  • Error Line 83, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=468 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 84, Column 11: there is no attribute "scrolling"
    scrolling=no></IFRAME></center></div>

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

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

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

  • Error Line 84, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    scrolling=no></IFRAME></center></div>
  • Error Line 84, Column 13: element "IFRAME" undefined
    scrolling=no></IFRAME></center></div>

    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 84, Column 31: end tag for element "center" which is not open
    scrolling=no></IFRAME></center></div>

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

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

  • Error Line 86, Column 34: there is no attribute "name"
                <form action="" name="searchform" method="post">

    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 87, Column 64: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="hidden" name="do" value="search" />

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

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

  • Error Line 88, Column 71: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="hidden" name="subaction" value="search" />

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

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

  • Error Line 89, Column 233: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ნდათ...';" onfocus="if(this.value=='მოძებნეთ რაც გინდათ...') this.value='';" />

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

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

  • Error Line 90, Column 61: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="submit" class="search-submit" />

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

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

  • Error Line 97, Column 91: an attribute specification must start with a name or name token
    …//abezara.com/index.php?do=register" style="color: #fff;"">რეგისტრაცია</a></li>

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

  • Error Line 108, Column 42: ID "login" already defined
    			<input name="login" type="hidden" id="login" value="submit" />

    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 93, Column 18: ID "login" first defined here
            <div id="login">
  • Warning Line 117, Column 43: cannot generate system identifier for general entity "category"
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>

    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 117, Column 43: general entity "category" not defined and no default entity
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>

    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 117, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>

    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 117, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>

    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 117, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 118, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=rchevebi">რჩევები</a></li>

    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 118, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=rchevebi">რჩევები</a></li>

    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 118, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=rchevebi">რჩევები</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 119, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=statusebi">სტატუსები</a></li>

    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 119, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=statusebi">სტატუსები</a></li>

    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 119, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=statusebi">სტატუსები</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 120, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=kultura">კულტურა</a></li>

    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 120, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=kultura">კულტურა</a></li>

    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 120, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=kultura">კულტურა</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 121, Column 51: reference not terminated by REFC delimiter
    …         <li><a href="index.php?do=cat&category=literatura">ლიტერატურა</a></li>

    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 121, Column 51: reference to external entity in attribute value
    …         <li><a href="index.php?do=cat&category=literatura">ლიტერატურა</a></li>

    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 121, Column 51: reference to entity "category" for which no system identifier could be generated
    …         <li><a href="index.php?do=cat&category=literatura">ლიტერატურა</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 122, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=horoskopi">ჰოროსკოპი</a></li>

    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 122, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=horoskopi">ჰოროსკოპი</a></li>

    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 122, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=horoskopi">ჰოროსკოპი</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 123, Column 51: reference not terminated by REFC delimiter
    …         <li><a href="index.php?do=cat&category=saintereso">საინტერესო</a></li>

    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 123, Column 51: reference to external entity in attribute value
    …         <li><a href="index.php?do=cat&category=saintereso">საინტერესო</a></li>

    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 123, Column 51: reference to entity "category" for which no system identifier could be generated
    …         <li><a href="index.php?do=cat&category=saintereso">საინტერესო</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 124, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=testi">ტესტები</a></li>

    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 124, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=testi">ტესტები</a></li>

    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 124, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=testi">ტესტები</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Error Line 125, Column 38: document type does not allow element "div" here; assuming missing "li" start-tag
                <div style="clear: both;"></div>
  • Error Line 126, Column 13: end tag for "li" omitted, but OMITTAG NO was specified
            </ul>

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

  • Info Line 125, Column 13: start tag was here
                <div style="clear: both;"></div>
  • Warning Line 128, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=klipi">კლიპი</a></li>

    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 128, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=klipi">კლიპი</a></li>

    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 128, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=klipi">კლიპი</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 129, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=foto">ფოტო</a></li>

    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 129, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=foto">ფოტო</a></li>

    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 129, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=foto">ფოტო</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 130, Column 51: reference not terminated by REFC delimiter
    …<li><a href="index.php?do=cat&category=qali-da-mamakaci">ქალი & მამაკაცი</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 130, Column 51: reference to external entity in attribute value
    …<li><a href="index.php?do=cat&category=qali-da-mamakaci">ქალი & მამაკაცი</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 130, Column 51: reference to entity "category" for which no system identifier could be generated
    …<li><a href="index.php?do=cat&category=qali-da-mamakaci">ქალი & მამაკაცი</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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 130, Column 75: character "&" is the first character of a delimiter but occurred as data
    …i><a href="index.php?do=cat&category=qali-da-mamakaci">ქალი & მამაკაცი</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.
  • Warning Line 131, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=moda">მოდა</a></li>

    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 131, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=moda">მოდა</a></li>

    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 131, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=moda">მოდა</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 132, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=anekdoti">ანეგდოტები</a></li>

    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 132, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=anekdoti">ანეგდოტები</a></li>

    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 132, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=anekdoti">ანეგდოტები</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 133, Column 51: reference not terminated by REFC delimiter
                <li><a href="index.php?do=cat&category=paparaci">პაპარაცი</a></li>

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

  • Warning Line 133, Column 51: reference to external entity in attribute value
                <li><a href="index.php?do=cat&category=paparaci">პაპარაცი</a></li>

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

  • Error Line 133, Column 51: reference to entity "category" for which no system identifier could be generated
                <li><a href="index.php?do=cat&category=paparaci">პაპარაცი</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Warning Line 134, Column 51: reference not terminated by REFC delimiter
    …<li><a href="index.php?do=cat&category=sasiyvarulo">სიყვარულის ისტორიები</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 134, Column 51: reference to external entity in attribute value
    …<li><a href="index.php?do=cat&category=sasiyvarulo">სიყვარულის ისტორიები</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 134, Column 51: reference to entity "category" for which no system identifier could be generated
    …<li><a href="index.php?do=cat&category=sasiyvarulo">სიყვარულის ისტორიები</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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Error Line 135, Column 58: there is no attribute "target"
                <li><a href="http://gogaggg.com/chat" target="blank">ჩატი</a></li>

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

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

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

  • Warning Line 136, Column 51: reference not terminated by REFC delimiter
    …         <li><a href="index.php?do=cat&category=sxvadasxva">სხვადასხვა</a></li>

    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 136, Column 51: reference to external entity in attribute value
    …         <li><a href="index.php?do=cat&category=sxvadasxva">სხვადასხვა</a></li>

    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 136, Column 51: reference to entity "category" for which no system identifier could be generated
    …         <li><a href="index.php?do=cat&category=sxvadasxva">სხვადასხვა</a></li>

    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 117, Column 42: entity was defined here
                <li><a href="index.php?do=cat&category=video">ვიდეო</a></li>
  • Error Line 137, Column 38: document type does not allow element "div" here; assuming missing "li" start-tag
                <div style="clear: both;"></div>
  • Error Line 138, Column 13: end tag for "li" omitted, but OMITTAG NO was specified
            </ul>

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

  • Info Line 137, Column 13: start tag was here
                <div style="clear: both;"></div>
  • Error Line 152, Column 609: there is no attribute "src"
    …oz">elioz</a></span></div><iframe src="http://www.abezara.com/728/index.php" 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.

  • Error Line 152, Column 658: there is no attribute "scrolling"
    ….abezara.com/728/index.php" scrolling="no" frameborder="0" style="border:none;…

    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 152, Column 675: there is no attribute "frameborder"
    …index.php" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 152, Column 685: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:100…

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

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

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

  • Error Line 152, Column 761: there is no attribute "allowtransparency"
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></iframe>

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

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

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

  • Error Line 152, Column 767: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 167, Column 765: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 182, Column 764: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 197, Column 764: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 212, Column 776: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 216, Column 68: required attribute "alt" not specified
    </div><img src="http://ww.gogaggg.com/images/share.jpg" width="650"></a><br>

    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 216, Column 72: end tag for element "a" which is not open
    </div><img src="http://ww.gogaggg.com/images/share.jpg" width="650"></a><br>

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

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

  • Error Line 216, Column 72: end tag for "img" omitted, but OMITTAG NO was specified
    </div><img src="http://ww.gogaggg.com/images/share.jpg" width="650"></a><br>

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

  • Info Line 216, Column 7: start tag was here
    </div><img src="http://ww.gogaggg.com/images/share.jpg" width="650"></a><br>
  • Error Line 216, Column 77: end tag for "br" omitted, but OMITTAG NO was specified
    </div><img src="http://ww.gogaggg.com/images/share.jpg" width="650"></a><br>

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

  • Info Line 216, Column 73: start tag was here
    </div><img src="http://ww.gogaggg.com/images/share.jpg" width="650"></a><br>
  • Error Line 218, Column 21: there is no attribute "marginwidth"
    <iframe marginwidth="0" marginheight="0" src="http://ww.gogaggg.com/share/index…

    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 218, Column 38: there is no attribute "marginheight"
    <iframe marginwidth="0" marginheight="0" src="http://ww.gogaggg.com/share/index…

    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 218, Column 109: there is no attribute "height"
    …are/index.php" frameborder="0" height="350" scrolling="yes" width="650"></ifra…

    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 218, Column 137: there is no attribute "width"
    …"0" height="350" scrolling="yes" width="650"></iframe><div class="single-news">

    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 218, Column 142: element "iframe" undefined
    …"0" height="350" scrolling="yes" width="650"></iframe><div class="single-news">

    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 228, Column 767: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 242, Column 807: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 256, Column 764: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 270, Column 766: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 285, Column 763: element "iframe" undefined
    … overflow:hidden; width:100px; height:25px;" allowtransparency="true"></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 291, Column 52: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            	<div class="sidebar-block"><IFRAME height=250 marginHeight=0
  • Error Line 291, Column 69: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            	<div class="sidebar-block"><IFRAME height=250 marginHeight=0
  • Warning Line 292, Column 85: reference not terminated by REFC delimiter
    …/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=300…

    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 292, Column 85: reference to external entity in attribute value
    …/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=300…

    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 292, Column 85: reference to entity "dt" for which no system identifier could be generated
    …/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=300…

    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 82, Column 82: entity was defined here
    …ead/ads?client=ca-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=…
  • Warning Line 292, Column 103: reference not terminated by REFC delimiter
    …-4998822984722167&dt=1234419618000&lmt=1234419618&format=300x250_as&output=htm…

    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 292, Column 103: reference to external entity in attribute value
    …-4998822984722167&dt=1234419618000&lmt=1234419618&format=300x250_as&output=htm…

    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 292, Column 103: reference to entity "lmt" for which no system identifier could be generated
    …-4998822984722167&dt=1234419618000&lmt=1234419618&format=300x250_as&output=htm…

    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 82, Column 99: entity was defined here
    …-pub-4998822984722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=…
  • Warning Line 292, Column 121: reference not terminated by REFC delimiter
    …dt=1234419618000&lmt=1234419618&format=300x250_as&output=html&correlator=12344…

    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 292, Column 121: reference to external entity in attribute value
    …dt=1234419618000&lmt=1234419618&format=300x250_as&output=html&correlator=12344…

    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 292, Column 121: reference to entity "format" for which no system identifier could be generated
    …dt=1234419618000&lmt=1234419618&format=300x250_as&output=html&correlator=12344…

    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 82, Column 114: entity was defined here
    …722167&dt=1234419618000&lmt=1234419618&format=468x60_as&output=html&correlator…
  • Warning Line 292, Column 139: reference not terminated by REFC delimiter
    …mt=1234419618&format=300x250_as&output=html&correlator=1234419618000&channel=7…

    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 292, Column 139: reference to external entity in attribute value
    …mt=1234419618&format=300x250_as&output=html&correlator=1234419618000&channel=7…

    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 292, Column 139: reference to entity "output" for which no system identifier could be generated
    …mt=1234419618&format=300x250_as&output=html&correlator=1234419618000&channel=7…

    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 82, Column 131: entity was defined here
    …618000&lmt=1234419618&format=468x60_as&output=html&correlator=1234419618000&ch…
  • Warning Line 292, Column 155: reference not terminated by REFC delimiter
    …rmat=300x250_as&output=html&correlator=1234419618000&channel=7516211662&url=ht…

    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 292, Column 155: reference to external entity in attribute value
    …rmat=300x250_as&output=html&correlator=1234419618000&channel=7516211662&url=ht…

    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 292, Column 155: reference to entity "correlator" for which no system identifier could be generated
    …rmat=300x250_as&output=html&correlator=1234419618000&channel=7516211662&url=ht…

    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 82, Column 143: entity was defined here
    …234419618&format=468x60_as&output=html&correlator=1234419618000&channel=751621…
  • Warning Line 292, Column 177: reference not terminated by REFC delimiter
    …=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality…

    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 292, Column 177: reference to external entity in attribute value
    …=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality…

    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 292, Column 177: reference to entity "channel" for which no system identifier could be generated
    …=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality…

    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 82, Column 168: entity was defined here
    …s&output=html&correlator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww…
  • Warning Line 292, Column 192: reference not terminated by REFC delimiter
    …r=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4-le…

    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 292, Column 192: reference to external entity in attribute value
    …r=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4-le…

    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 292, Column 192: reference to entity "url" for which no system identifier could be generated
    …r=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-4-le…

    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 82, Column 187: entity was defined here
    …lator=1234419618000&channel=7516211662&url=http%3A%2F%2Fwww.quality-insurance-…
  • Warning Line 292, Column 250: reference not terminated by REFC delimiter
    …ality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=266…

    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 292, Column 250: reference to external entity in attribute value
    …ality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=266…

    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 292, Column 250: reference to entity "color_bg" for which no system identifier could be generated
    …ality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=266…

    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 82, Column 240: entity was defined here
    …%2Fwww.quality-insurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color…
  • Warning Line 292, Column 268: reference not terminated by REFC delimiter
    …less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffff…

    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 292, Column 268: reference to external entity in attribute value
    …less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffff…

    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 292, Column 268: reference to entity "color_text" for which no system identifier could be generated
    …less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffff…

    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 82, Column 256: entity was defined here
    …nsurance-4-less.com%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&col…
  • Warning Line 292, Column 286: reference not terminated by REFC delimiter
    …bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ff…

    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 292, Column 286: reference to external entity in attribute value
    …bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ff…

    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 292, Column 286: reference to entity "color_link" for which no system identifier could be generated
    …bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ff…

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

  • Info Line 82, Column 274: entity was defined here
    …m%2F&color_bg=ffffff&color_text=ffffff&color_link=2666B9&color_url=ffffff&colo…
  • Warning Line 292, Column 303: reference not terminated by REFC delimiter
    …ext=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=htt…

    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 292, Column 303: reference to external entity in attribute value
    …ext=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=htt…

    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 292, Column 303: reference to entity "color_url" for which no system identifier could be generated
    …ext=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=htt…

    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 82, Column 292: entity was defined here
    …ff&color_text=ffffff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea…
  • Warning Line 292, Column 323: reference not terminated by REFC delimiter
    …k=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google…

    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 292, Column 323: reference to external entity in attribute value
    …k=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google…

    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 292, Column 323: reference to entity "color_border" for which no system identifier could be generated
    …k=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google…

    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 82, Column 309: entity was defined here
    …fff&color_link=2666B9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F…
  • Warning Line 292, Column 333: reference not terminated by REFC delimiter
    …olor_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsea…

    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 292, Column 333: reference to external entity in attribute value
    …olor_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsea…

    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 292, Column 333: reference to entity "ea" for which no system identifier could be generated
    …olor_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsea…

    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 82, Column 329: entity was defined here
    …9&color_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2F…
  • Warning Line 292, Column 339: reference not terminated by REFC delimiter
    …rl=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch%3F…

    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 292, Column 339: reference to external entity in attribute value
    …rl=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch%3F…

    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 292, Column 339: reference to entity "ref" for which no system identifier could be generated
    …rl=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearch%3F…

    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 82, Column 334: entity was defined here
    …or_url=ffffff&color_border=ffffff&ea=0&ref=http%3A%2F%2Fwww.google.com%2Fsearc…
  • Warning Line 292, Column 470: reference not terminated by REFC delimiter
    …ng%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12…

    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 292, Column 470: reference to external entity in attribute value
    …ng%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12…

    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 292, Column 470: reference to entity "frm" for which no system identifier could be generated
    …ng%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=12…

    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 82, Column 465: entity was defined here
    …osting%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_si…
  • Warning Line 292, Column 479: reference not terminated by REFC delimiter
    …D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&…

    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 292, Column 479: reference to external entity in attribute value
    …D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&…

    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 292, Column 479: reference to entity "ga_vid" for which no system identifier could be generated
    …D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&…

    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 82, Column 471: entity was defined here
    …%26aq%3D0%26oq%3Dweb%26aqi%3Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234…
  • Warning Line 292, Column 507: reference not terminated by REFC delimiter
    …m=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.…

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

  • Warning Line 292, Column 507: reference to external entity in attribute value
    …m=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.…

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

  • Error Line 292, Column 507: reference to entity "ga_sid" for which no system identifier could be generated
    …m=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.…

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

  • Info Line 82, Column 499: entity was defined here
    …Dg10&frm=0&ga_vid=739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flas…
  • Warning Line 292, Column 525: reference not terminated by REFC delimiter
    …57.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=…

    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 292, Column 525: reference to external entity in attribute value
    …57.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=…

    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 292, Column 525: reference to entity "ga_hid" for which no system identifier could be generated
    …57.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=…

    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 82, Column 517: entity was defined here
    …739969557.1234419618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=7…
  • Warning Line 292, Column 541: reference not terminated by REFC delimiter
    …_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&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 292, Column 541: reference to external entity in attribute value
    …_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&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 292, Column 541: reference to entity "flash" for which no system identifier could be generated
    …_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&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 82, Column 534: entity was defined here
    …618&ga_sid=1234419618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=…
  • Warning Line 292, Column 556: reference not terminated by REFC delimiter
    …&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32…

    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 292, Column 556: reference to external entity in attribute value
    …&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32…

    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 292, Column 556: reference to entity "u_h" for which no system identifier could be generated
    …&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32…

    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 82, Column 551: entity was defined here
    …9618&ga_hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_c…
  • Warning Line 292, Column 564: reference not terminated by REFC delimiter
    …805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-3…

    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 292, Column 564: reference to external entity in attribute value
    …805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-3…

    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 292, Column 564: reference to entity "u_w" for which no system identifier could be generated
    …805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-3…

    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 82, Column 559: entity was defined here
    …hid=805061676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_t…
  • Warning Line 292, Column 574: reference not terminated by REFC delimiter
    …flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7…

    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 292, Column 574: reference to external entity in attribute value
    …flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7…

    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 292, Column 574: reference to entity "u_ah" for which no system identifier could be generated
    …flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7…

    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 82, Column 568: entity was defined here
    …1676&flash=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_…
  • Warning Line 292, Column 583: reference not terminated by REFC delimiter
    …0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=t…

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

  • Warning Line 292, Column 583: reference to external entity in attribute value
    …0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=t…

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

  • Error Line 292, Column 583: reference to entity "u_aw" for which no system identifier could be generated
    …0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=t…

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

  • Info Line 82, Column 577: entity was defined here
    …h=10.0.12.36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_j…
  • Warning Line 292, Column 593: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28…

    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 292, Column 593: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28…

    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 292, Column 593: reference to entity "u_cd" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28…

    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 82, Column 587: entity was defined here
    …36&u_h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&d…
  • Warning Line 292, Column 601: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 601: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 601: reference to entity "u_tz" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 595: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Warning Line 292, Column 612: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 612: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 612: reference to entity "u_his" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 605: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Warning Line 292, Column 621: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 621: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 621: reference to entity "u_java" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 613: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Warning Line 292, Column 630: reference not terminated by REFC delimiter
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 630: reference to external entity in attribute value
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 292, Column 630: reference to entity "dtd" for which no system identifier could be generated
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"

    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 82, Column 625: entity was defined here
    …h=768&u_w=1280&u_ah=738&u_aw=1130&u_cd=32&u_tz=-300&u_his=7&u_java=true&dtd=28"
  • Error Line 293, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=300 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 293, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=300 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 293, Column 43: "allowTransparency" is not a member of a group specified for any attribute
    frameBorder=0 width=300 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 293, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=300 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 293, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    frameBorder=0 width=300 allowTransparency name=google_ads_frame marginWidth=0
  • Error Line 294, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    scrolling=no></IFRAME><br><br>
  • Error Line 294, Column 13: element "IFRAME" undefined
    scrolling=no></IFRAME><br><br>

    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 294, Column 27: end tag for "br" omitted, but OMITTAG NO was specified
    scrolling=no></IFRAME><br><br>

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

  • Info Line 294, Column 23: start tag was here
    scrolling=no></IFRAME><br><br>
  • Error Line 294, Column 31: end tag for "br" omitted, but OMITTAG NO was specified
    scrolling=no></IFRAME><br><br>

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

  • Info Line 294, Column 27: start tag was here
    scrolling=no></IFRAME><br><br>
  • Error Line 297, Column 108: there is no attribute "border"
    …213"><img src="http://img.by/i/r0elq.png" width="300" border="0" /></a><br><br>

    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 297, Column 113: required attribute "alt" not specified
    …213"><img src="http://img.by/i/r0elq.png" width="300" border="0" /></a><br><br>

    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 297, Column 122: end tag for "br" omitted, but OMITTAG NO was specified
    …213"><img src="http://img.by/i/r0elq.png" width="300" border="0" /></a><br><br>

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

  • Info Line 297, Column 118: start tag was here
    …213"><img src="http://img.by/i/r0elq.png" width="300" border="0" /></a><br><br>
  • Error Line 297, Column 126: end tag for "br" omitted, but OMITTAG NO was specified
    …213"><img src="http://img.by/i/r0elq.png" width="300" border="0" /></a><br><br>

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

  • Info Line 297, Column 122: start tag was here
    …213"><img src="http://img.by/i/r0elq.png" width="300" border="0" /></a><br><br>
  • Error Line 298, Column 111: required attribute "alt" not specified
    …=4798"><img src="http://img.by/i/Dki.png" width="300" border="0" /></a><br><br>

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

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

  • Error Line 298, Column 120: end tag for "br" omitted, but OMITTAG NO was specified
    …=4798"><img src="http://img.by/i/Dki.png" width="300" border="0" /></a><br><br>

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

  • Info Line 298, Column 116: start tag was here
    …=4798"><img src="http://img.by/i/Dki.png" width="300" border="0" /></a><br><br>
  • Error Line 298, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …=4798"><img src="http://img.by/i/Dki.png" width="300" border="0" /></a><br><br>

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

  • Info Line 298, Column 120: start tag was here
    …=4798"><img src="http://img.by/i/Dki.png" width="300" border="0" /></a><br><br>
  • Error Line 300, Column 363: there is no attribute "allowTransparency"
    …:hidden; width:300px; height:558px;" allowTransparency="true"></iframe><br><br>

    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 300, Column 369: element "iframe" undefined
    …:hidden; width:300px; height:558px;" allowTransparency="true"></iframe><br><br>

    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 300, Column 383: end tag for "br" omitted, but OMITTAG NO was specified
    …:hidden; width:300px; height:558px;" allowTransparency="true"></iframe><br><br>

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

  • Info Line 300, Column 379: start tag was here
    …:hidden; width:300px; height:558px;" allowTransparency="true"></iframe><br><br>
  • Error Line 300, Column 387: end tag for "br" omitted, but OMITTAG NO was specified
    …:hidden; width:300px; height:558px;" allowTransparency="true"></iframe><br><br>

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

  • Info Line 300, Column 383: start tag was here
    …:hidden; width:300px; height:558px;" allowTransparency="true"></iframe><br><br>
  • Error Line 302, Column 21: there is no attribute "onClick"
    <a href="#" onClick="window.open('http://ww.gogaggg.com/player/index.php','2858…

    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 302, Column 160: required attribute "alt" not specified
    …0,height=32');"><img src="http://gogaggg.com/banner/gggmusradio.gif"></a></div>

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

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

  • Error Line 302, Column 164: end tag for "img" omitted, but OMITTAG NO was specified
    …0,height=32');"><img src="http://gogaggg.com/banner/gggmusradio.gif"></a></div>

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

  • Info Line 302, Column 108: start tag was here
    …php','28583','width=320,height=32');"><img src="http://gogaggg.com/banner/gggm…
  • Error Line 304, Column 125: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …g" width="150" border="0" alt=""მგლები" 1/ გოჩა მანველიძე გვერდი 3-431 (ექსკლუ…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 304, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    …" width="150" border="0" alt=""მგლები" 1/ გოჩა მანველიძე გვერდი 3-431 (ექსკლუზ…

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

  • Info Line 304, Column 53: start tag was here
    …://abezara.com/index.php?newsid=4798"><img src="http://img.by/i/S4WuU.png" wid…
  • Error Line 332, Column 124: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …ng" width="150" border="0" alt=""მგლები" 2/ გოჩა მანველიძე გვერდი 3-165" /></a>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 332, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …ng" width="150" border="0" alt=""მგლები" 2/ გოჩა მანველიძე გვერდი 3-165" /></a>

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

  • Info Line 332, Column 53: start tag was here
    …://abezara.com/index.php?newsid=5213"><img src="http://img.by/i/v2dj.png" widt…
  • Warning Line 443, Column 129: character "&" is the first character of a delimiter but occurred as data
    …by/i/9idlL.png" width="150" border="0" alt="ვერძი ქალი & ტყუპი მამაკაცი" /></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.
  • Warning Line 447, Column 123: character "&" is the first character of a delimiter but occurred as data
    …href="http://abezara.com/index.php?newsid=5423">ვერძი ქალი & ტყუპი მამაკაცი</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 463, Column 292: element "iframe" undefined
    …d291" frameborder="0" height="630" scrolling="NO" width="300"></iframe><br><br>

    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 463, Column 306: end tag for "br" omitted, but OMITTAG NO was specified
    …d291" frameborder="0" height="630" scrolling="NO" width="300"></iframe><br><br>

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

  • Info Line 463, Column 302: start tag was here
    …d291" frameborder="0" height="630" scrolling="NO" width="300"></iframe><br><br>
  • Error Line 463, Column 310: end tag for "br" omitted, but OMITTAG NO was specified
    …d291" frameborder="0" height="630" scrolling="NO" width="300"></iframe><br><br>

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

  • Info Line 463, Column 306: start tag was here
    …d291" frameborder="0" height="630" scrolling="NO" width="300"></iframe><br><br>
  • Error Line 465, Column 52: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://kids2010.com">ბავშვებისთვის</a><br>

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

  • Info Line 465, Column 48: start tag was here
    <a href="http://kids2010.com">ბავშვებისთვის</a><br>
  • Error Line 466, Column 56: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://opa.ge">OPA.GE - original warez</a><br>

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

  • Info Line 466, Column 52: start tag was here
    <a href="http://opa.ge">OPA.GE - original warez</a><br>
  • Error Line 467, Column 65: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://www.livegoli.com/rustavi2.html">rustavi2</a><br>

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

  • Info Line 467, Column 61: start tag was here
    <a href="http://www.livegoli.com/rustavi2.html">rustavi2</a><br>
  • Error Line 468, Column 42: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://gameclub.ge">GAME</a><br>

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

  • Info Line 468, Column 38: start tag was here
    <a href="http://gameclub.ge">GAME</a><br>
  • Error Line 469, Column 49: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://bind.ge">FILMEBI-ფილმები</a><br>

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

  • Info Line 469, Column 45: start tag was here
    <a href="http://bind.ge">FILMEBI-ფილმები</a><br>
  • Error Line 470, Column 54: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://hdreliz.com">Filmebi Qartulad</a><br>

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

  • Info Line 470, Column 50: start tag was here
    <a href="http://hdreliz.com">Filmebi Qartulad</a><br>
  • Error Line 471, Column 56: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://gaicine.ge/statusebi">STATUSEBI</a><br>

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

  • Info Line 471, Column 52: start tag was here
    <a href="http://gaicine.ge/statusebi">STATUSEBI</a><br>
  • Error Line 472, Column 54: element "BR" undefined
    <a href="http://www.insoccer.in">LIVE FOOTBALL</a><BR>

    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 473, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://www.smovies.net">ფილმები ონლაინში </a><br>

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

  • Info Line 473, Column 55: start tag was here
    <a href="http://www.smovies.net">ფილმები ონლაინში </a><br>
  • Error Line 474, Column 44: element "BR" undefined
    <a href="http://xitebi.com/">ფილმები</a><BR>

    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 475, Column 60: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://www.geohiti.com/">ფილმები ქართულად </a><br>

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

  • Info Line 475, Column 56: start tag was here
    <a href="http://www.geohiti.com/">ფილმები ქართულად </a><br>
  • Error Line 478, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href="http://abezara.com/index.php?do=tags&amp;tag=asaki" class="clo…

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

  • Info Line 478, Column 1: start tag was here
    <br><br><a href="http://abezara.com/index.php?do=tags&amp;tag=asaki" class="clo…
  • Error Line 478, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href="http://abezara.com/index.php?do=tags&amp;tag=asaki" class="clo…

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

  • Info Line 478, Column 5: start tag was here
    <br><br><a href="http://abezara.com/index.php?do=tags&amp;tag=asaki" class="clo…
  • Error Line 478, Column 6663: end tag for "BR" omitted, but OMITTAG NO was specified
    … /><a href="http://abezara.com/index.php?do=tags">ყველა ტეგის ჩვენება</a></div>

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

  • Info Line 474, Column 41: start tag was here
    <a href="http://xitebi.com/">ფილმები</a><BR>
  • Error Line 478, Column 6663: end tag for "BR" omitted, but OMITTAG NO was specified
    … /><a href="http://abezara.com/index.php?do=tags">ყველა ტეგის ჩვენება</a></div>

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

  • Info Line 472, Column 51: start tag was here
    <a href="http://www.insoccer.in">LIVE FOOTBALL</a><BR>
  • Warning Line 483, Column 102: cannot generate system identifier for general entity "page"
    …served - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <a href="…

    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 483, Column 102: general entity "page" not defined and no default entity
    …served - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <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.

  • Warning Line 483, Column 106: reference not terminated by REFC delimiter
    …ed - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <a href="inde…

    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 483, Column 106: reference to external entity in attribute value
    …ed - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <a href="inde…

    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 483, Column 106: reference to entity "page" for which no system identifier could be generated
    …ed - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <a href="inde…

    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 483, Column 101: entity was defined here
    …eserved - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <a href=…
  • Error Line 488, Column 68: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <a target="_top" href="http://counter.top.ge/cgi-bin/showtop?67869">

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

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

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

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

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

  • Warning Line 497, Column 51: reference not terminated by REFC delimiter
    java1=""+"refer="+escape(document.referrer)+"&page="+

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

  • Error Line 497, Column 51: reference to entity "page" for which no system identifier could be generated
    java1=""+"refer="+escape(document.referrer)+"&page="+

    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 483, Column 101: entity was defined here
    …eserved - <a href="index.php?do=static&page=ads"><b>რეკლამა</b></a> | <a href=…
  • Warning Line 499, Column 48: cannot generate system identifier for general entity "c"
    …cument.cookie="astratop=1; path=/"; java1+="&c="+(document.cookie?"yes":"now");

    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 499, Column 48: general entity "c" not defined and no default entity
    …cument.cookie="astratop=1; path=/"; java1+="&c="+(document.cookie?"yes":"now");

    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 499, Column 49: reference not terminated by REFC delimiter
    …cument.cookie="astratop=1; path=/"; java1+="&c="+(document.cookie?"yes":"now");

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

  • Error Line 499, Column 49: reference to entity "c" for which no system identifier could be generated
    …cument.cookie="astratop=1; path=/"; java1+="&c="+(document.cookie?"yes":"now");

    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 499, Column 47: entity was defined here
    …cument.cookie="astratop=1; path=/"; java1+="&c="+(document.cookie?"yes":"now");
  • Error Line 501, Column 33: required attribute "type" not specified
    <script language="javascript1.1">java="1.1";java1+="&java="+(navigator.javaEnab…

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

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

  • Warning Line 501, Column 54: cannot generate system identifier for general entity "java"
    …e="javascript1.1">java="1.1";java1+="&java="+(navigator.javaEnabled()?"yes":"n…

    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 501, Column 54: general entity "java" not defined and no default entity
    …e="javascript1.1">java="1.1";java1+="&java="+(navigator.javaEnabled()?"yes":"n…

    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 501, Column 58: reference not terminated by REFC delimiter
    …avascript1.1">java="1.1";java1+="&java="+(navigator.javaEnabled()?"yes":"now")…

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

  • Error Line 501, Column 58: reference to entity "java" for which no system identifier could be generated
    …avascript1.1">java="1.1";java1+="&java="+(navigator.javaEnabled()?"yes":"now")…

    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 501, Column 53: entity was defined here
    …ge="javascript1.1">java="1.1";java1+="&java="+(navigator.javaEnabled()?"yes":"…
  • Error Line 502, Column 33: required attribute "type" not specified
    <script language="javascript1.2">java="1.2";

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

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

  • Warning Line 503, Column 10: cannot generate system identifier for general entity "razresh"
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

    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 503, Column 10: general entity "razresh" not defined and no default entity
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

    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 503, Column 17: reference not terminated by REFC delimiter
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

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

  • Error Line 503, Column 17: reference to entity "razresh" for which no system identifier could be generated
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

    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 503, Column 9: entity was defined here
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+
  • Warning Line 503, Column 53: cannot generate system identifier for general entity "cvet"
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

    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 503, Column 53: general entity "cvet" not defined and no default entity
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

    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 503, Column 57: reference not terminated by REFC delimiter
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

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

  • Error Line 503, Column 57: reference to entity "cvet" for which no system identifier could be generated
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+

    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 503, Column 52: entity was defined here
    java1+="&razresh="+screen.width+'x'+screen.height+"&cvet="+
  • Error Line 505, Column 78: required attribute "type" not specified
    …screen.pixelDepth)</script><script language="javascript1.3">java="1.3"</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 506, Column 30: required attribute "type" not specified
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

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

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

  • Warning Line 506, Column 40: cannot generate system identifier for general entity "jscript"
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

    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 506, Column 40: general entity "jscript" not defined and no default entity
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

    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 506, Column 47: reference not terminated by REFC delimiter
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

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

  • Error Line 506, Column 47: reference to entity "jscript" for which no system identifier could be generated
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

    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 506, Column 39: entity was defined here
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();
  • Warning Line 506, Column 57: cannot generate system identifier for general entity "rand"
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

    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 506, Column 57: general entity "rand" not defined and no default entity
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

    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 506, Column 61: reference not terminated by REFC delimiter
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

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

  • Error Line 506, Column 61: reference to entity "rand" for which no system identifier could be generated
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();

    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 506, Column 56: entity was defined here
    <script language="javascript">java1+="&jscript="+java+"&rand="+Math.random();
  • Error Line 507, Column 73: document type does not allow element "a" here
    document.write("<a href='http://topebi.com/?fromsite=57' target='_blank'><img "+

    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 507, Column 79: an attribute specification must start with a name or name token
    document.write("<a href='http://topebi.com/?fromsite=57' target='_blank'><img "+

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

  • Error Line 507, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
    document.write("<a href='http://topebi.com/?fromsite=57' target='_blank'><img "+

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

  • Info Line 507, Column 74: start tag was here
    document.write("<a href='http://topebi.com/?fromsite=57' target='_blank'><img "+
  • Warning Line 508, Column 39: character "&" is the first character of a delimiter but occurred as data
    " src='http://topebi.com/img.php?id=57&"+java1+"&' border=0 alt='TOPEBI.com' wi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 508, Column 49: character "&" is the first character of a delimiter but occurred as data
    …p://topebi.com/img.php?id=57&"+java1+"&' border=0 alt='TOPEBI.com' width='88' …

    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 509, Column 10: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <noscript><a href=http://topebi.com/?fromsite=57 target=_blank><img src="http:/…

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

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

  • Error Line 509, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <noscript><a href=http://topebi.com/?fromsite=57 target=_blank><img src="http:/…
  • Error Line 509, Column 25: NET-enabling start-tag not immediately followed by null end-tag
    <noscript><a href=http://topebi.com/?fromsite=57 target=_blank><img src="http:/…

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

  • Error Line 509, Column 25: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <noscript><a href=http://topebi.com/?fromsite=57 target=_blank><img src="http:/…

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

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

  • Error Line 509, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tp://topebi.com/img.php?id=57" border=0 alt="TOPEBI.com" width='88' height='31…
  • Error Line 509, Column 155: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …img.php?id=57" border=0 alt="TOPEBI.com" width='88' height='31'></a></noscript>

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

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

  • Error Line 509, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …img.php?id=57" border=0 alt="TOPEBI.com" width='88' height='31'></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 509, Column 64: start tag was here
    …topebi.com/?fromsite=57 target=_blank><img src="http://topebi.com/img.php?id=5…
  • Error Line 509, Column 159: end tag for "noscript" omitted, but OMITTAG NO was specified
    …img.php?id=57" border=0 alt="TOPEBI.com" width='88' height='31'></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 509, Column 1: start tag was here
    <noscript><a href=http://topebi.com/?fromsite=57 target=_blank><img src="http:/…
  • Error Line 509, Column 170: end tag for element "noscript" which is not open
    …img.php?id=57" border=0 alt="TOPEBI.com" width='88' height='31'></a></noscript>

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

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

  • Error Line 510, Column 4: end tag for element "a" which is not open
    </a>

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

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

  • Error Line 515, Column 21: required attribute "type" not specified
    <script id="_wau186">var _wau = _wau || [];

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

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

  • Warning Line 529, Column 77: cannot generate system identifier for general entity "tag"
    …pr.php?codex=aHR0cDovL2FiZXphcmEuY29t&tag=2" alt="Check Google Page Rank" styl…

    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 529, Column 77: general entity "tag" not defined and no default entity
    …pr.php?codex=aHR0cDovL2FiZXphcmEuY29t&tag=2" alt="Check Google Page Rank" styl…

    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 529, Column 80: reference not terminated by REFC delimiter
    …php?codex=aHR0cDovL2FiZXphcmEuY29t&tag=2" alt="Check Google Page Rank" style="…

    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 529, Column 80: reference to external entity in attribute value
    …php?codex=aHR0cDovL2FiZXphcmEuY29t&tag=2" alt="Check Google Page Rank" style="…

    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 529, Column 80: reference to entity "tag" for which no system identifier could be generated
    …php?codex=aHR0cDovL2FiZXphcmEuY29t&tag=2" alt="Check Google Page Rank" style="…

    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 529, Column 76: entity was defined here
    …tpr.php?codex=aHR0cDovL2FiZXphcmEuY29t&tag=2" alt="Check Google Page Rank" sty…

Visitor Analysis

Daily Visitor
  • 700 visits