Vitibet.com provides free betting tips for many sports and many leagues all around the world. You can find here free betting tips, predictions for football, baseball, basketball, handball and ice-hockey. Soccer betting tips, ...

vitibet.com
  • Domain Name
    vitibet.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #51921
  • Page Size
    140.6 KB
  • Ip Address
    81.0.233.8
  • Heading
    H1: 4, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    219 GIF, 22 JPG, 4 PNG

Website Meta Analysis

  • Title
    Betting tips,free betting predictions
  • Meta Keyword
    betting tips, betting predictions, livescore, live score, livescores, live scores, tips, pics
  • Meta Description
    Vitibet.com provides free betting tips for many sports and many leagues all around the world. You can find here free betting tips, predictions for football, baseball, basketball, handball and ice-hockey. Soccer betting tips, sports betting tips.

Technical Analysis

  • Webserver
    Apache/2.2.9
  • Ip Address
    81.0.233.8
  • Domain Age
    5 Years, 8 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 07 Aug 2013 11:48:10 GMT
  • server: Apache/2.2.9
  • x-powered-by: PHP/5.2.6-1+lenny13
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Wed, 07 Aug 2013 11:48:10 GMT
  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
domain: vitibet.com
owner: Jan Vitacek
organization: N/A
email: email
address: Na pekne vyhlidce 4
city: Praha
postal-code: 162 00
country: CZ
phone: +420.777347313
admin-c: CCOM-1939548 email
tech-c: CCOM-1939548 email
billing-c: CCOM-1939548 email
reseller: Registratorem domeny je ZONER software, a.s.
nserver: ns1.regzone.info
nserver: ns1.regzone.cz
nserver: ns1.regzone.de
status: lock
created: 2007-11-22 07:51:27 UTC
modified: 2012-07-04 04:30:58 UTC
expires: 2013-11-22 07:51:27 UTC
query-source: 68.67.72.27

contact-hdl: CCOM-1939548
person: Petr Horinek
organization: ZONER software a.s.
email: email
address: Nove Sady 18
city: Brno
state: Czech Republic
postal-code: 60200
country: CZ
phone: +420.543257244

source: joker.com live whois service
query-time: 0.0079
db-updated: 2013-02-26 13:22:22
NOTE: By submitting a WHOIS query, you agree to abide by the following
NOTE: terms of use: You agree that you may use this data only for lawful
NOTE: purposes and that under no circumstances will you use this data to:
NOTE: (1) allow, enable, or otherwise support the transmission of mass
NOTE: unsolicited, commercial advertising or solicitations via direct mail,
NOTE: e-mail, telephone, or facsimile; or (2) enable high volume, automated,
NOTE: electronic processes that apply to Joker.com (or its computer systems).
NOTE: The compilation, repackaging, dissemination or other use of this data
NOTE: is expressly prohibited without the prior written consent of Joker.com.

DNS Analysis


DNS servers
ns1.regzone.info [77.93.209.246]
ns1.regzone.cz [217.198.113.10]
ns1.regzone.de


DNS Records

Answer records
vitibet.com SOA
server: ns1.regzone.cz
email: administrator@czechia.cz
serial: 2012110701
refresh: 10800
retry: 1800
expire: 1814400
minimum ttl: 3600
3600s
vitibet.com A 81.0.233.8 86400s
vitibet.com NS  ns1.regzone.cz 3600s
vitibet.com NS  ns1.regzone.info 3600s
vitibet.com NS  ns1.regzone.de 3600s

Authority records

Additional records

