e-sompes.gr

Μεγάλη ποικιλία σε ΤΖΑΚΙΑ & ΣΟΜΠΕΣ - TZAKIA ΛΕΒΗΤΕΣ - ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ - tzakia αερόθερμα ξυλου - τζακια kalorifer - ΚΑΛΟΡΙΦΕΡ ΤΖΑΚΙ - energeiaka tzakia - ΘΕΡΜΑΣΤΡΕΣ ΠΕΛΛΕΤ - ΞΥΛΟΛΕΒΗΤΕΣ tzaki - ΥΔΡΑΥΛΙΚΟ ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 11:07:47  (update).

Overview Info

  • Domain Name
    e-sompes.gr
  • Favicon
  • Alexa Rank
    #3315071
  • Google Page Rank
    PR 2
  • Ip Address
    176.9.145.69
  • Page Size
    20.8 KB
  • Images
    2 GIF, 10 JPG, 7 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    e-sompes. :: ... Ενεργειακά τζάκια - εστίες - σόμπες ξύλου - Λέβητες - tzakia ΑΕΡΟΘΕΡΜΑ - ΚΑΛΟΡΙΦΕΡ ΤΖΑΚΙ - energeiaka tzakia - ΘΕΡΜΑΣΤΡΕΣ ΠΕΛΛΕΤ - ΞΥΛΟΛΕΒΗΤΕΣ - kalorifer tzaki - ΥΔΡΑΥΛΙΚΟ ΝΕΡΟΥ - ΤΖΑΚΙ ΚΑΛΟΡΙΦΕΡ ΘΕΣΣΑΛΟΝΙΚΗ
  • Meta Keyword
    ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ,ΣΟΜΠΕΣ,ΞΥΛΟΥ,kalorifer,ξυλολεβητες, καλοριφερ,αεροθερμα,λεβητες,ξυλοσομπες,υδραυλικο, τζακι,νερου,Πελλετ,Θεσσαλονικη, energeiaka tzakia,ενεργειακες,θερμαστρες,pellet,
  • Meta Description
    Μεγάλη ποικιλία σε ΤΖΑΚΙΑ & ΣΟΜΠΕΣ - TZAKIA ΛΕΒΗΤΕΣ - ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ - tzakia αερόθερμα ξυλου - τζακια kalorifer - ΚΑΛΟΡΙΦΕΡ ΤΖΑΚΙ - energeiaka tzakia - ΘΕΡΜΑΣΤΡΕΣ ΠΕΛΛΕΤ - ΞΥΛΟΛΕΒΗΤΕΣ tzaki - ΥΔΡΑΥΛΙΚΟ ΝΕΡΟΥ - ΤΖΑΚΙ ΚΑΛΟΡΙΦΕΡ ΘΕΣΣΑΛΟΝΙΚΗ

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    176.9.145.69
  • Domain Age
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from e-sompes.gr.

HTML Analysis

  • server: nginx
  • date: Tue, 17 Sep 2013 23:07:44 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for e-sompes.gr

DNS Analysis


DNS servers
ns1.grplus.com [176.9.145.69]
ns2.grplus.com [176.9.145.69]


DNS Records

Answer records
e-sompes.gr MX
preference: 0
exchange: e-sompes.gr
14400s
e-sompes.gr SOA
server: ns1.grplushost.info
email: info@infocus.gr
serial: 2012041401
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
e-sompes.gr NS  ns1.grplushost.info 86400s
e-sompes.gr NS  ns2.grplushost.info 86400s
e-sompes.gr A 176.9.145.69 14400s

Authority records

Additional records
e-sompes.gr A 176.9.145.69 14400s
ns1.grplushost.info A 176.9.145.69 14400s
ns2.grplushost.info A 176.9.145.69 14400s

IP 176.9.145.69 Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 92 Errors
  • 54 Warnings
Ratio Text/Html
  • 0.6312941176470588
