Το απόλυτο Ελληνικό portal ...

kanalia.eu
  • Domain Name
    kanalia.eu
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #106598
  • Page Size
    14.2 KB
  • Ip Address
    46.21.146.44
  • Heading
    H1: 0, H2: 0, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 3 JPG, 1 PNG

Website Meta Analysis

  • Title
    kanalia.eu - Αρχική
  • Meta Keyword
    kanalia, watch online tv, streams, streaming, sport tv, entertainment tv, movie tv, music, news, lifestyle, kids, internet tv, streaming tv, live tv, watch online tv, hdtv, broadband, tv, free tv, online tv, wwitv, webtv, web tv, cable, player, media, live tv, live tv, tv, stream, streaming, webstream, guide, broadcast, broadcasting, webcasting, webcast, webcasts
  • Meta Description
    Το απόλυτο Ελληνικό portal

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    46.21.146.44
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from kanalia.eu.

HTML Analysis

  • date: Sun, 29 Sep 2013 05:00:15 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-type: text/html
  • content-length: 14562
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for kanalia.eu

DNS Analysis


DNS servers
ns1.greekstream.net [109.169.34.133]
ns2.greekstream.net [46.21.146.43]


DNS Records

Answer records
kanalia.eu A 46.21.146.44 3600s
kanalia.eu NS  ns2.greekstream.net 3600s
kanalia.eu NS  ns3.greekstream.net 3600s
kanalia.eu NS  ns1.greekstream.net 3600s
kanalia.eu SOA
server: ns1.greekstream.net
email: hostmaster@greekstream.net
serial: 44
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
kanalia.eu MX
preference: 10
exchange: mail.kanalia.eu
3600s

Authority records

Additional records
ns2.greekstream.net A 46.21.146.43 3600s
ns3.greekstream.net A 178.162.134.43 3600s
ns1.greekstream.net A 109.169.34.133 3600s
mail.kanalia.eu A 109.169.34.134 3600s

IP 46.21.146.44 Analysis

  • Country Code
    NL
  • Country Code3
    NLD
  • Country Name
    Netherlands
  • City
    EU
  • Continent Code
    52.5° North
  • Latitude
    5.75
  • Longitude
  • No whois ip data for 46.21.146.44

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 100 Errors
  • 67 Warnings
Ratio Text/Html
  • 0.7451303155006859
