Televisie, internet en telefonie via de kabel voor particulieren. Ook oplossingen voor bedrijven waaronder huurlijnen en internet. ...

telenet.be
  • Domain Name
    telenet.be
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #6109
  • Page Size
    71.2 KB
  • Ip Address
    195.162.197.132
  • Heading
    H1: 1, H2: 2, H3: 22, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 8 PNG

Website Meta Analysis

  • Title
    Telenet.be
  • Meta Keyword
  • Meta Description
    Televisie, internet en telefonie via de kabel voor particulieren. Ook oplossingen voor bedrijven waaronder huurlijnen en internet.

Technical Analysis

  • Webserver
    nginx/1.2.2
  • Ip Address
    195.162.197.132
  • Domain Age
    16 Years, 5 Months, 0 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from telenet.be.

HTML Analysis

  • server: nginx/1.2.2
  • content-type: text/html; charset=utf-8
  • x-powered-by: PHP/5.3.5
  • x-drupal-cache: MISS
  • etag: "1412694484-1"
  • content-language: nl
  • x-generator: Drupal 7 (http://drupal.org)
  • link: ; rel="canonical",; rel="shortlink"
  • last-modified: Tue, 07 Oct 2014 15:08:04 +0000
  • vary: Cookie
  • content-encoding: gzip
  • content-length: 13676
  • date: Tue, 07 Oct 2014 15:54:15 GMT
  • x-varnish: 873089290 872955168
  • age: 2769
  • via: 1.1 varnish
  • connection: keep-alive
  • x-varnish-cache: HIT C1
  • x-google-cache-control: remote-fetch
No data whois for telenet.be

IP 195.162.197.132 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 195.162.197.132

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 49 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.5690125776674393
Message Error
  • Error Line 8, Column 186: there is no attribute "property"
    …ijnen en internet." /> <meta property="og:title" content="5 maart lanceert Tel…

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

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

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

  • Error Line 35, Column 127: required attribute "type" not specified
    ….overlay.min.js" type="text/javascript"></script><script language="javascript">

    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 39, Column 29: character "&" is the first character of a delimiter but occurred as data
      var regex = new RegExp("[?&]"+key+"=([^&#]*)");

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 39, Column 42: character "&" is the first character of a delimiter but occurred as data
      var regex = new RegExp("[?&]"+key+"=([^&#]*)");

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 58, Column 8: required attribute "type" not specified
    <script>

    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 66, Column 88: document type does not allow element "div" here
    …deHoeken_WitMetGeleRand').wrap('<div class="AfgerondeHoeken_GeleRand"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 68, Column 92: document type does not allow element "div" here
    …eken_WitMetZwarteRand').wrap('<div class="AfgerondeHoeken_ZwarteRand"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 70, Column 92: document type does not allow element "div" here
    …eken_WitMetGrijzeRand').wrap('<div class="AfgerondeHoeken_GrijzeRand"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 322, Column 93: document type does not allow element "div" here
    …class="container_rounded_f5f5f5_fulla"><div class="container_rounded_f5f5f5_fu…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 323, Column 98: document type does not allow element "div" here
    …_f5f5f5_fullc').prepend('<div class="container_rounded_f5f5f5_fullc1"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 324, Column 97: document type does not allow element "div" here
    …lla').append('<div class="container_rounded_f5f5f5_fulla1"><div></div></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 325, Column 111: document type does not allow element "div" here
    …ntainer_rounded_f5f5f5_full_bordereda"><div class="container_rounded_f5f5f5_fu…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 326, Column 116: document type does not allow element "div" here
    …redc').prepend('<div class="container_rounded_f5f5f5_full_borderedc1"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 327, Column 115: document type does not allow element "div" here
    …end('<div class="container_rounded_f5f5f5_full_bordereda1"><div></div></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 328, Column 93: document type does not allow element "div" here
    …class="container_rounded_f5f5f5_w573a"><div class="container_rounded_f5f5f5_w5…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 329, Column 83: document type does not allow element "div" here
    …<div class="container_rounded_yellowa"><div class="container_rounded_yellowb">…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 330, Column 88: document type does not allow element "div" here
    …er_rounded_yellowc').prepend('<div class="container_rounded_yellowc1"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 331, Column 87: document type does not allow element "div" here
    …_yellowa').append('<div class="container_rounded_yellowa1"><div></div></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 332, Column 112: document type does not allow element "div" here
    …tainer_rounded_ffffff_border_dedede_a"><div class="container_rounded_ffffff_bo…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 333, Column 118: document type does not allow element "div" here
    …e_c').prepend('<div class="container_rounded_ffffff_border_dedede_c1"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 334, Column 117: document type does not allow element "div" here
    …nd('<div class="container_rounded_ffffff_border_dedede_a1"><div></div></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 335, Column 136: document type does not allow element "div" here
    …ed_transparent_border_c5c5c5_shadow_a"><div class="container_rounded_transpare…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 336, Column 142: document type does not allow element "div" here
    …d('<div class="container_rounded_transparent_border_c5c5c5_shadow_c1"></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 337, Column 141: document type does not allow element "div" here
    …ss="container_rounded_transparent_border_c5c5c5_shadow_a1"><div></div></div>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 410, Column 21: character "&" is the first character of a delimiter but occurred as data
    	if (vinternet == 1 && vtelefonie == 1){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 410, Column 22: character "&" is the first character of a delimiter but occurred as data
    	if (vinternet == 1 && vtelefonie == 1){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 439, Column 111: end tag for "link" omitted, but OMITTAG NO was specified
    …ttp://css.tn-media.be/thd/teleonlt136/main.css" type="text/css" media="screen">

    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 439, Column 2: start tag was here
     <link rel="stylesheet" href="http://css.tn-media.be/thd/teleonlt136/main.css" …
  • Error Line 450, Column 91: document type does not allow element "link" here
    …tylesheet" type="text/css" href="http://css.tn-media.be/loading/loading.css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 458, Column 8: required attribute "type" not specified
    <script>

    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 490, Column 181: required attribute "alt" not specified
    ….gif" width="21" height="18" border="0" /><a id="logoutbutton">Afmelden</a></a>

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

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

  • Error Line 490, Column 202: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    ….gif" width="21" height="18" border="0" /><a id="logoutbutton">Afmelden</a></a>

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

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

  • Error Line 497, Column 196: required attribute "alt" not specified
    …="https://images.tn-media.be/header/bg_zoek_button.png" 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 507, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 544, Column 54: required attribute "type" not specified
    <script src="http://telenet.be/3253/nl/general-login"></script>

    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 545, Column 8: required attribute "type" not specified
    <script>

    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 575, Column 225: an attribute specification must start with a name or name token
    …rc="http://images.tn-media.be/pr20130221/sbox_yelotv_nl.jpg" border="0"" /></a>

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 575, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="http://images.tn-media.be/pr20130221/sbox_yelotv_nl.jpg" border="0"" /></a>

    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 575, Column 148: start tag was here
    …omepage', 'sbox', 'tab1-promoclick')"><img src="http://images.tn-media.be/pr20…
  • Error Line 577, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 678, Column 200: required attribute "alt" not specified
    …page/sbox_overlayer/20120102_dtv/overlayer_promoties.png" 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 678, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …page/sbox_overlayer/20120102_dtv/overlayer_promoties.png" border="0"></a></div>

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

  • Info Line 678, Column 92: start tag was here
    …://telenet.be/222/nl/thuis/televisie"><img src="http://images.tn-media.be/home…
  • Error Line 684, Column 169: required attribute "alt" not specified
    …tn-media.be/homepage/overlayer_bg_related_previous.png" 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 687, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …20110706_dtv/overlayer_chapter1.png" alt="" width="178" height="159" ></a></li>

    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 687, Column 187: start tag was here
    …DefaultLinkFunction" href="#chapter1"><img src="http://images.tn-media.be/home…
  • Error Line 688, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …20110706_dtv/overlayer_chapter2.png" alt="" width="178" height="159" ></a></li>

    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 688, Column 187: start tag was here
    …DefaultLinkFunction" href="#chapter1"><img src="http://images.tn-media.be/home…
  • Error Line 689, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …20110706_dtv/overlayer_chapter3.png" alt="" width="178" height="159" ></a></li>

    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 689, Column 187: start tag was here
    …DefaultLinkFunction" href="#chapter1"><img src="http://images.tn-media.be/home…
  • Error Line 690, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …20110706_dtv/overlayer_chapter4.png" alt="" width="178" height="159" ></a></li>

    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 690, Column 187: start tag was here
    …DefaultLinkFunction" href="#chapter1"><img src="http://images.tn-media.be/home…
  • Error Line 691, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …20110706_dtv/overlayer_chapter5.png" alt="" width="178" height="159" ></a></li>

    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 691, Column 187: start tag was here
    …DefaultLinkFunction" href="#chapter1"><img src="http://images.tn-media.be/home…
  • Error Line 692, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …20110706_dtv/overlayer_chapter6.png" alt="" width="178" height="159" ></a></li>

    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 692, Column 187: start tag was here
    …DefaultLinkFunction" href="#chapter1"><img src="http://images.tn-media.be/home…
  • Error Line 695, Column 171: required attribute "alt" not specified
    …ics.tn-media.be/homepage/overlayer_bg_related_next.png" 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 754, Column 238: required attribute "alt" not specified
    …erlayer/20120102_sportingtelenet/overlayer_promoties.png" 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 754, Column 242: end tag for "img" omitted, but OMITTAG NO was specified
    …erlayer/20120102_sportingtelenet/overlayer_promoties.png" border="0"></a></div>

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

  • Info Line 754, Column 118: start tag was here
    …s/televisie/archief/sporting-telenet"><img src="http://images.tn-media.be/home…
  • Error Line 776, Column 193: required attribute "alt" not specified
    …epage/sbox_overlayer/20120216_fibernet/overlayer_promoties.png" border="0"></a>

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

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

  • Error Line 776, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …epage/sbox_overlayer/20120216_fibernet/overlayer_promoties.png" border="0"></a>

    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 776, Column 80: start tag was here
    …uis/internet/internet-thuis/fibernet"><img src="http://images.tn-media.be/home…
  • Warning Line 778, Column 199: cannot generate system identifier for general entity "send"
    …Fsso_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&sho…

    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 778, Column 199: general entity "send" not defined and no default entity
    …Fsso_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&sho…

    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 778, Column 203: reference not terminated by REFC delimiter
    …_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_fa…

    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 778, Column 203: reference to external entity in attribute value
    …_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_fa…

    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 778, Column 203: reference to entity "send" for which no system identifier could be generated
    …_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_fa…

    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 778, Column 198: entity was defined here
    …3Fsso_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&sh…
  • Warning Line 778, Column 210: cannot generate system identifier for general entity "layout"
    …%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=fal…

    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 778, Column 210: general entity "layout" not defined and no default entity
    …%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=fal…

    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 778, Column 216: reference not terminated by REFC delimiter
    …6campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=false&act…

    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 778, Column 216: reference to external entity in attribute value
    …6campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=false&act…

    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 778, Column 216: reference to entity "layout" for which no system identifier could be generated
    …6campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=false&act…

    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 778, Column 209: entity was defined here
    …e%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=fa…
  • Warning Line 778, Column 227: cannot generate system identifier for general entity "width"
    …Dfibernet&send=false&layout=box_count&width=95&show_faces=false&action=like&co…

    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 778, Column 227: general entity "width" not defined and no default entity
    …Dfibernet&send=false&layout=box_count&width=95&show_faces=false&action=like&co…

    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 778, Column 232: reference not terminated by REFC delimiter
    …rnet&send=false&layout=box_count&width=95&show_faces=false&action=like&colorsc…

    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 778, Column 232: reference to external entity in attribute value
    …rnet&send=false&layout=box_count&width=95&show_faces=false&action=like&colorsc…

    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 778, Column 232: reference to entity "width" for which no system identifier could be generated
    …rnet&send=false&layout=box_count&width=95&show_faces=false&action=like&colorsc…

    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 778, Column 226: entity was defined here
    …3Dfibernet&send=false&layout=box_count&width=95&show_faces=false&action=like&c…
  • Warning Line 778, Column 236: cannot generate system identifier for general entity "show_faces"
    …&send=false&layout=box_count&width=95&show_faces=false&action=like&colorscheme…

    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 778, Column 236: general entity "show_faces" not defined and no default entity
    …&send=false&layout=box_count&width=95&show_faces=false&action=like&colorscheme…

    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 778, Column 246: reference not terminated by REFC delimiter
    …e&layout=box_count&width=95&show_faces=false&action=like&colorscheme=light&fon…

    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 778, Column 246: reference to external entity in attribute value
    …e&layout=box_count&width=95&show_faces=false&action=like&colorscheme=light&fon…

    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 778, Column 246: reference to entity "show_faces" for which no system identifier could be generated
    …e&layout=box_count&width=95&show_faces=false&action=like&colorscheme=light&fon…

    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 778, Column 235: entity was defined here
    …t&send=false&layout=box_count&width=95&show_faces=false&action=like&colorschem…
  • Warning Line 778, Column 253: cannot generate system identifier for general entity "action"
    …t=box_count&width=95&show_faces=false&action=like&colorscheme=light&font=verda…

    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 778, Column 253: general entity "action" not defined and no default entity
    …t=box_count&width=95&show_faces=false&action=like&colorscheme=light&font=verda…

    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 778, Column 259: reference not terminated by REFC delimiter
    …count&width=95&show_faces=false&action=like&colorscheme=light&font=verdana&hei…

    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 778, Column 259: reference to external entity in attribute value
    …count&width=95&show_faces=false&action=like&colorscheme=light&font=verdana&hei…

    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 778, Column 259: reference to entity "action" for which no system identifier could be generated
    …count&width=95&show_faces=false&action=like&colorscheme=light&font=verdana&hei…

    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 778, Column 252: entity was defined here
    …ut=box_count&width=95&show_faces=false&action=like&colorscheme=light&font=verd…
  • Warning Line 778, Column 265: cannot generate system identifier for general entity "colorscheme"
    …width=95&show_faces=false&action=like&colorscheme=light&font=verdana&height=90…

    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 778, Column 265: general entity "colorscheme" not defined and no default entity
    …width=95&show_faces=false&action=like&colorscheme=light&font=verdana&height=90…

    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 778, Column 276: reference not terminated by REFC delimiter
    …ow_faces=false&action=like&colorscheme=light&font=verdana&height=90&appId=2124…

    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 778, Column 276: reference to external entity in attribute value
    …ow_faces=false&action=like&colorscheme=light&font=verdana&height=90&appId=2124…

    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 778, Column 276: reference to entity "colorscheme" for which no system identifier could be generated
    …ow_faces=false&action=like&colorscheme=light&font=verdana&height=90&appId=2124…

    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 778, Column 264: entity was defined here
    …&width=95&show_faces=false&action=like&colorscheme=light&font=verdana&height=9…
  • Warning Line 778, Column 283: cannot generate system identifier for general entity "font"
    …s=false&action=like&colorscheme=light&font=verdana&height=90&appId=21247536209…

    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 778, Column 283: general entity "font" not defined and no default entity
    …s=false&action=like&colorscheme=light&font=verdana&height=90&appId=21247536209…

    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 778, Column 287: reference not terminated by REFC delimiter
    …lse&action=like&colorscheme=light&font=verdana&height=90&appId=212475362095892…

    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 778, Column 287: reference to external entity in attribute value
    …lse&action=like&colorscheme=light&font=verdana&height=90&appId=212475362095892…

    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 778, Column 287: reference to entity "font" for which no system identifier could be generated
    …lse&action=like&colorscheme=light&font=verdana&height=90&appId=212475362095892…

    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 778, Column 282: entity was defined here
    …es=false&action=like&colorscheme=light&font=verdana&height=90&appId=2124753620…
  • Warning Line 778, Column 296: cannot generate system identifier for general entity "height"
    …n=like&colorscheme=light&font=verdana&height=90&appId=212475362095892" scrolli…

    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 778, Column 296: general entity "height" not defined and no default entity
    …n=like&colorscheme=light&font=verdana&height=90&appId=212475362095892" scrolli…

    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 778, Column 302: reference not terminated by REFC delimiter
    …&colorscheme=light&font=verdana&height=90&appId=212475362095892" scrolling="no…

    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 778, Column 302: reference to external entity in attribute value
    …&colorscheme=light&font=verdana&height=90&appId=212475362095892" scrolling="no…

    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 778, Column 302: reference to entity "height" for which no system identifier could be generated
    …&colorscheme=light&font=verdana&height=90&appId=212475362095892" scrolling="no…

    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 778, Column 295: entity was defined here
    …on=like&colorscheme=light&font=verdana&height=90&appId=212475362095892" scroll…
  • Warning Line 778, Column 306: cannot generate system identifier for general entity "appId"
    …orscheme=light&font=verdana&height=90&appId=212475362095892" scrolling="no" fr…

    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 778, Column 306: general entity "appId" not defined and no default entity
    …orscheme=light&font=verdana&height=90&appId=212475362095892" scrolling="no" fr…

    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 778, Column 311: reference not terminated by REFC delimiter
    …eme=light&font=verdana&height=90&appId=212475362095892" scrolling="no" framebo…

    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 778, Column 311: reference to external entity in attribute value
    …eme=light&font=verdana&height=90&appId=212475362095892" scrolling="no" framebo…

    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 778, Column 311: reference to entity "appId" for which no system identifier could be generated
    …eme=light&font=verdana&height=90&appId=212475362095892" scrolling="no" framebo…

    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 778, Column 305: entity was defined here
    …lorscheme=light&font=verdana&height=90&appId=212475362095892" scrolling="no" f…
  • Error Line 778, Column 441: there is no attribute "allowTransparency"
    …flow:hidden; width:95px; height:90px;" allowTransparency="true"></iframe></div>

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

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

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

  • Error Line 811, Column 33: required attribute "type" not specified
    			<script language="javascript">

    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 819, Column 8: character "<" is the first character of a delimiter but occurred as data
    	if (5 < x){x=1;}

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 831, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 839, Column 23: character "<" is the first character of a delimiter but occurred as data
    		if (RememberTheLeft < 0){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 862, Column 173: required attribute "alt" not specified
    …g src="http://images.tn-media.be/pr20130221/block_promo_nl.png" border="0"></a>

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

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

  • Error Line 862, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="http://images.tn-media.be/pr20130221/block_promo_nl.png" border="0"></a>

    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 862, Column 96: start tag was here
    …digitale-tv-telefonie/fibernet-shake"><img src="http://images.tn-media.be/pr20…
  • Error Line 866, Column 247: required attribute "alt" not specified
    …mages.tn-media.be/homepage/block_20120919_sporting3maanden10euro_nl.gif" /></a>

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

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

  • Error Line 870, Column 191: required attribute "alt" not specified
    …rc="http://images.tn-media.be/homepage/block_20130208_snow.gif" border="0"></a>

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

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

  • Error Line 870, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="http://images.tn-media.be/homepage/block_20130208_snow.gif" border="0"></a>

    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 870, Column 111: start tag was here
    …net-met-anderen/een-huis-vol-plezier"><img src="http://images.tn-media.be/home…
  • Error Line 878, Column 195: required attribute "alt" not specified
    …="http://images.tn-media.be/header/bg_zoek_button2.png" 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>.

  • Warning Line 895, Column 185: character "&" is the first character of a delimiter but occurred as data
    …categorie-promoacties');" class="HelpCat" id="Cat_promo">Promoties & Acties</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 903, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …3715/nl/thuis/prijsindexering" target=_blank> Indexering van onze tarieven van…
  • Error Line 904, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meer-info/veelgestelde-vragen" target=_blank> Graag KING of KONG met smartphon…
  • Error Line 905, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …net-security-pack-installeren" target=_blank> Hoe Telenet Security Pack instal…
  • Error Line 906, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et.be/content/wat-is-phishing" target=_blank> Opgelet voor e-mailfraude!</a></…
  • Error Line 907, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ade-van-telenet-security-pack" target=_blank> Een probleem bij de upgrade van …
  • Error Line 908, Column 137: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dloze-internetverbinding-wifi" target=_blank> Ik heb een probleem met mijn dra…
  • Error Line 909, Column 69: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/klantenservice-be.telenet.be" target=_blank> Mobiel toestel instellen?</a></l…
  • Error Line 910, Column 128: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ant-en-wil-overstappen-wat-nu" target=_blank> Ik ben Telenet Mobile-klant en w…
  • Error Line 931, Column 136: end tag for element "span" which is not open
    …e/mijntelenet/account/recoverPassword.do">Wachtwoord vergeten?</a></span></div>

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

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

  • Error Line 945, Column 115: required attribute "alt" not specified
    …t: 6px;"><img src="http://graphics.tn-media.be/homepage/bg_top_SM.png" /></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>.

  • Warning Line 959, Column 136: character "&" is the first character of a delimiter but occurred as data
    …lugins/like.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.fac…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 959, Column 138: cannot generate system identifier for general entity "locale"
    …gins/like.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.faceb…

    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 959, Column 138: general entity "locale" not defined and no default entity
    …gins/like.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.faceb…

    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 959, Column 144: reference not terminated by REFC delimiter
    …ike.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.co…

    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 959, Column 144: reference to external entity in attribute value
    …ike.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.co…

    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 959, Column 144: reference to entity "locale" for which no system identifier could be generated
    …ike.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.co…

    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 959, Column 137: entity was defined here
    …ugins/like.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.face…
  • Warning Line 959, Column 151: cannot generate system identifier for general entity "href"
    …?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Ftel…

    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 959, Column 151: general entity "href" not defined and no default entity
    …?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Ftel…

    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 959, Column 155: reference not terminated by REFC delimiter
    …_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Ftelenet…

    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 959, Column 155: reference to external entity in attribute value
    …_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Ftelenet…

    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 959, Column 155: reference to entity "href" for which no system identifier could be generated
    …_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Ftelenet…

    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 959, Column 150: entity was defined here
    …p?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Fte…
  • Warning Line 959, Column 200: reference not terminated by REFC delimiter
    …A%2F%2Fwww.facebook.com%2Ftelenet&send=false&layout=button_count&width=100&loc…

    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 959, Column 200: reference to external entity in attribute value
    …A%2F%2Fwww.facebook.com%2Ftelenet&send=false&layout=button_count&width=100&loc…

    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 959, Column 200: reference to entity "send" for which no system identifier could be generated
    …A%2F%2Fwww.facebook.com%2Ftelenet&send=false&layout=button_count&width=100&loc…

    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 778, Column 198: entity was defined here
    …3Fsso_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&sh…
  • Warning Line 959, Column 213: reference not terminated by REFC delimiter
    …cebook.com%2Ftelenet&send=false&layout=button_count&width=100&locale=en_US&nod…

    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 959, Column 213: reference to external entity in attribute value
    …cebook.com%2Ftelenet&send=false&layout=button_count&width=100&locale=en_US&nod…

    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 959, Column 213: reference to entity "layout" for which no system identifier could be generated
    …cebook.com%2Ftelenet&send=false&layout=button_count&width=100&locale=en_US&nod…

    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 778, Column 209: entity was defined here
    …e%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=fa…
  • Warning Line 959, Column 232: reference not terminated by REFC delimiter
    …t&send=false&layout=button_count&width=100&locale=en_US&node_type=link&show_fa…

    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 959, Column 232: reference to external entity in attribute value
    …t&send=false&layout=button_count&width=100&locale=en_US&node_type=link&show_fa…

    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 959, Column 232: reference to entity "width" for which no system identifier could be generated
    …t&send=false&layout=button_count&width=100&locale=en_US&node_type=link&show_fa…

    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 778, Column 226: entity was defined here
    …3Dfibernet&send=false&layout=box_count&width=95&show_faces=false&action=like&c…
  • Warning Line 959, Column 243: reference not terminated by REFC delimiter
    …e&layout=button_count&width=100&locale=en_US&node_type=link&show_faces=false&a…

    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 959, Column 243: reference to external entity in attribute value
    …e&layout=button_count&width=100&locale=en_US&node_type=link&show_faces=false&a…

    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 959, Column 243: reference to entity "locale" for which no system identifier could be generated
    …e&layout=button_count&width=100&locale=en_US&node_type=link&show_faces=false&a…

    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 959, Column 137: entity was defined here
    …ugins/like.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.face…
  • Warning Line 959, Column 250: cannot generate system identifier for general entity "node_type"
    …t=button_count&width=100&locale=en_US&node_type=link&show_faces=false&action=l…

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

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

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

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

  • Error Line 959, Column 250: general entity "node_type" not defined and no default entity
    …t=button_count&width=100&locale=en_US&node_type=link&show_faces=false&action=l…

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

  • Warning Line 959, Column 259: reference not terminated by REFC delimiter
    …count&width=100&locale=en_US&node_type=link&show_faces=false&action=like&color…

    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 959, Column 259: reference to external entity in attribute value
    …count&width=100&locale=en_US&node_type=link&show_faces=false&action=like&color…

    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 959, Column 259: reference to entity "node_type" for which no system identifier could be generated
    …count&width=100&locale=en_US&node_type=link&show_faces=false&action=like&color…

    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 959, Column 249: entity was defined here
    …ut=button_count&width=100&locale=en_US&node_type=link&show_faces=false&action=…
  • Warning Line 959, Column 275: reference not terminated by REFC delimiter
    …locale=en_US&node_type=link&show_faces=false&action=like&colorscheme=light&fon…

    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 959, Column 275: reference to external entity in attribute value
    …locale=en_US&node_type=link&show_faces=false&action=like&colorscheme=light&fon…

    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 959, Column 275: reference to entity "show_faces" for which no system identifier could be generated
    …locale=en_US&node_type=link&show_faces=false&action=like&colorscheme=light&fon…

    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 778, Column 235: entity was defined here
    …t&send=false&layout=box_count&width=95&show_faces=false&action=like&colorschem…
  • Warning Line 959, Column 288: reference not terminated by REFC delimiter
    …node_type=link&show_faces=false&action=like&colorscheme=light&font&height=35" …

    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 959, Column 288: reference to external entity in attribute value
    …node_type=link&show_faces=false&action=like&colorscheme=light&font&height=35" …

    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 959, Column 288: reference to entity "action" for which no system identifier could be generated
    …node_type=link&show_faces=false&action=like&colorscheme=light&font&height=35" …

    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 778, Column 252: entity was defined here
    …ut=box_count&width=95&show_faces=false&action=like&colorscheme=light&font=verd…
  • Warning Line 959, Column 305: reference not terminated by REFC delimiter
    …ow_faces=false&action=like&colorscheme=light&font&height=35" scrolling="no" fr…

    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 959, Column 305: reference to external entity in attribute value
    …ow_faces=false&action=like&colorscheme=light&font&height=35" scrolling="no" fr…

    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 959, Column 305: reference to entity "colorscheme" for which no system identifier could be generated
    …ow_faces=false&action=like&colorscheme=light&font&height=35" scrolling="no" fr…

    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 778, Column 264: entity was defined here
    …&width=95&show_faces=false&action=like&colorscheme=light&font=verdana&height=9…
  • Warning Line 959, Column 316: reference not terminated by REFC delimiter
    …lse&action=like&colorscheme=light&font&height=35" scrolling="no" frameborder="…

    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 959, Column 316: reference to external entity in attribute value
    …lse&action=like&colorscheme=light&font&height=35" scrolling="no" frameborder="…

    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 959, Column 316: reference to entity "font" for which no system identifier could be generated
    …lse&action=like&colorscheme=light&font&height=35" scrolling="no" frameborder="…

    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 778, Column 282: entity was defined here
    …es=false&action=like&colorscheme=light&font=verdana&height=90&appId=2124753620…
  • Warning Line 959, Column 323: reference not terminated by REFC delimiter
    …ion=like&colorscheme=light&font&height=35" scrolling="no" frameborder="0" styl…

    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 959, Column 323: reference to external entity in attribute value
    …ion=like&colorscheme=light&font&height=35" scrolling="no" frameborder="0" styl…

    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 959, Column 323: reference to entity "height" for which no system identifier could be generated
    …ion=like&colorscheme=light&font&height=35" scrolling="no" frameborder="0" styl…

    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 778, Column 295: entity was defined here
    …on=like&colorscheme=light&font=verdana&height=90&appId=212475362095892" scroll…
  • Error Line 965, Column 116: required attribute "alt" not specified
    …"><img src="http://i.ytimg.com/vi/_1zjqNXZySg/default.jpg" height="38" /></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 989, Column 351: end tag for "img" omitted, but OMITTAG NO was specified
    … - Meer weten" src="https://graphics.tn-media.be/footer2011/bg_top_nl.png"></a>

    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 989, Column 139: start tag was here
    …'homepage', 'footer', 'why-online');"><img width="940" height="92" border="0" …
  • Warning Line 999, Column 188: character "&" is the first character of a delimiter but occurred as data
    …s/shakes/internet-digitale-tv-telefonie">Internet & Digitale tv & Telefonie</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 999, Column 202: character "&" is the first character of a delimiter but occurred as data
    …s/shakes/internet-digitale-tv-telefonie">Internet & Digitale tv & Telefonie</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1002, Column 174: character "&" is the first character of a delimiter but occurred as data
    …elenet.be/1115/nl/thuis/shakes/internet-digitale-tv">Internet & Digitale tv</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1005, Column 178: character "&" is the first character of a delimiter but occurred as data
    …enet.be/1116/nl/thuis/shakes/digitale-tv-telefonie">Digitale tv & Telefonie</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1055, Column 109: required attribute "alt" not specified
    …up2"><img src="https://graphics.tn-media.be/spacer.gif" width="1" height="1" />

    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 1098, Column 169: duplicate specification of attribute "target"
    …et="_blank" href="http://events.telenet.be/" target="_blank">Telenet Events</a>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1101, Column 180: duplicate specification of attribute "target"
    …nk" href="http://events.telenet.be/wedstrijden" target="_blank">Wedstrijden</a>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1118, Column 109: required attribute "alt" not specified
    …up2"><img src="https://graphics.tn-media.be/spacer.gif" width="1" height="1" />

    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 1166, Column 234: required attribute "alt" not specified
    …aphics.tn-media.be/footer/divider.png"><a onclick="pageTracker._trackEvent('fo…

    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 1166, Column 235: end tag for "img" omitted, but OMITTAG NO was specified
    …phics.tn-media.be/footer/divider.png"><a onclick="pageTracker._trackEvent('foo…

    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 1166, Column 127: start tag was here
    … href="/jobs" target="_blank">Jobs</a><img width="1" height="10" border="0" cl…
  • Error Line 1166, Column 525: required attribute "alt" not specified
    …aphics.tn-media.be/footer/divider.png"><a onclick="pageTracker._trackEvent('fo…

    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 1166, Column 526: end tag for "img" omitted, but OMITTAG NO was specified
    …phics.tn-media.be/footer/divider.png"><a onclick="pageTracker._trackEvent('foo…

    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 1166, Column 418: start tag was here
    …informatie en algemene voorwaarden</a><img width="1" height="10" border="0" cl…
  • Error Line 1166, Column 811: required attribute "alt" not specified
    …aphics.tn-media.be/footer/divider.png"><a onclick="pageTracker._trackEvent('fo…

    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 1166, Column 812: end tag for "img" omitted, but OMITTAG NO was specified
    …phics.tn-media.be/footer/divider.png"><a onclick="pageTracker._trackEvent('foo…

    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 1166, Column 704: start tag was here
    …/tarieven">Kabeltelevisie tarieven</a><img width="1" height="10" border="0" cl…
  • Error Line 1166, Column 1238: required attribute "alt" not specified
    …aphics.tn-media.be/footer/divider.png"><a target="_blank" href="http://www.bec…

    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 1166, Column 1239: end tag for "img" omitted, but OMITTAG NO was specified
    …phics.tn-media.be/footer/divider.png"><a target="_blank" href="http://www.beco…

    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 1166, Column 1131: start tag was here
    …ichtingen">Consumenteninlichtingen</a><img width="1" height="10" border="0" cl…
  • Error Line 1166, Column 1367: required attribute "alt" not specified
    …tn-media.be/footer/ill_becommerce.png"></a><a target="_blank" href="http://www…

    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 1166, Column 1371: end tag for "img" omitted, but OMITTAG NO was specified
    …edia.be/footer/ill_becommerce.png"></a><a target="_blank" href="http://www.uni…

    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 1166, Column 1291: start tag was here
    …ank" href="http://www.becommerce.be/"><img border="0" src="https://graphics.tn…
  • Error Line 1166, Column 1505: required attribute "alt" not specified
    …hics.tn-media.be/footer/ill_unizo.png"></a><a target="_blank" href="http://nl.…

    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 1166, Column 1509: end tag for "img" omitted, but OMITTAG NO was specified
    ….tn-media.be/footer/ill_unizo.png"></a><a target="_blank" href="http://nl.glob…

    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 1166, Column 1434: start tag was here
    …"http://www.unizo.be/e-commercelabel"><img border="0" src="https://graphics.tn…
  • Error Line 1166, Column 1641: required attribute "alt" not specified
    …tn-media.be/footer/ill_globalsign.png"></a><img width="1" height="10" border="…

    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 1166, Column 1645: end tag for "img" omitted, but OMITTAG NO was specified
    …edia.be/footer/ill_globalsign.png"></a><img width="1" height="10" border="0" c…

    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 1166, Column 1565: start tag was here
    …" href="http://nl.globalsign.com/nl/"><img border="0" src="https://graphics.tn…
  • Error Line 1166, Column 1753: required attribute "alt" not specified
    …rder="0" class="divider" src="https://graphics.tn-media.be/footer/divider.png">

    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 1166, Column 1754: end tag for "img" omitted, but OMITTAG NO was specified
    …rder="0" class="divider" src="https://graphics.tn-media.be/footer/divider.png">

    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 1166, Column 1646: start tag was here
    …dia.be/footer/ill_globalsign.png"></a><img width="1" height="10" border="0" cl…
  • Warning Line 1178, Column 102: character "&" is the first character of a delimiter but occurred as data
    …lugins/like.php?app_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.fac…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1178, Column 110: reference not terminated by REFC delimiter
    …ike.php?app_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.facebook.co…

    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 1178, Column 110: reference to external entity in attribute value
    …ike.php?app_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.facebook.co…

    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 1178, Column 110: reference to entity "locale" for which no system identifier could be generated
    …ike.php?app_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.facebook.co…

    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 959, Column 137: entity was defined here
    …ugins/like.php?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.face…
  • Warning Line 1178, Column 121: reference not terminated by REFC delimiter
    …_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.facebook.com%2Ftelenet…

    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 1178, Column 121: reference to external entity in attribute value
    …_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.facebook.com%2Ftelenet…

    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 1178, Column 121: reference to entity "href" for which no system identifier could be generated
    …_id=200296703347507&&locale=nl_NL&href=http%3A%2F%2Fwww.facebook.com%2Ftelenet…

    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 959, Column 150: entity was defined here
    …p?app_id=200296703347507&&locale=nl_BE&href=http%3A%2F%2Fwww.facebook.com%2Fte…
  • Warning Line 1178, Column 166: reference not terminated by REFC delimiter
    …A%2F%2Fwww.facebook.com%2Ftelenet&send=false&layout=standard&width=450&show_fa…

    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 1178, Column 166: reference to external entity in attribute value
    …A%2F%2Fwww.facebook.com%2Ftelenet&send=false&layout=standard&width=450&show_fa…

    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 1178, Column 166: reference to entity "send" for which no system identifier could be generated
    …A%2F%2Fwww.facebook.com%2Ftelenet&send=false&layout=standard&width=450&show_fa…

    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 778, Column 198: entity was defined here
    …3Fsso_ignore%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&sh…
  • Warning Line 1178, Column 179: reference not terminated by REFC delimiter
    …cebook.com%2Ftelenet&send=false&layout=standard&width=450&show_faces=false&act…

    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 1178, Column 179: reference to external entity in attribute value
    …cebook.com%2Ftelenet&send=false&layout=standard&width=450&show_faces=false&act…

    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 1178, Column 179: reference to entity "layout" for which no system identifier could be generated
    …cebook.com%2Ftelenet&send=false&layout=standard&width=450&show_faces=false&act…

    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 778, Column 209: entity was defined here
    …e%3D1%26campaign%3Dfibernet&send=false&layout=box_count&width=95&show_faces=fa…
  • Warning Line 1178, Column 194: reference not terminated by REFC delimiter
    …lenet&send=false&layout=standard&width=450&show_faces=false&action=like&colors…

    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 1178, Column 194: reference to external entity in attribute value
    …lenet&send=false&layout=standard&width=450&show_faces=false&action=like&colors…

    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 1178, Column 194: reference to entity "width" for which no system identifier could be generated
    …lenet&send=false&layout=standard&width=450&show_faces=false&action=like&colors…

    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 778, Column 226: entity was defined here
    …3Dfibernet&send=false&layout=box_count&width=95&show_faces=false&action=like&c…
  • Warning Line 1178, Column 209: reference not terminated by REFC delimiter
    …e&layout=standard&width=450&show_faces=false&action=like&colorscheme=light&fon…

    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 1178, Column 209: reference to external entity in attribute value
    …e&layout=standard&width=450&show_faces=false&action=like&colorscheme=light&fon…

    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 1178, Column 209: reference to entity "show_faces" for which no system identifier could be generated
    …e&layout=standard&width=450&show_faces=false&action=like&colorscheme=light&fon…

    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 778, Column 235: entity was defined here
    …t&send=false&layout=box_count&width=95&show_faces=false&action=like&colorschem…
  • Warning Line 1178, Column 222: reference not terminated by REFC delimiter
    …dard&width=450&show_faces=false&action=like&colorscheme=light&font&height=35" …

    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 1178, Column 222: reference to external entity in attribute value
    …dard&width=450&show_faces=false&action=like&colorscheme=light&font&height=35" …

    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 1178, Column 222: reference to entity "action" for which no system identifier could be generated
    …dard&width=450&show_faces=false&action=like&colorscheme=light&font&height=35" …

    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 778, Column 252: entity was defined here
    …ut=box_count&width=95&show_faces=false&action=like&colorscheme=light&font=verd…
  • Warning Line 1178, Column 239: reference not terminated by REFC delimiter
    …ow_faces=false&action=like&colorscheme=light&font&height=35" scrolling="no" fr…

    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 1178, Column 239: reference to external entity in attribute value
    …ow_faces=false&action=like&colorscheme=light&font&height=35" scrolling="no" fr…

    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 1178, Column 239: reference to entity "colorscheme" for which no system identifier could be generated
    …ow_faces=false&action=like&colorscheme=light&font&height=35" scrolling="no" fr…

    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 778, Column 264: entity was defined here
    …&width=95&show_faces=false&action=like&colorscheme=light&font=verdana&height=9…
  • Warning Line 1178, Column 250: reference not terminated by REFC delimiter
    …lse&action=like&colorscheme=light&font&height=35" scrolling="no" frameborder="…

    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 1178, Column 250: reference to external entity in attribute value
    …lse&action=like&colorscheme=light&font&height=35" scrolling="no" frameborder="…

    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 1178, Column 250: reference to entity "font" for which no system identifier could be generated
    …lse&action=like&colorscheme=light&font&height=35" scrolling="no" frameborder="…

    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 778, Column 282: entity was defined here
    …es=false&action=like&colorscheme=light&font=verdana&height=90&appId=2124753620…
  • Warning Line 1178, Column 257: reference not terminated by REFC delimiter
    …ion=like&colorscheme=light&font&height=35" scrolling="no" frameborder="0" styl…

    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 1178, Column 257: reference to external entity in attribute value
    …ion=like&colorscheme=light&font&height=35" scrolling="no" frameborder="0" styl…

    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 1178, Column 257: reference to entity "height" for which no system identifier could be generated
    …ion=like&colorscheme=light&font&height=35" scrolling="no" frameborder="0" styl…

    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 778, Column 295: entity was defined here
    …on=like&colorscheme=light&font=verdana&height=90&appId=212475362095892" scroll…
  • Warning Line 1228, Column 153: cannot generate system identifier for general entity "guid"
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 153: general entity "guid" not defined and no default entity
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 157: reference not terminated by REFC delimiter
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 157: reference to external entity in attribute value
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 157: reference to entity "guid" for which no system identifier could be generated
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 152: entity was defined here
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>
  • Warning Line 1228, Column 161: cannot generate system identifier for general entity "script"
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 161: general entity "script" not defined and no default entity
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 167: reference not terminated by REFC delimiter
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 167: reference to external entity in attribute value
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 167: reference to entity "script" for which no system identifier could be generated
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>

    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 1228, Column 160: entity was defined here
    ….com/pagead/conversion/996020579/?label=fDzsCOW-1QIQ46L42gM&guid=ON&script=0"/>
  • Error Line 1232, Column 8: required attribute "type" not specified
    <script>

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

Visitor Analysis

Daily Visitor
  • 24.500 visits