luban24.pl

Lubań Wiadomości z Lubania. Forum dyskusyjne, bieżące aktualności, plotki, katalog firm, mapa Lubania, lubańska kultura i sztuka. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    luban24.pl
  • Favicon
  • Alexa Rank
    #549268
  • Google Page Rank
    PR 3
  • Ip Address
    5.9.64.253
  • Page Size
    82.2 KB
  • Images
    6 GIF, 14 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Lubań Luban24 Wiadomości z Lubania
  • Meta Keyword
    Lubań, Luban24, Wiadomości, Lubania
  • Meta Description
    Lubań Wiadomości z Lubania. Forum dyskusyjne, bieżące aktualności, plotki, katalog firm, mapa Lubania, lubańska kultura i sztuka.

Technical Analysis



  • Webserver
    LiteSpeed
  • Ip Address
    5.9.64.253
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from luban24.pl.

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Wed, 18 Sep 2013 20:27:11 GMT
  • server: LiteSpeed
  • connection: Keep-Alive
  • x-powered-by: PHP/5.3.18
  • pragma: no-cache
  • cache-control: private
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Wed, 18 Sep 2013 20:27:10 GMT
  • content-type: text/html; charset=ISO-8859-2
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: luban24.pl
registrant type: individual
nameservers: ns1.d2.pl. [188.40.76.185]
ns2.d2.pl. [188.40.74.100]
created: 2007.01.24 15:30:17
last modified: 2012.03.01 23:29:31
renewal date: 2013.01.24 15:30:17

no option


TECHNICAL CONTACT:
company: Albert Jerka, Andrzej Kostrzewa
AZ.pl Sp. z o.o.
street: Sosnowa 6a
city: 71-468 Szczecin
location: PL
handle: tdc8747724016768
phone: +48.914243780
fax: +48.914243799
last modified: 2010.07.19


REGISTRAR:
AZ.pl Sp. z o.o.
ul. Niedzialkowskiego 24(IX p.)
71-410 Szczecin
Polska/Poland
+48.801080031
email

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

DNS Analysis


DNS servers
ns2.d2.pl [5.9.62.24]
ns1.d2.pl [5.9.127.76]


DNS Records

Answer records
luban24.pl SOA
server: ns1.d2.pl
email: hostmaster@luban24.pl
serial: 2012111001
refresh: 14400
retry: 314400
expire: 120914400
minimum ttl: 86400
14400s
luban24.pl NS  ns2.d2.pl 14400s
luban24.pl NS  ns1.d2.pl 14400s
luban24.pl A 5.9.64.253 14400s
luban24.pl MX
preference: 10
exchange: mail.luban24.pl
14400s
luban24.pl TXT v=spf1 ip4:5.9.64.253 ip4:5.9.127.69 a mx -all 14400s

Authority records

Additional records
ns1.d2.pl A 5.9.127.76 14400s
ns2.d2.pl A 5.9.62.24 14400s
mail.luban24.pl A 5.9.64.253 14400s

