hnonline.sk

spravodajstvo, ekonomika, politika, hospodarstvo, aktuality, slovensko, dennik, noviny, prilohy ...

This data was last updated from 18-08-2013 05:02:12  (update).

Overview Info



  • Domain Name
    hnonline.sk
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    6
  • Ip Address
    81.95.101.8
  • Page Size
    117.2 KB
  • Images
    6 GIF, 33 JPG, 21 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 6 11 26 4 0

Website Meta Analysis



  • Title
    HNonline.sk - Spravodajský server Hospodárskych novín
  • Meta Keyword
    spravodajstvo, ekonomika, politika, hospodarstvo, aktuality, slovensko, dennik, noviny, prilohy
  • Meta Description
    spravodajstvo, ekonomika, politika, hospodarstvo, aktuality, slovensko, dennik, noviny, prilohy

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    81.95.101.8
  • Domain Age
  • Javascript Library
    jquery, yui, gwt
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from hnonline.sk.

HTML Analysis

  • server: nginx
  • date: Sun, 18 Aug 2013 17:02:09 GMT
  • content-type: text/html; charset=windows-1250
  • connection: keep-alive
  • last-modified: Sun, 18 Aug 2013 17:02:09 GMT
  • cache-control: no-cache
  • expires: Mon, 2 Jan 2006 12:00:00 GMT
  • x-newest-article: Sun, 18 Aug 2013 16:30:00 GMT
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
%
% whois.sk-nic.sk - whois server for TLD .sk
%


Domain-name hnonline.sk
Admin-id ECOP-0004
Admin-name Ecopress
Admin-legal-form akciova spolocnost
Admin-org.-ID 31333524
Admin-address Seberiniho 1, Bratislava 82007
Admin-telephone 02/48 238 100
Admin-email email
Tech-id TELE-0028
Tech-name GTS Slovakia, s.r.o.
Tech-org.-ID 35795662
Tech-address Einsteinova 24, Bratislava 851 01
Tech-telephone +421232232232 hotline, +421258228111 desk
Tech-email email
dns_name ns.nextra.sk
Last-update 2012-08-17
Valid-date 2013-09-13
Domain-status DOM_OK

DNS Analysis


DNS servers
ns.nextra.sk [195.168.1.2]


DNS Records

Answer records
hnonline.sk SOA
server: ns.nextra.sk
email: hostmaster@nextra.sk
serial: 2013011700
refresh: 21600
retry: 7200
expire: 1209600
minimum ttl: 900
43200s
hnonline.sk NS  ns.nextra.sk 86400s
hnonline.sk NS  ns1.nextra.sk 86400s
hnonline.sk A 81.95.101.9 43200s
hnonline.sk MX
preference: 10
exchange: ip-mx.hnonline.sk
43200s
hnonline.sk MX
preference: 95
exchange: mx-backup1.nextra.sk
43200s
hnonline.sk MX
preference: 100
exchange: mx-backup2.nextra.sk
43200s

Authority records

Additional records
ns.nextra.sk A 195.168.1.2 86400s
ns.nextra.sk A 195.168.1.4 86400s
ns1.nextra.sk A 195.168.1.6 86400s
ip-mx.hnonline.sk A 195.168.43.202 43200s
mx-backup1.nextra.sk A 195.168.1.219 43200s
mx-backup1.nextra.sk A 195.168.1.216 43200s
mx-backup1.nextra.sk A 195.168.1.218 43200s
mx-backup2.nextra.sk A 195.168.1.217 43200s

