woop.gr

Ζωντανές μεταδόσεις αθλητικών αγώνων και όλα τα τελευταία αθλητικά νέα και εξελίξεις από την Ελλάδα και τον κόσμο μόνο στο Woop.gr. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 25-02-2013 09:19:14  (update).

Overview Info

  • Domain Name
    woop.gr
  • Favicon
  • Alexa Rank
    #54361
  • Google Page Rank
    PR 5
  • Ip Address
    62.1.159.28
  • Page Size
    155.7 KB
  • Images
    2 GIF, 55 JPG, 14 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 29 1 2 2 0

Website Meta Analysis



  • Title
    Woop.gr - Το πρώτο αθλητικό Web TV της Ελλάδας
  • Meta Keyword
    αθλητικές μεταδόσεις, athlitikes metadoseis, αθλητικα, ζωντανες μεταδοσεις, live αγωνες, live agones, αθλητικα νεα, athlitika nea, HD agones, olympiakos agones, ολυμπιακος αγωνες, ποδοσφαιρο, μπασκετ, WRC
  • Meta Description
    Ζωντανές μεταδόσεις αθλητικών αγώνων και όλα τα τελευταία αθλητικά νέα και εξελίξεις από την Ελλάδα και τον κόσμο μόνο στο Woop.gr.

Technical Analysis



  • Webserver
    nginx/0.7.65
  • Ip Address
    62.1.159.28
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/0.7.65
  • content-type: text/html; charset=utf-8
  • x-powered-by: PHP/5.2.17
  • last-modified: Mon, 25 Feb 2013 21:17:54 GMT
  • etag: "568e862edee9630e75f15b059c4fd335"
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 23723
  • cache-control: must-revalidate, max-age=0
  • expires: Mon, 25 Feb 2013 21:19:15 GMT
  • date: Mon, 25 Feb 2013 21:19:15 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for woop.gr

DNS Analysis


DNS servers
ns2.rackspace.com [65.61.188.4]
ns.rackspace.com [69.20.95.4]


DNS Records

Answer records
woop.gr NS  ns.rackspace.com 86400s
woop.gr NS  ns2.rackspace.com 86400s
woop.gr MX
preference: 10
exchange: ASPMX.L.GOOGLE.com
86400s
woop.gr MX
preference: 30
exchange: ASPMX5.GOOGLEMAIL.com
86400s
woop.gr MX
preference: 30
exchange: ASPMX4.GOOGLEMAIL.com
86400s
woop.gr MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.com
86400s
woop.gr MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.com
86400s
woop.gr MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.com
86400s
woop.gr MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.com
86400s
woop.gr A 62.1.159.28 86400s
woop.gr SOA
server: ns.rackspace.com.woop.gr
email: hostmaster@rackspace.com.woop.gr
serial: 1320732395
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
300s

Authority records

Additional records

IP 62.1.159.28 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 114 Errors
  • 38 Warnings
Ratio Text/Html
  • 0.6522325348049668
