sportske.net

Najnovije sportske vesti iz zemlje i sveta iz minuta u minut na Sportske.net. Mišljenja, analize, rezultati, najave događaja... ...

Display Widget for this domain on your website. Click Here
This data was last updated from 11-08-2013 06:53:52  (update).

Overview Info

  • Domain Name
    sportske.net
  • Favicon
  • Alexa Rank
    #45289
  • Google Page Rank
    PR 4
  • Ip Address
    85.10.214.186
  • Page Size
    83.1 KB
  • Images
    22 GIF, 64 JPG, 11 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    6 0 16 56 0 0

Website Meta Analysis



  • Title
    Sportske.net - sve sportske vesti na jednom mestu
  • Meta Keyword
    Sportske vesti, fudbal, kosarka, tenis, rukomet
  • Meta Description
    Najnovije sportske vesti iz zemlje i sveta iz minuta u minut na Sportske.net. Mišljenja, analize, rezultati, najave događaja...

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    85.10.214.186
  • Domain Age
    4 Years, 7 Months, 23 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sportske.net.

HTML Analysis

  • date: Sun, 11 Aug 2013 06:53:49 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.27
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
LimesSoft.com
D.Milovanovica Bene 61
Kragujevac, Serbia 34000
Serbia

Domain Name: SPORTSKE.NET
Created on: 10-Jan-09
Expires on: 10-Jan-13
Last Updated on: 13-Jul-11

Administrative Contact:
Djokic, Djordje email
LimesSoft.com
D.Milovanovica Bene 61
Kragujevac, Serbia 34000
Serbia
+64.1827757

Technical Contact:
Djokic, Djordje email
LimesSoft.com
D.Milovanovica Bene 61
Kragujevac, Serbia 34000
Serbia
+64.1827757

Domain servers in listed order:
NS3.SECOND-NS.DE
NS.SECOND-NS.COM
NS1.YOUR-SERVER.DE

DNS Analysis


DNS servers
ns1.your-server.de [213.133.106.251]
ns.second-ns.com [213.239.204.242]
ns3.second-ns.de [193.47.99.4]


DNS Records

Answer records
sportske.net SOA
server: ns1.your-server.de
email: postmaster@your-server.de
serial: 2012032202
refresh: 14400
retry: 1800
expire: 604800
minimum ttl: 86400
7200s
sportske.net MX
preference: 10
exchange: aspmx3.googlemail.com
7200s
sportske.net MX
preference: 10
exchange: aspmx2.googlemail.com
7200s
sportske.net MX
preference: 5
exchange: alt2.aspmx.l.google.com
7200s
sportske.net MX
preference: 5
exchange: alt1.aspmx.l.google.com
7200s
sportske.net MX
preference: 1
exchange: aspmx.l.google.com
7200s
sportske.net MX
preference: 1
exchange: aspmx.l.google.com priority
7200s
sportske.net NS  ns3.second-ns.de 7200s
sportske.net NS  ns.second-ns.com 7200s
sportske.net NS  ns1.your-server.de 7200s
sportske.net A 85.10.214.186 7200s

Authority records

Additional records
ns3.second-ns.de 28 [16 bytes] 600s
ns3.second-ns.de A 193.47.99.4 86400s
ns.second-ns.com A 213.239.204.242 7200s
ns1.your-server.de A 213.133.106.251 7200s

IP 85.10.214.186 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    N�rnberg
  • Continent Code
    EU
  • Latitude
    49.4478
  • Longitude
    11.0683
  • No whois ip data for 85.10.214.186

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 340 Errors
  • 87 Warnings
Ratio Text/Html
  • 0.6596227302109655