IP 81.0.233.8 Analysis

  • Country Code
    CZ
  • Country Code3
    CZE
  • Country Name
    Czech Republic
  • City
    EU
  • Continent Code
    49°75' North
  • Latitude
    15.5.
  • Longitude
  • No whois ip data for 81.0.233.8

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 271 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.7765709960347498
Message Error
  • Error Line 59, Column 6: document type does not allow element "BODY" here
    <body>

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

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

  • Error Line 96, Column 19: there is no attribute "BACKGROUND"
    <table background="./images/pictures/logocom_new.gif" width="100%"  border="3" …

    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 116, Column 839: cannot generate system identifier for general entity "sekce"
    …w.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title…

    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 116, Column 839: general entity "sekce" not defined and no default entity
    …w.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title…

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

  • Error Line 116, Column 844: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Foo…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Warning Line 116, Column 852: cannot generate system identifier for general entity "online"
    …/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football 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 116, Column 852: general entity "online" not defined and no default entity
    …/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football 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.

  • Error Line 116, Column 858: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football live" >F…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 914: end tag for "A" omitted, but its declaration does not permit this
    …tle="Football live" >Football live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 783: start tag was here
    …6]><table><tr><td><![endif]--><ul><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 918: end tag for element "A" which is not open
    …"Football live" >Football live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 984: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=hokej&lang=en" title="Ice…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 998: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=hokej&lang=en" title="Ice Hockey live" …

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1058: end tag for "A" omitted, but its declaration does not permit this
    …"Ice Hockey live" >Ice Hockey live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 923: start tag was here
    …ball live" >Football live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1062: end tag for element "A" which is not open
    … Hockey live" >Ice Hockey live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1128: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=tenis&lang=en" title="Ten…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1142: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=tenis&lang=en" title="Tennis live" >Ten…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1194: end tag for "A" omitted, but its declaration does not permit this
    …" title="Tennis live" >Tennis live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1067: start tag was here
    …ey live" >Ice Hockey live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1198: end tag for element "A" which is not open
    …tle="Tennis live" >Tennis live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1264: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=basket&lang=en" title="Ba…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1278: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=basket&lang=en" title="Basketball live"…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1339: end tag for "A" omitted, but its declaration does not permit this
    …"Basketball live" >Basketball live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1203: start tag was here
    …Tennis live" >Tennis live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1343: end tag for element "A" which is not open
    …ketball live" >Basketball live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1409: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=hazena&lang=en" title="Ha…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1423: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=hazena&lang=en" title="Handball live" >…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1480: end tag for "A" omitted, but its declaration does not permit this
    …tle="Handball live" >Handball live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1348: start tag was here
    …ll live" >Basketball live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1484: end tag for element "A" which is not open
    …"Handball live" >Handball live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1550: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=baseball&lang=en" title="…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1564: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=baseball&lang=en" title="Baseball live"…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1623: end tag for "A" omitted, but its declaration does not permit this
    …tle="Baseball live" >Baseball live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1489: start tag was here
    …ball live" >Handball live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1627: end tag for element "A" which is not open
    …"Baseball live" >Baseball live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1693: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=snooker&lang=en" title="S…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1707: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=snooker&lang=en" title="Snooker live" >…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1763: end tag for "A" omitted, but its declaration does not permit this
    …title="Snooker live" >Snooker live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1632: start tag was here
    …ball live" >Baseball live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1767: end tag for element "A" which is not open
    …e="Snooker live" >Snooker live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1833: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=volejbal&lang=en" title="…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1847: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=volejbal&lang=en" title="Volleyball liv…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 1910: end tag for "A" omitted, but its declaration does not permit this
    …"Volleyball live" >Volleyball live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1772: start tag was here
    …ooker live" >Snooker live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 1914: end tag for element "A" which is not open
    …leyball live" >Volleyball live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 1980: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=motor&lang=en" title="For…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 1994: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=motor&lang=en" title="Formula 1 live" >…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 2052: end tag for "A" omitted, but its declaration does not permit this
    …e="Formula 1 live" >Formula 1 live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 1919: start tag was here
    …ll live" >Volleyball live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 2056: end tag for element "A" which is not open
    …ormula 1 live" >Formula 1 live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 2122: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=lyze&lang=en" title="Ski …

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 2136: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=lyze&lang=en" title="Ski live" >Ski liv…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 2181: end tag for "A" omitted, but its declaration does not permit this
    …ang=en" title="Ski live" >Ski live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 2061: start tag was here
    …a 1 live" >Formula 1 live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 2185: end tag for element "A" which is not open
    …en" title="Ski live" >Ski live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 2251: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=amfotbal&lang=en" title="…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 2265: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=amfotbal&lang=en" title="American Footb…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 2342: end tag for "A" omitted, but its declaration does not permit this
    …ball live" >American Football live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 2190: start tag was here
    …itle="Ski live" >Ski live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 2346: end tag for element "A" which is not open
    … live" >American Football live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 2412: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=golf&lang=en" title="Golf…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 2426: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=golf&lang=en" title="Golf live" >Golf l…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 2473: end tag for "A" omitted, but its declaration does not permit this
    …g=en" title="Golf live" >Golf live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 2351: start tag was here
    …" >American Football live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 2477: end tag for element "A" which is not open
    …" title="Golf live" >Golf live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 2543: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=rugby&lang=en" title="Rug…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 2557: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=rugby&lang=en" title="Rugby live" >Rugb…

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 2607: end tag for "A" omitted, but its declaration does not permit this
    …en" title="Rugby live" >Rugby live</li></a><li><a href="http://www.vitibet.com…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 2482: start tag was here
    …le="Golf live" >Golf live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 2611: end tag for element "A" which is not open
    …title="Rugby live" >Rugby live</li></a><li><a href="http://www.vitibet.com/ind…

    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 116, Column 2677: reference to entity "sekce" for which no system identifier could be generated
    …ibet.com/index.php?clanek=online&sekce=online&online=kriket&lang=en" title="Cr…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 116, Column 2691: reference to entity "online" for which no system identifier could be generated
    ….php?clanek=online&sekce=online&online=kriket&lang=en" title="Cricket live" > …

    This is usually a cascading error caused by 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 116, Column 851: entity was defined here
    …m/index.php?clanek=online&sekce=online&online=fotbal&lang=en"title="Football l…
  • Error Line 116, Column 2747: end tag for "A" omitted, but its declaration does not permit this
    …itle="Cricket live" > Cricket live</li></a></ul><!--[if lte IE 6]></td></tr></…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 116, Column 2616: start tag was here
    …="Rugby live" >Rugby live</li></a><li><a href="http://www.vitibet.com/index.ph…
  • Error Line 116, Column 2751: end tag for element "A" which is not open
    …="Cricket live" > Cricket live</li></a></ul><!--[if lte IE 6]></td></tr></tabl…

    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 210, Column 17: start tag for "TR" omitted, but its declaration does not permit this
    <td width="100%">
  • Warning Line 230, Column 93: cannot generate system identifier for general entity "bannerId"
    …s://www.tipico.com/?affiliateId=36419&bannerId=83" title="Tipico" rel="nofollo…

    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 230, Column 93: general entity "bannerId" not defined and no default entity
    …s://www.tipico.com/?affiliateId=36419&bannerId=83" title="Tipico" rel="nofollo…

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

  • Error Line 230, Column 101: reference to entity "bannerId" for which no system identifier could be generated
    …tipico.com/?affiliateId=36419&bannerId=83" title="Tipico" rel="nofollow" targe…

    This is usually a cascading error caused by 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 230, Column 92: entity was defined here
    …ps://www.tipico.com/?affiliateId=36419&bannerId=83" title="Tipico" rel="nofoll…
  • Error Line 234, Column 101: reference to entity "bannerId" for which no system identifier could be generated
    …tipico.com/?affiliateId=36419&bannerId=83" title="Tipico" rel="nofollow" targe…

    This is usually a cascading error caused by 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 230, Column 92: entity was defined here
    …ps://www.tipico.com/?affiliateId=36419&bannerId=83" title="Tipico" rel="nofoll…
  • Warning Line 241, Column 114: cannot generate system identifier for general entity "bid"
    …interwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofol…

    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 241, Column 114: general entity "bid" not defined and no default entity
    …interwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofol…

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

  • Error Line 241, Column 117: reference to entity "bid" for which no system identifier could be generated
    …erwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofollow…

    This is usually a cascading error caused by 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 241, Column 113: entity was defined here
    ….interwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofo…
  • Error Line 245, Column 117: reference to entity "bid" for which no system identifier could be generated
    …erwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofollow…

    This is usually a cascading error caused by 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 241, Column 113: entity was defined here
    ….interwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofo…
  • Warning Line 252, Column 91: cannot generate system identifier for general entity "flag"
    …ttp://www.888sport.com/bet/?sr=356536&flag=0000" title="888.com" rel="nofollow…

    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 252, Column 91: general entity "flag" not defined and no default entity
    …ttp://www.888sport.com/bet/?sr=356536&flag=0000" title="888.com" rel="nofollow…

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

  • Error Line 252, Column 95: reference to entity "flag" for which no system identifier could be generated
    …//www.888sport.com/bet/?sr=356536&flag=0000" title="888.com" rel="nofollow" ta…

    This is usually a cascading error caused by 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 252, Column 90: entity was defined here
    …http://www.888sport.com/bet/?sr=356536&flag=0000" title="888.com" rel="nofollo…
  • Error Line 256, Column 95: reference to entity "flag" for which no system identifier could be generated
    …//www.888sport.com/bet/?sr=356536&flag=0000" title="888.com" rel="nofollow" ta…

    This is usually a cascading error caused by 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 252, Column 90: entity was defined here
    …http://www.888sport.com/bet/?sr=356536&flag=0000" title="888.com" rel="nofollo…
  • Error Line 274, Column 105: reference to entity "bid" for which no system identifier could be generated
    ….unibet.com/redirect.aspx?pid=8191&bid=15051" title="Unibet" rel="nofollow" ta…

    This is usually a cascading error caused by 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 241, Column 113: entity was defined here
    ….interwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofo…
  • Error Line 278, Column 105: reference to entity "bid" for which no system identifier could be generated
    ….unibet.com/redirect.aspx?pid=8191&bid=15051" title="Unibet" rel="nofollow" ta…

    This is usually a cascading error caused by 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 241, Column 113: entity was defined here
    ….interwetten.com/redirect.aspx?pid=459&bid=4089" title="Interwetten" rel="nofo…
  • Error Line 360, Column 74: required attribute "ALT" not specified
    <img class="obrazek" src="./reklama/screenshots/screens/bettingbonus.jpg">

    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 597, Column 74: required attribute "ALT" not specified
    <img class="obrazek" src="./reklama/screenshots/screens/bettingbonus.jpg">

    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 788, Column 80: document type does not allow element "LINK" here
    <link rel="stylesheet" type="text/css" href="./rss/zpravymainpage/rssstyle.css">

    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 799, Column 274: end tag for "A" omitted, but its declaration does not permit this
    …013 MLS Eastern Conference Preview</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 799, Column 47: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 799, Column 424: NET-enabling start-tag requires SHORTTAG YES
    ….com/230200/230211_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 799, Column 424: required attribute "ALT" not specified
    ….com/230200/230211_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 800, Column 426: end tag for "A" omitted, but its declaration does not permit this
    …out the wrong message for football</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 800, Column 186: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 800, Column 576: NET-enabling start-tag requires SHORTTAG YES
    ….com/257100/257138_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 800, Column 576: required attribute "ALT" not specified
    ….com/257100/257138_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 801, Column 421: end tag for "A" omitted, but its declaration does not permit this
    …celona waiting for Neymar's signal</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 801, Column 218: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 801, Column 571: NET-enabling start-tag requires SHORTTAG YES
    ….com/253100/253183_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 801, Column 571: required attribute "ALT" not specified
    ….com/253100/253183_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 802, Column 379: end tag for "A" omitted, but its declaration does not permit this
    …">Carew set for shock Inter switch</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 802, Column 204: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 802, Column 529: NET-enabling start-tag requires SHORTTAG YES
    ….com/258500/258595_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 802, Column 529: required attribute "ALT" not specified
    ….com/258500/258595_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 803, Column 381: end tag for "A" omitted, but its declaration does not permit this
    …nsea boss Laudrup, insists Toshack</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 803, Column 169: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 803, Column 531: NET-enabling start-tag requires SHORTTAG YES
    ….com/258100/258155_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 803, Column 531: required attribute "ALT" not specified
    ….com/258100/258155_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 804, Column 403: end tag for "A" omitted, but its declaration does not permit this
    …p Preview: Middlesbrough - Chelsea</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 804, Column 223: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 804, Column 553: NET-enabling start-tag requires SHORTTAG YES
    ….com/258000/258042_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 804, Column 553: required attribute "ALT" not specified
    ….com/258000/258042_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 805, Column 434: end tag for "A" omitted, but its declaration does not permit this
    … not like to complain to the press</td></tr><tr><td class="rsszpravaobsah" col…
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 805, Column 216: start tag was here
    …class="rsszpravanadpis" colspan ="3" ><a href="http://www.goal.com/en-us/news/…
  • Warning Line 805, Column 584: NET-enabling start-tag requires SHORTTAG YES
    ….com/251000/251062_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 805, Column 584: required attribute "ALT" not specified
    ….com/251000/251062_thumb.jpg" align="left" height="80" vspace="1" border="0" />

    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 833, Column 6: document type does not allow element "HTML" here
    <html>

    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 839, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 839, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 839, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 839, Column 193: character ";" not allowed in attribute specification list
    …er League</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 839, Column 194: character data is not allowed here
    …r League</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 842, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 842, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 842, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 842, Column 182: character ";" not allowed in attribute specification list
    …- La Liga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 842, Column 183: character data is not allowed here
    … La Liga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 845, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 845, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 845, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 845, Column 187: character ";" not allowed in attribute specification list
    …undesliga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 845, Column 188: character data is not allowed here
    …ndesliga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 848, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 848, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 848, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 848, Column 182: character ";" not allowed in attribute specification list
    …- Serie A</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 848, Column 183: character data is not allowed here
    … Serie A</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 851, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 851, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 851, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 851, Column 183: character ";" not allowed in attribute specification list
    …- Ligue 1</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 851, Column 184: character data is not allowed here
    … Ligue 1</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 854, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 854, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 854, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 854, Column 191: character ";" not allowed in attribute specification list
    …redivisie</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 854, Column 192: character data is not allowed here
    …edivisie</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 857, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 857, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 857, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 857, Column 191: character ";" not allowed in attribute specification list
    …er League</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 857, Column 192: character data is not allowed here
    …r League</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 860, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 860, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 860, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 860, Column 198: character ";" not allowed in attribute specification list
    …inus liga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 860, Column 199: character data is not allowed here
    …nus liga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 863, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 863, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 186: character ";" not allowed in attribute specification list
    …straklasa</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 863, Column 187: character data is not allowed here
    …traklasa</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 866, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 866, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 866, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 866, Column 191: character ";" not allowed in attribute specification list
    …eira Liga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 866, Column 192: character data is not allowed here
    …ira Liga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 869, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 869, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 869, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 869, Column 187: character ";" not allowed in attribute specification list
    …undesliga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 869, Column 188: character data is not allowed here
    …ndesliga</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 872, Column 29: document type does not allow element "TABLE" here
    <table class="prvnimistalig"><tr class="prvnimistalignadpis" ;><td colspan="10"…

    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 872, Column 62: character ";" not allowed in attribute specification list
    …alig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vl…
  • Error Line 872, Column 63: character data is not allowed here
    …lig"><tr class="prvnimistalignadpis" ;><td colspan="10"><img src="./images/vla…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 872, Column 194: character ";" not allowed in attribute specification list
    …er League</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td cla…
  • Error Line 872, Column 195: character data is not allowed here
    …r League</td></tr><tr class="nadpis" ;><td colspan="10"></td></tr><tr><td clas…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 878, Column 7: "HEAD" not finished but containing element ended
    </html> 
  • Error Line 878, Column 7: end tag for "HTML" which is not finished
    </html> 

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

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

  • Error Line 1026, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><…

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

  • Info Line 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Warning Line 1026, Column 153: cannot generate system identifier for general entity "liga"
    …index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src=…

    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 1026, Column 153: general entity "liga" not defined and no default entity
    …index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src=…

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

  • Error Line 1026, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./i…

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

  • Info Line 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Warning Line 1026, Column 171: cannot generate system identifier for general entity "tab"
    …nalyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/c…

    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 1026, Column 171: general entity "tab" not defined and no default entity
    …nalyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/c…

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

  • Error Line 1026, Column 174: reference to entity "tab" for which no system identifier could be generated
    …yzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.g…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Warning Line 1026, Column 177: cannot generate system identifier for general entity "zap"
    …&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif"…

    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 1026, Column 177: general entity "zap" not defined and no default entity
    …&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif"…

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

  • Error Line 1026, Column 180: reference to entity "zap" for which no system identifier could be generated
    …kce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif" bo…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1026, Column 239: required attribute "ALT" not specified
    …s/vlajky/cy.gif" border="0" width="15"></a></td><td class="standardbunka" widt…

    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 1026, Column 834: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><…

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

  • Info Line 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1026, Column 846: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./i…

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

  • Info Line 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1026, Column 863: reference to entity "tab" for which no system identifier could be generated
    …yzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1026, Column 869: reference to entity "zap" for which no system identifier could be generated
    …kce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1026, Column 932: required attribute "ALT" not specified
    …p=1"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1027, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1027, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=5"><img src=…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1027, Column 178: reference to entity "tab" for which no system identifier could be generated
    …sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=5"><img src="./images/vlajky/at.g…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1027, Column 184: reference to entity "zap" for which no system identifier could be generated
    …fotbal&liga=rakousko&lang=en&tab=1&zap=5"><img src="./images/vlajky/at.gif" bo…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1027, Column 243: required attribute "ALT" not specified
    …s/vlajky/at.gif" border="0" width="15"></a>1</td><td class="standardbunka" wid…

    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 1027, Column 865: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1027, Column 877: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=5"><img src=…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1027, Column 898: reference to entity "tab" for which no system identifier could be generated
    …sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=5"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1027, Column 904: reference to entity "zap" for which no system identifier could be generated
    …fotbal&liga=rakousko&lang=en&tab=1&zap=5"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1027, Column 967: required attribute "ALT" not specified
    …p=5"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1028, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=cernahora&lang=en&tab=1&zap…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1028, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=cernahora&lang=en&tab=1&zap=3"><img src…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1028, Column 179: reference to entity "tab" for which no system identifier could be generated
    …ekce=fotbal&liga=cernahora&lang=en&tab=1&zap=3"><img src="./images/vlajky/mont…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1028, Column 185: reference to entity "zap" for which no system identifier could be generated
    …otbal&liga=cernahora&lang=en&tab=1&zap=3"><img src="./images/vlajky/montenegro…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1028, Column 252: required attribute "ALT" not specified
    …/montenegro.gif" border="0" width="15"></a></td><td class="standardbunka" widt…

    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 1028, Column 859: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=cernahora&lang=en&tab=1&zap…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1028, Column 871: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=cernahora&lang=en&tab=1&zap=3"><img src…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1028, Column 893: reference to entity "tab" for which no system identifier could be generated
    …ekce=fotbal&liga=cernahora&lang=en&tab=1&zap=3"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1028, Column 899: reference to entity "zap" for which no system identifier could be generated
    …otbal&liga=cernahora&lang=en&tab=1&zap=3"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1028, Column 962: required attribute "ALT" not specified
    …p=3"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1029, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1029, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=7"><img src="./i…

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

  • Info Line 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1029, Column 174: reference to entity "tab" for which no system identifier could be generated
    …yzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=7"><img src="./images/vlajky/cy.g…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1029, Column 180: reference to entity "zap" for which no system identifier could be generated
    …kce=fotbal&liga=kypr&lang=en&tab=1&zap=7"><img src="./images/vlajky/cy.gif" bo…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1029, Column 239: required attribute "ALT" not specified
    …s/vlajky/cy.gif" border="0" width="15"></a></td><td class="standardbunka" widt…

    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 1029, Column 848: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1029, Column 860: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=7"><img src="./i…

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

  • Info Line 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1029, Column 877: reference to entity "tab" for which no system identifier could be generated
    …yzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=7"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1029, Column 883: reference to entity "zap" for which no system identifier could be generated
    …kce=fotbal&liga=kypr&lang=en&tab=1&zap=7"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1029, Column 946: required attribute "ALT" not specified
    …p=7"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1030, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=nemeckoctvrtas&lang=en&tab=…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1030, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=nemeckoctvrtas&lang=en&tab=1&zap=1"><im…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1030, Column 184: reference to entity "tab" for which no system identifier could be generated
    …fotbal&liga=nemeckoctvrtas&lang=en&tab=1&zap=1"><img src="./images/vlajky/de.g…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1030, Column 190: reference to entity "zap" for which no system identifier could be generated
    …&liga=nemeckoctvrtas&lang=en&tab=1&zap=1"><img src="./images/vlajky/de.gif" bo…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1030, Column 249: required attribute "ALT" not specified
    …s/vlajky/de.gif" border="0" width="15"></a>4S</td><td class="standardbunka" wi…

    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 1030, Column 888: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=nemeckoctvrtas&lang=en&tab=…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1030, Column 900: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=nemeckoctvrtas&lang=en&tab=1&zap=1"><im…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1030, Column 927: reference to entity "tab" for which no system identifier could be generated
    …fotbal&liga=nemeckoctvrtas&lang=en&tab=1&zap=1"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1030, Column 933: reference to entity "zap" for which no system identifier could be generated
    …&liga=nemeckoctvrtas&lang=en&tab=1&zap=1"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1030, Column 996: required attribute "ALT" not specified
    …p=1"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1031, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=srbsko&lang=en&tab=1&zap=5"…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1031, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=srbsko&lang=en&tab=1&zap=5"><img src=".…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1031, Column 176: reference to entity "tab" for which no system identifier could be generated
    …y&sekce=fotbal&liga=srbsko&lang=en&tab=1&zap=5"><img src="./images/vlajky/ser.…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1031, Column 182: reference to entity "zap" for which no system identifier could be generated
    …e=fotbal&liga=srbsko&lang=en&tab=1&zap=5"><img src="./images/vlajky/ser.gif" b…

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

  • Info Line 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1031, Column 242: required attribute "ALT" not specified
    …/vlajky/ser.gif" border="0" width="15"></a>1</td><td class="standardbunka" wid…

    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 1031, Column 873: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=srbsko&lang=en&tab=1&zap=5"…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1031, Column 885: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=srbsko&lang=en&tab=1&zap=5"><img src=".…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1031, Column 904: reference to entity "tab" for which no system identifier could be generated
    …y&sekce=fotbal&liga=srbsko&lang=en&tab=1&zap=5"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1031, Column 910: reference to entity "zap" for which no system identifier could be generated
    …e=fotbal&liga=srbsko&lang=en&tab=1&zap=5"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1031, Column 973: required attribute "ALT" not specified
    …p=5"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1032, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=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.

  • Info Line 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1032, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=4"><img src="…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1032, Column 177: reference to entity "tab" for which no system identifier could be generated
    …&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=4"><img src="./images/vlajky/sco.…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1032, Column 183: reference to entity "zap" for which no system identifier could be generated
    …=fotbal&liga=skotsko&lang=en&tab=1&zap=4"><img src="./images/vlajky/sco.gif" b…

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

  • Info Line 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1032, Column 243: required attribute "ALT" not specified
    …/vlajky/sco.gif" border="0" width="15"></a>1</td><td class="standardbunka" wid…

    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 1032, Column 850: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=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.

  • Info Line 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1032, Column 862: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=4"><img src="…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1032, Column 882: reference to entity "tab" for which no system identifier could be generated
    …&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=4"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1032, Column 888: reference to entity "zap" for which no system identifier could be generated
    …=fotbal&liga=skotsko&lang=en&tab=1&zap=4"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1032, Column 951: required attribute "ALT" not specified
    …p=4"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1033, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1033, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=1"><img src=…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1033, Column 178: reference to entity "tab" for which no system identifier could be generated
    …sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=1"><img src="./images/vlajky/at.g…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1033, Column 184: reference to entity "zap" for which no system identifier could be generated
    …fotbal&liga=rakousko&lang=en&tab=1&zap=1"><img src="./images/vlajky/at.gif" bo…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1033, Column 243: required attribute "ALT" not specified
    …s/vlajky/at.gif" border="0" width="15"></a>1</td><td class="standardbunka" wid…

    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 1033, Column 853: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1033, Column 865: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=1"><img src=…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1033, Column 886: reference to entity "tab" for which no system identifier could be generated
    …sekce=fotbal&liga=rakousko&lang=en&tab=1&zap=1"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1033, Column 892: reference to entity "zap" for which no system identifier could be generated
    …fotbal&liga=rakousko&lang=en&tab=1&zap=1"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1033, Column 955: required attribute "ALT" not specified
    …p=1"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1034, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=6…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1034, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=6"><img src="…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1034, Column 177: reference to entity "tab" for which no system identifier could be generated
    …&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=6"><img src="./images/vlajky/sco.…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1034, Column 183: reference to entity "zap" for which no system identifier could be generated
    …=fotbal&liga=skotsko&lang=en&tab=1&zap=6"><img src="./images/vlajky/sco.gif" b…

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

  • Info Line 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1034, Column 243: required attribute "ALT" not specified
    …/vlajky/sco.gif" border="0" width="15"></a>1</td><td class="standardbunka" wid…

    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 1034, Column 840: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=6…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1034, Column 852: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=6"><img src="…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1034, Column 872: reference to entity "tab" for which no system identifier could be generated
    …&sekce=fotbal&liga=skotsko&lang=en&tab=1&zap=6"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1034, Column 878: reference to entity "zap" for which no system identifier could be generated
    …=fotbal&liga=skotsko&lang=en&tab=1&zap=6"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1034, Column 941: required attribute "ALT" not specified
    …p=6"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1035, Column 145: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=angliepata&lang=en&tab=1&za…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1035, Column 157: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=angliepata&lang=en&tab=1&zap=2"><img sr…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1035, Column 180: reference to entity "tab" for which no system identifier could be generated
    …kce=fotbal&liga=angliepata&lang=en&tab=1&zap=2"><img src="./images/vlajky/eng.…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1035, Column 186: reference to entity "zap" for which no system identifier could be generated
    …tbal&liga=angliepata&lang=en&tab=1&zap=2"><img src="./images/vlajky/eng.gif" b…

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

  • Info Line 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1035, Column 246: required attribute "ALT" not specified
    …/vlajky/eng.gif" border="0" width="15"></a>5</td><td class="standardbunka" wid…

    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 1035, Column 847: reference to entity "sekce" for which no system identifier could be generated
    …port.cz/index.php?clanek=analyzy&sekce=fotbal&liga=angliepata&lang=en&tab=1&za…

    This is usually a cascading error caused by 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 116, Column 838: entity was defined here
    …ww.vitibet.com/index.php?clanek=online&sekce=online&online=fotbal&lang=en"titl…
  • Error Line 1035, Column 859: reference to entity "liga" for which no system identifier could be generated
    …x.php?clanek=analyzy&sekce=fotbal&liga=angliepata&lang=en&tab=1&zap=2"><img sr…

    This is usually a cascading error caused by 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 1026, Column 152: entity was defined here
    …/index.php?clanek=analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src…
  • Error Line 1035, Column 882: reference to entity "tab" for which no system identifier could be generated
    …kce=fotbal&liga=angliepata&lang=en&tab=1&zap=2"><img src="./images/pictures/lu…

    This is usually a cascading error caused by 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 1026, Column 170: entity was defined here
    …analyzy&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/…
  • Error Line 1035, Column 888: reference to entity "zap" for which no system identifier could be generated
    …tbal&liga=angliepata&lang=en&tab=1&zap=2"><img src="./images/pictures/lupa.gif…

    This is usually a cascading error caused by 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 1026, Column 176: entity was defined here
    …y&sekce=fotbal&liga=kypr&lang=en&tab=1&zap=1"><img src="./images/vlajky/cy.gif…
  • Error Line 1035, Column 951: required attribute "ALT" not specified
    …p=2"><img src="./images/pictures/lupa.gif" border="0" width="18"></a></td></tr>

    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 1218, Column 24: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    //--></script><noscript><img src="http://toplist.cz/count.asp?id=64381&amp;logo…

    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>").

  • Warning Line 1219, Column 39: NET-enabling start-tag requires SHORTTAG YES
    alt="TOPlist" width="88" height="120" /></noscript></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1226, Column 24: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    //--></script><noscript><img src="http://toplist.cz/dot.asp?id=1188282" border=…

    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>").

  • Warning Line 1227, Column 36: NET-enabling start-tag requires SHORTTAG YES
    alt="TOPlist" width="1" height="1" /></noscript></a> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1258, Column 150: NET-enabling start-tag requires SHORTTAG YES
    …op/button.php?u=vitisport" alt="ScoresPro - Top Sports Sites" border="0" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 1294, Column 145: NET-enabling start-tag requires SHORTTAG YES
    …psites.limso.net/button.php?u=vitisport" alt="Limso Topsites" border="0" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1330, Column 10: ID "BALLHELPER" already defined
    <div id="ballhelper">

    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 1321, Column 10: ID "BALLHELPER" first defined here
    <div id="ballhelper">
  • Error Line 1370, Column 5: value of attribute "ID" invalid: "6" cannot start a name
    id="639746cdadfb4743a6f0a4511aa21186" 

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

  • Warning Line 1377, Column 90: cannot generate system identifier for general entity "CID"
    …iliates.com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickT…

    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 1377, Column 90: general entity "CID" not defined and no default entity
    …iliates.com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickT…

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

  • Error Line 1377, Column 93: reference to entity "CID" for which no system identifier could be generated
    …ates.com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=…

    This is usually a cascading error caused by 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 1377, Column 89: entity was defined here
    …filiates.com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&Click…
  • Warning Line 1377, Column 98: cannot generate system identifier for general entity "DID"
    …com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%…

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

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

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

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

  • Error Line 1377, Column 98: general entity "DID" not defined and no default entity
    …com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%…

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

  • Error Line 1377, Column 101: reference to entity "DID" for which no system identifier could be generated
    …/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%…

    This is usually a cascading error caused by 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 1377, Column 97: entity was defined here
    ….com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http…
  • Warning Line 1377, Column 104: cannot generate system identifier for general entity "TID"
    …ffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=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 1377, Column 104: general entity "TID" not defined and no default entity
    …ffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=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.

  • Error Line 1377, Column 107: reference to entity "TID" for which no system identifier could be generated
    …liateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fi…

    This is usually a cascading error caused by 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 1377, Column 103: entity was defined here
    …AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f…
  • Warning Line 1377, Column 110: cannot generate system identifier for general entity "PID"
    …teCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimst…

    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 1377, Column 110: general entity "PID" not defined and no default entity
    …teCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimst…

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

  • Error Line 1377, Column 113: reference to entity "PID" for which no system identifier could be generated
    …ode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore…

    This is usually a cascading error caused by 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 1377, Column 109: entity was defined here
    …ateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fims…
  • Warning Line 1377, Column 118: cannot generate system identifier for general entity "LNG"
    …65_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet3…

    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 1377, Column 118: general entity "LNG" not defined and no default entity
    …65_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet3…

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

  • Error Line 1377, Column 121: reference to entity "LNG" for which no system identifier could be generated
    …047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365a…

    This is usually a cascading error caused by 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 1377, Column 117: entity was defined here
    …365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet…
  • Warning Line 1377, Column 124: cannot generate system identifier for general entity "ClickTag"
    …138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365affi…

    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 1377, Column 124: general entity "ClickTag" not defined and no default entity
    …138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365affi…

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

  • Error Line 1377, Column 132: reference to entity "ClickTag" for which no system identifier could be generated
    …194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365affiliates.c…

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

  • Info Line 1377, Column 123: entity was defined here
    …7138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365aff…
  • Warning Line 1377, Column 294: cannot generate system identifier for general entity "Popup"
    …3d365_047138%26CID%3d194%26DID%3d5%26TID%3d2%26PID%3d149%26LNG%3d1&Popup=true">

    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 1377, Column 294: general entity "Popup" not defined and no default entity
    …3d365_047138%26CID%3d194%26DID%3d5%26TID%3d2%26PID%3d149%26LNG%3d1&Popup=true">

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

  • Error Line 1377, Column 299: reference to entity "Popup" for which no system identifier could be generated
    …3d365_047138%26CID%3d194%26DID%3d5%26TID%3d2%26PID%3d149%26LNG%3d1&Popup=true">

    This is usually a cascading error caused by 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 1377, Column 293: entity was defined here
    …3d365_047138%26CID%3d194%26DID%3d5%26TID%3d2%26PID%3d149%26LNG%3d1&Popup=true">
  • Error Line 1389, Column 5: there is no attribute "SRC"
    src="http://imstore.bet365affiliates.com/?AffiliateCode=365_047138&CID=194&DID=…

    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 1389, Column 71: reference to entity "CID" for which no system identifier could be generated
    …ates.com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=…

    This is usually a cascading error caused by 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 1377, Column 89: entity was defined here
    …filiates.com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&Click…
  • Error Line 1389, Column 79: reference to entity "DID" for which no system identifier could be generated
    …/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%…

    This is usually a cascading error caused by 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 1377, Column 97: entity was defined here
    ….com/?AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http…
  • Error Line 1389, Column 85: reference to entity "TID" for which no system identifier could be generated
    …liateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fi…

    This is usually a cascading error caused by 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 1377, Column 103: entity was defined here
    …AffiliateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f…
  • Error Line 1389, Column 91: reference to entity "PID" for which no system identifier could be generated
    …ode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore…

    This is usually a cascading error caused by 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 1377, Column 109: entity was defined here
    …ateCode=365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fims…
  • Error Line 1389, Column 99: reference to entity "LNG" for which no system identifier could be generated
    …047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365a…

    This is usually a cascading error caused by 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 1377, Column 117: entity was defined here
    …365_047138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet…
  • Error Line 1389, Column 110: reference to entity "ClickTag" for which no system identifier could be generated
    …194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365affiliates.c…

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

  • Info Line 1377, Column 123: entity was defined here
    …7138&CID=194&DID=5&TID=2&PID=149&LNG=1&ClickTag=http%3a%2f%2fimstore.bet365aff…
  • Error Line 1389, Column 277: reference to entity "Popup" for which no system identifier could be generated
    …3d365_047138%26CID%3d194%26DID%3d5%26TID%3d2%26PID%3d149%26LNG%3d1&Popup=true" 

    This is usually a cascading error caused by 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 1377, Column 293: entity was defined here
    …3d365_047138%26CID%3d194%26DID%3d5%26TID%3d2%26PID%3d149%26LNG%3d1&Popup=true">
  • Error Line 1391, Column 9: there is no attribute "QUALITY"
    quality="high" 

    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 1393, Column 19: there is no attribute "ALLOWSCRIPTACCESS"
    allowScriptAccess="always" 

    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 1395, Column 17: there is no attribute "ALLOWNETWORKING"
    allowNetworking="external"  

    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 1397, Column 15: there is no attribute "SWLIVECONNECT"
    swLiveConnect="false" 

    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 1399, Column 7: there is no attribute "WIDTH"
    width="468" 

    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 1401, Column 8: there is no attribute "HEIGHT"
    height="60" 

    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 1403, Column 6: there is no attribute "NAME"
    name="639746cdadfb4743a6f0a4511aa21186" 

    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 1405, Column 6: there is no attribute "TYPE"
    type="application/x-shockwave-flash" 

    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 1407, Column 13: there is no attribute "PLUGINSPAGE"
    pluginspage="https://www.macromedia.com/go/getflashplayer" 

    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 1409, Column 7: there is no attribute "WMODE"
    wmode="transparent">

    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 1409, Column 20: element "EMBED" undefined
    wmode="transparent">

    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 1433, Column 7: end tag for "HTML" which is not finished
    </html> 

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

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

Visitor Analysis

Daily Visitor
  • 4.200 visits