Message Error
  • Error Line 51, Column 137: there is no attribute "hspace"
    …rginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling…

    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 51, Column 148: there is no attribute "vspace"
    …0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"></ifr…

    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 53, Column 98: there is no attribute "allowtransparency"
    …"slider/slider.php" allowtransparency="true" frameborder="0" scrolling="no" he…

    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 65, Column 20: there is no attribute "cellpadding"
    <TABLE cellpadding="0" cellspacing="0" border="0" class="menu-table"><tr><td al…

    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 65, Column 36: there is no attribute "cellspacing"
    <TABLE cellpadding="0" cellspacing="0" border="0" class="menu-table"><tr><td al…

    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 65, Column 47: there is no attribute "border"
    …ellpadding="0" cellspacing="0" border="0" class="menu-table"><tr><td align="ce…

    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 65, Column 57: there is no attribute "class"
    …dding="0" cellspacing="0" border="0" class="menu-table"><tr><td align="center">

    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 65, Column 69: element "TABLE" undefined
    …dding="0" cellspacing="0" border="0" class="menu-table"><tr><td align="center">

    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 76, Column 18: end tag for element "table" which is not open
    </td></tr></table>

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

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

  • Error Line 77, Column 6: end tag for "TABLE" omitted, but OMITTAG NO was specified
    </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 65, Column 1: start tag was here
    <TABLE cellpadding="0" cellspacing="0" border="0" class="menu-table"><tr><td al…
  • Error Line 107, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_35.jpg');">

    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 108, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 108, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 108, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 108, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 108, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 117, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_36.jpg');">

    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 118, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 118, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 118, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 118, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 118, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 127, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_40.jpg');">

    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 128, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 128, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 128, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 128, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 128, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 138, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_39.jpg');">

    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 139, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 139, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 139, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 139, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 139, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 148, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_38.jpg');">

    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 149, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 149, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 149, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 149, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 149, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 158, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_41.jpg');">

    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 159, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 159, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 159, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 159, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 159, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 169, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_42.jpg');">

    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 170, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 170, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 170, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 170, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 170, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 179, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_43.jpg');">

    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 180, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 180, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 180, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 180, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 180, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 189, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_44.jpg');">

    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 190, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 190, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 190, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 190, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 190, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 197, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                      <tr><td colspan=3><div align=center><p><p><a target="_blank" …
  • Error Line 197, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …         <tr><td colspan=3><div align=center><p><p><a target="_blank" href="ht…
  • Error Line 197, Column 60: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …><td colspan=3><div align=center><p><p><a target="_blank" href="http://www.gre…

    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 200, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_45.jpg');">

    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 201, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 201, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 201, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 201, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 201, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 210, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_46.jpg');">

    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 211, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 211, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 211, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 211, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 211, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 220, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_47.jpg');">

    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 221, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 221, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 221, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 221, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 221, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 231, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_66.jpg');">

    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 232, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 232, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 232, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 232, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 232, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 241, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_37.jpg');">

    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 242, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 242, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 242, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 242, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 242, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 251, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_49.jpg');">

    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 252, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 252, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 252, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 252, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 252, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 262, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_50.jpg');">

    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 263, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 263, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 263, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 263, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 263, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 272, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_51.jpg');">

    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 273, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 273, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 273, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 273, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 273, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 282, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_91.jpg');">

    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 283, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 283, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 283, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 283, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 283, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 290, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                      <tr><td colspan=3><div align=center><p><p><a target="_blank" …
  • Error Line 290, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …         <tr><td colspan=3><div align=center><p><p><a target="_blank" href="ht…
  • Error Line 290, Column 60: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …><td colspan=3><div align=center><p><p><a target="_blank" href="http://www.gre…

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

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

  • Error Line 293, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_53.jpg');">

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

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

  • Error Line 294, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 294, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 294, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 294, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 294, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 303, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_54.jpg');">

    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 304, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 304, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 304, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 304, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 304, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 313, Column 91: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="logo-tv" style="background-image:url('upload/products/product_tn_172.jpg');">

    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 314, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 314, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 314, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 314, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 314, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 324, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_55.jpg');">

    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 325, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 325, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 325, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 325, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 325, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 334, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_56.jpg');">

    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 335, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 335, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 335, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 335, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 335, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 344, Column 90: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="logo-tv" style="background-image:url('upload/products/product_tn_57.jpg');">

    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 345, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Error Line 345, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 345, Column 19: required attribute "alt" not specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 345, Column 19: end tag for "img" omitted, but OMITTAG NO was specified
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>

    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 345, Column 3: start tag was here
    		<img src=images/border.png width=200 height=120 border=0 alt=""/>
  • Warning Line 358, Column 62: cannot generate system identifier for general entity "totalRows_Channels"
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">

    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 358, Column 62: general entity "totalRows_Channels" not defined and no default entity
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">

    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 358, Column 80: reference not terminated by REFC delimiter
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">

    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 358, Column 80: reference to external entity in attribute value
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">

    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 358, Column 80: reference to entity "totalRows_Channels" for which no system identifier could be generated
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">

    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 358, Column 61: entity was defined here
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">
  • Error Line 359, Column 103: required attribute "alt" not specified
    …mg src="images/go_previous.png" width="53" height="50" title="Previous Page" />

    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 364, Column 81: reference not terminated by REFC delimiter
    …iv align="right"><a href="/index.php?pageNum_Channels=1&totalRows_Channels=71">

    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 364, Column 81: reference to external entity in attribute value
    …iv align="right"><a href="/index.php?pageNum_Channels=1&totalRows_Channels=71">

    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 364, Column 81: reference to entity "totalRows_Channels" for which no system identifier could be generated
    …iv align="right"><a href="/index.php?pageNum_Channels=1&totalRows_Channels=71">

    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 358, Column 61: entity was defined here
    …div align="left"><a href="/index.php?pageNum_Channels=0&totalRows_Channels=71">
  • Error Line 365, Column 96: required attribute "alt" not specified
    …      <img src="images/go_next.png" width="53" height="50" title="Next Page" />

    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 385, Column 134: required attribute "alt" not specified
    …blank"><img src="maria-banner.jpg" width="300" height="250"/></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 392, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Error Line 395, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a target="_blank" href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclic…

    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 395, Column 1: start tag was here
    <br><a target="_blank" href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclic…
  • Warning Line 395, Column 82: cannot generate system identifier for general entity "hosted_button_id"
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">

    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 395, Column 82: general entity "hosted_button_id" not defined and no default entity
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">

    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 395, Column 98: reference not terminated by REFC delimiter
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">

    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 395, Column 98: reference to external entity in attribute value
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">

    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 395, Column 98: reference to entity "hosted_button_id" for which no system identifier could be generated
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">

    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 395, Column 81: entity was defined here
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">
  • Error Line 396, Column 77: required attribute "alt" not specified
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">

    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 396, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">

    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 396, Column 1: start tag was here
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">
  • Error Line 398, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 398, Column 1: start tag was here
    <br>
  • Error Line 401, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a target="_blank" href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclic…

    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 401, Column 1: start tag was here
    <br><a target="_blank" href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclic…
  • Warning Line 401, Column 98: reference not terminated by REFC delimiter
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XTR9GNSPH2QNC">

    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 401, Column 98: reference to external entity in attribute value
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XTR9GNSPH2QNC">

    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 401, Column 98: reference to entity "hosted_button_id" for which no system identifier could be generated
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XTR9GNSPH2QNC">

    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 395, Column 81: entity was defined here
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">
  • Error Line 402, Column 77: required attribute "alt" not specified
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">

    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 402, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">

    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 402, Column 1: start tag was here
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">
  • Error Line 404, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 404, Column 1: start tag was here
    <br>
  • Error Line 408, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a target="_blank" href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclic…

    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 408, Column 1: start tag was here
    <br><a target="_blank" href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclic…
  • Warning Line 408, Column 98: reference not terminated by REFC delimiter
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=Z6WJD2NX5K6H8">

    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 408, Column 98: reference to external entity in attribute value
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=Z6WJD2NX5K6H8">

    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 408, Column 98: reference to entity "hosted_button_id" for which no system identifier could be generated
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=Z6WJD2NX5K6H8">

    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 395, Column 81: entity was defined here
    …://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YT83CV3HKN24Y">
  • Error Line 409, Column 77: required attribute "alt" not specified
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">

    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 409, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">

    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 409, Column 1: start tag was here
    <img src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0">
  • Error Line 417, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Error Line 425, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Error Line 426, Column 135: required attribute "alt" not specified
    …d/homepage/news_16.jpg" width="300" height="250" border="0"/></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 433, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Error Line 441, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Error Line 449, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Error Line 457, Column 18: ID "banner_right" already defined
            <div id="banner_right">

    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 384, Column 18: ID "banner_right" first defined here
            <div id="banner_right">
  • Warning Line 482, Column 67: cannot generate system identifier for general entity "width"
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 67: general entity "width" not defined and no default entity
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 72: reference not terminated by REFC delimiter
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 72: reference to external entity in attribute value
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 72: reference to entity "width" for which no system identifier could be generated
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 66: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 482, Column 77: cannot generate system identifier for general entity "height"
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 77: general entity "height" not defined and no default entity
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 83: reference not terminated by REFC delimiter
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 83: reference to external entity in attribute value
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 83: reference to entity "height" for which no system identifier could be generated
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 76: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 482, Column 88: cannot generate system identifier for general entity "sr"
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 88: general entity "sr" not defined and no default entity
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 90: reference not terminated by REFC delimiter
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 90: reference to external entity in attribute value
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 90: reference to entity "sr" for which no system identifier could be generated
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 87: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 482, Column 92: cannot generate system identifier for general entity "font"
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 92: general entity "font" not defined and no default entity
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 96: reference not terminated by REFC delimiter
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 96: reference to external entity in attribute value
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 96: reference to entity "font" for which no system identifier could be generated
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"

    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 482, Column 91: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Error Line 483, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …   width="250" height="250" scrolling=no marginwidth=0 marginheight=0 framebor…
  • Error Line 483, Column 60: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …height="250" scrolling=no marginwidth=0 marginheight=0 frameborder=0 border=0 …
  • Error Line 483, Column 75: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no marginwidth=0 marginheight=0 frameborder=0 border=0 style="border:0…
  • Error Line 483, Column 89: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ginwidth=0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padd…
  • Error Line 483, Column 98: there is no attribute "border"
    …0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padding: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 483, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padding:0;"><…
  • Error Line 483, Column 136: document type does not allow element "iframe" here; assuming missing "li" start-tag
    …frameborder=0 border=0 style="border:0;margin:0;padding:0;"></iframe>					</ul>
  • Error Line 483, Column 155: end tag for "li" omitted, but OMITTAG NO was specified
    …frameborder=0 border=0 style="border:0;margin:0;padding:0;"></iframe>					</ul>

    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 482, Column 7: start tag was here
    						<iframe src="http://zodia123.gr/widget1_show.php?speed=2000&width=250&hei…
  • Warning Line 490, Column 80: cannot generate system identifier for general entity "color"
    …r/ticker2_vscroll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=fffff…

    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 490, Column 80: general entity "color" not defined and no default entity
    …r/ticker2_vscroll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=fffff…

    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 490, Column 85: reference not terminated by REFC delimiter
    …ker2_vscroll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgc…

    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 490, Column 85: reference to external entity in attribute value
    …ker2_vscroll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgc…

    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 490, Column 85: reference to entity "color" for which no system identifier could be generated
    …ker2_vscroll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgc…

    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 490, Column 79: entity was defined here
    …gr/ticker2_vscroll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffff…
  • Warning Line 490, Column 93: cannot generate system identifier for general entity "color2"
    …roll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ff…

    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 490, Column 93: general entity "color2" not defined and no default entity
    …roll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ff…

    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 490, Column 99: reference not terminated by REFC delimiter
    …how.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&b…

    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 490, Column 99: reference to external entity in attribute value
    …how.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&b…

    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 490, Column 99: reference to entity "color2" for which no system identifier could be generated
    …how.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&b…

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

  • Info Line 490, Column 92: entity was defined here
    …croll_show.php?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=f…
  • Warning Line 490, Column 107: cannot generate system identifier for general entity "bgcolor"
    …speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=…

    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 490, Column 107: general entity "bgcolor" not defined and no default entity
    …speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=…

    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 490, Column 114: reference not terminated by REFC delimiter
    …500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&…

    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 490, Column 114: reference to external entity in attribute value
    …500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&…

    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 490, Column 114: reference to entity "bgcolor" for which no system identifier could be generated
    …500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&…

    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 490, Column 106: entity was defined here
    …?speed=1500&color=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1…
  • Warning Line 490, Column 122: cannot generate system identifier for general entity "bgcolor2"
    …r=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&…

    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 490, Column 122: general entity "bgcolor2" not defined and no default entity
    …r=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&…

    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 490, Column 130: reference not terminated by REFC delimiter
    …&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=25…

    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 490, Column 130: reference to external entity in attribute value
    …&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=25…

    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 490, Column 130: reference to entity "bgcolor2" for which no system identifier could be generated
    …&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=25…

    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 490, Column 121: entity was defined here
    …or=5f5f5f&color2=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11…
  • Warning Line 490, Column 138: cannot generate system identifier for general entity "bgcolor1"
    …00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height…

    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 490, Column 138: general entity "bgcolor1" not defined and no default entity
    …00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height…

    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 490, Column 146: reference not terminated by REFC delimiter
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 146: reference to external entity in attribute value
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 146: reference to entity "bgcolor1" for which no system identifier could be generated
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 137: entity was defined here
    …=00aa00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&heigh…
  • Warning Line 490, Column 158: reference not terminated by REFC delimiter
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 158: reference to external entity in attribute value
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 158: reference to entity "font" for which no system identifier could be generated
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 482, Column 91: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 490, Column 167: reference not terminated by REFC delimiter
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 167: reference to external entity in attribute value
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 167: reference to entity "width" for which no system identifier could be generated
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 482, Column 66: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 490, Column 178: reference not terminated by REFC delimiter
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 178: reference to external entity in attribute value
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 490, Column 178: reference to entity "height" for which no system identifier could be generated
    …00&bgcolor=ffffff&bgcolor2=ffffff&bgcolor1=f1f1f1&font=11&width=250&height=250"

    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 482, Column 76: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Error Line 491, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …   width="250" height="250" scrolling=no marginwidth=0 marginheight=0 framebor…
  • Error Line 491, Column 60: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …height="250" scrolling=no marginwidth=0 marginheight=0 frameborder=0 border=0 …
  • Error Line 491, Column 75: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no marginwidth=0 marginheight=0 frameborder=0 border=0 style="border:0…
  • Error Line 491, Column 89: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ginwidth=0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padd…
  • Error Line 491, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padding:0;"><…
  • Error Line 491, Column 136: document type does not allow element "iframe" here; assuming missing "li" start-tag
    …frameborder=0 border=0 style="border:0;margin:0;padding:0;"></iframe>					</ul>
  • Error Line 491, Column 155: end tag for "li" omitted, but OMITTAG NO was specified
    …frameborder=0 border=0 style="border:0;margin:0;padding:0;"></iframe>					</ul>

    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 490, Column 7: start tag was here
    						<iframe src="http://ticker.agones.gr/ticker2_vscroll_show.php?speed=1500&…
  • Warning Line 498, Column 90: reference not terminated by REFC delimiter
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 90: reference to external entity in attribute value
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 90: reference to entity "width" for which no system identifier could be generated
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 482, Column 66: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 498, Column 101: reference not terminated by REFC delimiter
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 101: reference to external entity in attribute value
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 101: reference to entity "height" for which no system identifier could be generated
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 482, Column 76: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 498, Column 108: reference not terminated by REFC delimiter
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 108: reference to external entity in attribute value
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 108: reference to entity "sr" for which no system identifier could be generated
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 482, Column 87: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Warning Line 498, Column 114: reference not terminated by REFC delimiter
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 114: reference to external entity in attribute value
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 498, Column 114: reference to entity "font" for which no system identifier could be generated
    …eorasis.gr/ticker_vscroll_show.php?speed=1500&width=250&height=250&sr=&font=10"

    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 482, Column 91: entity was defined here
    …ttp://zodia123.gr/widget1_show.php?speed=2000&width=250&height=250&sr=&font=10"
  • Error Line 499, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …   width="250" height="250" scrolling=no marginwidth=0 marginheight=0 framebor…
  • Error Line 499, Column 60: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …height="250" scrolling=no marginwidth=0 marginheight=0 frameborder=0 border=0 …
  • Error Line 499, Column 75: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no marginwidth=0 marginheight=0 frameborder=0 border=0 style="border:0…
  • Error Line 499, Column 89: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ginwidth=0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padd…
  • Error Line 499, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 marginheight=0 frameborder=0 border=0 style="border:0;margin:0;padding:0;"><…
  • Error Line 499, Column 136: document type does not allow element "iframe" here; assuming missing "li" start-tag
    …frameborder=0 border=0 style="border:0;margin:0;padding:0;"></iframe>					</ul>
  • Error Line 499, Column 155: end tag for "li" omitted, but OMITTAG NO was specified
    …frameborder=0 border=0 style="border:0;margin:0;padding:0;"></iframe>					</ul>

    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 498, Column 7: start tag was here
    						<iframe src="http://programmatileorasis.gr/ticker_vscroll_show.php?speed=…
  • Error Line 519, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 84, Column 2: start tag was here
    	<div id="body_block">
  • Error Line 519, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 83, Column 1: start tag was here
    <div id="has_sidebar">

Visitor Analysis

Daily Visitor
  • 1.342 visits