Message Error
  • Error Line 7, Column 13: there is no attribute "name"
    	<META name=Description content="Sportske vesti, online sportski žurnal (sports…

    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 7, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META name=Description content="Sportske vesti, online sportski žurnal (sports…
  • Error Line 7, Column 33: there is no attribute "content"
    	<META name=Description content="Sportske vesti, online sportski žurnal (sports…

    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 7, Column 127: element "META" undefined
    … online sportski žurnal (sportski zurnal), sve sportske vesti na jednom mestu">

    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 8, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META name=Keywords content="sportske vesti">
  • Error Line 8, Column 46: element "META" undefined
    	<META name=Keywords content="sportske vesti">

    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 16, Column 71: end tag for "link" omitted, but OMITTAG NO was specified
    	<link rel="SHORTCUT ICON" href="http://www.sportske.net/favicon.ico">	

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

  • Info Line 16, Column 2: start tag was here
    	<link rel="SHORTCUT ICON" href="http://www.sportske.net/favicon.ico">	
  • Error Line 17, Column 19: there is no attribute "HTTP-EQUIV"
    	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">

    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 17, Column 42: there is no attribute "CONTENT"
    	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">

    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 17, Column 68: element "META" undefined
    	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">

    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 20, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META content=Sport name=classification>
  • Error Line 20, Column 27: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META content=Sport name=classification>
  • Error Line 20, Column 41: element "META" undefined
    	<META content=Sport name=classification>

    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 21, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META content="1 days" name=revisit-after>
  • Error Line 21, Column 43: element "META" undefined
    	<META content="1 days" name=revisit-after>

    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 22, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META content=LimesSoft.com name=author>
  • Error Line 22, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<META content=LimesSoft.com name=author>
  • Error Line 22, Column 41: element "META" undefined
    	<META content=LimesSoft.com name=author>

    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 24, Column 17: there is no attribute "property"
    	<meta property="fb:app_id" content="117301371675821">

    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 24, Column 55: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta property="fb:app_id" content="117301371675821">

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

  • Info Line 24, Column 2: start tag was here
    	<meta property="fb:app_id" content="117301371675821">
  • Error Line 25, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

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

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

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

  • Error Line 78, Column 16: end tag for "META" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 22, Column 2: start tag was here
    	<META content=LimesSoft.com name=author>
  • Error Line 78, Column 16: end tag for "META" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 21, Column 2: start tag was here
    	<META content="1 days" name=revisit-after>
  • Error Line 78, Column 16: end tag for "META" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 20, Column 2: start tag was here
    	<META content=Sport name=classification>
  • Error Line 78, Column 16: end tag for "META" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 17, Column 2: start tag was here
    	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
  • Error Line 78, Column 16: end tag for "META" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 8, Column 2: start tag was here
    	<META name=Keywords content="sportske vesti">
  • Error Line 78, Column 16: end tag for "META" omitted, but OMITTAG NO was specified
    </script></head>

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

  • Info Line 7, Column 2: start tag was here
    	<META name=Description content="Sportske vesti, online sportski žurnal (sports…
  • Error Line 79, Column 14: there is no attribute "onLoad"
    <body onLoad="rankingsPush();">

    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 82, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Warning Line 86, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_GB/all.js#xfbml=1&appId=117301371675821";

    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 86, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_GB/all.js#xfbml=1&appId=117301371675821";

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

  • Warning Line 86, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_GB/all.js#xfbml=1&appId=117301371675821";

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

  • Error Line 86, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_GB/all.js#xfbml=1&appId=117301371675821";

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

  • Info Line 86, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_GB/all.js#xfbml=1&appId=117301371675821";
  • Error Line 95, Column 181: there is no attribute "border"
    …zjavaDana.gif" alt="Izjava Dana" width="30" height="88" border="0" /></a></div>

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

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

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

  • Error Line 115, Column 57: there is no attribute "target"
    …//www.tvprogram.rs/sport.html" target="_blank">TV program<span class="bg_right…

    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 122, Column 8: element "SCRIPT" undefined
    <SCRIPT>

    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).
  • Warning Line 123, Column 60: cannot generate system identifier for general entity "targetsite"
    …/ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pag…

    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 123, Column 60: general entity "targetsite" not defined and no default entity
    …/ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pag…

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

  • Warning Line 123, Column 70: reference not terminated by REFC delimiter
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';

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

  • Error Line 123, Column 70: reference to entity "targetsite" for which no system identifier could be generated
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 123, Column 82: cannot generate system identifier for general entity "AdSize"
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';

    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 123, Column 82: general entity "AdSize" not defined and no default entity
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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.

  • Warning Line 123, Column 88: reference not terminated by REFC delimiter
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';

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

  • Error Line 123, Column 88: reference to entity "AdSize" for which no system identifier could be generated
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 123, Column 97: cannot generate system identifier for general entity "PagePos"
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';

    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 123, Column 97: general entity "PagePos" not defined and no default entity
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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.

  • Warning Line 123, Column 104: reference not terminated by REFC delimiter
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';

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

  • Error Line 123, Column 104: reference to entity "PagePos" for which no system identifier could be generated
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 126, Column 22: an attribute specification must start with a name or name token
    document.write ('<scr'+'ipt LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ra…

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

  • Error Line 126, Column 22: element "scr" undefined
    document.write ('<scr'+'ipt LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ra…

    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).
  • Warning Line 126, Column 78: cannot generate system identifier for general entity "ran"
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

    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 126, Column 78: general entity "ran" not defined and no default entity
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Warning Line 126, Column 81: reference not terminated by REFC delimiter
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Error Line 126, Column 81: reference to entity "ran" for which no system identifier could be generated
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Info Line 126, Column 77: entity was defined here
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');
  • Error Line 126, Column 96: delimiter "'" invalid: only S separators and TAGC allowed here
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');
  • Error Line 129, Column 10: element "NOSCRIPT" undefined
    <NOSCRIPT>

    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 130, Column 9: there is no attribute "HREF"
    <A HREF="http://ad.httpool.com/click.ng/site=yusportske&targetsite=yusportske&A…

    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 130, Column 67: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

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

  • Warning Line 130, Column 67: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

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

  • Error Line 130, Column 67: reference to entity "targetsite" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 130, Column 85: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

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

  • Warning Line 130, Column 85: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

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

  • Error Line 130, Column 85: reference to entity "AdSize" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 130, Column 101: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

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

  • Warning Line 130, Column 101: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

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

  • Error Line 130, Column 101: reference to entity "PagePos" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 130, Column 104: element "A" undefined
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1">

    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 131, Column 10: there is no attribute "SRC"
    <IMG SRC="http://ad.httpool.com/image.ng/site=yusportske&targetsite=yusportske&…

    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 131, Column 68: reference not terminated by REFC delimiter
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></…

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

  • Warning Line 131, Column 68: reference to external entity in attribute value
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></…

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

  • Error Line 131, Column 68: reference to entity "targetsite" for which no system identifier could be generated
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 131, Column 86: reference not terminated by REFC delimiter
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Warning Line 131, Column 86: reference to external entity in attribute value
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Error Line 131, Column 86: reference to entity "AdSize" for which no system identifier could be generated
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 131, Column 102: reference not terminated by REFC delimiter
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Warning Line 131, Column 102: reference to external entity in attribute value
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Error Line 131, Column 102: reference to entity "PagePos" for which no system identifier could be generated
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 131, Column 105: element "IMG" undefined
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

    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 131, Column 109: end tag for "IMG" omitted, but OMITTAG NO was specified
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1"></A>

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

  • Info Line 131, Column 1: start tag was here
    <IMG SRC="http://ad.httpool.com/image.ng/site=yusportske&targetsite=yusportske&…
  • Error Line 186, Column 179: "Tretiraju" is not a member of a group specified for any attribute
    …border="0" alt="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujoš…
  • Error Line 186, Column 183: "nas" is not a member of a group specified for any attribute
    …er="0" alt="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević…
  • Error Line 186, Column 187: "kao" is not a member of a group specified for any attribute
    …0" alt="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "T…
  • Error Line 186, Column 192: "klub" is not a member of a group specified for any attribute
    …t="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "Tretir…
  • Error Line 186, Column 199: "drugog" is not a member of a group specified for any attribute
    …šević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "Tretiraju nas…
  • Error Line 186, Column 203: "reda" is not a member of a group specified for any attribute
    …ć: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "Tretiraju nas kao…
  • Error Line 186, Column 236: "Tretiraju" is not a member of a group specified for any attribute
    … reda!"" title="Vujošević: "Tretiraju nas kao klub drugog reda!""/><div class=…
  • Error Line 186, Column 240: "nas" is not a member of a group specified for any attribute
    …a!"" title="Vujošević: "Tretiraju nas kao klub drugog reda!""/><div class="fnT…
  • Error Line 186, Column 244: "kao" is not a member of a group specified for any attribute
    … title="Vujošević: "Tretiraju nas kao klub drugog reda!""/><div class="fnTextB…
  • Error Line 186, Column 249: "klub" is not a member of a group specified for any attribute
    …e="Vujošević: "Tretiraju nas kao klub drugog reda!""/><div class="fnTextBlk"><…
  • Error Line 186, Column 256: "drugog" is not a member of a group specified for any attribute
    …šević: "Tretiraju nas kao klub drugog reda!""/><div class="fnTextBlk"><em>Izvo…
  • Error Line 186, Column 260: "reda" is not a member of a group specified for any attribute
    …ć: "Tretiraju nas kao klub drugog reda!""/><div class="fnTextBlk"><em>Izvor: B…
  • Error Line 186, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …retiraju nas kao klub drugog reda!""/><div class="fnTextBlk"><em>Izvor: Beta</…

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

  • Info Line 186, Column 29: start tag was here
                <li>            <img src="http://www.sportske.net/text_images/20121…
  • Error Line 191, Column 175: "ratne" is not a member of a group specified for any attribute
    …"337" border="0" alt="Zvezdine "ratne igre"" title="Zvezdine "ratne igre""/><d…
  • Error Line 191, Column 179: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …" border="0" alt="Zvezdine "ratne igre"" title="Zvezdine "ratne igre""/><div c…

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

  • Error Line 191, Column 180: end tag for "img" omitted, but OMITTAG NO was specified
    … border="0" alt="Zvezdine "ratne igre"" title="Zvezdine "ratne igre""/><div cl…

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

  • Info Line 191, Column 29: start tag was here
                <li>            <img src="http://www.sportske.net/text_images/20130…
  • Error Line 200, Column 234: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …nalom?" title="Šta se dešava s Arsenalom?"/><h3>Šta se dešava s Arsenalom?</h3>

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

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

  • Error Line 201, Column 23: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
                    				<p>Puleni Arsena Vengera završili učešće u FA kup...</p></a…

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

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

  • Error Line 203, Column 238: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …" title="Šćepović doneo remi Partizanu"/><h3>Šćepović doneo remi Partizanu</h3>

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

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

  • Error Line 204, Column 23: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
                    				<p>Fudbaleri Partizana odigrali su prvu utakmicu na p...</p…

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

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

  • Error Line 205, Column 187: "Tretiraju" is not a member of a group specified for any attribute
    …border="0" alt="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujoš…
  • Error Line 205, Column 191: "nas" is not a member of a group specified for any attribute
    …er="0" alt="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević…
  • Error Line 205, Column 195: "kao" is not a member of a group specified for any attribute
    …0" alt="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "T…
  • Error Line 205, Column 200: "klub" is not a member of a group specified for any attribute
    …t="Vujošević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "Tretir…
  • Error Line 205, Column 207: "drugog" is not a member of a group specified for any attribute
    …šević: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "Tretiraju nas…
  • Error Line 205, Column 211: "reda" is not a member of a group specified for any attribute
    …ć: "Tretiraju nas kao klub drugog reda!"" title="Vujošević: "Tretiraju nas kao…
  • Error Line 205, Column 244: "Tretiraju" is not a member of a group specified for any attribute
    … reda!"" title="Vujošević: "Tretiraju nas kao klub drugog reda!""/><h3>Vujošev…
  • Error Line 205, Column 248: "nas" is not a member of a group specified for any attribute
    …a!"" title="Vujošević: "Tretiraju nas kao klub drugog reda!""/><h3>Vujošević: …
  • Error Line 205, Column 252: "kao" is not a member of a group specified for any attribute
    … title="Vujošević: "Tretiraju nas kao klub drugog reda!""/><h3>Vujošević: "Tre…
  • Error Line 205, Column 257: "klub" is not a member of a group specified for any attribute
    …e="Vujošević: "Tretiraju nas kao klub drugog reda!""/><h3>Vujošević: "Tretiraj…
  • Error Line 205, Column 264: "drugog" is not a member of a group specified for any attribute
    …šević: "Tretiraju nas kao klub drugog reda!""/><h3>Vujošević: "Tretiraju nas k…
  • Error Line 205, Column 268: "reda" is not a member of a group specified for any attribute
    …ć: "Tretiraju nas kao klub drugog reda!""/><h3>Vujošević: "Tretiraju nas kao k…
  • Error Line 205, Column 273: end tag for "img" omitted, but OMITTAG NO was specified
    …retiraju nas kao klub drugog reda!""/><h3>Vujošević: "Tretiraju nas kao klub d…

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

  • Info Line 205, Column 40: start tag was here
    …           <li><a href="javascript:;"><img src="http://www.sportske.net/text_i…
  • Error Line 205, Column 276: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …iraju nas kao klub drugog reda!""/><h3>Vujošević: "Tretiraju nas kao klub drug…

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

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

  • Error Line 206, Column 23: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
                    				<p>Trener košarkaša Partizana Duško Vujošević po...</p></a>…

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

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

  • Error Line 207, Column 199: "ratne" is not a member of a group specified for any attribute
    …="60" border="0" alt="Zvezdine "ratne igre"" title="Zvezdine "ratne igre""/><h…
  • Error Line 207, Column 203: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …" border="0" alt="Zvezdine "ratne igre"" title="Zvezdine "ratne igre""/><h3>Zv…

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

  • Error Line 207, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    … border="0" alt="Zvezdine "ratne igre"" title="Zvezdine "ratne igre""/><h3>Zve…

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

  • Info Line 207, Column 55: start tag was here
    …class="liLast"><a href="javascript:;"><img src="http://www.sportske.net/text_i…
  • Error Line 207, Column 240: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ine "ratne igre"" title="Zvezdine "ratne igre""/><h3>Zvezdine "ratne igre"</h3>

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

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

  • Error Line 208, Column 23: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
                    				<p>Fudbaleri Crvene zvezde broje sitno do povratka u ...</p…

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

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

  • Error Line 219, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok transferi">

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

  • Info Line 214, Column 63: start tag was here
    …cing="0" cellpadding="0" ><tr><td valign="top"><div class="blok domaci-fudbal">
  • Error Line 246, Column 42: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …							</tr><tr><td class="l" colspan=3><a href="http://www.sportske.net/trans…
  • Error Line 246, Column 169: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a></td></tr><tr><td class="l" colspan=3><a href="http://www.sportske.net/trans…
  • Error Line 247, Column 48: end tag for "div" omitted, but OMITTAG NO was specified
    …div></div><!-- #cela_vest kraj --></td></tr><tr><td valign="top"><div class="b…

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

  • Info Line 219, Column 35: start tag was here
    						</div></td><td valign="top"><div class="blok transferi">
  • Error Line 251, Column 240: there is no attribute "align"
    …urg grabi ka vrhu</a>&nbsp;<img align="absmiddle" src="http://www.sportske.net…

    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 251, Column 300: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 251, Column 304: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 251, Column 229: start tag was here
    …guran, Hamburg grabi ka vrhu</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 251, Column 1163: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 251, Column 1167: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 251, Column 1092: start tag was here
    …ol sa stilom do četvrtfinala</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 252, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok kosarka">

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

  • Info Line 247, Column 75: start tag was here
    …t kraj --></td></tr><tr><td valign="top"><div class="blok medjunarodni-fudbal">
  • Error Line 256, Column 1528: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 256, Column 1532: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 256, Column 1457: start tag was here
    …="dalje1">Farid sve zasenio!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 257, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td></tr><tr><td valign="top"><div class="blok tenis">

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

  • Info Line 252, Column 35: start tag was here
    						</div></td><td valign="top"><div class="blok kosarka">
  • Error Line 262, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok dzet-set">

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

  • Info Line 257, Column 44: start tag was here
    						</div></td></tr><tr><td valign="top"><div class="blok tenis">
  • Error Line 266, Column 433: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 266, Column 437: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 266, Column 362: start tag was here
    …class="dalje1">"Crtani" Ibra</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 266, Column 1273: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 266, Column 1277: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 266, Column 1202: start tag was here
    …e1">Tako to radi Majkl Skot!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 266, Column 2057: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 266, Column 2061: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 266, Column 1986: start tag was here
    …je1">Gaza - Poslednji čas...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 267, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td></tr><tr><td valign="top"><div class="blok taj-ludi-sport">

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

  • Info Line 262, Column 35: start tag was here
    						</div></td><td valign="top"><div class="blok dzet-set">
  • Error Line 270, Column 231: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/…

    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 270, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/text_…

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

  • Info Line 270, Column 160: start tag was here
    …e otvorene samo moja nije...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 278: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 282: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 207: start tag was here
    … se preorjentisao na košarku</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 537: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 541: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 466: start tag was here
    …>De Hea poput crtanog junaka</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 777: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 781: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 706: start tag was here
    …"dalje1">Kežman je u modi...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 1023: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 1027: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 952: start tag was here
    …lje1">Umesto slavlja – tuča!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 1463: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 1467: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 1392: start tag was here
    …eka "isterali" iz dvorane...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 1735: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 1739: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 1664: start tag was here
    …lu bi za ovo dobio crveni...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 2026: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 2030: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 1955: start tag was here
    … Parku, da li su ovo penali?</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 2286: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 2290: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 2215: start tag was here
    …olub koji je voleo fudbal...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 271, Column 2548: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 271, Column 2552: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 271, Column 2477: start tag was here
    … Ibri padne ''mrak na oči''!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 272, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok daj-gol">

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

  • Info Line 267, Column 44: start tag was here
    						</div></td></tr><tr><td valign="top"><div class="blok taj-ludi-sport">
  • Error Line 275, Column 227: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/…

    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 275, Column 232: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/text_…

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

  • Info Line 275, Column 156: start tag was here
    …bitovao golom i asistencijom</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 276, Column 281: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 276, Column 285: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 276, Column 210: start tag was here
    …alo bliže protivničkom golu?</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 276, Column 549: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 276, Column 553: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 276, Column 478: start tag was here
    …o da se igra druga utakmica?</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 276, Column 790: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 276, Column 794: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 276, Column 719: start tag was here
    …alje">Dešava se i najboljima</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 276, Column 1024: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 276, Column 1028: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 276, Column 953: start tag was here
    …="dalje">Razmisli i raspali!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 277, Column 12: end tag for "p" omitted, but OMITTAG NO was specified
    						</div></td></tr><tr><td valign="top"><div class="blok top-lista">

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

  • Info Line 276, Column 1063: start tag was here
    …</p></div><div class="inner clearfix"><p><a href="http://www.sportske.net/vest…
  • Error Line 277, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td></tr><tr><td valign="top"><div class="blok top-lista">

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

  • Info Line 272, Column 35: start tag was here
    						</div></td><td valign="top"><div class="blok daj-gol">
  • Error Line 280, Column 239: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/…

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

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

  • Error Line 280, Column 244: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/text_…

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

  • Info Line 280, Column 168: start tag was here
    …, Durant, Brajant, Lebron...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 281, Column 275: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

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

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

  • Error Line 281, Column 279: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 281, Column 204: start tag was here
    …10 - Nagetsi k'o Bronkosi...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 281, Column 520: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

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

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

  • Error Line 281, Column 524: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 281, Column 449: start tag was here
    …e">NBA top 10 - 'Air Canada'</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 281, Column 776: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

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

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

  • Error Line 281, Column 780: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 281, Column 705: start tag was here
    …le tajne velikih majstora...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 281, Column 1065: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

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

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

  • Error Line 281, Column 1069: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 281, Column 994: start tag was here
    …na zagrevanju, a i u igri...</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 282, Column 12: end tag for "p" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok sport-iz-fotelje">

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

  • Info Line 281, Column 1104: start tag was here
    …</p></div><div class="inner clearfix"><p><a href="http://www.sportske.net/vest…
  • Error Line 282, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok sport-iz-fotelje">

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

  • Info Line 277, Column 44: start tag was here
    						</div></td></tr><tr><td valign="top"><div class="blok top-lista">
  • Error Line 285, Column 271: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/…

    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 285, Column 276: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/text_…

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

  • Info Line 285, Column 200: start tag was here
    …tat protiv Pari Sen Žermena!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 286, Column 264: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 286, Column 268: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 286, Column 193: start tag was here
    …e">Dao 190 golova Totenhemu!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 286, Column 520: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 286, Column 524: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 286, Column 449: start tag was here
    …e">CR7 trenirao sa gejmerima</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 287, Column 12: end tag for "p" omitted, but OMITTAG NO was specified
    						</div></td></tr><tr><td valign="top"><div class="blok ultra-mentalita">

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

  • Info Line 286, Column 895: start tag was here
    …</p></div><div class="inner clearfix"><p><a href="http://www.sportske.net/vest…
  • Error Line 287, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td></tr><tr><td valign="top"><div class="blok ultra-mentalita">

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

  • Info Line 282, Column 35: start tag was here
    						</div></td><td valign="top"><div class="blok sport-iz-fotelje">
  • Error Line 290, Column 190: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/…

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

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

  • Error Line 290, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/text_…

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

  • Info Line 290, Column 119: start tag was here
    …115518.html">'Đavolja posla'</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 291, Column 245: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 291, Column 249: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 291, Column 174: start tag was here
    …ass="dalje">U čast navijača!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 291, Column 718: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 291, Column 722: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 291, Column 647: start tag was here
    …a slobode Milvolovog rasistu</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 292, Column 12: end tag for "p" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok vremenska-masina">

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

  • Info Line 291, Column 975: start tag was here
    …</p></div><div class="inner clearfix"><p><a href="http://www.sportske.net/vest…
  • Error Line 292, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td><td valign="top"><div class="blok vremenska-masina">

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

  • Info Line 287, Column 44: start tag was here
    						</div></td></tr><tr><td valign="top"><div class="blok ultra-mentalita">
  • Error Line 295, Column 215: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/…

    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 295, Column 220: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></h3><img src="http://www.sportske.net/text_…

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

  • Info Line 295, Column 144: start tag was here
    …Mendieta - DJ od 50 miliona!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 296, Column 276: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 296, Column 280: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 296, Column 205: start tag was here
    …e li biti dostojni istorije?</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 296, Column 932: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><…

    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 296, Column 936: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sportske.net/img/video-icon.gif"></p></div><div class="inner clearfix"><p><a…

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

  • Info Line 296, Column 861: start tag was here
    …olji strelac među golmanima!</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 297, Column 12: end tag for "p" omitted, but OMITTAG NO was specified
    						</div></td></tr></table></div><!-- #content kraj -->            						<di…

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

  • Info Line 296, Column 971: start tag was here
    …</p></div><div class="inner clearfix"><p><a href="http://www.sportske.net/vest…
  • Error Line 297, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    						</div></td></tr></table></div><!-- #content kraj -->            						<di…

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

  • Info Line 292, Column 35: start tag was here
    						</div></td><td valign="top"><div class="blok vremenska-masina">
  • Warning Line 324, Column 67: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

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

  • Warning Line 324, Column 67: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

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

  • Error Line 324, Column 67: reference to entity "targetsite" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 324, Column 85: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

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

  • Warning Line 324, Column 85: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

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

  • Error Line 324, Column 85: reference to entity "AdSize" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=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 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 324, Column 101: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

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

  • Warning Line 324, Column 101: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

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

  • Error Line 324, Column 101: reference to entity "PagePos" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=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 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 324, Column 104: element "A" undefined
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1">

    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).
  • Warning Line 325, Column 68: reference not terminated by REFC delimiter
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></…

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

  • Warning Line 325, Column 68: reference to external entity in attribute value
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></…

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

  • Error Line 325, Column 68: reference to entity "targetsite" for which no system identifier could be generated
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 325, Column 86: reference not terminated by REFC delimiter
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Warning Line 325, Column 86: reference to external entity in attribute value
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Error Line 325, Column 86: reference to entity "AdSize" for which no system identifier could be generated
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 325, Column 102: reference not terminated by REFC delimiter
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Warning Line 325, Column 102: reference to external entity in attribute value
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Error Line 325, Column 102: reference to entity "PagePos" for which no system identifier could be generated
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 325, Column 105: element "IMG" undefined
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

    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 325, Column 109: end tag for "IMG" omitted, but OMITTAG NO was specified
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=1"></A>

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

  • Info Line 325, Column 1: start tag was here
    <IMG SRC="http://ad.httpool.com/image.ng/site=yusportske&targetsite=yusportske&…
  • Error Line 332, Column 11: ID "poslednje-vesti" already defined
    		<ul id="poslednje-vesti" class="lista" style="display: block;">

    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 305, Column 11: ID "poslednje-vesti" first defined here
    		<ul id="poslednje-vesti" class="lista" style="display: block;">
  • Error Line 333, Column 275: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></li><li><a href="http://www.sportske.n…

    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 333, Column 280: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></li><li><a href="http://www.sportske.net/ve…

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

  • Info Line 333, Column 204: start tag was here
    …guran, Hamburg grabi ka vrhu</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Error Line 333, Column 1756: required attribute "alt" not specified
    …//www.sportske.net/img/video-icon.gif"></li><li><a href="http://www.sportske.n…

    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 333, Column 1761: end tag for "img" omitted, but OMITTAG NO was specified
    ….sportske.net/img/video-icon.gif"></li><li><a href="http://www.sportske.net/ve…

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

  • Info Line 333, Column 1685: start tag was here
    …ol sa stilom do četvrtfinala</a>&nbsp;<img align="absmiddle" src="http://www.s…
  • Warning Line 353, Column 67: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Warning Line 353, Column 67: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Error Line 353, Column 67: reference to entity "targetsite" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Info Line 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 353, Column 85: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Warning Line 353, Column 85: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Error Line 353, Column 85: reference to entity "AdSize" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 353, Column 101: reference not terminated by REFC delimiter
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Warning Line 353, Column 101: reference to external entity in attribute value
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Error Line 353, Column 101: reference to entity "PagePos" for which no system identifier could be generated
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 353, Column 104: element "A" undefined
    …l.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2">

    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).
  • Warning Line 354, Column 68: reference not terminated by REFC delimiter
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></…

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

  • Warning Line 354, Column 68: reference to external entity in attribute value
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></…

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

  • Error Line 354, Column 68: reference to entity "targetsite" for which no system identifier could be generated
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></…

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

  • Info Line 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 354, Column 86: reference not terminated by REFC delimiter
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Warning Line 354, Column 86: reference to external entity in attribute value
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Error Line 354, Column 86: reference to entity "AdSize" for which no system identifier could be generated
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 354, Column 102: reference not terminated by REFC delimiter
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Warning Line 354, Column 102: reference to external entity in attribute value
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Error Line 354, Column 102: reference to entity "PagePos" for which no system identifier could be generated
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 354, Column 105: element "IMG" undefined
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

    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 354, Column 109: end tag for "IMG" omitted, but OMITTAG NO was specified
    …m/image.ng/site=yusportske&targetsite=yusportske&AdSize=300x250&PagePos=2"></A>

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

  • Info Line 354, Column 1: start tag was here
    <IMG SRC="http://ad.httpool.com/image.ng/site=yusportske&targetsite=yusportske&…
  • Error Line 377, Column 12: ID "vesti-po-klubovima" already defined
    			<ul id="vesti-po-klubovima" class="lista">

    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 364, Column 12: ID "vesti-po-klubovima" first defined here
    			<ul id="vesti-po-klubovima" class="lista">
  • Error Line 392, Column 12: ID "vesti-po-klubovima" already defined
    			<ul id="vesti-po-klubovima" class="lista">

    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 364, Column 12: ID "vesti-po-klubovima" first defined here
    			<ul id="vesti-po-klubovima" class="lista">
  • Error Line 397, Column 203: end tag for "p" omitted, but OMITTAG NO was specified
    …sve znaš, al' nisi siguran...</a></div></p></li><li><div class="inner clearfix…

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

  • Info Line 397, Column 35: start tag was here
    		<li><div class="inner clearfix"><p><a class="dalje" href="http://www.sportske…
  • Error Line 397, Column 207: end tag for element "p" which is not open
    …znaš, al' nisi siguran...</a></div></p></li><li><div class="inner clearfix"><p…

    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 397, Column 396: end tag for "p" omitted, but OMITTAG NO was specified
    …Prva strana</em> - Aplauz za pobednika</a></div></p></li></ul></div>		</div>			

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

  • Info Line 397, Column 245: start tag was here
    …></li><li><div class="inner clearfix"><p><a class="dalje" href="http://www.spo…
  • Error Line 397, Column 400: end tag for element "p" which is not open
    …Prva strana</em> - Aplauz za pobednika</a></div></p></li></ul></div>		</div>			

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

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

  • Error Line 405, Column 12: ID "vesti-po-klubovima" already defined
    			<ul id="vesti-po-klubovima" class="lista">

    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 364, Column 12: ID "vesti-po-klubovima" first defined here
    			<ul id="vesti-po-klubovima" class="lista">
  • Error Line 408, Column 829: end tag for "p" omitted, but OMITTAG NO was specified
    …Šta je Mažić rekao Maskeranu?</a></div></p></li><li><div class="inner clearfix…

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

  • Info Line 408, Column 684: start tag was here
    …></li><li><div class="inner clearfix"><p><a class="dalje" href="http://www.spo…
  • Error Line 408, Column 833: end tag for element "p" which is not open
    …je Mažić rekao Maskeranu?</a></div></p></li><li><div class="inner clearfix"><p…

    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 408, Column 1099: end tag for "p" omitted, but OMITTAG NO was specified
    …m u najvećem klubu na svetu!"</a></div></p></li></ul></div>		</div><iframe src…

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

  • Info Line 408, Column 871: start tag was here
    …></li><li><div class="inner clearfix"><p><a class="dalje" href="http://www.spo…
  • Error Line 408, Column 1103: end tag for element "p" which is not open
    …najvećem klubu na svetu!"</a></div></p></li></ul></div>		</div><iframe src="//…

    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 408, Column 1140: there is no attribute "src"
    …p></li></ul></div>		</div><iframe src="//www.facebook.com/plugins/likebox.php?…

    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 408, Column 1389: there is no attribute "scrolling"
    …&amp;appId=168607733184288" scrolling="no" frameborder="0" style="border:none;…

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

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

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

  • Error Line 408, Column 1406: there is no attribute "frameborder"
    …733184288" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

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

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

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

  • Error Line 408, Column 1416: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:292…

    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 408, Column 1493: there is no attribute "allowTransparency"
    …ow:hidden; width:292px; height:258px;" allowTransparency="true"></iframe><br />

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

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

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

  • Error Line 408, Column 1499: element "iframe" undefined
    …ow:hidden; width:292px; height:258px;" allowTransparency="true"></iframe><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 409, Column 14: there is no attribute "href"
    <g:plus href="https://plus.google.com/102977676828403240307" size="badge"></g:p…

    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 409, Column 67: there is no attribute "size"
    …lus href="https://plus.google.com/102977676828403240307" size="badge"></g:plus>

    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 409, Column 74: element "g:plus" undefined
    …lus href="https://plus.google.com/102977676828403240307" size="badge"></g:plus>

    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 414, Column 12: ID "vesti-po-klubovima" already defined
    			<ul id="vesti-po-klubovima" class="lista">

    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 364, Column 12: ID "vesti-po-klubovima" first defined here
    			<ul id="vesti-po-klubovima" class="lista">
  • Error Line 418, Column 384: end tag for "p" omitted, but OMITTAG NO was specified
    … -  za nas su civilizacija...</a></div></p></li><li><div class="inner clearfix…

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

  • Info Line 418, Column 46: start tag was here
    …></li><li><div class="inner clearfix"><p><img src="http://www.sportske.net/ban…
  • Error Line 418, Column 388: end tag for element "p" which is not open
    …za nas su civilizacija...</a></div></p></li><li><div class="inner clearfix"><p…

    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 418, Column 753: end tag for "p" omitted, but OMITTAG NO was specified
    …a, prava iskušenja tek slede!</a></div></p></li><li><div class="inner clearfix…

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

  • Info Line 418, Column 426: start tag was here
    …></li><li><div class="inner clearfix"><p><img src="http://www.sportske.net/ban…
  • Error Line 418, Column 757: end tag for element "p" which is not open
    …rava iskušenja tek slede!</a></div></p></li><li><div class="inner clearfix"><p…

    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 418, Column 1131: end tag for "p" omitted, but OMITTAG NO was specified
    …je Džordž Best čistio kopačke</a></div></p></li><li><div class="inner clearfix…

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

  • Info Line 418, Column 795: start tag was here
    …></li><li><div class="inner clearfix"><p><img src="http://www.sportske.net/ban…
  • Error Line 418, Column 1135: end tag for element "p" which is not open
    …žordž Best čistio kopačke</a></div></p></li><li><div class="inner clearfix"><p…

    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 418, Column 1473: end tag for "p" omitted, but OMITTAG NO was specified
    …dojević</em> - Radnički, sad budi ratnički!</a></div></p></li></ul></div></div>

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

  • Info Line 418, Column 1173: start tag was here
    …></li><li><div class="inner clearfix"><p><img src="http://www.sportske.net/ban…
  • Error Line 418, Column 1477: end tag for element "p" which is not open
    …dojević</em> - Radnički, sad budi ratnički!</a></div></p></li></ul></div></div>

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

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

  • Error Line 428, Column 12: ID "vesti-po-klubovima" already defined
    			<ul id="vesti-po-klubovima" class="lista">

    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 364, Column 12: ID "vesti-po-klubovima" first defined here
    			<ul id="vesti-po-klubovima" class="lista">
  • Error Line 448, Column 8: element "SCRIPT" undefined
    <SCRIPT>

    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).
  • Warning Line 449, Column 70: reference not terminated by REFC delimiter
    ….httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1';

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

  • Error Line 449, Column 70: reference to entity "targetsite" for which no system identifier could be generated
    ….httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 449, Column 88: reference not terminated by REFC delimiter
    ….httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1';

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

  • Error Line 449, Column 88: reference to entity "AdSize" for which no system identifier could be generated
    ….httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=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 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 449, Column 100: reference not terminated by REFC delimiter
    ….httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1';

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

  • Error Line 449, Column 100: reference to entity "PagePos" for which no system identifier could be generated
    ….httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=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 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 452, Column 22: an attribute specification must start with a name or name token
    document.write ('<scr'+'ipt LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ra…

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

  • Error Line 452, Column 22: element "scr" undefined
    document.write ('<scr'+'ipt LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ra…

    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).
  • Warning Line 452, Column 81: reference not terminated by REFC delimiter
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Error Line 452, Column 81: reference to entity "ran" for which no system identifier could be generated
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Info Line 126, Column 77: entity was defined here
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');
  • Error Line 452, Column 96: delimiter "'" invalid: only S separators and TAGC allowed here
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');
  • Error Line 455, Column 10: element "NOSCRIPT" undefined
    <NOSCRIPT>

    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).
  • Warning Line 456, Column 67: reference not terminated by REFC delimiter
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

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

  • Warning Line 456, Column 67: reference to external entity in attribute value
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

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

  • Error Line 456, Column 67: reference to entity "targetsite" for which no system identifier could be generated
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=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 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 456, Column 85: reference not terminated by REFC delimiter
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

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

  • Warning Line 456, Column 85: reference to external entity in attribute value
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

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

  • Error Line 456, Column 85: reference to entity "AdSize" for which no system identifier could be generated
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=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 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 456, Column 97: reference not terminated by REFC delimiter
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

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

  • Warning Line 456, Column 97: reference to external entity in attribute value
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

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

  • Error Line 456, Column 97: reference to entity "PagePos" for which no system identifier could be generated
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=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 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 456, Column 100: element "A" undefined
    …tpool.com/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1">

    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).
  • Warning Line 457, Column 68: reference not terminated by REFC delimiter
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Warning Line 457, Column 68: reference to external entity in attribute value
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Error Line 457, Column 68: reference to entity "targetsite" for which no system identifier could be generated
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Info Line 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 457, Column 86: reference not terminated by REFC delimiter
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Warning Line 457, Column 86: reference to external entity in attribute value
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Error Line 457, Column 86: reference to entity "AdSize" for which no system identifier could be generated
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 457, Column 98: reference not terminated by REFC delimiter
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Warning Line 457, Column 98: reference to external entity in attribute value
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Error Line 457, Column 98: reference to entity "PagePos" for which no system identifier could be generated
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Error Line 457, Column 101: element "IMG" undefined
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

    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 457, Column 105: end tag for "IMG" omitted, but OMITTAG NO was specified
    …l.com/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=1"></A>

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

  • Info Line 457, Column 1: start tag was here
    <IMG SRC="http://ad.httpool.com/image.ng/site=yusportske&targetsite=yusportske&…
  • Error Line 461, Column 14: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--Search*--->
  • Info Line 461, Column 1: comment declaration started here
    <!--Search*--->
  • Error Line 464, Column 79: there is no attribute "name"
    …ion="http://www.sportske.net/pretraga.html" id="cse-search-box" name="tsearch">

    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 469, Column 60: duplicate specification of attribute "name"
    … <input name="query" type="text" class="searchBox" name="q" value="" size="20" 

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 480, Column 21: invalid comment declaration: found name character outside comment but inside comment declaration
        <!--Search End--->
  • Info Line 480, Column 5: comment declaration started here
        <!--Search End--->
  • Error Line 497, Column 39: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <a href="http://www.addfreestats.com" >

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

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

  • Error Line 498, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …connect.cgi?usr=00634716Pauto" border=0 alt="AddFreeStats.com Free Web Stats!"…
  • Error Line 498, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …sr=00634716Pauto" border=0 alt="AddFreeStats.com Free Web Stats!">Web Stats</a>

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

  • Info Line 498, Column 1: start tag was here
    <img src="http://www6.addfreestats.com/cgi-bin/connect.cgi?usr=00634716Pauto" b…
  • Error Line 510, Column 72: there is no attribute "alt"
    …eograd.co.rs" title="OFK Beograd" alt="OFK Beograd"><img src="http://www.sport…

    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 510, Column 166: required attribute "alt" not specified
    …rc="http://www.sportske.net/img/partner_ofk.jpg" width="100" height="100"/></a>

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

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

  • Error Line 512, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 513, Column 170: required attribute "alt" not specified
    …rc="http://www.sportske.net/img/partner_sloboda.jpg" width="100" height="100"/>

    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 514, Column 8: end tag for "a" omitted, but OMITTAG NO was specified
    		</div>

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

  • Info Line 513, Column 10: start tag was here
            	<a href="http://www.fksloboda.rs" title="Sloboda Užice" alt="Sloboda U…
  • Error Line 515, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 516, Column 170: required attribute "alt" not specified
    …ttp://www.sportske.net/img/partner_jagodina.jpg" width="100" height="100"/></a>

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

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

  • Error Line 518, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 519, Column 162: required attribute "alt" not specified
    …c="http://www.sportske.net/img/partner_kula.jpg" width="100" height="100"/></a>

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

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

  • Error Line 521, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 522, Column 167: required attribute "alt" not specified
    …c="http://www.sportske.net/img/partner_vosa.jpg" width="100" height="100"/></a>

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

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

  • Error Line 524, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 525, Column 168: required attribute "alt" not specified
    …ttp://www.sportske.net/img/partner_napredak.jpg" width="100" height="100"/></a>

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

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

  • Error Line 527, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 528, Column 179: required attribute "alt" not specified
    …//www.sportske.net/img/partner_radnicki_nis.jpg" width="100" height="100"/></a>

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

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

  • Error Line 530, Column 18: ID "partner" already defined
            <div id="partner">

    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 509, Column 12: ID "partner" first defined here
    		<div id="partner">
  • Error Line 531, Column 151: required attribute "alt" not specified
    …rc="http://www.sportske.net/img/partner_rad.jpg" width="100" height="100"/></a>

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

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

  • Error Line 663, Column 105: required attribute "alt" not specified
    …="http://www.iab.rs"><img src="http://www.sportske.net/img/iab.jpg" /></a></td>

    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 665, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
    				</div>

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

  • Info Line 649, Column 6: start tag was here
    					<table><tr><td><div id="logo_mali">
  • Error Line 667, Column 8: element "SCRIPT" undefined
    <SCRIPT>

    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).
  • Warning Line 668, Column 70: reference not terminated by REFC delimiter
    …l.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Error Line 668, Column 70: reference to entity "targetsite" for which no system identifier could be generated
    …l.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Info Line 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 668, Column 88: reference not terminated by REFC delimiter
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Error Line 668, Column 88: reference to entity "AdSize" for which no system identifier could be generated
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 668, Column 100: reference not terminated by REFC delimiter
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Error Line 668, Column 100: reference to entity "PagePos" for which no system identifier could be generated
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 668, Column 103: cannot generate system identifier for general entity "subcat"
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

    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 668, Column 103: general entity "subcat" not defined and no default entity
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Warning Line 668, Column 109: reference not terminated by REFC delimiter
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Error Line 668, Column 109: reference to entity "subcat" for which no system identifier could be generated
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';

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

  • Info Line 668, Column 102: entity was defined here
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';
  • Error Line 671, Column 22: an attribute specification must start with a name or name token
    document.write ('<scr'+'ipt LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ra…

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

  • Error Line 671, Column 22: element "scr" undefined
    document.write ('<scr'+'ipt LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ra…

    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).
  • Warning Line 671, Column 81: reference not terminated by REFC delimiter
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Error Line 671, Column 81: reference to entity "ran" for which no system identifier could be generated
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');

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

  • Info Line 126, Column 77: entity was defined here
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');
  • Error Line 671, Column 96: delimiter "'" invalid: only S separators and TAGC allowed here
    …t LANGUAGE="JavaScript1.1" sr'+'c="'+httpool_src+'&ran='+ran+'"></scr'+'ipt>');
  • Error Line 674, Column 10: element "NOSCRIPT" undefined
    <NOSCRIPT>

    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).
  • Warning Line 675, Column 67: reference not terminated by REFC delimiter
    …om/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Warning Line 675, Column 67: reference to external entity in attribute value
    …om/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Error Line 675, Column 67: reference to entity "targetsite" for which no system identifier could be generated
    …om/click.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Info Line 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 675, Column 85: reference not terminated by REFC delimiter
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Warning Line 675, Column 85: reference to external entity in attribute value
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Error Line 675, Column 85: reference to entity "AdSize" for which no system identifier could be generated
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 675, Column 97: reference not terminated by REFC delimiter
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Warning Line 675, Column 97: reference to external entity in attribute value
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Error Line 675, Column 97: reference to entity "PagePos" for which no system identifier could be generated
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 675, Column 106: reference not terminated by REFC delimiter
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Warning Line 675, Column 106: reference to external entity in attribute value
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Error Line 675, Column 106: reference to entity "subcat" for which no system identifier could be generated
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

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

  • Info Line 668, Column 102: entity was defined here
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';
  • Error Line 675, Column 116: element "A" undefined
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding">

    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).
  • Warning Line 676, Column 68: reference not terminated by REFC delimiter
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Warning Line 676, Column 68: reference to external entity in attribute value
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Error Line 676, Column 68: reference to entity "targetsite" for which no system identifier could be generated
    …om/image.ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=…

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

  • Info Line 123, Column 59: entity was defined here
    …//ad.httpool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&Pa…
  • Warning Line 676, Column 86: reference not terminated by REFC delimiter
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Warning Line 676, Column 86: reference to external entity in attribute value
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Error Line 676, Column 86: reference to entity "AdSize" for which no system identifier could be generated
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Info Line 123, Column 81: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 676, Column 98: reference not terminated by REFC delimiter
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Warning Line 676, Column 98: reference to external entity in attribute value
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Error Line 676, Column 98: reference to entity "PagePos" for which no system identifier could be generated
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Info Line 123, Column 96: entity was defined here
    …pool.com/js.ng/site=yusportske&targetsite=yusportske&AdSize=980x100&PagePos=1';
  • Warning Line 676, Column 107: reference not terminated by REFC delimiter
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Warning Line 676, Column 107: reference to external entity in attribute value
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Error Line 676, Column 107: reference to entity "subcat" for which no system identifier could be generated
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Info Line 668, Column 102: entity was defined here
    …ng/site=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding';
  • Error Line 676, Column 117: element "IMG" undefined
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

    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 676, Column 121: end tag for "IMG" omitted, but OMITTAG NO was specified
    …ite=yusportske&targetsite=yusportske&AdSize=1x1&PagePos=2&subcat=branding"></A>

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

  • Info Line 676, Column 1: start tag was here
    <IMG SRC="http://ad.httpool.com/image.ng/site=yusportske&targetsite=yusportske&…
  • Warning Line 701, Column 28: character "&" is the first character of a delimiter but occurred as data
    var parts = url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m,key,value)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 701, Column 35: character "&" is the first character of a delimiter but occurred as data
    var parts = url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m,key,value)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 701, Column 43: character "&" is the first character of a delimiter but occurred as data
    var parts = url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m,key,value)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 5.250 visits