Message Error
  • Error Line 10, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
      <meta http-equiv="refresh" content="180">

    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 10, Column 3: start tag was here
      <meta http-equiv="refresh" content="180">
  • Error Line 41, Column 72: there is no attribute "onLoad"
    …y class="front not-logged-in no-sidebars promo- home-terms" onLoad="curTime()">

    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 84, Column 76: required attribute "alt" not specified
    								<img src="/sites/all/modules/wedia/mediafilter/images/loader.gif" />

    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 116, Column 104: required attribute "alt" not specified
    …ter.com/woop_gr"><img src="/sites/all/themes/woop/images/follow_btn.png" /></a>

    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 119, Column 33: there is no attribute "src"
                        <iframe src="http://www.facebook.com/plugins/like.php?local…

    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 119, Column 306: there is no attribute "scrolling"
    …rscheme=dark&amp;height=21" 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 119, Column 323: there is no attribute "frameborder"
    …height=21" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

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

    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 119, Column 409: there is no attribute "allowTransparency"
    … overflow:hidden; width:450px; height:21px;" allowTransparency="true"></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 119, Column 415: element "iframe" undefined
    … overflow:hidden; width:450px; height:21px;" allowTransparency="true"></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 122, Column 37: there is no attribute "size"
                       	<g:plusone size="medium" href="http://www.woop.gr/"></g:plu…

    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 122, Column 51: there is no attribute "href"
    …            	<g:plusone size="medium" href="http://www.woop.gr/"></g:plusone> 	

    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 122, Column 72: element "g:plusone" undefined
    …            	<g:plusone size="medium" href="http://www.woop.gr/"></g:plusone> 	

    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 132, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    							<span class=time id=clock style="position:relative;"></span>
  • Error Line 132, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    							<span class=time id=clock style="position:relative;"></span>
  • Error Line 167, Column 249: value of attribute "name" must be a single token
    …/podosphairo/super-league" name="Super League" rel="menu item">Super League</a…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 378: value of attribute "name" must be a single token
    …airo/champions-league" name="Champions League" rel="menu item">Champions Leagu…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 505: value of attribute "name" must be a single token
    …odosphairo/europa-league" name="Europa League" rel="menu item">Europa League</…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 629: value of attribute "name" must be a single token
    …odosphairo/ethnike-omada" name="Εθνική ομάδα" rel="menu item">Εθνική ομάδα</a>…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 1365: value of attribute "name" must be a single token
    …rt-category/basket/acb-liga" name="ACB Liga" rel="menu item">ACB Liga</a></li>…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 1692: value of attribute "name" must be a single token
    …sket-2010/prophil-omadon" name="Προφίλ Ομάδων" rel="menu item">Προφίλ Ομάδων</…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 1838: value of attribute "name" must be a single token
    …/teleutaies-eideseis" name="Τελευταίες Ειδήσεις" rel="menu item">Τελευταίες Ει…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 1965: value of attribute "name" must be a single token
    …ory/basket/ethnike-omada" name="Εθνική ομάδα" rel="menu item">Εθνική ομάδα</a>…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 2526: value of attribute "name" must be a single token
    …nokineta/bmw-mini-challenge" name="BMW Mini Challenge" rel="menu item">BMW Min…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 3035: value of attribute "name" must be a single token
    …tegory/mehanokineta/jet-ski" name="Jet Ski" rel="menu item">Jet Ski</a></li><l…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 4248: character "/" is not allowed in the value of attribute "name"
    …-spor/kitesurfsnowkite" name="Kitesurf/Snowkite" rel="menu item">Kitesurf/Snow…

    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 167, Column 4600: value of attribute "name" must be a single token
    …a-spor/mixed-martial-arts" name="Mixed Martial Arts" rel="menu item">Mixed Mar…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 167, Column 5061: value of attribute "name" must be a single token
    …por/upoloipa-athlemata" name="Υπόλοιπα αθλήματα" rel="menu item">Υπόλοιπα αθλή…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 215, Column 138: ID "slide-1" already defined
    …1"><div class="slide pager-first" id="slide-1"><div class="title">O Γουαρδιόλα…

    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 206, Column 60: ID "slide-1" first defined here
    …r"><div class="slide slide-first" id="slide-1"><div class="title"><a href="/co…
  • Error Line 215, Column 146: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …class="slide pager-first" id="slide-1"><div class="title">O Γουαρδιόλα... κατα…

    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 215, Column 583: ID "slide-2" already defined
    …ref="#slide-2"><div class="slide" id="slide-2"><div class="title">Και ο Ρας σε…

    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 206, Column 1341: ID "slide-2" first defined here
    …iv></div></div><div class="slide" id="slide-2"><div class="title"><a href="/co…
  • Error Line 215, Column 591: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ide-2"><div class="slide" id="slide-2"><div class="title">Και ο Ρας σε ρυθμούς…

    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 215, Column 1035: ID "slide-3" already defined
    …ref="#slide-3"><div class="slide" id="slide-3"><div class="title">«Είναι δυνατ…

    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 206, Column 2680: ID "slide-3" first defined here
    …iv></div></div><div class="slide" id="slide-3"><div class="title"><a href="/co…
  • Error Line 215, Column 1043: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ide-3"><div class="slide" id="slide-3"><div class="title">«Είναι δυνατόν πια;»…

    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 215, Column 1490: ID "slide-4" already defined
    …-4"><div class="slide pager-last" id="slide-4"><div class="title">Η Σουόνσι δε…

    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 206, Column 3910: ID "slide-4" first defined here
    …div><div class="slide slide-last" id="slide-4"><div class="title"><a href="/co…
  • Error Line 215, Column 1498: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    … class="slide pager-last" id="slide-4"><div class="title">Η Σουόνσι δεν ξεχνά.…

    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 625, Column 104: character "&" is the first character of a delimiter but occurred as data
    …="/editorial-articles/8" title="Kings & Queens">Kings & Queens</a><div class="…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 625, Column 120: character "&" is the first character of a delimiter but occurred as data
    …icles/8" title="Kings & Queens">Kings & Queens</a><div class="view view-edarti…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 627, Column 56: character "&" is the first character of a delimiter but occurred as data
    …="/editorial-articles/8" title="Kings & Queens" >Kings & Queens</a></h4>    </…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 627, Column 73: character "&" is the first character of a delimiter but occurred as data
    …editorial-articles/8" title="Kings & Queens" >Kings & Queens</a></h4>    </div>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 655, Column 68: character "&" is the first character of a delimiter but occurred as data
    …icles/8" title="Περισσότερα από Kings & Queens..." >Περισσότερα από Kings & Qu…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 655, Column 104: character "&" is the first character of a delimiter but occurred as data
    …σσότερα από Kings & Queens..." >Περισσότερα από Kings & Queens...</a>    </div>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 697, Column 73: required attribute "alt" not specified
    …rc="/sites/default/files/once_BANNER.jpg" width="320" height="172"></a>  </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 697, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/sites/default/files/once_BANNER.jpg" width="320" height="172"></a>  </div>

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

  • Info Line 697, Column 1: start tag was here
    <img src="/sites/default/files/once_BANNER.jpg" width="320" height="172"></a>  …
  • Error Line 777, Column 70: required attribute "alt" not specified
    <a href="/sirinagirls" ><img src="/sites/default/files/sirina.jpg"  /></a>

    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 793, Column 83: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ball"><span class="article_header"><h2><a href="/home/football">Ποδόσφαιρο</a>…

    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 819, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 820, Column 165: cannot generate system identifier for general entity "t"
    …'/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσέ…

    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 820, Column 165: general entity "t" not defined and no default entity
    …'/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσέ…

    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 820, Column 166: reference not terminated by REFC delimiter
    …/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσέ'…

    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 820, Column 166: reference to external entity in attribute value
    …/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσέ'…

    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 820, Column 166: reference to entity "t" for which no system identifier could be generated
    …/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσέ'…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 822, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 848, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 849, Column 182: reference not terminated by REFC delimiter
    …ektiei-me-platania-o-katsouranes')+'&t='+encodeURIComponent('Εκτίει με Πλατανι…

    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 849, Column 182: reference to external entity in attribute value
    …ektiei-me-platania-o-katsouranes')+'&t='+encodeURIComponent('Εκτίει με Πλατανι…

    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 849, Column 182: reference to entity "t" for which no system identifier could be generated
    …ektiei-me-platania-o-katsouranes')+'&t='+encodeURIComponent('Εκτίει με Πλατανι…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 851, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 877, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 878, Column 205: reference not terminated by REFC delimiter
    …o-ergoteles-isopalia-sten-kavala')+'&t='+encodeURIComponent('Πρώτος και με δια…

    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 878, Column 205: reference to external entity in attribute value
    …o-ergoteles-isopalia-sten-kavala')+'&t='+encodeURIComponent('Πρώτος και με δια…

    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 878, Column 205: reference to entity "t" for which no system identifier could be generated
    …o-ergoteles-isopalia-sten-kavala')+'&t='+encodeURIComponent('Πρώτος και με δια…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 880, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 906, Column 88: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …cars"><span class="article_header"><h2><a href="/home/motorsports">Μηχανοκίνητ…

    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 932, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 933, Column 206: reference not terminated by REFC delimiter
    …15hrono-gio-tou-verstappen-video')+'&t='+encodeURIComponent('O Schumacher κόντ…

    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 933, Column 206: reference to external entity in attribute value
    …15hrono-gio-tou-verstappen-video')+'&t='+encodeURIComponent('O Schumacher κόντ…

    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 933, Column 206: reference to entity "t" for which no system identifier could be generated
    …15hrono-gio-tou-verstappen-video')+'&t='+encodeURIComponent('O Schumacher κόντ…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 935, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 961, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 962, Column 194: reference not terminated by REFC delimiter
    …e-phetos-thaumata-apo-te-mercede')+'&t='+encodeURIComponent('«Μη περιμένετε φέ…

    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 962, Column 194: reference to external entity in attribute value
    …e-phetos-thaumata-apo-te-mercede')+'&t='+encodeURIComponent('«Μη περιμένετε φέ…

    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 962, Column 194: reference to entity "t" for which no system identifier could be generated
    …e-phetos-thaumata-apo-te-mercede')+'&t='+encodeURIComponent('«Μη περιμένετε φέ…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 964, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 990, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 991, Column 192: reference not terminated by REFC delimiter
    …-ricciardo-einai-pia-adagonistes')+'&t='+encodeURIComponent('Vergne και Riccia…

    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 991, Column 192: reference to external entity in attribute value
    …-ricciardo-einai-pia-adagonistes')+'&t='+encodeURIComponent('Vergne και Riccia…

    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 991, Column 192: reference to entity "t" for which no system identifier could be generated
    …-ricciardo-einai-pia-adagonistes')+'&t='+encodeURIComponent('Vergne και Riccia…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 993, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1019, Column 90: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …rope"><span class="article_header"><h2><a href="/category/free-tags/diethne">Δ…

    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 1045, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1046, Column 200: reference not terminated by REFC delimiter
    …der-kai-apisteuto-autogol-videos')+'&t='+encodeURIComponent('Πρώτο γκολ για Σν…

    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 1046, Column 200: reference to external entity in attribute value
    …der-kai-apisteuto-autogol-videos')+'&t='+encodeURIComponent('Πρώτο γκολ για Σν…

    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 1046, Column 200: reference to entity "t" for which no system identifier could be generated
    …der-kai-apisteuto-autogol-videos')+'&t='+encodeURIComponent('Πρώτο γκολ για Σν…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1048, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1074, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1075, Column 174: reference not terminated by REFC delimiter
    …/101105/poios-sou-phtaiei-napoli')+'&t='+encodeURIComponent('Ποιός σου φταίει,…

    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 1075, Column 174: reference to external entity in attribute value
    …/101105/poios-sou-phtaiei-napoli')+'&t='+encodeURIComponent('Ποιός σου φταίει,…

    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 1075, Column 174: reference to entity "t" for which no system identifier could be generated
    …/101105/poios-sou-phtaiei-napoli')+'&t='+encodeURIComponent('Ποιός σου φταίει,…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1077, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1103, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1104, Column 185: reference not terminated by REFC delimiter
    …o-te-nike-prepei-na-skephtomaste')+'&t='+encodeURIComponent('«Μόνο τη νίκη πρέ…

    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 1104, Column 185: reference to external entity in attribute value
    …o-te-nike-prepei-na-skephtomaste')+'&t='+encodeURIComponent('«Μόνο τη νίκη πρέ…

    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 1104, Column 185: reference to entity "t" for which no system identifier could be generated
    …o-te-nike-prepei-na-skephtomaste')+'&t='+encodeURIComponent('«Μόνο τη νίκη πρέ…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1106, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1132, Column 89: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ther"><span class="article_header"><h2><a href="/home/othersports">Άλλα</a></h…

    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 1158, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1159, Column 182: reference not terminated by REFC delimiter
    …etoimos-gia-clasico-o-pido-photo')+'&t='+encodeURIComponent('Έτοιμος για clasi…

    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 1159, Column 182: reference to external entity in attribute value
    …etoimos-gia-clasico-o-pido-photo')+'&t='+encodeURIComponent('Έτοιμος για clasi…

    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 1159, Column 182: reference to entity "t" for which no system identifier could be generated
    …etoimos-gia-clasico-o-pido-photo')+'&t='+encodeURIComponent('Έτοιμος για clasi…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1161, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1187, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1188, Column 190: reference not terminated by REFC delimiter
    …ke-e-hathagouei-sta-oskar-photos')+'&t='+encodeURIComponent('Προκλητική η Χάθα…

    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 1188, Column 190: reference to external entity in attribute value
    …ke-e-hathagouei-sta-oskar-photos')+'&t='+encodeURIComponent('Προκλητική η Χάθα…

    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 1188, Column 190: reference to entity "t" for which no system identifier could be generated
    …ke-e-hathagouei-sta-oskar-photos')+'&t='+encodeURIComponent('Προκλητική η Χάθα…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1190, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1216, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1217, Column 178: reference not terminated by REFC delimiter
    …090/e-agonia-tes-viktoria-photos')+'&t='+encodeURIComponent('Η... αγωνία της Β…

    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 1217, Column 178: reference to external entity in attribute value
    …090/e-agonia-tes-viktoria-photos')+'&t='+encodeURIComponent('Η... αγωνία της Β…

    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 1217, Column 178: reference to entity "t" for which no system identifier could be generated
    …090/e-agonia-tes-viktoria-photos')+'&t='+encodeURIComponent('Η... αγωνία της Β…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1219, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1245, Column 90: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …sket"><span class="article_header"><h2><a href="/home/basketball">Μπάσκετ</a><…

    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 1271, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1272, Column 188: reference not terminated by REFC delimiter
    …ese-horis-spanoule-kai-mpartzoka')+'&t='+encodeURIComponent('Προπόνηση χωρίς Σ…

    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 1272, Column 188: reference to external entity in attribute value
    …ese-horis-spanoule-kai-mpartzoka')+'&t='+encodeURIComponent('Προπόνηση χωρίς Σ…

    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 1272, Column 188: reference to entity "t" for which no system identifier could be generated
    …ese-horis-spanoule-kai-mpartzoka')+'&t='+encodeURIComponent('Προπόνηση χωρίς Σ…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1274, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1300, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1301, Column 174: reference not terminated by REFC delimiter
    …/101099/vema-paramones-gia-ikaro')+'&t='+encodeURIComponent('Βήμα παραμονής γι…

    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 1301, Column 174: reference to external entity in attribute value
    …/101099/vema-paramones-gia-ikaro')+'&t='+encodeURIComponent('Βήμα παραμονής γι…

    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 1301, Column 174: reference to entity "t" for which no system identifier could be generated
    …/101099/vema-paramones-gia-ikaro')+'&t='+encodeURIComponent('Βήμα παραμονής γι…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1303, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1329, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="social">

    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 1330, Column 169: reference not terminated by REFC delimiter
    …ntent/101100/premiera-me-souedia')+'&t='+encodeURIComponent('Πρεμιέρα με Σουηδ…

    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 1330, Column 169: reference to external entity in attribute value
    …ntent/101100/premiera-me-souedia')+'&t='+encodeURIComponent('Πρεμιέρα με Σουηδ…

    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 1330, Column 169: reference to entity "t" for which no system identifier could be generated
    …ntent/101100/premiera-me-souedia')+'&t='+encodeURIComponent('Πρεμιέρα με Σουηδ…

    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 820, Column 164: entity was defined here
    …('/content/101095/nok-aout-o-totse')+'&t='+encodeURIComponent('Νοκ άουτ ο Τοτσ…
  • Error Line 1332, Column 27: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="comment-stats">

    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 1379, Column 110: there is no attribute "width"
    …gueHighlights.aspx?a_id=261070" width="300" height="410" marginheight="0" marg…

    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 1379, Column 123: there is no attribute "height"
    ….aspx?a_id=261070" width="300" height="410" marginheight="0" marginwidth="0" f…

    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 1379, Column 142: there is no attribute "marginheight"
    …width="300" height="410" marginheight="0" marginwidth="0" frameborder="0"></if…

    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 1379, Column 158: there is no attribute "marginwidth"
    …height="410" marginheight="0" marginwidth="0" frameborder="0"></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 1379, Column 177: element "iframe" undefined
    …height="410" marginheight="0" marginwidth="0" frameborder="0"></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 1397, Column 93: there is no attribute "name"
    …style="border:0px #FFFFFF none;" name="myiFrame" scrolling="no" frameborder="0…

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

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

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

  • Error Line 1397, Column 200: element "iframe" undefined
    …inheight="0px" marginwidth="0px" height="250px" width="300px"></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 1740, Column 307: element "iframe" undefined
    …tp://www.woop.gr/sites/all/themes/woop/css/facebookfunbox.css?151111"></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 1846, Column 248: value of attribute "name" must be a single token
    …/podosphairo/super-league" name="Super League" rel="menu item">Super League</a…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 377: value of attribute "name" must be a single token
    …airo/champions-league" name="Champions League" rel="menu item">Champions Leagu…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 504: value of attribute "name" must be a single token
    …odosphairo/europa-league" name="Europa League" rel="menu item">Europa League</…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 628: value of attribute "name" must be a single token
    …odosphairo/ethnike-omada" name="Εθνική ομάδα" rel="menu item">Εθνική ομάδα</a>…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 1364: value of attribute "name" must be a single token
    …rt-category/basket/acb-liga" name="ACB Liga" rel="menu item">ACB Liga</a></li>…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 1691: value of attribute "name" must be a single token
    …sket-2010/prophil-omadon" name="Προφίλ Ομάδων" rel="menu item">Προφίλ Ομάδων</…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 1837: value of attribute "name" must be a single token
    …/teleutaies-eideseis" name="Τελευταίες Ειδήσεις" rel="menu item">Τελευταίες Ει…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 1964: value of attribute "name" must be a single token
    …ory/basket/ethnike-omada" name="Εθνική ομάδα" rel="menu item">Εθνική ομάδα</a>…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 2525: value of attribute "name" must be a single token
    …nokineta/bmw-mini-challenge" name="BMW Mini Challenge" rel="menu item">BMW Min…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 3034: value of attribute "name" must be a single token
    …tegory/mehanokineta/jet-ski" name="Jet Ski" rel="menu item">Jet Ski</a></li><l…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 4247: character "/" is not allowed in the value of attribute "name"
    …-spor/kitesurfsnowkite" name="Kitesurf/Snowkite" rel="menu item">Kitesurf/Snow…

    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 1846, Column 4599: value of attribute "name" must be a single token
    …a-spor/mixed-martial-arts" name="Mixed Martial Arts" rel="menu item">Mixed Mar…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1846, Column 5060: value of attribute "name" must be a single token
    …por/upoloipa-athlemata" name="Υπόλοιπα αθλήματα" rel="menu item">Υπόλοιπα αθλή…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 1855, Column 64: there is no attribute "target"
    …<a href="http://www.intime.gr" target="_blank"><span>ΦΩΤΟΓΡΑΦΙΕΣ ΑΠΟ ΤΟ</span>…

    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 1855, Column 161: required attribute "alt" not specified
    …ΠΟ ΤΟ</span><img src="/sites/all/themes/woop/images/intime_logo.jpg"/></a></li>

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

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

  • Warning Line 1960, Column 37: character "<" is the first character of a delimiter but occurred as data
                    if (offset.top - 10 < $(window).scrollTop()) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1989, Column 71: document type does not allow element "a" here
    …ontrols").html('<a href="#" title="" class="loginslider">Eίσοδος/Εγγραφή</a>');

    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
  • 3.267 visits
Daily Visitor

In Page Analysis