IP 81.95.101.8 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 80 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.6567996067616992
Message Error
  • Error Line 88, Column 11: document type does not allow element "noscript" here; assuming missing "object" start-tag
    	<noscript>
  • Warning Line 133, Column 38: character "<" is the first character of a delimiter but occurred as data
          for (var i = carousel.first; i <= carousel.last; i++) {

    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 224, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>  

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

  • Info Line 88, Column 2: start tag was here
    	<noscript>
  • Error Line 228, Column 10: required attribute "type" not specified
      <script>

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

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

  • Error Line 329, Column 138: there is no attribute "onClick"
    …'Hľadaný výraz s diakritikou' onClick="if (this.value=='Hľadaný výraz s diakri…

    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 329, Column 231: end tag for "input" omitted, but OMITTAG NO was specified
    …e=='Hľadaný výraz s diakritikou') this.value='';" title="Jednoduché hľadanie.">

    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 329, Column 6: start tag was here
    					<input type="text" name="search[what]" size="20" id="searchinput" class="s…
  • Error Line 331, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
              <input type="hidden" name="search[search]" value="yes">

    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 331, Column 11: start tag was here
              <input type="hidden" name="search[search]" value="yes">
  • Error Line 332, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
              <input type="hidden" name="search[sklonuj]" value="on">

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

  • Info Line 332, Column 11: start tag was here
              <input type="hidden" name="search[sklonuj]" value="on">
  • Error Line 333, Column 65: end tag for "input" omitted, but OMITTAG NO was specified
              <input type="hidden" name="search[sefira]" value="SK">

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

  • Info Line 333, Column 11: start tag was here
              <input type="hidden" name="search[sefira]" value="SK">
  • Error Line 334, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="s1" value="k">

    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 334, Column 6: start tag was here
    					<input type="hidden" name="s1" value="k">
  • Error Line 335, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="s2" value="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 335, Column 6: start tag was here
    					<input type="hidden" name="s2" value="0">
  • Error Line 336, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="s3" value="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 336, Column 6: start tag was here
    					<input type="hidden" name="s3" value="0">
  • Error Line 337, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="s4" value="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 337, Column 6: start tag was here
    					<input type="hidden" name="s4" value="0">
  • Error Line 338, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="s5" value="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 338, Column 6: start tag was here
    					<input type="hidden" name="s5" value="0">
  • Error Line 339, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="s6" value="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 339, Column 6: start tag was here
    					<input type="hidden" name="s6" value="0">
  • Error Line 340, Column 57: end tag for "input" omitted, but OMITTAG NO was specified
    					<input type="hidden" name="m" value="singlesearch">

    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 340, Column 6: start tag was here
    					<input type="hidden" name="m" value="singlesearch">
  • Error Line 391, Column 14: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <h4><a href="http://hnonline.sk/c1-60443500-zahranicie-evakuuje-slova…

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

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

  • Error Line 393, Column 27: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <p class="perex">Európske cestovky zájazdy do Egypta zrušili už dávno…

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

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

  • Error Line 394, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <div class="cleaner"></div>

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

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

  • Error Line 416, Column 14: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <h4><a href="http://finweb.hnonline.sk/c1-60443580-europa-riskuje-dal…

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

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

  • Error Line 418, Column 27: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <p class="perex">Podľa odborníkov riskuje Británia a Holandsko neuváž…

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

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

  • Error Line 420, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <div class="cleaner"></div>

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

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

  • Error Line 437, Column 239: end tag for "img" omitted, but OMITTAG NO was specified
    …aunch/poradna_otazka.png" alt="Potrebujete poradiť?" style="width: 250px;"></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 437, Column 121: start tag was here
    …t="_top" title="Potrebujete poradiť?"><img src="http://hnonline.sk/img/sk/_rel…
  • Error Line 460, Column 14: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <h4><a href="http://hnonline.sk/nazory/c1-60433860-smer-ne-ma-vzdy-pr…

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

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

  • Error Line 462, Column 27: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <p class="perex">Smer má vždy pravdu. Ostatní klamú. Predstavitelia v…

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

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

  • Error Line 463, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <div class="cleaner"></div>

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

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

  • Error Line 491, Column 14: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <h4><a href="http://style.hnonline.sk/auto/c1-60442250-hyundai-chce-s…

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

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

  • Error Line 493, Column 27: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <p class="perex">Juhokórejská automobilka začala mieriť na zákazníkov…

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

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

  • Error Line 494, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <div class="cleaner"></div>

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

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

  • Error Line 521, Column 14: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <h4><a href="http://style.hnonline.sk/digital/c1-60441460-zmenili-sme…

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

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

  • Error Line 523, Column 27: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <p class="perex">Mladí rodičia museli čeliť výzve, že ich dieťa bude …

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

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

  • Error Line 524, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
              <div class="cleaner"></div>

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

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

  • Warning Line 594, Column 1494: character "&" is the first character of a delimiter but occurred as data
    …dila-rating-polska">Agentúra Standard & Poor&#39;s potvrdila rating Poľska</a>…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 609, Column 80: ID "scripting_image" already defined
    …lováci do Egypta lietajú naďalej" id="scripting_image"><img src="http://img.ih…

    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 601, Column 110: ID "scripting_image" first defined here
    …lovaci-do-egypta-lietaju-nadalej" id="scripting_image"><img src="http://img.ih…
  • Error Line 610, Column 19: ID "scripting_title" already defined
              <h1 id="scripting_title"><a href="Zahraničie evakuuje, Slováci do Egy…

    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 602, Column 19: ID "scripting_title" first defined here
              <h1 id="scripting_title"><a href="http://hnonline.sk/c1-60443500-zahr…
  • Error Line 611, Column 32: ID "scripting_perex" already defined
              <p class="perex" id="scripting_perex">Európske cestovky zájazdy do Eg…

    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 603, Column 32: ID "scripting_perex" first defined here
              <p class="perex" id="scripting_perex">Európske cestovky zájazdy do Eg…
  • Error Line 613, Column 20: ID "scripting_box" already defined
              <div id="scripting_box"></div>

    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 605, Column 20: ID "scripting_box" first defined here
              <div id="scripting_box"></div>
  • Error Line 725, Column 102: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …are.hnonline.sk" class="no_change"><h3><span>HN</span>komentáre&nbsp;&raquo;</…

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

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

  • Error Line 795, Column 101: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …na.hnonline.sk/" class="no_change"><h3><span>HN</span>poradňa&nbsp;&raquo;</h3…

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

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

  • Error Line 800, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div class="float">

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

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

  • Error Line 808, Column 31: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div class="float">

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

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

  • Error Line 824, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                  <h4><a href="http://hnporadna.hnonline.sk/c1-60436610-pri-mailoch…

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

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

  • Error Line 828, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                  <h4><a href="Pri mailoch zbytočne „preflákame“ až 80 percent času…

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

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

  • Error Line 840, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                  <h4><a href="http://hnporadna.hnonline.sk/c1-60431200-nerozumiete…

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

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

  • Error Line 844, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                  <h4><a href="Nerozumiete bankárom? Naučte sa „bankárčinu“" class=…

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

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

  • Error Line 863, Column 96: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tv.hnonline.sk/" class="no_change"><h3><span>HN</span>TV&nbsp;&raquo;</h3></a>…

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

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

  • Error Line 871, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            						<h4>Zmenili sme porážku na výzvu <b><font color="ff9900">(video)<…

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

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

  • Error Line 876, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            						<h4>Tento rozpočet bude najdrahší na svete <b><font color="ff9900…

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

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

  • Error Line 881, Column 18: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            						<h4>Pozrite si neskrátenú reláciu s Thapir (Piano)</h4>

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

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

  • Warning Line 972, Column 1264: character "&" is the first character of a delimiter but occurred as data
    …i..."><span ></span>Agentúra Standard & Poor&#39;s potvrdila rating Poľska</a>…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1017, Column 41: there is no attribute "onClick"
    …          <li><a href="#tab5" onClick="loadFragmentInToElement('fragment_url',…

    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 1024, Column 46: there is no attribute "CELLPADDING"
    …                  	<table CELLPADDING="0" CELLSPACING="0" class="table-kurzovy…

    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 1024, Column 62: there is no attribute "CELLSPACING"
    …          	<table CELLPADDING="0" CELLSPACING="0" class="table-kurzovy-cennik">

    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 1025, Column 35: there is no attribute "COLSPAN"
                      <tr><th COLSPAN="2">Mena</th><th>Názov meny</th><th COLSPAN="…

    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 1118, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …w.php?iks=274702,176,333" frameborder=0 width="100%" height="250" scrolling="N…
  • Error Line 1118, Column 165: value of attribute "scrolling" cannot be "NO"; must be one of "yes", "no", "auto"
    …idth="100%" height="250" scrolling="NO">Nedokážeme zobraziť komodity, nakoľko …

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1140, Column 175: required attribute "alt" not specified
    …launch/HNONLINE_FINAL_21.jpg" style="margin-top: 20px;" id="new_media" /></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 1149, Column 104: document type does not allow element "link" here
    …heet" type="text/css" href="http://www.floowie.com/vendors/css/fancybox.css" />

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

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

  • Error Line 1187, Column 78: there is no attribute "href"
    …n-top: 20px;"></div><fb:like-box href="http://www.facebook.com/hospodarskenovi…

    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 1187, Column 128: there is no attribute "width"
    …facebook.com/hospodarskenoviny" width="299" show_faces="true" border_color="" …

    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 1187, Column 145: there is no attribute "show_faces"
    …odarskenoviny" width="299" show_faces="true" border_color="" stream="false" he…

    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 1187, Column 165: there is no attribute "border_color"
    …="299" show_faces="true" border_color="" stream="false" header="false"></fb:li…

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

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

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

  • Error Line 1187, Column 175: there is no attribute "stream"
    …w_faces="true" border_color="" stream="false" header="false"></fb:like-box>   …

    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 1187, Column 190: there is no attribute "header"
    …"true" border_color="" stream="false" header="false"></fb:like-box>            

    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 1187, Column 197: element "fb:like-box" undefined
    …"true" border_color="" stream="false" header="false"></fb:like-box>            

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

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

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

  • Error Line 1344, Column 35: an attribute specification must start with a name or name token
                  document.write('<scr'+'ipt type="text/javascript" src="http://dat…

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

  • Error Line 1344, Column 35: element "scr" undefined
                  document.write('<scr'+'ipt type="text/javascript" src="http://dat…

    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 1344, Column 133: delimiter "'" invalid: only S separators and TAGC allowed here
    …c="http://data.hnonline.sk/vaniti3/jsexport.php?op=HNonline"></scr'+'ipt>');   
  • Error Line 1347, Column 35: an attribute specification must start with a name or name token
                  document.write('<scr'+'ipt type="text/javascript" src="http://dat…

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

  • Error Line 1347, Column 35: element "scr" undefined
                  document.write('<scr'+'ipt type="text/javascript" src="http://dat…

    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 1347, Column 133: delimiter "'" invalid: only S separators and TAGC allowed here
    …src="http://data.hnonline.sk/vaniti3/jsexport.php?op=HNonline"></scr'+'ipt>'); 
  • Error Line 1381, Column 42: there is no attribute "async"
    … <script type="text/javascript" async="true" charset="utf-8" src="http://sk.se…

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

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

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

  • Error Line 1401, Column 44: document type does not allow element "div" here
    …ar content_rectangleSource = $('<div />').append($("#rectangle-source-block di…

    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 1402, Column 39: character "&" is the first character of a delimiter but occurred as data
        if (content_rectangleSource != "" && $('#rectangle-destination-block').leng…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1402, Column 40: character "&" is the first character of a delimiter but occurred as data
    …   if (content_rectangleSource != "" && $('#rectangle-destination-block').leng…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1422, Column 112: character "&" is the first character of a delimiter but occurred as data
    …o.indexOf('hnporadna.hnonline.sk') >= 0)*/) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1422, Column 113: character "&" is the first character of a delimiter but occurred as data
    …o.indexOf('hnporadna.hnonline.sk') >= 0)*/) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1427, Column 56: character "&" is the first character of a delimiter but occurred as data
    … ((urlPiano.indexOf('hn.hnonline.sk') >= 0) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1427, Column 57: character "&" is the first character of a delimiter but occurred as data
    … ((urlPiano.indexOf('hn.hnonline.sk') >= 0) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1432, Column 130: character "&" is the first character of a delimiter but occurred as data
    …ttp://style.hnonline.sk/preconie') >= 0)*/) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1432, Column 131: character "&" is the first character of a delimiter but occurred as data
    …ttp://style.hnonline.sk/preconie') >= 0)*/) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1437, Column 60: character "&" is the first character of a delimiter but occurred as data
    …rlPiano.indexOf('hnonline.sk/nazory') >= 0) && (urlPiano.indexOf('/c') >= 0)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1437, Column 61: character "&" is the first character of a delimiter but occurred as data
    …rlPiano.indexOf('hnonline.sk/nazory') >= 0) && (urlPiano.indexOf('/c') >= 0)) {

    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 1453, Column 24: an attribute specification must start with a name or name token
        document.write('<sc'+'rip'+'t type="text/javascript" charset="utf-8" src="h…

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

  • Error Line 1453, Column 24: element "sc" undefined
        document.write('<sc'+'rip'+'t type="text/javascript" charset="utf-8" src="h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1453, Column 139: cannot generate system identifier for general entity "mode"
    …ia.sk/bar/?serviceID='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pian…

    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 1453, Column 139: general entity "mode" not defined and no default entity
    …ia.sk/bar/?serviceID='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pian…

    This is usually a cascading error caused by 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 1453, Column 143: reference not terminated by REFC delimiter
    …k/bar/?serviceID='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArt…

    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 1453, Column 143: reference to entity "mode" for which no system identifier could be generated
    …k/bar/?serviceID='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArt…

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

  • Info Line 1453, Column 138: entity was defined here
    …dia.sk/bar/?serviceID='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pia…
  • Warning Line 1453, Column 158: cannot generate system identifier for general entity "bar"
    …D='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+…

    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 1453, Column 158: general entity "bar" not defined and no default entity
    …D='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+…

    This is usually a cascading error caused by 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 1453, Column 161: reference not terminated by REFC delimiter
    …+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ri…

    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 1453, Column 161: reference to entity "bar" for which no system identifier could be generated
    …+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ri…

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

  • Info Line 1453, Column 157: entity was defined here
    …ID='+servicePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'…
  • Warning Line 1453, Column 169: cannot generate system identifier for general entity "art"
    …icePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ript>');

    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 1453, Column 169: general entity "art" not defined and no default entity
    …icePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ript>');

    This is usually a cascading error caused by 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 1453, Column 172: reference not terminated by REFC delimiter
    …icePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ript>');

    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 1453, Column 172: reference to entity "art" for which no system identifier could be generated
    …icePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ript>');

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

  • Info Line 1453, Column 168: entity was defined here
    …icePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ript>');
  • Error Line 1453, Column 196: delimiter "'" invalid: only S separators and TAGC allowed here
    …icePiano+'&mode='+modePiano+'&bar=normal&art='+pianoArticles+'"></sc'+'ript>');

Visitor Analysis

Daily Visitor
  • 16.683 visits

In Page Analysis