Όλα τα τελευταία αθλητικά νέα από την Ελλάδα και τον Κόσμο, Video, Gossip με την υπογραφή του λαγωνικού των αθλητικών Portal ...

sportdog.gr
  • Domain Name
    sportdog.gr
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #10244
  • Page Size
    130.3 KB
  • Ip Address
    46.4.100.79
  • Heading
    H1: 0, H2: 0, H3: 14, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 67 JPG, 4 PNG

Website Meta Analysis

  • Title
    Sportdog.gr - To λαγωνικό των αθλητικών portal
  • Meta Keyword
  • Meta Description
    Όλα τα τελευταία αθλητικά νέα από την Ελλάδα και τον Κόσμο, Video, Gossip με την υπογραφή του λαγωνικού των αθλητικών Portal

Technical Analysis

  • Webserver
    nginx/1.1.19
  • Ip Address
    46.4.100.79
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.1.19
  • content-type: text/html; charset=utf-8
  • content-length: 19271
  • x-powered-by: PHP/5.2.17
  • last-modified: Thu, 28 Feb 2013 14:15:10 GMT
  • etag: "a85e16f1156565771ed32c66229c1c54"
  • content-encoding: gzip
  • cache-control: must-revalidate, max-age=0
  • expires: Thu, 28 Feb 2013 14:19:28 GMT
  • date: Thu, 28 Feb 2013 14:19:28 GMT
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for sportdog.gr

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 101 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.6677183411022347
Message Error
  • Error Line 7, Column 47: end tag for "meta" omitted, but OMITTAG NO was specified
    …ta http-equiv="refresh" content="420">      <meta name="viewport" content="wid…

    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 7, Column 6: start tag was here
    	    <meta http-equiv="refresh" content="420">      <meta name="viewport" conte…
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:title" content="Sportdog.gr - To λαγωνικό των αθλητικών port…

    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 19, Column 36: there is no attribute "sizes"
    <link rel="apple-touch-icon" sizes="72x72" href="/sites/all/themes/responsive/i…

    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 23, Column 118: cannot generate system identifier for general entity "subset"
    …lic,700italic|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' typ…

    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 23, Column 118: general entity "subset" not defined and no default entity
    …lic,700italic|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' typ…

    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 23, Column 124: reference not terminated by REFC delimiter
    …0italic|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' type='tex…

    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 23, Column 124: reference to external entity in attribute value
    …0italic|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' type='tex…

    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 23, Column 124: reference to entity "subset" for which no system identifier could be generated
    …0italic|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' type='tex…

    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 23, Column 117: entity was defined here
    …alic,700italic|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' ty…
  • Error Line 23, Column 171: end tag for "link" omitted, but OMITTAG NO was specified
    …c|Open+Sans+Condensed:300&subset=latin,greek' rel='stylesheet' type='text/css'>

    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 5: start tag was here
        <link href='http://fonts.googleapis.com/css?family=Open+Sans:400,700,400ita…
  • Error Line 257, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 265, Column 63: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ass="field-content"><div class="title"><a href="/article/156903/tha-itan-kotar…

    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 266, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="teaser">Ο Κώστας Κετσετζόγλου γράφει στον σκύλο για το μπάχαλο στα …

    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 267, Column 18: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="date"><span class="date-display-single">28-02-2013 | 15:45</span></…

    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 271, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 279, Column 63: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ass="field-content"><div class="title"><a href="/article/156889/oyte-ton-kosmo…

    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 280, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="teaser">Ο Βασιλής Κωνσταντίνου σχολίασε στον sportdog ότι ο Παναθην…

    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 281, Column 18: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="date"><span class="date-display-single">28-02-2013 | 14:30</span></…

    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 285, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 293, Column 63: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ass="field-content"><div class="title"><a href="/article/156872/mono-etsi-gia-…

    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 294, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="teaser">Επειδή πολλά γράφονται σήμερα για το φλερτ Σιμάο &ndash; Ολ…

    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 295, Column 18: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="date"><span class="date-display-single">28-02-2013 | 13:00</span></…

    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 299, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 307, Column 63: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ass="field-content"><div class="title"><a href="/article/156850/i-pio-omorfi-g…

    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 308, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="teaser">Δείτε το super model, Μπαρ Ρεφαέλι σε μία καυτή διαφήμιση γ…

    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 309, Column 18: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="date"><span class="date-display-single">28-02-2013 | 13:00</span></…

    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 317, Column 29: end tag for "ul" which is not finished
          <ul class="pager"></ul>

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

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

  • Error Line 350, Column 175: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    … με έναν κανονικό πρόεδρο!</a><div class="date">28-02-2013 - 15:45</div></span>

    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 362, Column 115: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …4/poia-mpala">Ποια μπάλα; </a><div class="date">27-02-2013 - 22:23</div></span>

    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 374, Column 154: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …βρει την άκρη ο Αλαφούζος;</a><div class="date">27-02-2013 - 19:30</div></span>

    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 386, Column 177: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ώνια και το ξεσκαρτάρισμα!</a><div class="date">27-02-2013 - 13:45</div></span>

    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 398, Column 189: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …αι η άνευ λόγου αλαζονεία!</a><div class="date">26-02-2013 - 17:06</div></span>

    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 410, Column 197: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ουν ...&quot;φίλους&quot;!</a><div class="date">26-02-2013 - 15:30</div></span>

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

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

  • Error Line 420, Column 105: there is no attribute "width"
    …er"><a class="twitter-timeline" width="210" height="440" href="https://twitter…

    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 420, Column 118: there is no attribute "height"
    …"twitter-timeline" width="210" height="440" href="https://twitter.com/penalty_…

    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 420, Column 179: there is no attribute "data-widget-id"
    …tter.com/penalty_sdog" data-widget-id="268666343451148288">Tweets σχετικά με @…

    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 421, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 423, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 446, Column 184: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ώβρακα με όλες τις ομάδες!</a><div class="date">27-02-2013 - 15:40</div></span>

    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 458, Column 183: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …αι το λάθος ...του Σακίρα!</a><div class="date">27-02-2013 - 11:15</div></span>

    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 488, Column 45: character "(" is not allowed in the value of attribute "id"
    …iv id="gam-holder-Sportdog_Home_468x60(1)" class="gam-holder"><script type="te…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 514, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 542, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 570, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 598, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 610, Column 45: character "(" is not allowed in the value of attribute "id"
    …iv id="gam-holder-Sportdog_Home_468x60(2)" class="gam-holder"><script type="te…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 636, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 664, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 692, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 720, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 732, Column 45: character "(" is not allowed in the value of attribute "id"
    …iv id="gam-holder-Sportdog_Home_468x60(3)" class="gam-holder"><script type="te…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 752, Column 95: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …span class="field-content"><div class="emvideo emvideo-video emvideo-youtube"> 

    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 753, Column 12: there is no attribute "id"
    <iframe id="media-youtube-html5-1" title="YouTube video player" class="media-yo…

    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 753, Column 42: there is no attribute "title"
    …rame id="media-youtube-html5-1" title="YouTube video player" class="media-yout…

    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 753, Column 71: there is no attribute "class"
    …1" title="YouTube video player" class="media-youtube-html5" type="text/html" w…

    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 753, Column 98: there is no attribute "type"
    …yer" class="media-youtube-html5" type="text/html" width="670" height="450" src…

    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 753, Column 116: there is no attribute "width"
    …youtube-html5" type="text/html" width="670" height="450" src="http://www.youtu…

    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 753, Column 129: there is no attribute "height"
    …" type="text/html" width="670" height="450" src="http://www.youtube.com/embed/…

    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 753, Column 139: there is no attribute "src"
    …xt/html" width="670" height="450" src="http://www.youtube.com/embed/n_JisxlR7a…

    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 753, Column 199: cannot generate system identifier for general entity "hd"
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 199: general entity "hd" not defined and no default entity
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 201: reference not terminated by REFC delimiter
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 201: reference to external entity in attribute value
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 201: reference to entity "hd" for which no system identifier could be generated
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 198: entity was defined here
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>
  • Error Line 753, Column 217: there is no attribute "frameborder"
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 220: element "iframe" undefined
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 847, Column 45: character "(" is not allowed in the value of attribute "id"
    …iv id="gam-holder-Sportdog_Home_468x60(4)" class="gam-holder"><script type="te…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 873, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 902, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 930, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 958, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 970, Column 45: character "(" is not allowed in the value of attribute "id"
    …iv id="gam-holder-Sportdog_Home_468x60(5)" class="gam-holder"><script type="te…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 996, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 1025, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 1053, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 1081, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ommentscount"><div class="com_counter"><span class="com_count"><a href="/artic…

    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 1092, Column 45: character "(" is not allowed in the value of attribute "id"
    …iv id="gam-holder-Sportdog_Home_468x60(6)" class="gam-holder"><script type="te…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1247, Column 139: there is no attribute "target"
    …kthrgh.asp?btag=a_43645b_8007" target="_blank"><img src="/sites/default/files/…

    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 1543, Column 95: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …span class="field-content"><div class="emvideo emvideo-video emvideo-youtube"> 

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

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

  • Warning Line 1544, Column 201: reference not terminated by REFC delimiter
    …youtube.com/embed/XzeQxoIcIZ0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 1544, Column 201: reference to external entity in attribute value
    …youtube.com/embed/XzeQxoIcIZ0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 1544, Column 201: reference to entity "hd" for which no system identifier could be generated
    …youtube.com/embed/XzeQxoIcIZ0?wmode=transparent&hd=1" frameborder="0"></iframe>

    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 753, Column 198: entity was defined here
    …youtube.com/embed/n_JisxlR7a0?wmode=transparent&hd=1" frameborder="0"></iframe>
  • Error Line 1544, Column 220: element "iframe" undefined
    …youtube.com/embed/XzeQxoIcIZ0?wmode=transparent&hd=1" frameborder="0"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1695, Column 423: required attribute "alt" not specified
    …al_images/newspapers/sb28-02-13.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 782: required attribute "alt" not specified
    …_images/newspapers/17397809_920.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 1149: required attribute "alt" not specified
    …images/newspapers/17398019_6067.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 1512: required attribute "alt" not specified
    …images/newspapers/17397759_5435.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 1875: required attribute "alt" not specified
    …images/newspapers/17397853_1841.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 2241: required attribute "alt" not specified
    …images/newspapers/17397950_1854.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 2605: required attribute "alt" not specified
    …l_images/newspapers/17398072_25.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 2972: required attribute "alt" not specified
    …_images/newspapers/17396871_194.jpg" /></a></div></div></div><div class="views…

    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 1695, Column 3339: required attribute "alt" not specified
    …_images/newspapers/17397886_193.jpg" /></a></div></div></div></div></div></div…

    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 1707, Column 222: there is no attribute "scrolling"
    …header=true&amp;height=287" scrolling="no" frameborder="0" style="border:none;…

    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 1707, Column 249: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:300…

    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 1707, Column 326: there is no attribute "allowTransparency"
    …:hidden; width:300px; height:287px;" allowTransparency="true"></iframe>  </div>

    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 1707, Column 332: element "iframe" undefined
    …:hidden; width:300px; height:287px;" allowTransparency="true"></iframe>  </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 1745, Column 104: cannot generate system identifier for general entity "hide_mods"
    …com/combination_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recen…

    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 1745, Column 104: general entity "hide_mods" not defined and no default entity
    …com/combination_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recen…

    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 1745, Column 113: reference not terminated by REFC delimiter
    …nation_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt…

    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 1745, Column 113: reference to external entity in attribute value
    …nation_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt…

    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 1745, Column 113: reference to entity "hide_mods" for which no system identifier could be generated
    …nation_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt…

    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 1745, Column 103: entity was defined here
    ….com/combination_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=rece…
  • Warning Line 1745, Column 116: cannot generate system identifier for general entity "color"
    …ion_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_le…

    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 1745, Column 116: general entity "color" not defined and no default entity
    …ion_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_le…

    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 1745, Column 121: reference not terminated by REFC delimiter
    …idget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=…

    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 1745, Column 121: reference to external entity in attribute value
    …idget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=…

    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 1745, Column 121: reference to entity "color" for which no system identifier could be generated
    …idget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=…

    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 1745, Column 115: entity was defined here
    …tion_widget.js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_l…
  • Warning Line 1745, Column 127: cannot generate system identifier for general entity "default_tab"
    …js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"><…

    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 1745, Column 127: general entity "default_tab" not defined and no default entity
    …js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"><…

    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 1745, Column 138: reference not terminated by REFC delimiter
    …s=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  <…

    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 1745, Column 138: reference to external entity in attribute value
    …s=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  <…

    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 1745, Column 138: reference to entity "default_tab" for which no system identifier could be generated
    …s=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  <…

    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 1745, Column 126: entity was defined here
    ….js?num_items=5&hide_mods=1&color=grey&default_tab=recent&excerpt_length=200">…
  • Warning Line 1745, Column 146: cannot generate system identifier for general entity "excerpt_length"
    …hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  </div>

    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 1745, Column 146: general entity "excerpt_length" not defined and no default entity
    …hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  </div>

    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 1745, Column 160: reference not terminated by REFC delimiter
    …hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  </div>

    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 1745, Column 160: reference to external entity in attribute value
    …hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  </div>

    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 1745, Column 160: reference to entity "excerpt_length" for which no system identifier could be generated
    …hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  </div>

    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 1745, Column 145: entity was defined here
    …hide_mods=1&color=grey&default_tab=recent&excerpt_length=200"></script>  </div>
  • Error Line 1763, Column 169: element "iframe" undefined
    …auto; padding:0;" src="http://services.wedia.gr/innewsfeed?1"></iframe>  </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).
  • Error Line 1771, Column 10: end tag for element "div" which is not open
        </div> 

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

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

  • Warning Line 1799, Column 71: cannot generate system identifier for general entity "cg"
    …orldwide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/>…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 1799, Column 71: general entity "cg" not defined and no default entity
    …orldwide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/>…

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

  • Warning Line 1799, Column 73: reference not terminated by REFC delimiter
    …ldwide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></…

    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 1799, Column 73: reference to external entity in attribute value
    …ldwide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></…

    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 1799, Column 73: reference to entity "cg" for which no system identifier could be generated
    …ldwide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></…

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

  • Info Line 1799, Column 70: entity was defined here
    …worldwide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/…
  • Warning Line 1799, Column 76: cannot generate system identifier for general entity "cc"
    …ide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></div…

    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 1799, Column 76: general entity "cc" not defined and no default entity
    …ide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></div…

    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 1799, Column 78: reference not terminated by REFC delimiter
    …ide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></div>

    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 1799, Column 78: reference to external entity in attribute value
    …ide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></div>

    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 1799, Column 78: reference to entity "cc" for which no system identifier could be generated
    …ide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></div>

    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 1799, Column 75: entity was defined here
    …wide.com/cgi-bin/m?ci=gr-sportdog&cg=0&cc=1" style="display:none" alt=""/></di…

Visitor Analysis

Daily Visitor
  • 20.183 visits
Daily Visitor