Καιρος: Ο καιρός στην Ελλάδα | Πρόγνωση Καιρού Ελλάδας | Καιρός Αθήνα Θεσσαλονίκη | Ο καιρός σημερα. | Μετεωρολογικές προγνώσεις | Δελτίο Καιρού ...

weather.in.gr
  • Domain Name
    weather.in.gr
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #2732
  • Page Size
    75.3 KB
  • Ip Address
    194.63.247.211
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    5 GIF, 5 JPG, 3 PNG

Website Meta Analysis

  • Title
    Καιρός - in.gr
  • Meta Keyword
    καιρος,καιρός,kairos,kairos athina,καιρός για Αθήνα,kairos ellada
  • Meta Description
    Καιρος: Ο καιρός στην Ελλάδα | Πρόγνωση Καιρού Ελλάδας | Καιρός Αθήνα Θεσσαλονίκη | Ο καιρός σημερα. | Μετεωρολογικές προγνώσεις | Δελτίο Καιρού

Technical Analysis

  • Webserver
  • Ip Address
    194.63.247.211
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from weather.in.gr.

HTML Analysis

  • cache-control: private,max-age=1,stale-while-revalidate=100,stale-if-error=3600
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-cache-object-ttl: 3600.000
  • content-length: 19230
  • accept-ranges: bytes
  • date: Wed, 19 Jun 2013 00:52:37 GMT
  • age: 1892
  • connection: keep-alive
  • x-cache: HIT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for weather.in.gr

DNS Analysis


DNS servers
ns.dolnet.gr [194.63.247.134]
ns1.in.gr [195.97.55.98]
ns.in.gr [194.63.247.20]


DNS Records

Answer records
weather.in.gr A 194.63.247.211 86400s

Authority records
in.gr NS  ns1.in.gr 86400s
in.gr NS  ns.dolnet.gr 86400s
in.gr NS  ns.in.gr 86400s

Additional records
ns.in.gr A 194.63.247.20 86400s
ns.dolnet.gr A 194.63.247.134 43200s
ns1.in.gr A 195.97.55.98 86400s

IP 194.63.247.211 Analysis

  • Country Code
    GR
  • Country Code3
    GRC
  • Country Name
    Greece
  • City
    EU
  • Continent Code
    39° North
  • Latitude
    22.
  • Longitude
  • No whois ip data for 194.63.247.211

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 58 Errors
  • 61 Warnings
Ratio Text/Html
  • 0.5869021224733233
