ΟΠΑΠ ΑΕ, η Καλή Εταιρεία. Τυχερά παιχνίδια αξιόπιστα και υπεύθυνα. Πολλοί νικητές, απίθανα κέρδη, άμεση πληρωμή, μεγάλες αποδόσεις. Καλό για όλους. ...

opap.gr
  • Domain Name
    opap.gr
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #10199
  • Page Size
    81.6 KB
  • Ip Address
    195.97.99.120
  • Heading
    H1: 2, H2: 1, H3: 10, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 9 PNG

Website Meta Analysis

  • Title
    ΟΠΑΠ AE | ΣΤΟΙΧΗΜΑ | ΚΙΝΟ | ΤΖΟΚΕΡ | ΛΟΤΤΟ | ΠΡΟΤΟ | ΠΡΟΠΟ - opap.gr
  • Meta Keyword
    ΠΑΜΕ ΣΤΟΙΧΗΜΑ, ΚΙΝΟ, ΤΖΟΚΕΡ, ΠΡΟΤΟ, ΛΟΤΤΟ, ΠΡΟΠΟ,ΠΑΜΕ ΣΤΟΙΧΗΜΑ LIVE , BETTING
  • Meta Description
    ΟΠΑΠ ΑΕ, η Καλή Εταιρεία. Τυχερά παιχνίδια αξιόπιστα και υπεύθυνα. Πολλοί νικητές, απίθανα κέρδη, άμεση πληρωμή, μεγάλες αποδόσεις. Καλό για όλους.

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    195.97.99.120
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • content-encoding: gzip
  • etag: "d8bd2b63"
  • content-type: text/html;charset=UTF-8
  • content-length: 15061
  • vary: Accept-Encoding
  • date: Thu, 28 Feb 2013 10:26:03 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for opap.gr

DNS Analysis


DNS servers
ns2.otenet.gr [195.170.2.1]
ns1.otenet.gr [195.170.0.2]


DNS Records

Answer records
opap.gr SOA
server: ns1.otenet.gr
email: hostmaster@ns1.otenet.gr
serial: 2013011110
refresh: 10800
retry: 3600
expire: 1814400
minimum ttl: 3600
3600s
opap.gr A 195.97.99.120 3600s
opap.gr MX
preference: 10
exchange: mail.lc.opap.gr
3600s
opap.gr NS  ns2.otenet.gr 3600s
opap.gr NS  ns1.otenet.gr 3600s

Authority records

Additional records
ns1.otenet.gr A 195.170.0.2 86400s
ns2.otenet.gr A 195.170.2.1 86400s

IP 195.97.99.120 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 122 Errors
  • 30 Warnings
Ratio Text/Html
  • 0.7541993683001531
