Ελληνική εταιρεία ενημέρωσης γονέων. Forum | υγεία & ασφάλεια | διατροφή | ψυχολογία | δραστηριότητες | ειδήσεις ...

parents.gr
  • Domain Name
    parents.gr
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #42209
  • Page Size
    54.6 KB
  • Ip Address
    78.46.77.162
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    26 GIF, 13 JPG, 6 PNG

Website Meta Analysis

  • Title
    Parents.gr - Ελληνική Εταιρία Ενημέρωσης Γονέων
  • Meta Keyword
  • Meta Description
    Ελληνική εταιρεία ενημέρωσης γονέων. Forum | υγεία & ασφάλεια | διατροφή | ψυχολογία | δραστηριότητες | ειδήσεις

Technical Analysis

  • Webserver
    Apache/2.2
  • Ip Address
    78.46.77.162
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 13 Feb 2013 20:51:28 GMT
  • server: Apache/2.2
  • x-powered-by: PHP/5.3.5
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 7936
  • connection: close
  • content-type: text/html; charset="iso-8859-7"
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for parents.gr

DNS Analysis


DNS servers
h2.velocityfarm.com [78.47.182.92]
h1.velocityfarm.com [78.46.77.162]


DNS Records

Answer records
parents.gr SOA
server: h1.velocityfarm.com
email: noc@velocityfarm.com
serial: 2012041302
refresh: 3600
retry: 300
expire: 86400
minimum ttl: 3600
300s
parents.gr NS  h2.velocityfarm.com 300s
parents.gr NS  h1.velocityfarm.com 300s
parents.gr MX
preference: 1
exchange: hyperion.nss.gr
300s
parents.gr A 78.46.77.162 300s

Authority records

Additional records
h1.velocityfarm.com A 78.46.77.162 300s
h2.velocityfarm.com A 78.47.182.92 300s