IP 5.9.64.253 Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 161 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.6173238449384006
Message Error
  • Error Line 7, Column 52: end tag for "meta" omitted, but OMITTAG NO was specified
      <meta http-equiv="content-language" content="pl">

    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 3: start tag was here
      <meta http-equiv="content-language" content="pl">
  • Error Line 10, Column 49: end tag for "link" omitted, but OMITTAG NO was specified
    	<link rel="shortcut icon" href="luban24pl.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 10, Column 2: start tag was here
    	<link rel="shortcut icon" href="luban24pl.ico">
  • Error Line 30, Column 41: document type does not allow element "style" here
    		document.write('<style type="text/css">');	 

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

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

  • Warning Line 31, Column 48: character "<" is the first character of a delimiter but occurred as data
    		document.write('div.domtab div{display:none;}<');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 32, Column 22: delimiter "'" invalid: only S separators and TAGC allowed here
    		document.write('</s'+'tyle>');	 
  • Error Line 32, Column 22: end tag for element "s" which is not open
    		document.write('</s'+'tyle>');	 

    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 33, Column 11: end tag for "style" omitted, but OMITTAG NO was specified
    	 </script>

    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 30, Column 19: start tag was here
    		document.write('<style type="text/css">');	 
  • Error Line 69, Column 8: required attribute "type" not specified
    	<style>

    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 149, Column 48: character data is not allowed here
    	 <ul id="eventTicker" style="display:inline"> Nadchodzące wydarzenia: 

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 206, Column 66: end tag for "br" omitted, but OMITTAG NO was specified
    											<div id="media" style="margin-left:20px;"> </div> <br><br>

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

  • Info Line 206, Column 62: start tag was here
    											<div id="media" style="margin-left:20px;"> </div> <br><br>
  • Error Line 206, Column 70: end tag for "br" omitted, but OMITTAG NO was specified
    											<div id="media" style="margin-left:20px;"> </div> <br><br>

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

  • Info Line 206, Column 66: start tag was here
    											<div id="media" style="margin-left:20px;"> </div> <br><br>
  • Error Line 230, Column 488: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p?action=media"><span>Galeria<b style=color:red>!</b></span></a></li><li><a  h…
  • Error Line 230, Column 629: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ezentacja</span></a></li><li><a style=color:yellow href="http://www.luban24.pl…
  • Error Line 242, Column 22: character data is not allowed here
    	<ul id="newsTicker">Najnowsze: 

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 277, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <img src="reklamy/powiat_luban.jpg" border=0 width=200>
  • Error Line 277, Column 52: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <img src="reklamy/powiat_luban.jpg" border=0 width=200>
  • Error Line 277, Column 55: required attribute "alt" not specified
    <img src="reklamy/powiat_luban.jpg" border=0 width=200>

    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 277, Column 56: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="reklamy/powiat_luban.jpg" border=0 width=200>

    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 1: start tag was here
    <img src="reklamy/powiat_luban.jpg" border=0 width=200>
  • Error Line 289, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=#  onMouseover="ddrivetip('<img src=http://lcr.net.pl/sites/default/fil…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 289, Column 24: there is no attribute "onMouseover"
    <a href=#  onMouseover="ddrivetip('<img src=http://lcr.net.pl/sites/default/fil…

    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 289, Column 36: character "<" is the first character of a delimiter but occurred as data
    <a href=#  onMouseover="ddrivetip('<img src=http://lcr.net.pl/sites/default/fil…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 289, Column 116: there is no attribute "onMouseout"
    …iles/luban24.jpg />',550)" onMouseout="hideddrivetip()"><img alt='' title='' s…

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

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

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

  • Error Line 291, Column 9: an attribute value must be a literal unless it contains only name characters
    <a href=# onMouseover="ddrivetip('<img src=http://xn--luba24-leb.pl/mdk/photos/…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 291, Column 35: character "<" is the first character of a delimiter but occurred as data
    <a href=# onMouseover="ddrivetip('<img src=http://xn--luba24-leb.pl/mdk/photos/…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 292, Column 129: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ew"><img src="http://www.luban24.pl/reklamy/karkonosze_logo.jpg" width=200></a>
  • Error Line 292, Column 132: required attribute "alt" not specified
    …ew"><img src="http://www.luban24.pl/reklamy/karkonosze_logo.jpg" width=200></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 292, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …ew"><img src="http://www.luban24.pl/reklamy/karkonosze_logo.jpg" width=200></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 292, Column 62: start tag was here
    …an24.pl/index.php?topic=7251.new#new"><img src="http://www.luban24.pl/reklamy/…
  • Error Line 294, Column 115: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …pic=7177.0"><img src="http://www.luban24.pl/patronat/superw.gif" width=200></a>
  • Error Line 294, Column 118: required attribute "alt" not specified
    …pic=7177.0"><img src="http://www.luban24.pl/patronat/superw.gif" width=200></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 294, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …pic=7177.0"><img src="http://www.luban24.pl/patronat/superw.gif" width=200></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 294, Column 56: start tag was here
    …ww.luban24.pl/index.php?topic=7177.0"><img src="http://www.luban24.pl/patronat…
  • Error Line 298, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …dzisiejszą datą w kalendarzu.<br></div></div><div class="tborder" style="margi…

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

  • Info Line 298, Column 105: start tag was here
    …darzeń z dzisiejszą datą w kalendarzu.<br></div></div><div class="tborder" sty…
  • Error Line 301, Column 130: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …er.php?partner=http://nj24.pl" target=_blank><br /><img src=partnerzy/nj24_200…
  • Error Line 301, Column 152: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nj24.pl" target=_blank><br /><img src=partnerzy/nj24_200.jpg width=190 /><br /…
  • Error Line 301, Column 162: NET-enabling start-tag not immediately followed by null end-tag
    …arget=_blank><br /><img src=partnerzy/nj24_200.jpg width=190 /><br /></a><a hr…

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

  • Error Line 301, Column 162: required attribute "alt" not specified
    …arget=_blank><br /><img src=partnerzy/nj24_200.jpg width=190 /><br /></a><a hr…

    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 301, Column 162: end tag for "img" omitted, but OMITTAG NO was specified
    …arget=_blank><br /><img src=partnerzy/nj24_200.jpg width=190 /><br /></a><a hr…

    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 301, Column 143: start tag was here
    …r=http://nj24.pl" target=_blank><br /><img src=partnerzy/nj24_200.jpg width=19…
  • Error Line 301, Column 240: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ef="index.php?page=14"><br /><img src=reklamy/dostepna_tlb.gif /><br /></a><a …
  • Error Line 301, Column 248: NET-enabling start-tag not immediately followed by null end-tag
    …x.php?page=14"><br /><img src=reklamy/dostepna_tlb.gif /><br /></a><a href="ht…

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

  • Error Line 301, Column 248: required attribute "alt" not specified
    …x.php?page=14"><br /><img src=reklamy/dostepna_tlb.gif /><br /></a><a href="ht…

    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 301, Column 248: end tag for "img" omitted, but OMITTAG NO was specified
    …x.php?page=14"><br /><img src=reklamy/dostepna_tlb.gif /><br /></a><a href="ht…

    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 301, Column 231: start tag was here
    …</a><a href="index.php?page=14"><br /><img src=reklamy/dostepna_tlb.gif /><br …
  • Error Line 301, Column 351: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …hp?partner=http://gryfow.info" target=_blank><br /><img src=partnerzy/gryfowin…
  • Error Line 301, Column 373: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ow.info" target=_blank><br /><img src=partnerzy/gryfowinfo.jpg width=190 /><br…
  • Error Line 301, Column 383: NET-enabling start-tag not immediately followed by null end-tag
    …arget=_blank><br /><img src=partnerzy/gryfowinfo.jpg width=190 /><br /></a><a …

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

  • Error Line 301, Column 383: required attribute "alt" not specified
    …arget=_blank><br /><img src=partnerzy/gryfowinfo.jpg width=190 /><br /></a><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 301, Column 383: end tag for "img" omitted, but OMITTAG NO was specified
    …arget=_blank><br /><img src=partnerzy/gryfowinfo.jpg width=190 /><br /></a><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 301, Column 364: start tag was here
    …tp://gryfow.info" target=_blank><br /><img src=partnerzy/gryfowinfo.jpg width=…
  • Error Line 301, Column 499: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rtner=http://lwowekslaski.net" target=_blank><br /><img src=partnerzy/baner-ls…
  • Error Line 301, Column 521: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ski.net" target=_blank><br /><img src=partnerzy/baner-ls.gif width=190 /><br /…
  • Error Line 301, Column 531: NET-enabling start-tag not immediately followed by null end-tag
    …arget=_blank><br /><img src=partnerzy/baner-ls.gif width=190 /><br /></a></div…

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

  • Error Line 301, Column 531: required attribute "alt" not specified
    …arget=_blank><br /><img src=partnerzy/baner-ls.gif width=190 /><br /></a></div…

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

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

  • Error Line 301, Column 531: end tag for "img" omitted, but OMITTAG NO was specified
    …arget=_blank><br /><img src=partnerzy/baner-ls.gif width=190 /><br /></a></div…

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

  • Info Line 301, Column 512: start tag was here
    …lwowekslaski.net" target=_blank><br /><img src=partnerzy/baner-ls.gif width=19…
  • Error Line 305, Column 14: there is no attribute "ALIGN"
    <table ALIGN="center" width=200>

    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 305, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table ALIGN="center" width=200>
  • Error Line 307, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 307, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 311, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 311, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 315, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 315, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 319, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 319, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 323, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 323, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 327, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 327, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<td valign=top width=62><center>
  • Error Line 331, Column 6: end tag for "tr" which is not finished
    	</tr>

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

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

  • Error Line 377, Column 43: end tag for "br" omitted, but OMITTAG NO was specified
    											<div id="eurobank"> </div> <br><br>

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

  • Info Line 377, Column 39: start tag was here
    											<div id="eurobank"> </div> <br><br>
  • Error Line 377, Column 47: end tag for "br" omitted, but OMITTAG NO was specified
    											<div id="eurobank"> </div> <br><br>

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

  • Info Line 377, Column 43: start tag was here
    											<div id="eurobank"> </div> <br><br>
  • Error Line 378, Column 182: end tag for "img" omitted, but OMITTAG NO was specified
    …//zlobekluban.pl/zlobek.gif" alt="prywatny zlobek w lubaniu"></a></center><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 378, Column 103: start tag was here
    …an, zlobek w lubaniu" target="_blank"><img src="http://zlobekluban.pl/zlobek.g…
  • Error Line 411, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>W dniu 18.01.2013 r. w Ośrodku Szkoleń …

    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 422, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Powiat Lubański zajął 1 miejsce w Wojew…

    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 433, Column 204: there is no attribute "type"
    …l/index.php?topic=7789.0"><embed type="application/x-shockwave-flash" src="htt…

    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 433, Column 240: there is no attribute "src"
    …e="application/x-shockwave-flash" src="http://www.youtube.com/v/u2P9HYioh9o?ve…

    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 433, Column 312: there is no attribute "width"
    …h9o?version=3&amp;amp;hl=pl_PL" width="490" height="300" play="true" loop="tru…

    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 433, Column 325: there is no attribute "height"
    …&amp;amp;hl=pl_PL" width="490" height="300" play="true" loop="true" quality="h…

    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 433, Column 336: there is no attribute "play"
    …=pl_PL" width="490" height="300" play="true" loop="true" quality="high" AllowS…

    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 433, Column 348: there is no attribute "loop"
    …h="490" height="300" play="true" loop="true" quality="high" AllowScriptAccess=…

    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 433, Column 363: there is no attribute "quality"
    …"300" play="true" loop="true" quality="high" AllowScriptAccess="never" /><noem…

    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 433, Column 388: there is no attribute "AllowScriptAccess"
    …rue" quality="high" AllowScriptAccess="never" /><noembed><a href="http://www.y…

    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 433, Column 397: element "embed" undefined
    …ity="high" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.co…

    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 433, Column 406: element "noembed" undefined
    …" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.com/v/u2P9H…

    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 444, Column 302: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Lubański Finał Wielkiej Orkiestry Świąt…

    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 444, Column 547: unclosed start-tag requires SHORTTAG YES
    …ie zajął się po raz dwudziesty Miejski Dom Kultury.<br /><br...</a></div>	</td>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 444, Column 547: element "br..." undefined
    …ie zajął się po raz dwudziesty Miejski Dom Kultury.<br /><br...</a></div>	</td>

    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 444, Column 550: end tag for "br..." omitted, but OMITTAG NO was specified
    …ie zajął się po raz dwudziesty Miejski Dom Kultury.<br /><br...</a></div>	</td>

    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 444, Column 541: start tag was here
    …ie zajął się po raz dwudziesty Miejski Dom Kultury.<br /><br...</a></div>	</td>
  • Error Line 455, Column 299: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Mieszka w Lubaniu, ma 26 lat, studiuje …

    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 466, Column 328: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Ana Julia studiuje biochemię, Christina…

    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 477, Column 397: element "embed" undefined
    …ity="high" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.co…

    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 477, Column 406: element "noembed" undefined
    …" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.com/v/oU0Dc…

    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 488, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Łużyckie Centrum Rozwoju i Lubańskie Ce…

    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 499, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Początek roku skłania większość z nas d…

    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 510, Column 397: element "embed" undefined
    …ity="high" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.co…

    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 510, Column 406: element "noembed" undefined
    …" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.com/v/_HX-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 521, Column 397: element "embed" undefined
    …ity="high" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.co…

    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 521, Column 406: element "noembed" undefined
    …" AllowScriptAccess="never" /><noembed><a href="http://www.youtube.com/v/_NV5i…

    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 532, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Społeczność Gimnazjum nr 1 im. Stanisł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 543, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Drogowskazem tegorocznego BETLEJEMSKIEG…

    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 554, Column 342: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Śnieg skrzypiał pod stopami, mrozisko s…

    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 565, Column 316: required attribute "alt" not specified
    …5" hspace="10" border="0" width="200"/>Olszyńskie stowarzyszenie na rzecz rozw…

    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 583, Column 178: end tag for element "a" which is not open
    …e  (3)')" onMouseout="hideddrivetip()">Pomóż samotnej matce... </a> </a>  </li>

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

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

  • Error Line 584, Column 194: end tag for element "a" which is not open
    …" onMouseout="hideddrivetip()">Rusza SZLACHETNA PACZKA 2012... </a> </a>  </li>

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

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

  • Error Line 585, Column 236: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Wodociąg gminny czyli &quot;Ni... </a> </a>  </li>

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

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

  • Error Line 586, Column 201: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">20 lat Straży Miejskiej w Luba... </a> </a>  </li>

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

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

  • Error Line 587, Column 207: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Piknik historyczno-kulturalny ... </a> </a>  </li>

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

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

  • Error Line 588, Column 209: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Dziesiątki milionów euro na fo... </a> </a>  </li>

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

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

  • Error Line 589, Column 201: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Zebranie w Kościelnikach Dolny... </a> </a>  </li>

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

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

  • Error Line 590, Column 202: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Spotkanie z poseł Marzeną Mach... </a> </a>  </li>

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

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

  • Error Line 591, Column 166: end tag for element "a" which is not open
    …Lubań ?  (0)')" onMouseout="hideddrivetip()">Browar Lubań ?... </a> </a>  </li>

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

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

  • Error Line 592, Column 212: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">5 do 8 % wzrośnie VAT na lody ... </a> </a>  </li>

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

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

  • Error Line 627, Column 208: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Pinokio - aternative (Dni Luba... </a> </a>  </li>

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

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

  • Error Line 628, Column 224: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">&quot;Podróż do osiemnastowiec... </a> </a>  </li>

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

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

  • Error Line 629, Column 230: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Projekcja filmu &quot;List z P... </a> </a>  </li>

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

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

  • Error Line 630, Column 190: end tag for element "a" which is not open
    …')" onMouseout="hideddrivetip()">Wspomnienie Papieża Polaka... </a> </a>  </li>

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

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

  • Error Line 631, Column 204: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Obchody rocznicy katastrofy TU... </a> </a>  </li>

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

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

  • Error Line 632, Column 172: end tag for element "a" which is not open
    …zony  (3)')" onMouseout="hideddrivetip()">Menuet zakończony... </a> </a>  </li>

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

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

  • Error Line 633, Column 210: end tag for element "a" which is not open
    …onMouseout="hideddrivetip()">Otwarcie Lubańskiego Centrum H... </a> </a>  </li>

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

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

  • Error Line 634, Column 188: end tag for element "a" which is not open
    …)')" onMouseout="hideddrivetip()">II Winter Blues w Lubaniu... </a> </a>  </li>

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

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

  • Error Line 684, Column 54: ID "blockx62" already defined
    						<div class="windowbg" style="padding:0px;" id="blockx62">

    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 666, Column 54: ID "blockx62" first defined here
    						<div class="windowbg" style="padding:0px;" id="blockx62">
  • Warning Line 689, Column 179: cannot generate system identifier for general entity "q..."
    …(5)')" onMouseout="hideddrivetip()">Jesteśmy świata męką...&q... </a> (5) </li>

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

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

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

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

  • Error Line 689, Column 179: general entity "q..." not defined and no default entity
    …(5)')" onMouseout="hideddrivetip()">Jesteśmy świata męką...&q... </a> (5) </li>

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

  • Warning Line 689, Column 183: reference not terminated by REFC delimiter
    …(5)')" onMouseout="hideddrivetip()">Jesteśmy świata męką...&q... </a> (5) </li>

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

  • Error Line 689, Column 183: reference to entity "q..." for which no system identifier could be generated
    …(5)')" onMouseout="hideddrivetip()">Jesteśmy świata męką...&q... </a> (5) </li>

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

  • Info Line 689, Column 178: entity was defined here
    …(5)')" onMouseout="hideddrivetip()">Jesteśmy świata męką...&q... </a> (5) </li>
  • Error Line 701, Column 54: ID "blockx50" already defined
    						<div class="windowbg" style="padding:0px;" id="blockx50">

    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 580, Column 54: ID "blockx50" first defined here
    						<div class="windowbg" style="padding:0px;" id="blockx50">
  • Error Line 703, Column 195: end tag for element "a" which is not open
    …olędowanie u Bukowińczyków... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 407: end tag for element "a" which is not open
    …nazja- Kuszenie świętego A... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 585: end tag for element "a" which is not open
    …etip()">Kierowca i pieszy.... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 802: end tag for element "a" which is not open
    …zór Wspomnień o Janie od B... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 973: end tag for element "a" which is not open
    …drivetip()">21 Finał WOŚP ... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 1155: end tag for element "a" which is not open
    …ip()">Pieniądze na zabytki... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 1335: end tag for element "a" which is not open
    …tip()">Wędruj razem z nami... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 1539: end tag for element "a" which is not open
    … Komendant Straży Miejskie... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 1770: end tag for element "a" which is not open
    …łych oraz Błogosławionych ... </a> </a>  </li><li><a href="http://www.luban24.…

    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 703, Column 1959: end tag for element "a" which is not open
    …18)')" onMouseout="hideddrivetip()">JUTRO KONIEC ŚWIATA !!!... </a> </a>  </li>

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

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

  • Error Line 733, Column 17: ID "rightbarHeader" already defined
    					  <div id="rightbarHeader" style="width: 200px; text-align: left; padding-…

    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 574, Column 17: ID "rightbarHeader" first defined here
    					  <div id="rightbarHeader" style="width: 200px; text-align: left; padding-…
  • Error Line 738, Column 104: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 
  • Error Line 738, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 
  • Error Line 738, Column 115: required attribute "alt" not specified
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 

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

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

  • Error Line 738, Column 119: end tag for "img" omitted, but OMITTAG NO was specified
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 

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

  • Info Line 738, Column 54: start tag was here
    …/www.luban24.pl/index.php?topic=7725"><img src="reklamy/spoldzielcza200x200.jp…
  • Error Line 738, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 

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

  • Info Line 738, Column 120: start tag was here
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 
  • Error Line 738, Column 128: end tag for "br" omitted, but OMITTAG NO was specified
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 

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

  • Info Line 738, Column 124: start tag was here
    …25"><img src="reklamy/spoldzielcza200x200.jpg" border=0 width=200></a><br><br> 
  • Error Line 741, Column 114: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>
  • Error Line 741, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>
  • Error Line 741, Column 125: required attribute "alt" not specified
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>

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

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

  • Error Line 741, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>

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

  • Info Line 741, Column 76: start tag was here
    …p?partner=http://www.komislombard.pl"><img src="reklamy/lombard.gif" border=0 …
  • Error Line 741, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>

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

  • Info Line 741, Column 130: start tag was here
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>
  • Error Line 741, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>

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

  • Info Line 741, Column 134: start tag was here
    …komislombard.pl"><img src="reklamy/lombard.gif" border=0 width=200></a><br><br>
  • Error Line 744, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>
  • Error Line 744, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>
  • Error Line 744, Column 103: required attribute "alt" not specified
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>

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

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

  • Error Line 744, Column 107: end tag for "img" omitted, but OMITTAG NO was specified
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>

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

  • Info Line 744, Column 54: start tag was here
    …/www.luban24.pl/index.php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 …
  • Error Line 744, Column 112: end tag for "br" omitted, but OMITTAG NO was specified
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>

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

  • Info Line 744, Column 108: start tag was here
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>
  • Error Line 744, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>

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

  • Info Line 744, Column 112: start tag was here
    ….php?topic=7688"><img src="reklamy/tkacka4.gif" border=0 width=200></a><br><br>
  • Error Line 747, Column 49: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ttp://www.sunny-holiday.org"><img src=reklamy/sunny_holiday_baner_200x200.gif …
  • Error Line 747, Column 57: NET-enabling start-tag not immediately followed by null end-tag
    …w.sunny-holiday.org"><img src=reklamy/sunny_holiday_baner_200x200.gif border=0…

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

  • Error Line 747, Column 57: required attribute "alt" not specified
    …w.sunny-holiday.org"><img src=reklamy/sunny_holiday_baner_200x200.gif border=0…

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

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

  • Error Line 747, Column 57: end tag for "img" omitted, but OMITTAG NO was specified
    …w.sunny-holiday.org"><img src=reklamy/sunny_holiday_baner_200x200.gif border=0…

    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 747, Column 40: start tag was here
    …a href="http://www.sunny-holiday.org"><img src=reklamy/sunny_holiday_baner_200…
  • Error Line 747, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
    …img src=reklamy/sunny_holiday_baner_200x200.gif border=0 width=200></a><br><br>

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

  • Info Line 747, Column 112: start tag was here
    …img src=reklamy/sunny_holiday_baner_200x200.gif border=0 width=200></a><br><br>
  • Error Line 747, Column 120: end tag for "br" omitted, but OMITTAG NO was specified
    …img src=reklamy/sunny_holiday_baner_200x200.gif border=0 width=200></a><br><br>

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

  • Info Line 747, Column 116: start tag was here
    …img src=reklamy/sunny_holiday_baner_200x200.gif border=0 width=200></a><br><br>
  • Error Line 753, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>
  • Error Line 753, Column 103: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>
  • Error Line 753, Column 106: required attribute "alt" not specified
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>

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

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

  • Error Line 753, Column 110: end tag for "img" omitted, but OMITTAG NO was specified
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>

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

  • Info Line 753, Column 54: start tag was here
    …/www.luban24.pl/index.php?topic=7644"><img src="reklamy/ratuszowa7.gif" border…
  • Error Line 753, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>

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

  • Info Line 753, Column 111: start tag was here
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>
  • Error Line 753, Column 119: end tag for "br" omitted, but OMITTAG NO was specified
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>

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

  • Info Line 753, Column 115: start tag was here
    …p?topic=7644"><img src="reklamy/ratuszowa7.gif" border=0 width=200></a><br><br>
  • Error Line 754, Column 69: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …title="moto" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg bor…
  • Error Line 754, Column 75: NET-enabling start-tag not immediately followed by null end-tag
    …"moto" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg border=0 …

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

  • Error Line 754, Column 75: required attribute "alt" not specified
    …"moto" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg border=0 …

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

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

  • Error Line 754, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    …"moto" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg border=0 …

    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 754, Column 60: start tag was here
    …okus.pl" title="moto" target="_blank"><img src=http://luban24.pl/reklamy/kleci…
  • Error Line 754, Column 245: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …radow-zdroj" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg bor…
  • Error Line 754, Column 251: NET-enabling start-tag not immediately followed by null end-tag
    …zdroj" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg border=0 …

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

  • Error Line 754, Column 251: required attribute "alt" not specified
    …zdroj" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg border=0 …

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

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

  • Error Line 754, Column 251: end tag for "img" omitted, but OMITTAG NO was specified
    …zdroj" target="_blank"><img src=http://luban24.pl/reklamy/klecie.jpg border=0 …

    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 754, Column 236: start tag was here
    …ania swieradow-zdroj" target="_blank"><img src=http://luban24.pl/reklamy/kleci…
  • Error Line 754, Column 334: end tag for "center" omitted, but OMITTAG NO was specified
    …=0 height=0 alt="engine car"></a></div></div><div class="tborder" style="margi…

    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 736, Column 60: start tag was here
    		<div class="windowbg" style="padding:0px; " id="block61"><center>

Visitor Analysis

Daily Visitor
  • 292 visits

In Page Analysis