Message Error
  • Error Line 1, Column 136: there is no attribute "class"
    …xhtml1-transitional.dtd"> <html class="ltr" dir="ltr" lang="el-GR"> <head> <ti…

    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 1, Column 124: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …/xhtml1/DTD/xhtml1-transitional.dtd"> <html class="ltr" dir="ltr" lang="el-GR"…

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 5, Column 215: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … portlet-static portlet-static-end  " > <a id="p_bonLoginPortlet_WAR_bonportle…

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

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

  • Error Line 5, Column 1677: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rmal" /> <span id="A4925:myPanel2"> <p>Άν είσαι μέλος στο opap.gr και ξέχασες …

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

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

  • Error Line 5, Column 1799: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ρακάτω πεδίο:</p><table class="forgot"> <tbody> <tr> <td> <div></td> </tr> <tr…

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

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

  • Error Line 5, Column 1828: end tag for "div" omitted, but OMITTAG NO was specified
    …="forgot"> <tbody> <tr> <td> <div></td> </tr> <tr> <td><div id="A4925:j_idt16"…

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

  • Info Line 5, Column 1819: start tag was here
    …ble class="forgot"> <tbody> <tr> <td> <div></td> </tr> <tr> <td><div id="A4925…
  • Error Line 5, Column 1931: end tag for "td" omitted, but OMITTAG NO was specified
    …dget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div…

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

  • Info Line 5, Column 1922: start tag was here
    …ges ui-widget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> …
  • Error Line 5, Column 1931: end tag for "tr" omitted, but OMITTAG NO was specified
    …dget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div…

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

  • Info Line 5, Column 1917: start tag was here
    …messages ui-widget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> …
  • Error Line 5, Column 1931: end tag for "tbody" omitted, but OMITTAG NO was specified
    …dget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div…

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

  • Info Line 5, Column 1801: start tag was here
    …κάτω πεδίο:</p><table class="forgot"> <tbody> <tr> <td> <div></td> </tr> <tr> …
  • Error Line 5, Column 1931: end tag for "table" omitted, but OMITTAG NO was specified
    …dget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div…

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

  • Info Line 5, Column 1778: start tag was here
    …σε το mail σου στο παρακάτω πεδίο:</p><table class="forgot"> <tbody> <tr> <td>…
  • Error Line 5, Column 1931: end tag for "span" omitted, but OMITTAG NO was specified
    …dget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div…

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

  • Info Line 5, Column 1648: start tag was here
    …_p_mode=view&amp;p_p_state=normal" /> <span id="A4925:myPanel2"> <p>Άν είσαι μ…
  • Error Line 5, Column 1931: end tag for "form" omitted, but OMITTAG NO was specified
    …dget"></div></td> </tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div…

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

  • Info Line 5, Column 899: start tag was here
    …e" title="Ξεχάσατε το password σας;"> <form id="A4925:frmSendPassword" name="A…
  • Error Line 5, Column 1949: end tag for element "td" which is not open
    …</tr> <tr> <td></div> <div> </div></td> </tr> <tr> <td> <div><label for="A4925…

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

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

  • Error Line 5, Column 1955: end tag for element "tr" which is not open
    …<tr> <td></div> <div> </div></td> </tr> <tr> <td> <div><label for="A4925:txtEm…

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

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

  • Error Line 5, Column 1960: document type does not allow element "tr" here; assuming missing "table" start-tag
    …<td></div> <div> </div></td> </tr> <tr> <td> <div><label for="A4925:txtEmail2"…
  • Error Line 5, Column 2191: end tag for element "tbody" which is not open
    …ail2"></div> </div></td> </tr> </tbody> </table> <div class="sendButton"><butt…

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

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

  • Error Line 5, Column 2599: end tag for "div" omitted, but OMITTAG NO was specified
    …t26",{});/*]]>*/</script> </div></span><input type="hidden" name="javax.faces.…

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

  • Info Line 5, Column 315: start tag was here
    …rtlet-borderless-container" style=""> <div class="portlet-body"> <!--p:ajaxSta…
  • Error Line 5, Column 2599: end tag for "div" omitted, but OMITTAG NO was specified
    …t26",{});/*]]>*/</script> </div></span><input type="hidden" name="javax.faces.…

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

  • Info Line 5, Column 263: start tag was here
    …_bonLoginPortlet_WAR_bonportlet"></a> <div class="portlet-borderless-container…
  • Error Line 5, Column 2599: end tag for "div" omitted, but OMITTAG NO was specified
    …t26",{});/*]]>*/</script> </div></span><input type="hidden" name="javax.faces.…

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

  • Info Line 5, Column 55: start tag was here
    …</li> </ul> <span class="login-area"> <div id="p_p_id_bonLoginPortlet_WAR_bonp…
  • Error Line 5, Column 3131: there is no attribute "autocomplete"
    …VADDlW6AgDM3QSPqwEAAA==" autocomplete="off" /> </form></div><script type="text…

    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 5, Column 3146: end tag for element "form" which is not open
    …qwEAAA==" autocomplete="off" /> </form></div><script type="text/javascript">/*…

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

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

  • Error Line 5, Column 3399: required attribute "type" not specified
    …Body:true})});/*]]>*/</script> <script></script> <script>/*<![CDATA[*/PlayerCl…

    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 5, Column 3417: required attribute "type" not specified
    …>*/</script> <script></script> <script>/*<![CDATA[*/PlayerClub.userName="";Pla…

    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 5, Column 4678: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …<span id="A4925:pnlNotLoggedIn"><table> <tbody> <tr> <td><input id="A4925:txtE…

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

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

  • Error Line 5, Column 5660: ID "javax.faces.ViewState" already defined
    …den" name="javax.faces.ViewState" id="javax.faces.ViewState" value="H4sIAAAAAA…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 5, Column 2654: ID "javax.faces.ViewState" first defined here
    …den" name="javax.faces.ViewState" id="javax.faces.ViewState" value="H4sIAAAAAA…
  • Error Line 5, Column 6161: required attribute "type" not specified
    … autocomplete="off" /> </form> <script>/*<![CDATA[*/jQuery(document).ready(fun…

    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 5, Column 6493: end tag for element "span" which is not open
    …/</script> </div> </div> </div> </span> </div> </div> </div> <div id="wrapper-…

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

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

  • Error Line 5, Column 6500: end tag for element "div" which is not open
    …pt> </div> </div> </div> </span> </div> </div> </div> <div id="wrapper-header"…

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

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

  • Error Line 5, Column 6507: end tag for element "div" which is not open
    …iv> </div> </div> </span> </div> </div> </div> <div id="wrapper-header"> <head…

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

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

  • Error Line 5, Column 6514: end tag for element "div" which is not open
    …iv> </div> </span> </div> </div> </div> <div id="wrapper-header"> <header id="…

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

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

  • Error Line 5, Column 6553: there is no attribute "id"
    … <div id="wrapper-header"> <header id="banner" role="banner"> <hgroup id="head…

    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 5, Column 6567: there is no attribute "role"
    …per-header"> <header id="banner" role="banner"> <hgroup id="heading"> <h1 clas…

    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 5, Column 6575: element "header" undefined
    …er"> <header id="banner" role="banner"> <hgroup id="heading"> <h1 class="compa…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 5, Column 6588: there is no attribute "id"
    …id="banner" role="banner"> <hgroup id="heading"> <h1 class="company-title"> <a…

    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 5, Column 6597: element "hgroup" undefined
    …r" role="banner"> <hgroup id="heading"> <h1 class="company-title"> <a class="l…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 5, Column 6765: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …id="header_right" style="float:right;"> <div id="BannerWebContent"> <div id="p…

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

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

  • Error Line 5, Column 8876: syntax of attribute value does not conform to declared value
    …href="/el/web/guest/rssfeeds" target=""><img alt="RSS Δελτίων Τύπου" src="/ima…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 5, Column 9933: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …b/guest/corporate"  class="home"> <div><span>+</span></div> </a> </li> <li cla…

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

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

  • Error Line 24, Column 44: document type does not allow element "ul" here; assuming missing "li" start-tag
    …						</a> <ul class="child-menu"> <ul> <li> <a href="/el/web/guest/demo2" > B…
  • Error Line 31, Column 52: end tag for "li" omitted, but OMITTAG NO was specified
    …				</a> </li> </ul> </li> </ul> </div> </div> </header> </div> <div id="wrapp…

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

  • Info Line 23, Column 85: start tag was here
    …ass="menu-seperator"><div></div></li> <li class=""> <a href="/el/web/guest/dem…
  • Error Line 31, Column 52: end tag for "ul" omitted, but OMITTAG NO was specified
    …				</a> </li> </ul> </li> </ul> </div> </div> </header> </div> <div id="wrapp…

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

  • Info Line 5, Column 9852: start tag was here
    …<div class="navigation-main-content"> <ul> <li class="selected "> <a href="/el…
  • Error Line 31, Column 304: there is no attribute "role"
    …ss="columns-1" id="main-content" role="main"> <div class="portlet-layout"> <di…

    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 31, Column 887: required attribute "type" not specified
    …r" style=""> <div class="portlet-body"> <style> #wrapper-content {padding:0px;}

    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 31, Column 887: document type does not allow element "style" here
    …r" style=""> <div class="portlet-body"> <style> #wrapper-content {padding:0px;}

    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 34, Column 466: there is no attribute "accesskey"
    …" width="1000" height="300" accesskey="f" title="explore"> <param name="movie"…

    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 34, Column 701: there is no attribute "src"
    …de" value="transparent" /> <embed src="http://media.opap.gr/Swf/opap1000x300_g…

    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 35, Column 29: there is no attribute "quality"
    						            		quality="low" 		

    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 36, Column 27: there is no attribute "wmode"
    						            		wmode="transparent"	

    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 37, Column 29: there is no attribute "bgcolor"
    						            		bgcolor="transparent"					            								    

    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 38, Column 26: there is no attribute "type"
    						            		type="application/x-shockwave-flash" 

    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 27: there is no attribute "width"
    						            		width="1000" 

    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 40, Column 28: there is no attribute "height"
    						            		height="300"> </embed> </object> </div> </div> <div class="…

    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 40, Column 33: element "embed" undefined
    						            		height="300"> </embed> </object> </div> </div> <div class="…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 46, Column 35: element "embed" undefined
    								            		height="230"> </embed> </object> </div> <!-- <h3></h3> <p…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 54, Column 35: element "embed" undefined
    								            		height="130"> </embed> </object> </div> </div> <div  clas…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 54, Column 936: required attribute "alt" not specified
    …portlet/html/images/monitor-text.png"/> <div class="thelogo"></div> <h3></h3> …

    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 60, Column 35: element "embed" undefined
    								            		height="240"> </embed> </object> </div> </div> </div> </d…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 66, Column 37: element "embed" undefined
    										            		height="200"> </embed> </object> </div> </div> </div> <…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 66, Column 656: cannot generate system identifier for general entity "TzokerMoirazei"
    …p://media.opap.gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/…

    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 66, Column 656: general entity "TzokerMoirazei" not defined and no default entity
    …p://media.opap.gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/…

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

  • Warning Line 66, Column 670: reference not terminated by REFC delimiter
    ….gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Warning Line 66, Column 670: reference to external entity in attribute value
    ….gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Error Line 66, Column 670: reference to entity "TzokerMoirazei" for which no system identifier could be generated
    ….gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/joker-promo.xm…

    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 66, Column 655: entity was defined here
    …tp://media.opap.gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf…
  • Warning Line 66, Column 712: cannot generate system identifier for general entity "Tzoker2TyxeraDeltia"
    …p://media.opap.gr/Swf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr…

    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 66, Column 712: general entity "Tzoker2TyxeraDeltia" not defined and no default entity
    …p://media.opap.gr/Swf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr…

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

  • Warning Line 66, Column 731: reference not terminated by REFC delimiter
    …wf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Warning Line 66, Column 731: reference to external entity in attribute value
    …wf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Error Line 66, Column 731: reference to entity "Tzoker2TyxeraDeltia" for which no system identifier could be generated
    …wf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr/Swf/joker-promo.xm…

    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 66, Column 711: entity was defined here
    …tp://media.opap.gr/Swf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.g…
  • Warning Line 66, Column 773: cannot generate system identifier for general entity "Tzoker1TyxeroDeltio"
    …p://media.opap.gr/Swf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr…

    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 66, Column 773: general entity "Tzoker1TyxeroDeltio" not defined and no default entity
    …p://media.opap.gr/Swf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr…

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

  • Warning Line 66, Column 792: reference not terminated by REFC delimiter
    …wf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Warning Line 66, Column 792: reference to external entity in attribute value
    …wf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Error Line 66, Column 792: reference to entity "Tzoker1TyxeroDeltio" for which no system identifier could be generated
    …wf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr/Swf/joker-promo.xm…

    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 66, Column 772: entity was defined here
    …tp://media.opap.gr/Swf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.g…
  • Error Line 67, Column 32: there is no attribute "FlashVars"
    							           		 FlashVars="TzokerTzakPot=http://media.opap.gr/Swf/joker-pr…

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

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

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

  • Warning Line 67, Column 107: reference not terminated by REFC delimiter
    …wf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Warning Line 67, Column 107: reference to external entity in attribute value
    …wf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Error Line 67, Column 107: reference to entity "Tzoker1TyxeroDeltio" for which no system identifier could be generated
    …wf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.gr/Swf/joker-promo.xm…

    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 66, Column 772: entity was defined here
    …tp://media.opap.gr/Swf/joker-promo.xml&Tzoker1TyxeroDeltio=http://media.opap.g…
  • Warning Line 67, Column 168: reference not terminated by REFC delimiter
    …wf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Warning Line 67, Column 168: reference to external entity in attribute value
    …wf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Error Line 67, Column 168: reference to entity "Tzoker2TyxeraDeltia" for which no system identifier could be generated
    …wf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.gr/Swf/joker-promo.xm…

    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 66, Column 711: entity was defined here
    …tp://media.opap.gr/Swf/joker-promo.xml&Tzoker2TyxeraDeltia=http://media.opap.g…
  • Warning Line 67, Column 224: reference not terminated by REFC delimiter
    ….gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Warning Line 67, Column 224: reference to external entity in attribute value
    ….gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/joker-promo.xm…

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

  • Error Line 67, Column 224: reference to entity "TzokerMoirazei" for which no system identifier could be generated
    ….gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf/joker-promo.xm…

    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 66, Column 655: entity was defined here
    …tp://media.opap.gr/Swf/joker-promo.xml&TzokerMoirazei=http://media.opap.gr/Swf…
  • Error Line 73, Column 34: element "embed" undefined
    							            		height="230"> </embed> </object> </div> <div class="client…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 73, Column 1029: cannot generate system identifier for general entity "Lotto1TyxeroDeltio"
    …p://media.opap.gr/Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/…

    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 73, Column 1029: general entity "Lotto1TyxeroDeltio" not defined and no default entity
    …p://media.opap.gr/Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/…

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

  • Warning Line 73, Column 1047: reference not terminated by REFC delimiter
    …Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Warning Line 73, Column 1047: reference to external entity in attribute value
    …Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Error Line 73, Column 1047: reference to entity "Lotto1TyxeroDeltio" for which no system identifier could be generated
    …Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/Swf/lotto-promo.xm…

    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 73, Column 1028: entity was defined here
    …tp://media.opap.gr/Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr…
  • Warning Line 73, Column 1089: cannot generate system identifier for general entity "Lotto2TyxeraDeltia"
    …p://media.opap.gr/Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/…

    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 73, Column 1089: general entity "Lotto2TyxeraDeltia" not defined and no default entity
    …p://media.opap.gr/Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/…

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

  • Warning Line 73, Column 1107: reference not terminated by REFC delimiter
    …Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Warning Line 73, Column 1107: reference to external entity in attribute value
    …Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Error Line 73, Column 1107: reference to entity "Lotto2TyxeraDeltia" for which no system identifier could be generated
    …Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/Swf/lotto-promo.xm…

    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 73, Column 1088: entity was defined here
    …tp://media.opap.gr/Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr…
  • Warning Line 73, Column 1149: cannot generate system identifier for general entity "LottoMoirazei"
    …p://media.opap.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/l…

    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 73, Column 1149: general entity "LottoMoirazei" not defined and no default entity
    …p://media.opap.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/l…

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

  • Warning Line 73, Column 1162: reference not terminated by REFC delimiter
    …p.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Warning Line 73, Column 1162: reference to external entity in attribute value
    …p.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Error Line 73, Column 1162: reference to entity "LottoMoirazei" for which no system identifier could be generated
    …p.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/lotto-promo.xm…

    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 73, Column 1148: entity was defined here
    …tp://media.opap.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/…
  • Warning Line 74, Column 106: reference not terminated by REFC delimiter
    …Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Warning Line 74, Column 106: reference to external entity in attribute value
    …Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Error Line 74, Column 106: reference to entity "Lotto1TyxeroDeltio" for which no system identifier could be generated
    …Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr/Swf/lotto-promo.xm…

    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 73, Column 1028: entity was defined here
    …tp://media.opap.gr/Swf/lotto-promo.xml&Lotto1TyxeroDeltio=http://media.opap.gr…
  • Warning Line 74, Column 166: reference not terminated by REFC delimiter
    …Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Warning Line 74, Column 166: reference to external entity in attribute value
    …Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Error Line 74, Column 166: reference to entity "Lotto2TyxeraDeltia" for which no system identifier could be generated
    …Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr/Swf/lotto-promo.xm…

    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 73, Column 1088: entity was defined here
    …tp://media.opap.gr/Swf/lotto-promo.xml&Lotto2TyxeraDeltia=http://media.opap.gr…
  • Warning Line 74, Column 221: reference not terminated by REFC delimiter
    …p.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Warning Line 74, Column 221: reference to external entity in attribute value
    …p.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/lotto-promo.xm…

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

  • Error Line 74, Column 221: reference to entity "LottoMoirazei" for which no system identifier could be generated
    …p.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/lotto-promo.xm…

    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 73, Column 1148: entity was defined here
    …tp://media.opap.gr/Swf/lotto-promo.xml&LottoMoirazei=http://media.opap.gr/Swf/…
  • Error Line 80, Column 35: element "embed" undefined
    								            		height="230"> </embed> </object> </div> <!-- <h3></h3> <p…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 86, Column 34: element "embed" undefined
    							            		height="230"> </embed> </object> </div> <div class="client…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 92, Column 34: element "embed" undefined
    							            		height="230"> </embed> </object> </div> <div class="client…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 99, Column 34: element "embed" undefined
    							            		height="230"> </embed> </object> </div> <div class="client…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 105, Column 34: element "embed" undefined
    							            		height="200"> </embed> </object> </div> <div class="client…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 113, Column 34: element "embed" undefined
    							            		height="300"> </embed> </object> </div> <div class="client…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 113, Column 9738: required attribute "alt" not specified
    …-portlet/html/images/lotto_logo.png" /></a></li> <li id="jokertab"><a href="#"…

    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 113, Column 9874: required attribute "alt" not specified
    …-portlet/html/images/joker_logo.png" /></a></li> <li id="kinotab"><a href="#" …

    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 113, Column 10006: required attribute "alt" not specified
    …s-portlet/html/images/kino_logo.png" /></a></li> <li id="prototab"><a href="#"…

    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 113, Column 10141: required attribute "alt" not specified
    …-portlet/html/images/proto_logo.png" /></a></li> <li id="extra5tab"><a href="#…

    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 113, Column 10279: required attribute "alt" not specified
    …portlet/html/images/extra5_logo.png" /></a></li> <li id="super3tab"><a href="#…

    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 113, Column 10417: required attribute "alt" not specified
    …portlet/html/images/super3_logo.png" /></a></li> </ul> <div class="latestresul…

    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 113, Column 15162: required attribute "action" not specified
    …ass="stoixima-out-inner-layout"> <form> <div class="stoixima-logo"><span id="g…

    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 113, Column 20774: required attribute "action" not specified
    …="main-store-locator-container"> <form> <div class="group-by"></div> <div> <di…

    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 113, Column 22125: there is no attribute "id"
    … <div id="wrapper-footer"> <footer id="footer" role="contentinfo"> <div id="na…

    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 113, Column 22139: there is no attribute "role"
    …per-footer"> <footer id="footer" role="contentinfo"> <div id="navigation-botto…

    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 113, Column 22152: element "footer" undefined
    …<footer id="footer" role="contentinfo"> <div id="navigation-bottom"> <table cl…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 126, Column 61: ID "navigation_bottom_tr" already defined
    …	</a> </li> </ul> </td> </tr> <tr id="navigation_bottom_tr"> <td> <ul class="f…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 114, Column 41: ID "navigation_bottom_tr" first defined here
    …									</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="f…
  • Error Line 132, Column 42: end tag for "ul" omitted, but OMITTAG NO was specified
    …																				</a> </li> </table> </td> <td id="navigation-bottom-item">…

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

  • Info Line 130, Column 52: start tag was here
    …										</a> </li> </ul> </td> <td> <ul class="footer-left"> <li> <a href="/…
  • Error Line 132, Column 42: end tag for "td" omitted, but OMITTAG NO was specified
    …																				</a> </li> </table> </td> <td id="navigation-bottom-item">…

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

  • Info Line 130, Column 47: start tag was here
    …															</a> </li> </ul> </td> <td> <ul class="footer-left"> <li> <a hr…
  • Error Line 132, Column 42: end tag for "tr" omitted, but OMITTAG NO was specified
    …																				</a> </li> </table> </td> <td id="navigation-bottom-item">…

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

  • Info Line 126, Column 53: start tag was here
    …									</a> </li> </ul> </td> </tr> <tr id="navigation_bottom_tr"> <td> <ul …
  • Error Line 132, Column 58: ID "navigation-bottom-item" already defined
    …				</a> </li> </table> </td> <td id="navigation-bottom-item"> <a style="curso…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 113, Column 22261: ID "navigation-bottom-item" first defined here
    …"navigation_bottom_outer_tr"> <td id="navigation-bottom-item"> <a style="curso…
  • Error Line 133, Column 41: ID "navigation_bottom_tr" already defined
    …									</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="f…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 114, Column 41: ID "navigation_bottom_tr" first defined here
    …									</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="f…
  • Error Line 139, Column 42: end tag for "ul" omitted, but OMITTAG NO was specified
    …																				</a> </li> </table> </td> <td id="navigation-bottom-item-r…

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

  • Info Line 137, Column 52: start tag was here
    …										</a> </li> </ul> </td> <td> <ul class="footer-left"> <li> <a href="/…
  • Error Line 139, Column 42: end tag for "td" omitted, but OMITTAG NO was specified
    …																				</a> </li> </table> </td> <td id="navigation-bottom-item-r…

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

  • Info Line 137, Column 47: start tag was here
    …															</a> </li> </ul> </td> <td> <ul class="footer-left"> <li> <a hr…
  • Error Line 139, Column 42: end tag for "tr" omitted, but OMITTAG NO was specified
    …																				</a> </li> </table> </td> <td id="navigation-bottom-item-r…

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

  • Info Line 133, Column 33: start tag was here
    											</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="…
  • Error Line 140, Column 41: ID "navigation_bottom_tr" already defined
    …									</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="f…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 114, Column 41: ID "navigation_bottom_tr" first defined here
    …									</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="f…
  • Error Line 148, Column 54: end tag for "tr" omitted, but OMITTAG NO was specified
    …								</a> </li> </ul> </td> </table> </td> </tr> <tr style="height:15px;"><…

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

  • Info Line 140, Column 33: start tag was here
    											</span> </a> <table> <tr id="navigation_bottom_tr"> <td> <ul class="…
  • Error Line 148, Column 97: end tag for "tr" which is not finished
    …d> </tr> <tr style="height:15px;"></tr> </table> </div> </footer> </div> <div …

    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 148, Column 266: end tag for element "div" which is not open
    … Rights Reserved.		</div> </div> </div> </body> <script src="/opap-home-slides…

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

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

  • Error Line 148, Column 432: document type does not allow element "script" here
    …=1359126426000" type="text/javascript"></script> <script src="/LatestResults-p…

    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 148, Column 602: document type does not allow element "script" here
    …=1314362451000" type="text/javascript"></script> <script src="/LatestResults-p…

    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 148, Column 781: document type does not allow element "script" here
    …=1314362451000" type="text/javascript"></script> <script src="/LatestResults-p…

    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 148, Column 945: document type does not allow element "script" here
    …=1314362451000" type="text/javascript"></script> <script src="/GameOfTheDayNew…

    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 148, Column 1111: document type does not allow element "script" here
    …=1352731407000" type="text/javascript"></script> <script src="/opap-store-loca…

    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 148, Column 1280: document type does not allow element "script" here
    …=1324297155000" type="text/javascript"></script> <script src="/opap-store-loca…

    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 148, Column 1462: document type does not allow element "script" here
    …=1324297155000" type="text/javascript"></script> <script src="/opap-store-loca…

    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 148, Column 1635: document type does not allow element "script" here
    …=1324297155000" type="text/javascript"></script> <script type="text/javascript…

    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 148, Column 1676: document type does not allow element "script" here
    …script> <script type="text/javascript">/*<![CDATA[*/Liferay.Util.addInputFocus…

    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 148, Column 1766: document type does not allow element "script" here
    …script> <script type="text/javascript">/*<![CDATA[*/Liferay.Portlet.onLoad({ca…

    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 148, Column 7059: document type does not allow element "script" here
    …=1361966522000" type="text/javascript"></script> <script type="text/javascript…

    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 148, Column 7100: document type does not allow element "script" here
    …script> <script type="text/javascript"></script> <script type="text/javascript…

    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 148, Column 7141: document type does not allow element "script" here
    …script> <script type="text/javascript">/*<![CDATA[*/var _gaq=_gaq||[];_gaq.pus…

    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 148, Column 7532: document type does not allow element "script" here
    …script> <script type="text/javascript">/*<![CDATA[*/$(document).ready(function…

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

Visitor Analysis

Daily Visitor
  • 19.717 visits
Daily Visitor