Message Error
  • Error Line 12, Column 9: 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>.

  • Warning Line 16, Column 19: character "<" is the first character of a delimiter but occurred as data
    for (var i = 0; i < elements.length; 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.
  • Warning Line 17, Column 21: character "<" is the first character of a delimiter but occurred as data
    //for (var i = 0; i < 10; 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 91, Column 81: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    ….in.gr/click?webspace=668&amp;dfl=yes"><img src="http://adman.in.gr/banner?web…

    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 91, Column 161: there is no attribute "border"
    …ace=668&amp;dfl=yes&amp;js=no" border="0" width="1" height="1" alt="" /></a><b…

    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 91, Column 204: document type does not allow element "br" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    …=668&amp;dfl=yes&amp;js=no" border="0" width="1" height="1" alt="" /></a><br />

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

    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 93, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

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

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

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

  • Error Line 109, Column 117: there is no attribute "linkindex"
    …α" href="http://www.in.gr/" linkindex="6"><img height="53" width="90" src="/Th…

    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 109, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …="/Themes/1/Default/Media/Layout/ingr-beta-logo.gif?_=1" alt="in.gr"></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 109, Column 121: start tag was here
    …ref="http://www.in.gr/" linkindex="6"><img height="53" width="90" src="/Themes…
  • Error Line 110, Column 151: required attribute "alt" not specified
    …8 "><img src="/files/1/BannerPlaceHolders/Banner728x90.gif" class="loader"><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 110, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …8 "><img src="/files/1/BannerPlaceHolders/Banner728x90.gif" class="loader"><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 110, Column 81: start tag was here
    …HeaderBanner" class="banner bnr_728 "><img src="/files/1/BannerPlaceHolders/Ba…
  • Error Line 110, Column 156: end tag for "hr" omitted, but OMITTAG NO was specified
    …8 "><img src="/files/1/BannerPlaceHolders/Banner728x90.gif" class="loader"><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 110, Column 152: start tag was here
    …8 "><img src="/files/1/BannerPlaceHolders/Banner728x90.gif" class="loader"><hr>
  • Error Line 114, Column 32: there is no attribute "target"
    <p class="freemeteo"><a target="_blank" rel="nofollow" title="freemeteo.com" hr…

    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 134, Column 167: required attribute "alt" not specified
    …edia/banner-loader.gif" class="loader"></span><form id="LoginForm" method="pos…

    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 134, Column 174: end tag for "img" omitted, but OMITTAG NO was specified
    …nner-loader.gif" class="loader"></span><form id="LoginForm" method="post" acti…

    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 134, Column 100: start tag was here
    …style="display:none; margin: 0 auto;"><img src="/Themes/1/Default/Media/banner…
  • Error Line 136, Column 216: end tag for "input" omitted, but OMITTAG NO was specified
    …-field" id="UserName" name="UserName"><span style="color: Red; display: none;"…

    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 136, Column 147: start tag was here
    …στη:</label><span class="login-field"><input type="text" class="login-field" i…
  • Error Line 136, Column 506: end tag for "input" omitted, but OMITTAG NO was specified
    …-field" id="Password" name="Password"><span style="color: Red; display: none;"…

    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 136, Column 433: start tag was here
    …σης:</label><span class="login-field"><input type="password" class="login-fiel…
  • Error Line 136, Column 813: end tag for "input" omitted, but OMITTAG NO was specified
    …').val().replace('@in.gr',''))"></span><strong><a title="Επιλέξτε εδώ για να ε…

    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 136, Column 641: start tag was here
    …pan></span><span class="login-button"><input type="submit" class="login-button…
  • Error Line 459, Column 121: ID "news-flyout" already defined
    …>Θάλασσα</span></a><div class="flyout" id="news-flyout" style="display: none;">

    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 274, Column 108: ID "news-flyout" first defined here
    …ικονομία</span></a><div class="flyout" id="news-flyout" style="display: none;">
  • Error Line 595, Column 123: ID "news-flyout" already defined
    …rong></span></span><div class="flyout" id="news-flyout" style="display: none;">

    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 274, Column 108: ID "news-flyout" first defined here
    …ικονομία</span></a><div class="flyout" id="news-flyout" style="display: none;">
  • Error Line 642, Column 151: end tag for "input" omitted, but OMITTAG NO was specified
    …ogle" title="Αναζήτηση στο Διαδίκτυο"><label for="search-google" class="search…

    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 642, Column 45: start tag was here
    …egend>Αναζήτηση στο διαδίκτυο</legend><input type="radio" id="search-google" n…
  • Error Line 644, Column 107: end tag for "input" omitted, but OMITTAG NO was specified
    … name="search-place" value="in" title="Αναζήτηση In.gr"><label for="search-in">

    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 644, Column 17: start tag was here
            </label><input type="radio" id="search-in" name="search-place" value="i…
  • Error Line 646, Column 88: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …-section" name="search-place" checked value="section"><label for="search-in-ne…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 646, Column 104: end tag for "input" omitted, but OMITTAG NO was specified
    …ction" name="search-place" checked value="section"><label for="search-in-news">

    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 646, Column 17: start tag was here
            </label><input type="radio" id="search-in-section" name="search-place" …
  • Error Line 649, Column 90: end tag for "input" omitted, but OMITTAG NO was specified
    …bindex="1" id="search-field" value=""><span class="search-button" style="paddi…

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

  • Info Line 649, Column 17: start tag was here
            </label><input type="text" accesskey="s" tabindex="1" id="search-field"…
  • Error Line 649, Column 268: end tag for "input" omitted, but OMITTAG NO was specified
    …"height:19px" title="Αναζήτηση"></span></span><a href="#DetailedSearch" class=…

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

  • Info Line 649, Column 151: start tag was here
    …ton" style="padding-bottom:1px"><span><input type="button" value="" name="sear…
  • Error Line 649, Column 437: end tag for "input" omitted, but OMITTAG NO was specified
    …//find.in.gr/?pg=1&amp;src=0&amp;qs="><input type="hidden" id="insearch" value…

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

  • Info Line 649, Column 348: start tag was here
    …etailedSearch">Αναλυτική Αναζήτηση</a><input type="hidden" id="googlesearch" v…
  • Error Line 649, Column 522: end tag for "input" omitted, but OMITTAG NO was specified
    …//find.in.gr/?pg=1&amp;src=1&amp;qs="><input type="hidden" name="cx" value="pa…

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

  • Info Line 649, Column 437: start tag was here
    …//find.in.gr/?pg=1&amp;src=0&amp;qs="><input type="hidden" id="insearch" value…
  • Error Line 649, Column 602: end tag for "input" omitted, but OMITTAG NO was specified
    …ner-pub-3451081775397713:xyj62df99ux"><input type="hidden" name="cof" value="F…

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

  • Info Line 649, Column 522: start tag was here
    …//find.in.gr/?pg=1&amp;src=1&amp;qs="><input type="hidden" name="cx" value="pa…
  • Error Line 649, Column 651: end tag for "input" omitted, but OMITTAG NO was specified
    …="hidden" name="cof" value="FORID:11"><input type="hidden" name="ie" value="IS…

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

  • Info Line 649, Column 602: start tag was here
    …ner-pub-3451081775397713:xyj62df99ux"><input type="hidden" name="cof" value="F…
  • Error Line 649, Column 701: end tag for "input" omitted, but OMITTAG NO was specified
    …"hidden" name="ie" value="ISO-8859-7"><input type="hidden" id="sectionsearch" …

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

  • Info Line 649, Column 651: start tag was here
    …="hidden" name="cof" value="FORID:11"><input type="hidden" name="ie" value="IS…
  • Error Line 649, Column 782: end tag for "input" omitted, but OMITTAG NO was specified
    …ue="http://weather.in.gr/search/?qs="><p class="hidden"><a title="Επιλέξτε εδώ…

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

  • Info Line 649, Column 701: start tag was here
    …"hidden" name="ie" value="ISO-8859-7"><input type="hidden" id="sectionsearch" …
  • Error Line 656, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …;"><img src="files/1/Fasa/Weather/weather_fasa.jpg" alt="" id="in-promo"></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 656, Column 97: start tag was here
    … 5px; text-align:center; width:100%;"><img src="files/1/Fasa/Weather/weather_f…
  • Error Line 988, Column 13: character data is not allowed here
                 

    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 989, Column 19: end tag for "select" which is not finished
              </select>

    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.

  • Warning Line 1029, Column 82: cannot generate system identifier for general entity "lat"
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

    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 1029, Column 82: general entity "lat" not defined and no default entity
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

    This is usually a cascading error caused by 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 1029, Column 85: reference not terminated by REFC delimiter
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

    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 1029, Column 85: reference to entity "lat" for which no system identifier could be generated
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

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

  • Info Line 1029, Column 81: entity was defined here
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;
  • Warning Line 1029, Column 102: cannot generate system identifier for general entity "long"
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

    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 1029, Column 102: general entity "long" not defined and no default entity
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

    This is usually a cascading error caused by 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 1029, Column 106: reference not terminated by REFC delimiter
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

    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 1029, Column 106: reference to entity "long" for which no system identifier could be generated
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;

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

  • Info Line 1029, Column 101: entity was defined here
    …ref= ResultsUrl + "?radius="+ radius +"&lat="+ lat.value +"&long="+ long.value;
  • Error Line 1067, Column 124: required attribute "alt" not specified
    … "><img src="/Themes/1/Default/Media/Layout/banner_150.gif" class="loader"><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 1067, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    … "><img src="/Themes/1/Default/Media/Layout/banner_150.gif" class="loader"><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 1067, Column 53: start tag was here
    …"LeftBanner1" class="banner bnr_150 "><img src="/Themes/1/Default/Media/Layout…
  • Error Line 1067, Column 129: end tag for "hr" omitted, but OMITTAG NO was specified
    … "><img src="/Themes/1/Default/Media/Layout/banner_150.gif" class="loader"><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 1067, Column 125: start tag was here
    … "><img src="/Themes/1/Default/Media/Layout/banner_150.gif" class="loader"><hr>
  • Error Line 1076, Column 45: there is no attribute "scrolling"
    …d="in-weather-main"><iframe scrolling="no" height="425" frameborder="0" width=…

    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 1076, Column 57: there is no attribute "height"
    …r-main"><iframe scrolling="no" height="425" frameborder="0" width="520" allowt…

    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 1076, Column 75: there is no attribute "frameborder"
    …rolling="no" height="425" frameborder="0" width="520" allowtransparency="true"…

    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 1076, Column 85: there is no attribute "width"
    …o" height="425" frameborder="0" width="520" allowtransparency="true" marginwid…

    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 1076, Column 109: there is no attribute "allowtransparency"
    …der="0" width="520" allowtransparency="true" marginwidth="0" marginheight="0" …

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

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

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

  • Error Line 1076, Column 128: there is no attribute "marginwidth"
    … allowtransparency="true" marginwidth="0" marginheight="0" hspace="0" vspace="…

    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 1076, Column 145: there is no attribute "marginheight"
    …y="true" marginwidth="0" marginheight="0" hspace="0" vspace="0" src="http://we…

    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 1076, Column 156: there is no attribute "hspace"
    …rginwidth="0" marginheight="0" hspace="0" vspace="0" src="http://weather.in.gr…

    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 1076, Column 167: there is no attribute "vspace"
    …0" marginheight="0" hspace="0" vspace="0" src="http://weather.in.gr/kairosifra…

    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 1076, Column 175: there is no attribute "src"
    …nheight="0" hspace="0" vspace="0" src="http://weather.in.gr/kairosiframemap"><…

    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 1076, Column 213: element "iframe" undefined
    …="0" hspace="0" vspace="0" src="http://weather.in.gr/kairosiframemap"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1078, Column 47: there is no attribute "name"
    …rsion="1.0" encoding="utf-8"?><a name="startMap" xmlns:dt="urn:schemas-microso…

    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 1081, Column 143: required attribute "alt" not specified
    …oshadow/30.png" title="Πιθανή βροχή" /></td><td class="description">Πιθανή βρο…

    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 1081, Column 288: required attribute "alt" not specified
    …s/1/Default/Media/Weather/Icons/cold.gif" title="10 °C - 15 °C" /><span>10 °C -

    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 1083, Column 151: required attribute "alt" not specified
    …ather/Icons/weak_NW.gif" title="ΒΔ&#xA;           &#xA;          3 μποφόρ" />ΒΔ

    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 1086, Column 143: required attribute "alt" not specified
    …oshadow/30.png" title="Πιθανή βροχή" /></td><td class="description">Πιθανή βρο…

    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 1086, Column 287: required attribute "alt" not specified
    …mes/1/Default/Media/Weather/Icons/cold.gif" title="9 °C - 12 °C" /><span>9 °C -

    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 1088, Column 151: required attribute "alt" not specified
    …ather/Icons/weak_NE.gif" title="ΒΑ&#xA;           &#xA;          3 μποφόρ" />ΒΑ

    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 1091, Column 142: required attribute "alt" not specified
    …Noshadow/2.png" title="Λίγα σύννεφα" /></td><td class="description">Λίγα σύννε…

    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 1091, Column 286: required attribute "alt" not specified
    …mes/1/Default/Media/Weather/Icons/cold.gif" title="7 °C - 13 °C" /><span>7 °C -

    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 1093, Column 149: required attribute "alt" not specified
    …/Weather/Icons/weak_N.gif" title="Β&#xA;           &#xA;          3 μποφόρ" />Β

    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 1096, Column 138: required attribute "alt" not specified
    …/pngNoshadow/3.png" title="Συννεφιά" /></td><td class="description">Συννεφιά</…

    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 1096, Column 278: required attribute "alt" not specified
    …mes/1/Default/Media/Weather/Icons/cold.gif" title="9 °C - 14 °C" /><span>9 °C -

    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 1098, Column 151: required attribute "alt" not specified
    …ather/Icons/weak_SE.gif" title="ΝΑ&#xA;           &#xA;          2 μποφόρ" />ΝΑ

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

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

  • Error Line 1101, Column 144: required attribute "alt" not specified
    …shadow/31.png" title="Ασθενής βροχή" /></td><td class="description">Ασθενής βρ…

    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 1101, Column 290: required attribute "alt" not specified
    …s/1/Default/Media/Weather/Icons/cold.gif" title="10 °C - 12 °C" /><span>10 °C -

    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 1103, Column 153: required attribute "alt" not specified
    …her/Icons/medium_NE.gif" title="ΒΑ&#xA;           &#xA;          5 μποφόρ" />ΒΑ

    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 1106, Column 142: required attribute "alt" not specified
    …Noshadow/2.png" title="Λίγα σύννεφα" /></td><td class="description">Λίγα σύννε…

    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 1106, Column 286: required attribute "alt" not specified
    …mes/1/Default/Media/Weather/Icons/cold.gif" title="8 °C - 14 °C" /><span>8 °C -

    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 1108, Column 151: required attribute "alt" not specified
    …ather/Icons/weak_NW.gif" title="ΒΔ&#xA;           &#xA;          3 μποφόρ" />ΒΔ

    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 1116, Column 85: there is no attribute "onClick"
    …hemes/1/Default/Media/Weather/images/weather_vimaFM.png" onClick="openWin()" />

    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 9: 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 1130, Column 130: end tag for "img" omitted, but OMITTAG NO was specified
    …gnettes/weather_title_videothiki.png"><ins datetime="2013-02-27T17:34:18">27/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 1130, Column 31: start tag was here
      <div class="title clearfix"><img height="11" width="65" alt="Βιντεοθήκη" src=…
  • Error Line 1176, Column 119: required attribute "alt" not specified
    … "><img src="/files/1/BannerPlaceHolders/Banner300x250.gif" class="loader"><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 1176, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    … "><img src="/files/1/BannerPlaceHolders/Banner300x250.gif" class="loader"><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 1176, Column 48: start tag was here
    …RightBanner1" class="banner bnr_300 "><img src="/files/1/BannerPlaceHolders/Ba…
  • Error Line 1176, Column 124: end tag for "hr" omitted, but OMITTAG NO was specified
    … "><img src="/files/1/BannerPlaceHolders/Banner300x250.gif" class="loader"><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 1176, Column 120: start tag was here
    … "><img src="/files/1/BannerPlaceHolders/Banner300x250.gif" class="loader"><hr>
  • Error Line 1183, Column 150: end tag for "img" omitted, but OMITTAG NO was specified
    …1/Vignettes/weather_title_agrotourismos.png" alt="in.gr - Αγροτουρισμός"></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 1183, Column 31: start tag was here
      <div class="title clearfix"><img height="13" width="126" src="/Files/1/Vignet…
  • Error Line 1188, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …83A1A7E10A3692D7E74B0DDD6858A.jpg"></a><a href="#24854" title="Βόνιτσα" class=…

    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 1188, Column 96: start tag was here
    …"Εκδρομή στην Πύλο" class="AlbumLink"><img alt="φωτοάλμπουμ:Εκδρομή στην Πύλο"…
  • Error Line 1188, Column 394: end tag for "img" omitted, but OMITTAG NO was specified
    …C86B498043F07BCBF613AA92E5F31.jpg"></a><a href="#24739" title="Οργάνωση Γη-Κέν…

    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 1188, Column 276: start tag was here
    …54" title="Βόνιτσα" class="AlbumLink"><img alt="φωτοάλμπουμ:Βόνιτσα" width="71…
  • Error Line 1188, Column 626: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://static.in.gr/webstatic/9FF42E1518CB8CD95C04CA4B6CCCF02A.jpg"></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 1188, Column 477: start tag was here
    …ης Γης-Λαχανόκηπος" class="AlbumLink"><img alt="φωτοάλμπουμ:Οργάνωση Γη-Κέντρο…
  • Warning Line 1269, Column 40: character "&" is the first character of a delimiter but occurred as data
          Result += i + "=" + values[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.
  • Warning Line 1273, Column 40: character "&" is the first character of a delimiter but occurred as data
          Result += i + "=" + values[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 1290, Column 81: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    ….in.gr/click?webspace=597&amp;dfl=yes"><img src="http://adman.in.gr/banner?web…

    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 1290, Column 207: document type does not allow element "br" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    …7&amp;dfl=yes&amp;js=no" border="0" width="728" height="90" alt="" /></a><br />

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

    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 1307, Column 81: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    ….in.gr/click?webspace=598&amp;dfl=yes"><img src="http://adman.in.gr/banner?web…

    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 1307, Column 208: document type does not allow element "br" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    …&amp;dfl=yes&amp;js=no" border="0" width="150" height="300" alt="" /></a><br />

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

    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 1324, Column 81: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    ….in.gr/click?webspace=599&amp;dfl=yes"><img src="http://adman.in.gr/banner?web…

    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 1324, Column 208: document type does not allow element "br" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    …&amp;dfl=yes&amp;js=no" border="0" width="300" height="250" alt="" /></a><br />

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

    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 1341, Column 81: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    ….in.gr/click?webspace=600&amp;dfl=yes"><img src="http://adman.in.gr/banner?web…

    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 1341, Column 207: document type does not allow element "br" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    …0&amp;dfl=yes&amp;js=no" border="0" width="468" height="60" alt="" /></a><br />

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

    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 1356, Column 53: required attribute "type" not specified
                </script><div id="BMIBanner3589"><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 1365, Column 67: document type does not allow element "div" here
    …="promoTitle" style="text-align:left;"><a href="https://www.google.com/adsense…

    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 1366, Column 27: character "<" is the first character of a delimiter but occurred as data
                for (i = 0; i < google_ads.length; 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 1367, Column 43: document type does not allow element "div" here
                    s += '<div class="manyAds">' +

    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 1369, Column 114: an attribute specification must start with a name or name token
    …ef="' + google_ads[i].url + ' "onmouseout="window.status=\'\';return true;" ' +

    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 1378, Column 90: an attribute specification must start with a name or name token
    …ef="' + google_ads[i].url + ' "onmouseout="window.status=\'\';return true;" ' +

    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 1417, Column 33: there is no attribute "type"
              </script><Script type="text/javascript">

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

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

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

  • Error Line 1417, Column 50: element "Script" undefined
              </script><Script type="text/javascript">

    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 1436, Column 70: cannot generate system identifier for general entity "cg"
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

    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 1436, Column 70: general entity "cg" not defined and no default entity
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

    This is usually a cascading error caused by 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 1436, Column 72: reference not terminated by REFC delimiter
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Warning Line 1436, Column 72: reference to external entity in attribute value
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Error Line 1436, Column 72: reference to entity "cg" for which no system identifier could be generated
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Info Line 1436, Column 69: entity was defined here
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"
  • Warning Line 1436, Column 75: cannot generate system identifier for general entity "cc"
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

    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 1436, Column 75: general entity "cc" not defined and no default entity
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

    This is usually a cascading error caused by 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 1436, Column 77: reference not terminated by REFC delimiter
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Warning Line 1436, Column 77: reference to external entity in attribute value
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Error Line 1436, Column 77: reference to entity "cc" for which no system identifier could be generated
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Info Line 1436, Column 74: entity was defined here
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"
  • Warning Line 1436, Column 80: cannot generate system identifier for general entity "ts"
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

    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 1436, Column 80: general entity "ts" not defined and no default entity
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

    This is usually a cascading error caused by 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 1436, Column 82: reference not terminated by REFC delimiter
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Warning Line 1436, Column 82: reference to external entity in attribute value
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Error Line 1436, Column 82: reference to entity "ts" for which no system identifier could be generated
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"

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

  • Info Line 1436, Column 79: entity was defined here
    …<img src="//secure-uk.imrworldwide.com/cgi-bin/m?ci=ingr&cg=0&cc=1&ts=noscript"
  • Warning Line 986, Column 19: reference to non-existent ID "weather-city"
          <label for="weather-city">Μεγαλύτερες πόλεις του Νομού:</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 1052, Column 21: reference to non-existent ID "weather-radius"
            <label for="weather-radius">αναζήτηση σε ακτίνα</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 930, Column 19: reference to non-existent ID "weather-area"
          <label for="weather-area">Νομός ή περιοχή:</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 646, Column 116: reference to non-existent ID "search-in-news"
    …ction" name="search-place" checked value="section"><label for="search-in-news">

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 45.500 visits
Daily Visitor