IP 78.46.77.162 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 78.46.77.162

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 112 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.5018596666905085
Message Error
  • Error Line 14, Column 20: there is no attribute "BOTTOMMARGIN"
    <body bottomMargin=0 leftMargin=0  topMargin=0 rightMargin=0 bgcolor="#FFFFFF">

    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 14, Column 33: there is no attribute "LEFTMARGIN"
    <body bottomMargin=0 leftMargin=0  topMargin=0 rightMargin=0 bgcolor="#FFFFFF">

    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 14, Column 46: there is no attribute "TOPMARGIN"
    <body bottomMargin=0 leftMargin=0  topMargin=0 rightMargin=0 bgcolor="#FFFFFF">

    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 14, Column 60: there is no attribute "RIGHTMARGIN"
    <body bottomMargin=0 leftMargin=0  topMargin=0 rightMargin=0 bgcolor="#FFFFFF">

    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 21, Column 31: there is no attribute "HEIGHT"
        <table width="990" height="100%" border="0" align="center" cellpadding="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 27, Column 28: there is no attribute "BACKGROUND"
                <td background="/images/minibaks/utop_m.gif">

    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 30, Column 32: an attribute value must be a literal unless it contains only name characters
                      <form action=/search method=POST>

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

  • Error Line 30, Column 51: document type does not allow element "FORM" here
                      <form action=/search method=POST>

    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 31, Column 40: document type does not allow element "TR" here
                        <tr valign="middle">

    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 35, Column 78: an attribute value must be a literal unless it contains only name characters
    …align="right" class="topright"><a href=/links class=topright>Σύνδεσμοι Α-Ω</a> 

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

  • Error Line 36, Column 35: an attribute value must be a literal unless it contains only name characters
                            | <a href=/chat class=topright>chat</a></td>

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

  • Error Line 39, Column 86: there is no attribute "WIDTH"
    …pe="image" src="/images/utility/search.gif" width="20" height="20" align="top">

    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 39, Column 98: there is no attribute "HEIGHT"
    …pe="image" src="/images/utility/search.gif" width="20" height="20" align="top">

    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 42, Column 85: an attribute value must be a literal unless it contains only name characters
    …opright"> <div align="center"><a href=/age/age:0-2,page:1 class=topright>0-2</…

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

  • Error Line 43, Column 33: an attribute value must be a literal unless it contains only name characters
                          | <a href=/age/age:3-5,page:1 class=topright>3-5</a> | <a…

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

  • Error Line 43, Column 86: an attribute value must be a literal unless it contains only name characters
    …ge:1 class=topright>3-5</a> | <a href=/age/age:6-12,page:1 class=topright>6-12…

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

  • Error Line 44, Column 198: required attribute "ALT" not specified
    …images/header/parentscafelink.gif" width="100" height="25" border="0"></a></td>

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

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

  • Error Line 48, Column 20: end tag for "TABLE" which is not finished
                </table></td>

    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 54, Column 99: "TR" is not a member of a group specified for any attribute
    …/images/header/logo_stripe_m.jpg" height="10" colspan="2" bgcolor="#cde9fc"tr> 
  • Error Line 58, Column 37: an attribute value must be a literal unless it contains only name characters
                <td width="495"><a href=/><img src="/images/header/logo.gif" width=…

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

  • Error Line 58, Column 110: required attribute "ALT" not specified
    …/><img src="/images/header/logo.gif" width="475" height="100" border="0" ></td>

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

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

  • Error Line 58, Column 115: end tag for "A" omitted, but its declaration does not permit this
    …/><img src="/images/header/logo.gif" width="475" height="100" border="0" ></td>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 58, Column 29: start tag was here
                <td width="495"><a href=/><img src="/images/header/logo.gif" width=…
  • Error Line 65, Column 109: required attribute "ALT" not specified
    …ign="bottom"><img src="/images/header/tmleft.gif" width="180" height="30"></td>

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

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

  • Error Line 69, Column 53: an attribute value must be a literal unless it contains only name characters
    …      <td width="110" align="center"> <a href=/forum class=basic>forum</a></td>

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

  • Error Line 70, Column 53: an attribute value must be a literal unless it contains only name characters
    …d width="140" align="center"> <a href=/health class=basic>υγεία & ασφάλεια</a>…

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

  • Error Line 71, Column 53: an attribute value must be a literal unless it contains only name characters
    …    <td width="125" align="center"> <a href=/food class=basic>διατροφή</a></td>

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

  • Error Line 72, Column 53: an attribute value must be a literal unless it contains only name characters
    …  <td width="125" align="center"> <a href=/psych class=basic>ψυχολογία</a></td>

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

  • Error Line 73, Column 53: an attribute value must be a literal unless it contains only name characters
    …d width="140" align="center"> <a href=/events class=basic>δραστηριότητες</a></…

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

  • Error Line 74, Column 53: an attribute value must be a literal unless it contains only name characters
    …    <td width="110" align="center"> <a href=/news class=basic>ειδήσεις</a></td>

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

  • Warning Line 81, Column 12: NET-enabling start-tag requires SHORTTAG YES
           <br /><div align="right">            <table border="0" cellspacing="0" c…

    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 81, Column 344: NET-enabling start-tag requires SHORTTAG YES
    …eft">Οδηγίες πλοήγησης</a> </p><p><br /><br />          <a href="../prosfores"…

    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 81, Column 350: NET-enabling start-tag requires SHORTTAG YES
    …δηγίες πλοήγησης</a> </p><p><br /><br />          <a href="../prosfores" class…

    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 81, Column 990: NET-enabling start-tag requires SHORTTAG YES
    …"logotypo-synd" title="logotypo-synd" /></a>            </p></td>         <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 81, Column 1290: NET-enabling start-tag requires SHORTTAG YES
    …"logotypo-synd" title="logotypo-synd" /></a></p></td>         <td class="left"…

    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 116, Column 90: cannot generate system identifier for general entity "cb"
    …nts.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http://…

    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 116, Column 90: general entity "cb" not defined and no default entity
    …nts.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http://…

    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 116, Column 92: reference to entity "cb" for which no system identifier could be generated
    …s.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http://ad…

    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 116, Column 89: entity was defined here
    …ents.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http:/…
  • Error Line 116, Column 182: reference to entity "cb" for which no system identifier could be generated
    …/www/delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt=''…

    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 116, Column 89: entity was defined here
    …ents.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http:/…
  • Warning Line 116, Column 186: cannot generate system identifier for general entity "n"
    …/delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /><…

    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 116, Column 186: general entity "n" not defined and no default entity
    …/delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /><…

    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 116, Column 187: reference to entity "n" for which no system identifier could be generated
    …delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /></…

    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 116, Column 185: entity was defined here
    …w/delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' />…
  • Warning Line 116, Column 197: cannot generate system identifier for general entity "ct0"
    …vw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /></a></noscri…

    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 116, Column 197: general entity "ct0" not defined and no default entity
    …vw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /></a></noscri…

    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 116, Column 200: reference to entity "ct0" for which no system identifier could be generated
    ….php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /></a></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 116, Column 196: entity was defined here
    …avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /></a></noscr…
  • Warning Line 116, Column 223: NET-enabling start-tag requires SHORTTAG YES
    ….php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' /></a></noscript>

    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 122, Column 33: an attribute value must be a literal unless it contains only name characters
                        <td width=98% align="center"> 

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

  • Error Line 149, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 157, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 157, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c502/ class=pwd>Τα νέα μας!</a></s…

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

  • Error Line 167, Column 92: required attribute "ALT" not specified
    …"><img src="/images/upload/forummembers.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 198, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 206, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/health class=pwd>Υγεία και ασφάλεια</a>…

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

  • Error Line 206, Column 139: an attribute value must be a literal unless it contains only name characters
    …=pwd>Υγεία και ασφάλεια</a> : <a href=/health/c102/ class=pwd>Ασφάλεια & Πρόλη…

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

  • Error Line 216, Column 112: required attribute "ALT" not specified
    …ww.parents.gr/images/upload/dangergreen.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 251, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 259, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 259, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c504/ class=pwd>Σεμινάρια</a></spa…

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

  • Error Line 269, Column 100: required attribute "ALT" not specified
    …rc="/images/upload/thilasmosfreeseminar.gif" width="100" border="0"></div></td>

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

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

  • Error Line 302, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 310, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/food class=pwd>Διατροφή</a> : <a href=/…

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

  • Error Line 310, Column 127: an attribute value must be a literal unless it contains only name characters
    …food class=pwd>Διατροφή</a> : <a href=/food/c201/ class=pwd>Συνταγές για μικρο…

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

  • Error Line 320, Column 114: required attribute "ALT" not specified
    ….parents.gr/images/upload/cinnamonroll0.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 355, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 363, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/events class=pwd>Δραστηριότητες</a> : <…

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

  • Error Line 363, Column 135: an attribute value must be a literal unless it contains only name characters
    …lass=pwd>Δραστηριότητες</a> : <a href=/events/c406/ class=pwd>Προτάσεις για εξ…

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

  • Error Line 373, Column 94: required attribute "ALT" not specified
    …<img src="/images/upload/mixkakogiannis.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 404, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 412, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/events class=pwd>Δραστηριότητες</a> : <…

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

  • Error Line 412, Column 135: an attribute value must be a literal unless it contains only name characters
    …lass=pwd>Δραστηριότητες</a> : <a href=/events/c406/ class=pwd>Προτάσεις για εξ…

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

  • Error Line 422, Column 89: required attribute "ALT" not specified
    …ter"><img src="/images/upload/dwrean200.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 457, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 465, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 465, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c504/ class=pwd>Σεμινάρια</a></spa…

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

  • Error Line 475, Column 87: required attribute "ALT" not specified
    …enter"><img src="/images/upload/seminar.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 506, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 514, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 514, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c501/ class=pwd>Επικαιρότητα</a></…

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

  • Error Line 524, Column 96: required attribute "ALT" not specified
    …mg src="/images/upload/surveyresearch_2.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 560, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 568, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 568, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c501/ class=pwd>Επικαιρότητα</a></…

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

  • Error Line 578, Column 90: required attribute "ALT" not specified
    …er"><img src="/images/upload/encahellas.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 609, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 617, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 617, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c501/ class=pwd>Επικαιρότητα</a></…

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

  • Error Line 627, Column 89: required attribute "ALT" not specified
    …ter"><img src="/images/upload/ifbanlogo.png" width="100" border="0"></div></td>

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

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

  • Error Line 662, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 670, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/health class=pwd>Υγεία και ασφάλεια</a>…

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

  • Error Line 670, Column 139: an attribute value must be a literal unless it contains only name characters
    …=pwd>Υγεία και ασφάλεια</a> : <a href=/health/c101/ class=pwd>Υγεία & Ιατρική<…

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

  • Error Line 680, Column 89: required attribute "ALT" not specified
    …ter"><img src="/images/upload/vivliario.png" width="100" border="0"></div></td>

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

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

  • Error Line 711, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 719, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 719, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c501/ class=pwd>Επικαιρότητα</a></…

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

  • Error Line 729, Column 115: required attribute "ALT" not specified
    …parents.gr/images/upload/fainareti_logo.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 764, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 772, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/events class=pwd>Δραστηριότητες</a> : <…

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

  • Error Line 772, Column 135: an attribute value must be a literal unless it contains only name characters
    …lass=pwd>Δραστηριότητες</a> : <a href=/events/c406/ class=pwd>Προτάσεις για εξ…

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

  • Error Line 782, Column 94: required attribute "ALT" not specified
    …<img src="/images/upload/drasthriothtes.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 814, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 822, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 822, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c501/ class=pwd>Επικαιρότητα</a></…

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

  • Error Line 832, Column 94: required attribute "ALT" not specified
    …<img src="/images/upload/epsypegrammi12.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 867, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 875, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/news class=pwd>Ειδήσεις</a> : <a href=/…

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

  • Error Line 875, Column 127: an attribute value must be a literal unless it contains only name characters
    …news class=pwd>Ειδήσεις</a> : <a href=/news/c501/ class=pwd>Επικαιρότητα</a></…

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

  • Error Line 885, Column 91: required attribute "ALT" not specified
    …r"><img src="/images/upload/depression2.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 916, Column 62: required attribute "ALT" not specified
    			  <td colspan="2"><img src="/images/utility/art_strip.gif"></td>

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

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

  • Error Line 924, Column 88: an attribute value must be a literal unless it contains only name characters
    …ticletitle"><span class="pwd"><a href=/health class=pwd>Υγεία και ασφάλεια</a>…

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

  • Error Line 924, Column 139: an attribute value must be a literal unless it contains only name characters
    …=pwd>Υγεία και ασφάλεια</a> : <a href=/health/c101/ class=pwd>Υγεία & Ιατρική<…

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

  • Error Line 934, Column 95: required attribute "ALT" not specified
    …img src="/images/upload/child_at_doctor.jpg" width="100" border="0"></div></td>

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

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

  • Error Line 953, Column 33: an attribute specification must start with a name or name token
    <div align=center><a href= class=more></a></div>

    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).

  • Warning Line 975, Column 269: NET-enabling start-tag requires SHORTTAG YES
    …="120" height="230" style="border: 0px;" /></a><br/><!-- Facebook Badge END -->

    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 975, Column 269: required attribute "ALT" not specified
    …="120" height="230" style="border: 0px;" /></a><br/><!-- Facebook Badge END -->

    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 975, Column 278: NET-enabling start-tag requires SHORTTAG YES
    …="120" height="230" style="border: 0px;" /></a><br/><!-- Facebook Badge END -->

    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 979, Column 236: NET-enabling start-tag requires SHORTTAG YES
    …="120" height="194" style="border: 0px;" /></a><br/><!-- Facebook Badge END -->

    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 979, Column 236: required attribute "ALT" not specified
    …="120" height="194" style="border: 0px;" /></a><br/><!-- Facebook Badge END -->

    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 979, Column 245: NET-enabling start-tag requires SHORTTAG YES
    …="120" height="194" style="border: 0px;" /></a><br/><!-- Facebook Badge END -->

    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 1000, Column 92: reference to entity "cb" for which no system identifier could be generated
    …s.gr/www/delivery/ck.php?n=aa45e96a&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 116, Column 89: entity was defined here
    …ents.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http:/…
  • Error Line 1000, Column 206: reference to entity "cb" for which no system identifier could be generated
    …www/delivery/avw.php?campaignid=106&cb=INSERT_RANDOM_NUMBER_HERE&n=aa45e96a' 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 116, Column 89: entity was defined here
    …ents.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http:/…
  • Error Line 1000, Column 234: reference to entity "n" for which no system identifier could be generated
    …nid=106&cb=INSERT_RANDOM_NUMBER_HERE&n=aa45e96a' border='0' alt='' /></a></nos…

    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 116, Column 185: entity was defined here
    …w/delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' />…
  • Warning Line 1000, Column 263: NET-enabling start-tag requires SHORTTAG YES
    …06&cb=INSERT_RANDOM_NUMBER_HERE&n=aa45e96a' border='0' alt='' /></a></noscript>

    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 1039, Column 92: reference to entity "cb" for which no system identifier could be generated
    …s.gr/www/delivery/ck.php?n=aedd5443&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 116, Column 89: entity was defined here
    …ents.gr/www/delivery/ck.php?n=a1a10a60&cb=%n' target='_blank'><img src='http:/…
  • Error Line 1039, Column 203: reference to entity "n" for which no system identifier could be generated
    …gr/www/delivery/avw.php?campaignid=9&n=aedd5443' border='0' alt='' /></a></nos…

    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 116, Column 185: entity was defined here
    …w/delivery/avw.php?campaignid=87&cb=%n&n=a1a10a60&ct0=%c' border='0' alt='' />…
  • Warning Line 1039, Column 232: NET-enabling start-tag requires SHORTTAG YES
    …w/delivery/avw.php?campaignid=9&n=aedd5443' border='0' alt='' /></a></noscript>

    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 1056, Column 58: an attribute value must be a literal unless it contains only name characters
    …ght="40" class="down"><strong><a href=/who class=down>ποιοί είμαστε</a></stron…

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

  • Error Line 1056, Column 119: an attribute value must be a literal unless it contains only name characters
    …ίμαστε</a></strong> | <strong><a href=/contact class=down>επικοινωνία</a></str…

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

  • Error Line 1057, Column 33: an attribute value must be a literal unless it contains only name characters
                  | <strong><a href=/statistics class=down>στατιστικά</a></strong> …

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

  • Warning Line 1119, Column 30: NET-enabling start-tag requires SHORTTAG YES
     width="1" height="1" alt="" />

    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.

Visitor Analysis

Daily Visitor
  • 4.550 visits
Daily Visitor