Message Error
  • Error Line 2, Column 1: no document type declaration; will parse without validation
    <head>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 3, Column 75: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1253" />

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

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

  • Warning Line 5, Column 71: NET-enabling start-tag requires SHORTTAG YES
    <meta name="description" content="Μεγάλη ποικιλία σε ΤΖΑΚΙΑ & ΣΟΜΠΕΣ" />

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

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

  • Warning Line 10, Column 39: NET-enabling start-tag requires SHORTTAG YES
     Σόμπες Λέβητες,Τιμές,τζακια pellet," />

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

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

  • Warning Line 13, Column 84: NET-enabling start-tag requires SHORTTAG YES
    …href="skins/Classic/styleSheets/layout.css" rel="stylesheet" type="text/css" />

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

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

  • Warning Line 14, Column 83: NET-enabling start-tag requires SHORTTAG YES
    … href="skins/Classic/styleSheets/style.css" rel="stylesheet" type="text/css" />

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

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

  • Warning Line 15, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …nk rel="stylesheet" type="text/css" href="skins/Classic/styleSheets/fad.css" />

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

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

  • Warning Line 20, Column 72: NET-enabling start-tag requires SHORTTAG YES
    <LINK REL="SHORTCUT ICON" HREF="skins/Classic/styleImages/favicon.ico" />

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

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

  • Warning Line 23, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …"stylesheet" type="text/css" href="skins/Classic/styleSheets/validation.css" />

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

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

  • Warning Line 27, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …k href="skins/Classic/styleSheets/menu.css" rel="stylesheet" type="text/css" />

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

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

  • Warning Line 29, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <link rel="stylesheet" href="css/lightbox.css" type="text/css" media="screen" />

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

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

  • Error Line 91, Column 100: document type does not allow element "BODY" here
    …e" text="#000000" leftmargin="0" marginwidth="0" rightmargin="0" topmargin="0">

    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 96, Column 149: NET-enabling start-tag requires SHORTTAG YES
    …php?hit=1"><img src="skins/Classic/styleImages/logo.png" border="0" /></a></td>

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

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

  • Warning Line 118, Column 150: NET-enabling start-tag requires SHORTTAG YES
    …ns/Classic/styleImages/trans.gif" width="35" height="25" border="0" /></a></td>

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

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

  • Warning Line 120, Column 73: cannot generate system identifier for general entity "amp"
    …op:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtSe…

    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 120, Column 73: general entity "amp" not defined and no default entity
    …op:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtSe…

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

  • Error Line 120, Column 76: reference to entity "amp" for which no system identifier could be generated
    …5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtSessi…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 120, Column 157: cannot generate system identifier for general entity "nbsp"
    …>Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?act…

    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 120, Column 157: general entity "nbsp" not defined and no default entity
    …>Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?act…

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

  • Error Line 120, Column 161: reference to entity "nbsp" for which no system identifier could be generated
    …οδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?act=reg…

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Error Line 120, Column 168: reference to entity "nbsp" for which no system identifier could be generated
    …><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?act=reg&amp;re…

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Error Line 120, Column 205: reference to entity "amp" for which no system identifier could be generated
    …p;</span><a href="cart.php?act=reg&amp;redir=L2luZGV4LnBocA==" class="txtSessi…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 121, Column 62: reference to entity "nbsp" for which no system identifier could be generated
            <td width="290px" align="right" valign="middle">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Warning Line 126, Column 106: NET-enabling start-tag requires SHORTTAG YES
    …="right" valign="middle"><img src="skins/Classic/styleImages/flags.png" /></td>

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

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

  • Error Line 128, Column 39: reference to entity "nbsp" for which no system identifier could be generated
      <tr> <td height="38" width="5">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Error Line 131, Column 45: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=1">ΕΤΑΙΡΙΑ</a></li> </ul> <ul> <l…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 131, Column 121: reference to entity "amp" for which no system identifier could be generated
    …</li> </ul> <ul> <li><a href="index.php?act=viewCat&amp;catId=18">ΠΡΟΪΟΝΤΑ</a> 

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 132, Column 46: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=27">ΣΟΜΠΕΣ ΞΥΛΟΥ ΑΠΟ ΑΤΣΑΛΙ ΕΝΕΡΓ…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 46: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=39">THORMA  ΣΛΟΒΑΚΙΑΣ</a></li> <l…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 122: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=40">SKLADOVA  ΒΟΥΛΓΑΡΙΑΣ</a></li>…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 201: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=41">PRITY  ΒΟΥΛΓΑΡΙΑΣ</a></li> <l…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 277: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=42">TIM SISTEM  ΣΕΡΒΙΑΣ</a></li> …

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 366: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=23">ΣΟΜΠΕΣ & ΑΕΡΟΘΕΡΜΑ ΠΕΤΡΕΛΑΙΟΥ…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 454: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=24">ΤΖΑΚΙΑ ΕΝΕΡΓΕΙΑΚΑ</a></li> <l…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 530: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=25">ΣΟΜΠΕΣ ΞΥΛΟΥ ΑΠΟ ΜΑΝΤΕΜΙ</a><…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 613: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=26">ΕΝΕΡΓΕΙΑΚΕΣ ΣΟΜΠΕΣ ΞΥΛΟΥ LA N…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 707: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=28">ΕΝΕΡΓΕΙΑΚΕΣ ΚΟΥΖΙΝΕΣ ΞΥΛΟΥ LA…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 803: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=29">ΕΝΕΡΓΕΙΑΚΕΣ ΚΑΣΕΤΕΣ ΞΥΛΟΥ & P…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 133, Column 896: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=30">ΕΝΕΡΓΕΙΑΚΕΣ ΘΕΡΜΑΣΤΡΕΣ & ΚΟΥΖ…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 134, Column 46: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=54">BOILER - ΘΕΡΜΟΣΙΦΩΝΕΣ</a></li…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 134, Column 137: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=31">ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ ΛΕΒΗΤΕΣ</a>…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 135, Column 46: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=43">KYΚΛΟΦΟΡΗΤΕΣ</a></li> <li><a …

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 135, Column 117: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=45">ΔΟΧΕΙΑ ΑΔΡΑΝΕΙΑΣ  BUFFER</a><…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 135, Column 211: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=32">ΛΕΒΗΤΕΣ ΞΥΛΟΥ & ΠΕΛΛΕΤ</a></l…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 135, Column 292: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=33">ΕΣΤΙΕΣ ΤΖΑΚΙΟΥ</a></li> <li><…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 135, Column 365: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=34">ΣΟΜΠΕΣ ΞΥΛΟΥ ΚΑΛΟΡΙΦΕΡ-Boiler…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 46: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=46">ΚΙΤ τριοδης βανας</a></li> <l…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 122: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=47">Ups</a></li> </ul></li> <li><…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 195: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=35">ΣΟΜΠΕΣ ΞΥΛΟΥ  ΕΜΑΓΙΕ</a></li>…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 274: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=36">ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ ΜΕ Boiler</…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 360: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=37">ΣΟΜΠΕΣ ΜΕ ΦΟΥΡΝΟ PRITY ΕΝΕΡΓΕ…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 453: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=55">ΚΑΥΣΤΗΡΕΣ ΠΕΛΛΕΤ</a></li> <li…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 528: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=51">ΚΑΠΝΟΔΟΧΟΙ- ΜΠΟΥΡΙΑ</a></li> …

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 606: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=53">ΗΛΕΚΤΡΙΚΑ ΘΕΡΜΑΝΤΙΚΑ</a></li>…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 685: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=21">ΣΟΜΠΕΣ PELLET & IDRO</a></li>…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 786: reference to entity "amp" for which no system identifier could be generated
    …<li><a href="index.php?act=viewCat&amp;catId=19">ΕΞΥΠΗΡΕΤΗΣΗ ΠΕΛΑΤΩΝ</a></li> …

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 136, Column 875: reference to entity "amp" for which no system identifier could be generated
    …ul> <li><a href="index.php?act=viewCat&amp;catId=20">ΕΠΙΚΟΙΝΩΝΙΑ</a></li> </ul>

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 141, Column 37: reference to entity "nbsp" for which no system identifier could be generated
        <td height="38" width="15">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Error Line 151, Column 43: reference to entity "nbsp" for which no system identifier could be generated
            <td height="5px" colspan="3">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Error Line 175, Column 43: reference to entity "nbsp" for which no system identifier could be generated
            <td height="5px" colspan="3">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Error Line 177, Column 17: end tag for element "TD" which is not open
        </table></td>

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

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

  • Error Line 178, Column 7: end tag for element "TR" which is not open
      </tr>

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

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

  • Warning Line 182, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …ter" valign="bottom"><img src="skins/Classic/styleImages/top_white.png" /></td>

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

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

  • Error Line 192, Column 47: reference to entity "nbsp" for which no system identifier could be generated
    …    <td valign="top" width="227">&nbsp;<img alt="" src="/images/uploads/order.…

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Warning Line 192, Column 92: NET-enabling start-tag requires SHORTTAG YES
    …ign="top" width="227">&nbsp;<img alt="" src="/images/uploads/order.jpg" /></td>

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

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

  • Error Line 193, Column 22: reference to entity "nbsp" for which no system identifier could be generated
                <td>&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Warning Line 198, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 199, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=24"><img title="ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 199, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …ΚΙΑ" border="0" src="../../../../images/uploads/energiaka_tzakia1.jpg" /><br />

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

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

  • Warning Line 199, Column 228: NET-enabling start-tag requires SHORTTAG YES
    …ΚΙΑ" border="0" src="../../../../images/uploads/energiaka_tzakia1.jpg" /><br />

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

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

  • Warning Line 201, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 202, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=26"><img title="ΕΝΕΡΓΕΙΑΚΕΣ ΣΟΜΠΕ…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 202, Column 260: NET-enabling start-tag requires SHORTTAG YES
    …der="0" src="../../../../images/uploads/energiakes_sompes_nortika.jpg" /><br />

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

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

  • Warning Line 202, Column 266: NET-enabling start-tag requires SHORTTAG YES
    …der="0" src="../../../../images/uploads/energiakes_sompes_nortika.jpg" /><br />

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

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

  • Warning Line 203, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …                    <span style="color: rgb(0,0,0)"><b>ΕΝΕΡΓΕΙΑΚΕΣ ΣΟΜΠΕΣ<br />

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

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

  • Warning Line 205, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 206, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=29"><img title="ΚΑΣΣΕΤΕΣ ΞΥΛΟΥ &a…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 206, Column 132: reference to entity "amp" for which no system identifier could be generated
    …Id=29"><img title="ΚΑΣΣΕΤΕΣ ΞΥΛΟΥ &amp; PELLET" alt="ΚΑΣΣΕΤΕΣ ΞΥΛΟΥ &amp; PELL…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 206, Column 166: reference to entity "amp" for which no system identifier could be generated
    …&amp; PELLET" alt="ΚΑΣΣΕΤΕΣ ΞΥΛΟΥ &amp; PELLET" border="0" src="../../../../im…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 206, Column 233: NET-enabling start-tag requires SHORTTAG YES
    …&amp; PELLET" border="0" src="../../../../images/uploads/kassetes.jpg" /><br />

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

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

  • Warning Line 206, Column 239: NET-enabling start-tag requires SHORTTAG YES
    …&amp; PELLET" border="0" src="../../../../images/uploads/kassetes.jpg" /><br />

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

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

  • Error Line 207, Column 90: reference to entity "amp" for which no system identifier could be generated
    …olor: rgb(0,0,0)"><b>ΕΝΕΡΓΕΙΑΚΕΣ ΚΑΣΕΤΕΣ ΞΥΛΟΥ &amp; PELLET</b></span></a></td>

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 210, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 211, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=31"><img title="ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 211, Column 245: NET-enabling start-tag requires SHORTTAG YES
    …rder="0" src="../../../../images/uploads/energiaka_tzakia_levites.jpg" /><br />

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

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

  • Warning Line 211, Column 251: NET-enabling start-tag requires SHORTTAG YES
    …rder="0" src="../../../../images/uploads/energiaka_tzakia_levites.jpg" /><br />

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

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

  • Warning Line 213, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 214, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=32"><img title="ΛΕΒΗΤΕΣ ΞΥΛΟΥ &am…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 214, Column 131: reference to entity "amp" for which no system identifier could be generated
    …tId=32"><img title="ΛΕΒΗΤΕΣ ΞΥΛΟΥ &amp; ΠΕΛΛΕΤ" alt="ΛΕΒΗΤΕΣ ΞΥΛΟΥ &amp; ΠΕΛΛΕ…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 214, Column 164: reference to entity "amp" for which no system identifier could be generated
    … &amp; ΠΕΛΛΕΤ" alt="ΛΕΒΗΤΕΣ ΞΥΛΟΥ &amp; ΠΕΛΛΕΤ" border="0" src="../../../../im…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 214, Column 242: NET-enabling start-tag requires SHORTTAG YES
    …Τ" border="0" src="../../../../images/uploads/levites_xilu_pellet.jpg" /><br />

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

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

  • Warning Line 214, Column 248: NET-enabling start-tag requires SHORTTAG YES
    …Τ" border="0" src="../../../../images/uploads/levites_xilu_pellet.jpg" /><br />

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

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

  • Error Line 215, Column 78: reference to entity "amp" for which no system identifier could be generated
    …pan style="color: rgb(0,0,0)"><b>ΛΕΒΗΤΕΣ ΞΥΛΟΥ &amp; ΠΕΛΛΕΤ</b></span></a></td>

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 216, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 217, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=34"><img title="ΣΟΜΠΕΣ ΞΥΛΟΥ ΚΑΛΟ…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 217, Column 235: NET-enabling start-tag requires SHORTTAG YES
    …" border="0" src="../../../../images/uploads/somes_xilu_kalorifer.jpg" /><br />

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

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

  • Warning Line 217, Column 241: NET-enabling start-tag requires SHORTTAG YES
    …" border="0" src="../../../../images/uploads/somes_xilu_kalorifer.jpg" /><br />

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

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

  • Warning Line 221, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 222, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=36"><img title="ΕΝΕΡΓΕΙΑΚΑ ΤΖΑΚΙΑ…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 222, Column 251: NET-enabling start-tag requires SHORTTAG YES
    …er="0" src="../../../../images/uploads/energiaka_tzakia_me_boiler.jpg" /><br />

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

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

  • Warning Line 222, Column 257: NET-enabling start-tag requires SHORTTAG YES
    …er="0" src="../../../../images/uploads/energiaka_tzakia_me_boiler.jpg" /><br />

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

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

  • Warning Line 224, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 225, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=37"><img title="ΣΟΜΠΕΣ ΜΕ ΦΟΥΡΝΟ …

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 225, Column 236: NET-enabling start-tag requires SHORTTAG YES
    … border="0" src="../../../../images/uploads/sompes_me_furno_prity.jpg" /><br />

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

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

  • Warning Line 225, Column 242: NET-enabling start-tag requires SHORTTAG YES
    … border="0" src="../../../../images/uploads/sompes_me_furno_prity.jpg" /><br />

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

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

  • Warning Line 227, Column 48: NET-enabling start-tag requires SHORTTAG YES
                            <td align="center"><br />

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

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

  • Error Line 228, Column 90: reference to entity "amp" for which no system identifier could be generated
    …"../../../../index.php?act=viewCat&amp;catId=21"><img title="ΣΟΜΠΕΣ PELLET &am…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 228, Column 131: reference to entity "amp" for which no system identifier could be generated
    …tId=21"><img title="ΣΟΜΠΕΣ PELLET &amp; IDRO" alt="ΣΟΜΠΕΣ PELLET &amp; IDRO" b…

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

  • Info Line 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 228, Column 162: reference to entity "amp" for which no system identifier could be generated
    …ET &amp; IDRO" alt="ΣΟΜΠΕΣ PELLET &amp; IDRO" border="0" src="../../../../imag…

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Error Line 228, Column 231: reference to entity "amp" for which no system identifier could be generated
    …rder="0" src="../../../../images/uploads/sompes_pellet_&amp;_idro.jpg" /><br />

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 228, Column 243: NET-enabling start-tag requires SHORTTAG YES
    …rder="0" src="../../../../images/uploads/sompes_pellet_&amp;_idro.jpg" /><br />

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

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

  • Warning Line 228, Column 249: NET-enabling start-tag requires SHORTTAG YES
    …rder="0" src="../../../../images/uploads/sompes_pellet_&amp;_idro.jpg" /><br />

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

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

  • Error Line 229, Column 78: reference to entity "amp" for which no system identifier could be generated
    …<span style="color: rgb(0,0,0)"><b>ΣΟΜΠΕΣ PELLET &amp; IDRO</b></span></a></td>

    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 120, Column 72: entity was defined here
    …top:5px;"><a href="index.php?act=login&amp;redir=L2luZGV4LnBocA==" class="txtS…
  • Warning Line 253, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …ter" valign="top"><img src="skins/Classic/styleImages/bottom_white.png" /></td>

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

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

  • Error Line 256, Column 31: reference to entity "nbsp" for which no system identifier could be generated
            <td height="9px">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Warning Line 261, Column 294: NET-enabling start-tag requires SHORTTAG YES
    …/styleImages/facebook.png" border="0" /></a><img src="skins/Classic/styleImage…

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

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

  • Warning Line 261, Column 349: NET-enabling start-tag requires SHORTTAG YES
    ….png" border="0" /></a><img src="skins/Classic/styleImages/tweeter.png" /></td>

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

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

  • Error Line 262, Column 36: reference to entity "nbsp" for which no system identifier could be generated
                <td width="398px">&nbsp;</td>

    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 120, Column 156: entity was defined here
    …">Είσοδος</a><span class="txtSession">&nbsp;|&nbsp;</span><a href="cart.php?ac…
  • Warning Line 263, Column 149: NET-enabling start-tag requires SHORTTAG YES
    …=1"><img src="skins/Classic/styleImages/footer_logo.png" border="0" /></a></td>

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

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

  • Warning Line 270, Column 9: NET-enabling start-tag requires SHORTTAG YES
        <br />

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

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

  • Warning Line 271, Column 41: cannot generate system identifier for general entity "copy"
    …  <span class="textsmall1">Copyright &copy; 2011 -- <a href="http://www.infocu…

    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 271, Column 41: general entity "copy" not defined and no default entity
    …  <span class="textsmall1">Copyright &copy; 2011 -- <a href="http://www.infocu…

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

  • Error Line 271, Column 45: reference to entity "copy" for which no system identifier could be generated
    …pan class="textsmall1">Copyright &copy; 2011 -- <a href="http://www.infocus.gr…

    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 271, Column 40: entity was defined here
    …   <span class="textsmall1">Copyright &copy; 2011 -- <a href="http://www.infoc…
  • Warning Line 272, Column 168: NET-enabling start-tag requires SHORTTAG YES
    …shop" ><b>infocus</b></a><a href="" class="txtCopyright"></a></span><br /></td>

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

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

  • Error Line 274, Column 8: end tag for element "TABLE" which is not open
    </table>

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

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

Visitor Analysis

Daily Visitor
  • 25 visits

In Page Analysis