vi.nl has Alexa Rank 6.979 and Google Page Rank is 5

vi.nl
  • Domain Name
    vi.nl
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #6979
  • Page Size
    139 B
  • Ip Address
    213.75.28.140
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    redirect
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    213.75.28.140
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from vi.nl.

HTML Analysis

  • server: Apache
  • last-modified: Wed, 07 May 2014 07:47:01 GMT
  • etag: "b09df0-97-4f8ca91db6740"
  • x-served-server: pvapps170
  • content-type: text/html; charset=utf-8
  • x-url: /
  • x-host: www.vi.nl
  • x-host-url: www.vi.nl/
  • x-cache-server: pproxy15
  • vary: Accept-Encoding
  • content-length: 151
  • accept-ranges: bytes
  • date: Thu, 24 Jul 2014 12:05:17 GMT
  • x-varnish: 194106955 194076888
  • age: 101
  • via: 1.1 varnish
  • connection: keep-alive
  • x-cache-hits: 3
  • x-google-cache-control: remote-fetch
Domain Domain Name: vi.nl
Domain Status: active
Registrar:
XS4ALL Internet B.V. *
Teleportboulevard 121
1043EJ Amsterdam
Netherlands

Name Servers:
ns.xs4all.nl
ns.xs4all.nl
ns2.xs4all.nl
ns2.xs4all.nl
Registrar: NL Domain Registry
Copyright notice
No part of this publication may be reproduced, published, stored in a
retrieval system, or transmitted, in any form or by any means,
electronic, mechanical, recording, or otherwise, without prior
permission of the Foundation for Internet Domain Registration in the
Netherlands (SIDN).
These restrictions apply equally to registrars, except in that
reproductions and publications are permitted insofar as they are
reasonable, necessary and solely in the context of the registration
activities referred to in the General Terms and Conditions for .nl
Registrars.
Any use of this material for advertising, targeting commercial offers or
similar activities is explicitly forbidden and liable to result in legal
action. Anyone who is aware or suspects that such activities are taking
place is asked to inform the Foundation for Internet Domain Registration
in the Netherlands.
(c) The Foundation for Internet Domain Registration in the Netherlands
(SIDN) Dutch Copyright Act, protection of authors' rights (Section 10,
subsection 1, clause 1).

IP 213.75.28.140 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 1 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.7913669064748201
Message Error
  • Error Line 4, Column 17: there is no attribute "property"
    	<meta property="fb:page_id" content="215198838503274" />

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

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

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

  • Error Line 31, Column 146: document type does not allow element "script" here
    …/scripts/libs/jquery-1.7.1.min.js" type="text/javascript"><\/script>')</script>

    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 31, Column 147: character "<" is the first character of a delimiter but occurred as data
    …/scripts/libs/jquery-1.7.1.min.js" type="text/javascript"><\/script>')</script>

    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 32, Column 107: document type does not allow element "script" here
    …text/javascript" src="/static/vi/scripts/libs/jquery.timers-1.0.0.js"></script>

    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 33, Column 97: document type does not allow element "script" here
    …pt" type="text/javascript" src="/static/vi/scripts/vi_scripts.min.js"></script>

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

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

  • Error Line 34, Column 89: document type does not allow element "script" here
    …javascript" type="text/javascript" src="/static/vi/scripts/gx.min.js"></script>

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

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

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

  • Error Line 39, Column 83: document type does not allow element "script" here
    …e="text/javascript" src="http://smartbase.cdnservices.net/megatag.js"></script>

    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 40, Column 101: document type does not allow element "script" here
    …javascript' src='http://partner.googleadservices.com/gampad/google_service.js'>

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

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

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

  • Error Line 46, Column 35: document type does not allow element "script" here
        <script type="text/javascript">

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

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

  • Error Line 49, Column 35: document type does not allow element "script" here
        <script type='text/javascript'>

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

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

  • Error Line 72, Column 35: document type does not allow element "script" here
        <script type='text/javascript'>

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

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

  • Error Line 76, Column 33: document type does not allow element "script" here
    		<script type="text/javascript">

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

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

  • Error Line 93, Column 33: document type does not allow element "script" here
    		<script type="text/javascript">function comScore(t)

    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 97, Column 48: character ";" not allowed in attribute specification list
    		{p=o.cookie.split(";");for(h=0,f=p.length;h<f;h++)
  • Error Line 97, Column 48: element "f" undefined
    		{p=o.cookie.split(";");for(h=0,f=p.length;h<f;h++)

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 99, Column 7: character "&" is the first character of a delimiter but occurred as data
    		{a="&"+unescape(p[h].substring(q+b.length+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 100, Column 9: cannot generate system identifier for general entity "ns__t"
    		t=t+"&ns__t="+(new

    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 100, Column 9: general entity "ns__t" not defined and no default entity
    		t=t+"&ns__t="+(new

    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 100, Column 14: reference not terminated by REFC delimiter
    		t=t+"&ns__t="+(new

    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.

  • Error Line 100, Column 14: reference to entity "ns__t" for which no system identifier could be generated
    		t=t+"&ns__t="+(new

    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 100, Column 8: entity was defined here
    		t=t+"&ns__t="+(new
  • Warning Line 101, Column 27: cannot generate system identifier for general entity "ns_c"
    		Date().getTime());t=t+"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a…

    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 101, Column 27: general entity "ns_c" not defined and no default entity
    		Date().getTime());t=t+"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+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.

  • Warning Line 101, Column 31: reference not terminated by REFC delimiter
    		Date().getTime());t=t+"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+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.

  • Error Line 101, Column 31: reference to entity "ns_c" for which no system identifier could be generated
    		Date().getTime());t=t+"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+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 101, Column 26: entity was defined here
    		Date().getTime());t=t+"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a…
  • Warning Line 101, Column 63: cannot generate system identifier for general entity "c8"
    …"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.h…

    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 101, Column 63: general entity "c8" not defined and no default entity
    …"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.h…

    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 101, Column 65: reference not terminated by REFC delimiter
    …ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.hre…

    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.

  • Error Line 101, Column 65: reference to entity "c8" for which no system identifier could be generated
    …ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.hre…

    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 101, Column 62: entity was defined here
    …+"&ns_c="+(o[r]?o[r]:(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.…
  • Warning Line 101, Column 83: cannot generate system identifier for general entity "c7"
    …(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(…

    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 101, Column 83: general entity "c7" not defined and no default entity
    …(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(…

    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 101, Column 85: reference not terminated by REFC delimiter
    …[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.…

    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.

  • Error Line 101, Column 85: reference to entity "c7" for which no system identifier could be generated
    …[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.…

    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 101, Column 82: entity was defined here
    …:(o[n]?o[n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m…
  • Warning Line 101, Column 91: character "&" is the first character of a delimiter but occurred as data
    …n]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referr…

    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 101, Column 93: cannot generate system identifier for general entity "f.href"
    …:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer…

    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 101, Column 93: general entity "f.href" not defined and no default entity
    …:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer…

    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 101, Column 99: reference not terminated by REFC delimiter
    …"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t…

    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.

  • Error Line 101, Column 99: reference to entity "f.href" for which no system identifier could be generated
    …"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t…

    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 101, Column 92: entity was defined here
    …]:""))+"&c8="+m(o.title)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referre…
  • Warning Line 101, Column 116: cannot generate system identifier for general entity "c9"
    …+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.inde…

    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 101, Column 116: general entity "c9" not defined and no default entity
    …+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.inde…

    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 101, Column 118: reference not terminated by REFC delimiter
    …+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexO…

    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.

  • Error Line 101, Column 118: reference to entity "c9" for which no system identifier could be generated
    …+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexO…

    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 101, Column 115: entity was defined here
    …)+a+"&c7="+m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.ind…
  • Warning Line 101, Column 148: character "&" is the first character of a delimiter but occurred as data
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>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.
  • Warning Line 101, Column 150: cannot generate system identifier for general entity "t.indexOf"
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>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 101, Column 150: general entity "t.indexOf" not defined and no default entity
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>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 101, Column 159: reference not terminated by REFC delimiter
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>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.

  • Error Line 101, Column 159: reference to entity "t.indexOf" for which no system identifier could be generated
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>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 101, Column 149: entity was defined here
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>0)
  • Warning Line 101, Column 161: character "&" is the first character of a delimiter but occurred as data
    …m(f&&f.href?f.href:o.URL)+"&c9="+m(o.referrer);if(t.length>g&&t.indexOf("&")>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.
  • Warning Line 102, Column 35: character "&" is the first character of a delimiter but occurred as data
    		{s=t.substr(0,g-8).lastIndexOf("&");t=(t.substring(0,s)+"&ns_cut="+m(t.substr…

    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 102, Column 61: cannot generate system identifier for general entity "ns_cut"
    …astIndexOf("&");t=(t.substring(0,s)+"&ns_cut="+m(t.substring(s+1))).substr(0,g…

    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 102, Column 61: general entity "ns_cut" not defined and no default entity
    …astIndexOf("&");t=(t.substring(0,s)+"&ns_cut="+m(t.substring(s+1))).substr(0,g…

    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 102, Column 67: reference not terminated by REFC delimiter
    …stIndexOf("&");t=(t.substring(0,s)+"&ns_cut="+m(t.substring(s+1))).substr(0,g)}

    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.

  • Error Line 102, Column 67: reference to entity "ns_cut" for which no system identifier could be generated
    …stIndexOf("&");t=(t.substring(0,s)+"&ns_cut="+m(t.substring(s+1))).substr(0,g)}

    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 102, Column 60: entity was defined here
    …lastIndexOf("&");t=(t.substring(0,s)+"&ns_cut="+m(t.substring(s+1))).substr(0,…
  • Warning Line 108, Column 14: character "<" is the first character of a delimiter but occurred as data
    		{o.write(["<","p","><",'img src="',t,'"height="1" width="1" alt="*"',"><","/p…

    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 108, Column 23: character "<" is the first character of a delimiter but occurred as data
    		{o.write(["<","p","><",'img src="',t,'"height="1" width="1" alt="*"',"><","/p…

    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 108, Column 74: character "<" is the first character of a delimiter but occurred as data
    …',t,'"height="1" width="1" alt="*"',"><","/p",">"].join(""))}};comScore('http'…

    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 108, Column 202: cannot generate system identifier for general entity "c2"
    …://b')+'.scorecardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cv…

    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 108, Column 202: general entity "c2" not defined and no default entity
    …://b')+'.scorecardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cv…

    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 108, Column 204: reference not terminated by REFC delimiter
    …/b')+'.scorecardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoe…

    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.

  • Error Line 108, Column 204: reference to entity "c2" for which no system identifier could be generated
    …/b')+'.scorecardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoe…

    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 108, Column 201: entity was defined here
    …'://b')+'.scorecardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2C…
  • Warning Line 108, Column 214: cannot generate system identifier for general entity "c6"
    …recardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoetbal');</s…

    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 108, Column 214: general entity "c6" not defined and no default entity
    …recardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoetbal');</s…

    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 108, Column 216: reference not terminated by REFC delimiter
    …cardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoetbal');</scr…

    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.

  • Error Line 108, Column 216: reference to entity "c6" for which no system identifier could be generated
    …cardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoetbal');</scr…

    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 108, Column 213: entity was defined here
    …orecardresearch.com/p?c1=2&c2=13026505&c6=webads%2Clifestyleman%2Cvoetbal');</…
  • Error Line 108, Column 259: end tag for "f" omitted, but OMITTAG NO was specified
    …ds%2Clifestyleman%2Cvoetbal');</script><noscript><p><img src="http://b.scoreca…

    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 97, Column 46: start tag was here
    		{p=o.cookie.split(";");for(h=0,f=p.length;h<f;h++)
  • Error Line 108, Column 269: document type does not allow element "noscript" here
    …tyleman%2Cvoetbal');</script><noscript><p><img src="http://b.scorecardresearch…

    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 109, Column 33: end tag for "img" omitted, but OMITTAG NO was specified
    		height="1"width="1"alt="*"></p></noscript>

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

  • Info Line 108, Column 273: start tag was here
    …man%2Cvoetbal');</script><noscript><p><img src="http://b.scorecardresearch.com…
  • Error Line 112, Column 32: document type does not allow element "script" here
    	<script type="text/javascript"> 

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

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

  • Error Line 121, Column 54: document type does not allow element "script" here
    …ge="javascript" type="text/javascript">$(document).ready(function(){cookieBarC…

    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 122, Column 87: document type does not allow element "script" here
    …="javascript" type="text/javascript" src="/static/vi/scripts/date.js"></script>

    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 123, Column 100: document type does not allow element "script" here
    … type="text/javascript" src="/static/vi/scripts/libs/mustache.min.js"></script>

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

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

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

  • Error Line 129, Column 8: end tag for "script" omitted, but OMITTAG NO was specified
     </head>

    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 31, Column 2: start tag was here
    	<script type="text/javascript">window.jQuery || document.write('<script src="/…
  • Error Line 343, Column 1171: required attribute "type" not specified
    …>Seizoen<br />gids</a></li></ul><style>.sideItemBlock{float: left;width: 177px…

    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 343, Column 1171: document type does not allow element "style" here
    …>Seizoen<br />gids</a></li></ul><style>.sideItemBlock{float: left;width: 177px…

    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 347, Column 192: cannot generate system identifier for general entity "achternaam"
    …e_proglide_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.…

    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 347, Column 192: general entity "achternaam" not defined and no default entity
    …e_proglide_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.…

    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 347, Column 202: reference not terminated by REFC delimiter
    …_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-…

    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 347, Column 202: reference to external entity in attribute value
    …_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-…

    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 347, Column 202: reference to entity "achternaam" for which no system identifier could be generated
    …_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-…

    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 347, Column 191: entity was defined here
    …te_proglide_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi…
  • Warning Line 347, Column 209: cannot generate system identifier for general entity "clickTag"
    …0.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-…

    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 347, Column 209: general entity "clickTag" not defined and no default entity
    …0.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-…

    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 347, Column 217: reference not terminated by REFC delimiter
    …ornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-week-1/R…

    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 347, Column 217: reference to external entity in attribute value
    …ornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-week-1/R…

    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 347, Column 217: reference to entity "clickTag" for which no system identifier could be generated
    …ornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-week-1/R…

    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 347, Column 208: entity was defined here
    …00.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de…
  • Warning Line 347, Column 432: reference not terminated by REFC delimiter
    …_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-…

    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 347, Column 432: reference to external entity in attribute value
    …_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-…

    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 347, Column 432: reference to entity "achternaam" for which no system identifier could be generated
    …_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-…

    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 347, Column 191: entity was defined here
    …te_proglide_205x100.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi…
  • Warning Line 347, Column 447: reference not terminated by REFC delimiter
    …ornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-week-1/R…

    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 347, Column 447: reference to external entity in attribute value
    …ornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-week-1/R…

    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 347, Column 447: reference to entity "clickTag" for which no system identifier could be generated
    …ornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de-week-1/R…

    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 347, Column 208: entity was defined here
    …00.swf?voornaam=Denni&achternaam=Avdic&clickTag=http://www.vi.nl/Speler-van-de…
  • Warning Line 362, Column 62: character "&" is the first character of a delimiter but occurred as data
    …div class="block_header"><h2 class="blockHeader">VI FEITEN & CIJFERS</h2></div>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 365, Column 45: element "BR" undefined
    					Rode kaarten in Eredivisie naar club<BR><br />

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 366, Column 8: end tag for "BR" omitted, but OMITTAG NO was specified
    				</p>

    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 365, Column 42: start tag was here
    					Rode kaarten in Eredivisie naar club<BR><br />
  • Error Line 369, Column 53: element "B" undefined
    						<td class="normal" width="70%" valign="top"><B>Club</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 369, Column 62: end tag for "B" omitted, but OMITTAG NO was specified
    						<td class="normal" width="70%" valign="top"><B>Club</td>

    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 369, Column 51: start tag was here
    						<td class="normal" width="70%" valign="top"><B>Club</td>
  • Error Line 370, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER><B>Aantal</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 370, Column 61: element "B" undefined
    						<td class="normal" width="30%" valign="top"><CENTER><B>Aantal</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 370, Column 72: end tag for "B" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER><B>Aantal</td>

    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 370, Column 59: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER><B>Aantal</td>
  • Error Line 370, Column 72: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER><B>Aantal</td>

    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 370, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER><B>Aantal</td>
  • Error Line 374, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>7</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 374, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>7</td>

    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 374, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>7</td>
  • Error Line 378, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>7</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 378, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>7</td>

    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 378, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>7</td>
  • Error Line 382, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>6</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 382, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>6</td>

    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 382, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>6</td>
  • Error Line 386, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>5</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 386, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>5</td>

    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 386, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>5</td>
  • Error Line 390, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 390, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

    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 390, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>
  • Error Line 394, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 394, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

    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 394, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>
  • Error Line 398, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 398, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

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

  • Info Line 398, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>
  • Error Line 402, Column 58: element "CENTER" undefined
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 402, Column 64: end tag for "CENTER" omitted, but OMITTAG NO was specified
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>

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

  • Info Line 402, Column 51: start tag was here
    						<td class="normal" width="30%" valign="top"><CENTER>4</td>
  • Error Line 442, Column 25: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		<ul class="socialList">

    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 525, Column 7: document type does not allow element "ul" here
    			<ul>

    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 526, Column 4: character data is not allowed here
    			{{#.}}

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 527, Column 334: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0" height="113" /><p class="itemTitle">{{title}}</p><p class="itemDate">{{pubD…

    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 527, Column 367: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …><p class="itemTitle">{{title}}</p><p class="itemDate">{{pubDate}}</p></a></li>

    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 528, Column 4: character data is not allowed here
    			{{/.}} 	

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 612, Column 161: character "&" is the first character of a delimiter but occurred as data
    …uentes.htm">'t Wereldje 22/2: penalty's Ajax, Kuijt, Pastoor & Fuentes</a></td>

    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 826, Column 22: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					 <div id="vi_bc"> </div>              

    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 831, Column 138: required attribute "type" not specified
    …tangle_336x280");</script></div><style>#google_ads_div_Home_Rectangle_336x280_…

    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 831, Column 138: document type does not allow element "style" here
    …tangle_336x280");</script></div><style>#google_ads_div_Home_Rectangle_336x280_…

    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 831, Column 326: required attribute "type" not specified
    … both;}</style>										<script language="JavaScript"> images = new Array(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 832, Column 67: document type does not allow element "a" here
    …://www.vi.nl/Geschenkabonnementen.htm'><img src='http://www.vi.nl/files/commer…

    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 832, Column 189: end tag for "img" omitted, but OMITTAG NO was specified
    …uttons/132202_button_geschenkabonnement.jpg' border='0' alt='Bestel nu!'></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 832, Column 68: start tag was here
    …//www.vi.nl/Geschenkabonnementen.htm'><img src='http://www.vi.nl/files/commerc…
  • Error Line 833, Column 110: document type does not allow element "a" here
    …ulier-abonnementen.htm?formid=6020259'><img src='http://www.vi.nl/files/commer…

    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 833, Column 224: end tag for "img" omitted, but OMITTAG NO was specified
    …ercie/4buttons/button_maandabonnement.jpg?1' border='0' alt='Bestel nu!'></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 833, Column 111: start tag was here
    …lier-abonnementen.htm?formid=6020259'><img src='http://www.vi.nl/files/commerc…
  • Error Line 838, Column 220: required attribute "alt" not specified
    …cie/com_snelmenu/elclasico_16px.jpg" /><a href="http://www.audi.nl/nl/brand/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>.

  • Warning Line 838, Column 345: cannot generate system identifier for general entity "utm_source"
    …vaties.html?utm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=…

    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 838, Column 345: general entity "utm_source" not defined and no default entity
    …vaties.html?utm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=…

    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 838, Column 355: reference not terminated by REFC delimiter
    …l?utm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink"…

    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 838, Column 355: reference to external entity in attribute value
    …l?utm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink"…

    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 838, Column 355: reference to entity "utm_source" for which no system identifier could be generated
    …l?utm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink"…

    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 838, Column 344: entity was defined here
    …ovaties.html?utm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term…
  • Warning Line 838, Column 359: cannot generate system identifier for general entity "utm_medium"
    …m_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" tar…

    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 838, Column 359: general entity "utm_medium" not defined and no default entity
    …m_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" tar…

    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 838, Column 369: reference not terminated by REFC delimiter
    …=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blan…

    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 838, Column 369: reference to external entity in attribute value
    …=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blan…

    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 838, Column 369: reference to entity "utm_medium" for which no system identifier could be generated
    …=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blan…

    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 838, Column 358: entity was defined here
    …tm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" ta…
  • Warning Line 838, Column 376: cannot generate system identifier for general entity "utm_term"
    …rtback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blank" onCl…

    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 838, Column 376: general entity "utm_term" not defined and no default entity
    …rtback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blank" onCl…

    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 838, Column 384: reference not terminated by REFC delimiter
    …tm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blank" onClick="_ga…

    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 838, Column 384: reference to external entity in attribute value
    …tm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blank" onClick="_ga…

    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 838, Column 384: reference to entity "utm_term" for which no system identifier could be generated
    …tm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blank" onClick="_ga…

    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 838, Column 375: entity was defined here
    …ortback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" target="_blank" onC…
  • Error Line 838, Column 420: there is no attribute "onClick"
    …rm=tekstlink" target="_blank" onClick="_gaq.push(['_trackEvent', 'Commercieel …

    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 838, Column 626: required attribute "alt" not specified
    …commercie/com_snelmenu/gillette.gif" /><a href="http://www.proteammanager.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 838, Column 911: required attribute "alt" not specified
    …/com_snelmenu/seizoengids_16x16.png" /><a href="http://itunes.apple.com/nl/app…

    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 838, Column 1212: required attribute "alt" not specified
    …ercie/com_snelmenu/sportstadion.jpg" /><a href="http://www.sportstadion.nl/voe…

    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 838, Column 1503: required attribute "alt" not specified
    …mercie/com_snelmenu/marktplaats.jpg" /><a href="http://www.worldticketshop.com…

    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 838, Column 1762: required attribute "alt" not specified
    …mmercie/com_snelmenu/apps_16x16.jpg" /><a href="http://www.vi.nl/Meer-VI.htm" …

    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 838, Column 2029: required attribute "alt" not specified
    …ie/com_snelmenu/16x16_viwebshop.gif" /><a href="http://www.vi.nl/webshop" targ…

    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 838, Column 2285: required attribute "alt" not specified
    …ommercie/com_snelmenu/vliegtuig.gif" /><a href="http://www.vi-travel.nl" targe…

    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 838, Column 2514: required attribute "type" not specified
    …!</a></li></ul>										<script language="JavaScript"> images = new Array(5); 

    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 96: reference not terminated by REFC delimiter
    …e/Games-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img…

    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 839, Column 96: reference to external entity in attribute value
    …e/Games-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img…

    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 839, Column 96: reference to entity "utm_medium" for which no system identifier could be generated
    …e/Games-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img…

    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 838, Column 358: entity was defined here
    …tm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" ta…
  • Warning Line 839, Column 104: cannot generate system identifier for general entity "utm_campaign"
    …4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='ht…

    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 839, Column 104: general entity "utm_campaign" not defined and no default entity
    …4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='ht…

    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 839, Column 116: reference not terminated by REFC delimiter
    …urce=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='http://www.vi.…

    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 839, Column 116: reference to external entity in attribute value
    …urce=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='http://www.vi.…

    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 839, Column 116: reference to entity "utm_campaign" for which no system identifier could be generated
    …urce=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='http://www.vi.…

    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 839, Column 103: entity was defined here
    …-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='h…
  • Error Line 839, Column 131: document type does not allow element "a" here
    …ium=button&utm_campaign=webshop_pes13'><img src='http://www.vi.nl/files/commer…

    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 839, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …l/files/commercie/4buttons/button_pes13.jpg' border='0' alt='Bestel nu!'></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 839, Column 132: start tag was here
    …um=button&utm_campaign=webshop_pes13'><img src='http://www.vi.nl/files/commerc…
  • Error Line 840, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    images[1] = "<a href = http://www.vi.nl/webshop/product/Geen-Genade.htm?utm_sou…
  • Error Line 840, Column 30: NET-enabling start-tag not immediately followed by null end-tag
    images[1] = "<a href = http://www.vi.nl/webshop/product/Geen-Genade.htm?utm_sou…

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

  • Error Line 840, Column 30: document type does not allow element "a" here
    images[1] = "<a href = http://www.vi.nl/webshop/product/Geen-Genade.htm?utm_sou…

    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 840, Column 97: reference not terminated by REFC delimiter
    …en-Genade.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_geengenade'…

    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.

  • Error Line 840, Column 97: reference to entity "utm_medium" for which no system identifier could be generated
    …en-Genade.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_geengenade'…

    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 838, Column 358: entity was defined here
    …tm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" ta…
  • Warning Line 840, Column 117: reference not terminated by REFC delimiter
    …urce=vi&utm_medium=button&utm_campaign=webshop_geengenade'><img src='http://ww…

    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.

  • Error Line 840, Column 117: reference to entity "utm_campaign" for which no system identifier could be generated
    …urce=vi&utm_medium=button&utm_campaign=webshop_geengenade'><img src='http://ww…

    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 839, Column 103: entity was defined here
    …-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='h…
  • Error Line 840, Column 244: document type does not allow element "img" here
    …ommercie/4buttons/button_geen_genade_v2.jpg' border='0' alt='Bestel nu!'></a>";

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

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

  • Error Line 840, Column 248: end tag for element "a" which is not open
    …ommercie/4buttons/button_geen_genade_v2.jpg' border='0' alt='Bestel nu!'></a>";

    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 840, Column 248: end tag for "img" omitted, but OMITTAG NO was specified
    …ommercie/4buttons/button_geen_genade_v2.jpg' border='0' alt='Bestel nu!'></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 840, Column 138: start tag was here
    …tton&utm_campaign=webshop_geengenade'><img src='http://www.vi.nl/files/commerc…
  • Warning Line 841, Column 107: reference not terminated by REFC delimiter
    …boek-2013.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_jaarboek201…

    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 841, Column 107: reference to external entity in attribute value
    …boek-2013.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_jaarboek201…

    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 841, Column 107: reference to entity "utm_medium" for which no system identifier could be generated
    …boek-2013.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_jaarboek201…

    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 838, Column 358: entity was defined here
    …tm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" ta…
  • Warning Line 841, Column 127: reference not terminated by REFC delimiter
    …urce=vi&utm_medium=button&utm_campaign=webshop_jaarboek2013'><img src='http://…

    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 841, Column 127: reference to external entity in attribute value
    …urce=vi&utm_medium=button&utm_campaign=webshop_jaarboek2013'><img src='http://…

    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 841, Column 127: reference to entity "utm_campaign" for which no system identifier could be generated
    …urce=vi&utm_medium=button&utm_campaign=webshop_jaarboek2013'><img src='http://…

    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 839, Column 103: entity was defined here
    …-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='h…
  • Error Line 841, Column 149: document type does not allow element "a" here
    …ton&utm_campaign=webshop_jaarboek2013'><img src='http://www.vi.nl/files/commer…

    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 841, Column 265: end tag for "img" omitted, but OMITTAG NO was specified
    …cie/4buttons/button_voetbaljaarboek2013.jpg' border='0' alt='Bestel nu!'></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 841, Column 150: start tag was here
    …on&utm_campaign=webshop_jaarboek2013'><img src='http://www.vi.nl/files/commerc…
  • Warning Line 842, Column 100: reference not terminated by REFC delimiter
    …Guardiola.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pep'><img s…

    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 842, Column 100: reference to external entity in attribute value
    …Guardiola.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pep'><img s…

    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 842, Column 100: reference to entity "utm_medium" for which no system identifier could be generated
    …Guardiola.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pep'><img s…

    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 838, Column 358: entity was defined here
    …tm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" ta…
  • Warning Line 842, Column 120: reference not terminated by REFC delimiter
    …urce=vi&utm_medium=button&utm_campaign=webshop_pep'><img src='http://www.vi.nl…

    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 842, Column 120: reference to external entity in attribute value
    …urce=vi&utm_medium=button&utm_campaign=webshop_pep'><img src='http://www.vi.nl…

    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 842, Column 120: reference to entity "utm_campaign" for which no system identifier could be generated
    …urce=vi&utm_medium=button&utm_campaign=webshop_pep'><img src='http://www.vi.nl…

    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 839, Column 103: entity was defined here
    …-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='h…
  • Error Line 842, Column 133: document type does not allow element "a" here
    …edium=button&utm_campaign=webshop_pep'><img src='http://www.vi.nl/files/commer…

    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 842, Column 243: end tag for "img" omitted, but OMITTAG NO was specified
    …commercie/4buttons/button_pep_biografie.jpg' border='0' alt='Bestel nu!'></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 842, Column 134: start tag was here
    …dium=button&utm_campaign=webshop_pep'><img src='http://www.vi.nl/files/commerc…
  • Warning Line 843, Column 102: reference not terminated by REFC delimiter
    …-Football.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_copa'><img …

    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 843, Column 102: reference to external entity in attribute value
    …-Football.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_copa'><img …

    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 843, Column 102: reference to entity "utm_medium" for which no system identifier could be generated
    …-Football.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_copa'><img …

    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 838, Column 358: entity was defined here
    …tm_campaign=a3-sportback&utm_source=vi&utm_medium=fixed&utm_term=tekstlink" ta…
  • Warning Line 843, Column 122: reference not terminated by REFC delimiter
    …urce=vi&utm_medium=button&utm_campaign=webshop_copa'><img src='http://www.vi.n…

    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 843, Column 122: reference to external entity in attribute value
    …urce=vi&utm_medium=button&utm_campaign=webshop_copa'><img src='http://www.vi.n…

    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 843, Column 122: reference to entity "utm_campaign" for which no system identifier could be generated
    …urce=vi&utm_medium=button&utm_campaign=webshop_copa'><img src='http://www.vi.n…

    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 839, Column 103: entity was defined here
    …-4.htm?utm_source=vi&utm_medium=button&utm_campaign=webshop_pes13'><img src='h…
  • Error Line 843, Column 136: document type does not allow element "a" here
    …dium=button&utm_campaign=webshop_copa'><img src='http://www.vi.nl/files/commer…

    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 843, Column 242: end tag for "img" omitted, but OMITTAG NO was specified
    …les/commercie/4buttons/button_copa_2013.jpg' border='0' alt='Bestel nu!'></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 843, Column 137: start tag was here
    …ium=button&utm_campaign=webshop_copa'><img src='http://www.vi.nl/files/commerc…
  • Warning Line 854, Column 57: character "&" is the first character of a delimiter but occurred as data
    … (mycookie.indexOf('-1578695-') == -1 && getCookie('cookie')) {               …

    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 854, Column 58: character "&" is the first character of a delimiter but occurred as data
    … (mycookie.indexOf('-1578695-') == -1 && getCookie('cookie')) {                

    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 855, Column 34: character "<" is the first character of a delimiter but occurred as data
                        tmp = tmp + '<' + '!-- TEST: vipollwideelementform --' + '>…

    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 855, Column 98: an attribute value must be a literal unless it contains only name characters
    …elementform --' + '>\n        <div id=\"poll329230\" class=\"right_block_gradi…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 98: character "\" is not allowed in the value of attribute "id"
    …elementform --' + '>\n        <div id=\"poll329230\" class=\"right_block_gradi…

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

  • Error Line 855, Column 119: an attribute value must be a literal unless it contains only name characters
    …n        <div id=\"poll329230\" class=\"right_block_gradient marginBottom\">\n…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 154: "marginBottom" is not a member of a group specified for any attribute
    …ss=\"right_block_gradient marginBottom\">\n            <div class=\"block_head…
  • Error Line 855, Column 156: document type does not allow element "div" here
    …=\"right_block_gradient marginBottom\">\n            <div class=\"block_header…

    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 855, Column 182: an attribute value must be a literal unless it contains only name characters
    …rginBottom\">\n            <div class=\"block_header\"><h2 class=\"blockHeader…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 209: an attribute value must be a literal unless it contains only name characters
    …<div class=\"block_header\"><h2 class=\"blockHeader\">POLL</h2></div>\n       …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 265: an attribute value must be a literal unless it contains only name characters
    …LL</h2></div>\n            <div class=\"block_content\">\n                <p>W…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 395: an attribute value must be a literal unless it contains only name characters
    …rd-PSV?</p>\n                <form id=\"pollForm329230\" method=\"post\" actio…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 395: character "\" is not allowed in the value of attribute "id"
    …rd-PSV?</p>\n                <form id=\"pollForm329230\" method=\"post\" actio…

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

  • Error Line 855, Column 421: an attribute value must be a literal unless it contains only name characters
    …   <form id=\"pollForm329230\" method=\"post\" action=\"/web/form\"><ins>\n<in…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 421: character "\" is not allowed in the value of attribute "method"
    …   <form id=\"pollForm329230\" method=\"post\" action=\"/web/form\"><ins>\n<in…

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

  • Error Line 855, Column 421: value of attribute "method" cannot be "\"post\""; must be one of "get", "post"
    …   <form id=\"pollForm329230\" method=\"post\" action=\"/web/form\"><ins>\n<in…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 855, Column 437: an attribute value must be a literal unless it contains only name characters
    …llForm329230\" method=\"post\" action=\"/web/form\"><ins>\n<input type=\"hidde…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 470: an attribute value must be a literal unless it contains only name characters
    …tion=\"/web/form\"><ins>\n<input type=\"hidden\" name=\"formelement\" value=\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 470: character "\" is not allowed in the value of attribute "type"
    …tion=\"/web/form\"><ins>\n<input type=\"hidden\" name=\"formelement\" value=\"…

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

  • Error Line 855, Column 470: value of attribute "type" cannot be "\"hidden\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …tion=\"/web/form\"><ins>\n<input type=\"hidden\" name=\"formelement\" value=\"…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 855, Column 486: an attribute value must be a literal unless it contains only name characters
    …\"><ins>\n<input type=\"hidden\" name=\"formelement\" value=\"poll\" />\n<inpu…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 508: an attribute value must be a literal unless it contains only name characters
    …\"hidden\" name=\"formelement\" value=\"poll\" />\n<input type=\"hidden\" name…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 533: an attribute value must be a literal unless it contains only name characters
    …ment\" value=\"poll\" />\n<input type=\"hidden\" name=\"originalurl\" value=\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 533: character "\" is not allowed in the value of attribute "type"
    …ment\" value=\"poll\" />\n<input type=\"hidden\" name=\"originalurl\" value=\"…

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

  • Error Line 855, Column 533: value of attribute "type" cannot be "\"hidden\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …ment\" value=\"poll\" />\n<input type=\"hidden\" name=\"originalurl\" value=\"…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 855, Column 549: an attribute value must be a literal unless it contains only name characters
    … value=\"poll\" />\n<input type=\"hidden\" name=\"originalurl\" value=\"http:';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 855, Column 571: an attribute value must be a literal unless it contains only name characters
    … value=\"poll\" />\n<input type=\"hidden\" name=\"originalurl\" value=\"http:';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 7: there is no attribute "tmp"
    tmp = tmp + '//www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\"…

    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 856, Column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    tmp = tmp + '//www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\"…
  • Error Line 856, Column 11: character "+" not allowed in attribute specification list
    tmp = tmp + '//www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\"…
  • Error Line 856, Column 12: end tag for "input" omitted, but OMITTAG NO was specified
    tmp = tmp + '//www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\"…

    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 855, Column 521: start tag was here
    …me=\"formelement\" value=\"poll\" />\n<input type=\"hidden\" name=\"originalur…
  • Error Line 856, Column 54: an attribute value must be a literal unless it contains only name characters
    …www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\" value=\"15786…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 54: character "\" is not allowed in the value of attribute "type"
    …www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\" value=\"15786…

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

  • Error Line 856, Column 54: value of attribute "type" cannot be "\"hidden\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …www.vi.nl/home.html\" />\n<input type=\"hidden\" name=\"pollid\" value=\"15786…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 856, Column 70: an attribute value must be a literal unless it contains only name characters
    …tml\" />\n<input type=\"hidden\" name=\"pollid\" value=\"1578695\" /></ins>\n …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 87: an attribute value must be a literal unless it contains only name characters
    …type=\"hidden\" name=\"pollid\" value=\"1578695\" /></ins>\n                 <…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 138: an attribute value must be a literal unless it contains only name characters
    …></ins>\n                 <input type=\"hidden\" name=\"formpartcode\" value=\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 138: character "\" is not allowed in the value of attribute "type"
    …></ins>\n                 <input type=\"hidden\" name=\"formpartcode\" value=\…

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

  • Error Line 856, Column 138: value of attribute "type" cannot be "\"hidden\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …></ins>\n                 <input type=\"hidden\" name=\"formpartcode\" value=\…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 856, Column 154: an attribute value must be a literal unless it contains only name characters
    …          <input type=\"hidden\" name=\"formpartcode\" value=\"pollid\" />\n  …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 177: an attribute value must be a literal unless it contains only name characters
    …"hidden\" name=\"formpartcode\" value=\"pollid\" />\n                    <inpu…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 224: an attribute value must be a literal unless it contains only name characters
    …" />\n                    <input type=\"radio\" name=\"pollitem\" value=\"1578…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 224: character "\" is not allowed in the value of attribute "type"
    …" />\n                    <input type=\"radio\" name=\"pollitem\" value=\"1578…

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

  • Error Line 856, Column 224: value of attribute "type" cannot be "\"radio\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …" />\n                    <input type=\"radio\" name=\"pollitem\" value=\"1578…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 856, Column 239: an attribute value must be a literal unless it contains only name characters
    …           <input type=\"radio\" name=\"pollitem\" value=\"1578696\" /><label …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 258: an attribute value must be a literal unless it contains only name characters
    …ype=\"radio\" name=\"pollitem\" value=\"1578696\" /><label for=\"1578696\">Win…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 283: an attribute value must be a literal unless it contains only name characters
    …item\" value=\"1578696\" /><label for=\"1578696\">Winst Feyenoord</label>\n   …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 283: character "\" is not allowed in the value of attribute "for"
    …item\" value=\"1578696\" /><label for=\"1578696\">Winst Feyenoord</label>\n   …

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

  • Error Line 856, Column 384: an attribute value must be a literal unless it contains only name characters
    …r />\n                    <input type=\"radio\" name=\"pollitem\" value=\"1578…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 384: character "\" is not allowed in the value of attribute "type"
    …r />\n                    <input type=\"radio\" name=\"pollitem\" value=\"1578…

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

  • Error Line 856, Column 384: value of attribute "type" cannot be "\"radio\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …r />\n                    <input type=\"radio\" name=\"pollitem\" value=\"1578…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 856, Column 399: an attribute value must be a literal unless it contains only name characters
    …           <input type=\"radio\" name=\"pollitem\" value=\"1578697\" /><label …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 418: an attribute value must be a literal unless it contains only name characters
    …ype=\"radio\" name=\"pollitem\" value=\"1578697\" /><label for=\"1578697\">Win…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 443: an attribute value must be a literal unless it contains only name characters
    …item\" value=\"1578697\" /><label for=\"1578697\">Winst PSV</label>\n         …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 443: character "\" is not allowed in the value of attribute "for"
    …item\" value=\"1578697\" /><label for=\"1578697\">Winst PSV</label>\n         …

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

  • Error Line 856, Column 538: an attribute value must be a literal unless it contains only name characters
    …                       <br />\n                    <input type=\"radio\" name';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 856, Column 538: character "\" is not allowed in the value of attribute "type"
    …                       <br />\n                    <input type=\"radio\" name';

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

  • Error Line 856, Column 538: value of attribute "type" cannot be "\"radio\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …                       <br />\n                    <input type=\"radio\" name';

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 856, Column 552: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …                       <br />\n                    <input type=\"radio\" name';

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 856, Column 553: end tag for "input" omitted, but OMITTAG NO was specified
    …                       <br />\n                    <input type=\"radio\" name';

    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 856, Column 526: start tag was here
    …                       <br />\n                    <input type=\"radio\" name';
  • Error Line 857, Column 59: an attribute value must be a literal unless it contains only name characters
    …item\" value=\"1578698\" /><label for=\"1578698\">Gelijkspel</label>\n        …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 59: character "\" is not allowed in the value of attribute "for"
    …item\" value=\"1578698\" /><label for=\"1578698\">Gelijkspel</label>\n        …

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

  • Error Line 857, Column 124: an attribute value must be a literal unless it contains only name characters
    …el>\n                <ins><input type=\"hidden\" name=\"swfrmsig\" value=\"cd3…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 124: character "\" is not allowed in the value of attribute "type"
    …el>\n                <ins><input type=\"hidden\" name=\"swfrmsig\" value=\"cd3…

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

  • Error Line 857, Column 124: value of attribute "type" cannot be "\"hidden\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …el>\n                <ins><input type=\"hidden\" name=\"swfrmsig\" value=\"cd3…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 857, Column 140: an attribute value must be a literal unless it contains only name characters
    …     <ins><input type=\"hidden\" name=\"swfrmsig\" value=\"cd34203ec41a9ff09f0…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 159: an attribute value must be a literal unless it contains only name characters
    …pe=\"hidden\" name=\"swfrmsig\" value=\"cd34203ec41a9ff09f0891f79ce88660d90de2…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 336: an attribute value must be a literal unless it contains only name characters
    …s>\n</form>\n                <p align=\"right\" style=\"margin:0px;margin-righ…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 336: character "\" is not allowed in the value of attribute "align"
    …s>\n</form>\n                <p align=\"right\" style=\"margin:0px;margin-righ…

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

  • Error Line 857, Column 336: value of attribute "align" cannot be "\"right\""; must be one of "left", "center", "right", "justify"
    …s>\n</form>\n                <p align=\"right\" style=\"margin:0px;margin-righ…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 857, Column 352: an attribute value must be a literal unless it contains only name characters
    …             <p align=\"right\" style=\"margin:0px;margin-right:10px;margin-to…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 433: an attribute value must be a literal unless it contains only name characters
    …0px;\">\n                    <img src=\"/static/vi/images/icon_bal.gif\" borde…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 475: an attribute value must be a literal unless it contains only name characters
    …tatic/vi/images/icon_bal.gif\" border=\"0\" alt=\"\" /><a href=\"#\" onclick=\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 485: an attribute value must be a literal unless it contains only name characters
    …mages/icon_bal.gif\" border=\"0\" alt=\"\" /><a href=\"#\" onclick=\"document.…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 500: an attribute value must be a literal unless it contains only name characters
    …gif\" border=\"0\" alt=\"\" /><a href=\"#\" onclick=\"document.getElementById(…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 857, Column 514: an attribute value must be a literal unless it contains only name characters
    … border=\"0\" alt=\"\" /><a href=\"#\" onclick=\"document.getElementById(\'po';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 858, Column 7: there is no attribute "tmp"
    tmp = tmp + 'llForm329230\').submit(); return false;\" class=\"link_blue\">Stem…

    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 858, Column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    tmp = tmp + 'llForm329230\').submit(); return false;\" class=\"link_blue\">Stem…
  • Error Line 858, Column 11: character "+" not allowed in attribute specification list
    tmp = tmp + 'llForm329230\').submit(); return false;\" class=\"link_blue\">Stem…
  • Error Line 858, Column 151: an attribute value must be a literal unless it contains only name characters
    …       </div>\n            <div class=\"block_footer\">&nbsp;</div>\n        <…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 861, Column 34: character "<" is the first character of a delimiter but occurred as data
                        tmp = tmp + '<' + '!-- TEST: vipollwideelementresult --' + …

    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 861, Column 92: an attribute value must be a literal unless it contains only name characters
    …llwideelementresult --' + '>\n<div id=\"poll329230\" class=\"right_block_gradi…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 92: character "\" is not allowed in the value of attribute "id"
    …llwideelementresult --' + '>\n<div id=\"poll329230\" class=\"right_block_gradi…

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

  • Error Line 861, Column 92: ID "\"poll329230\"" already defined
    …llwideelementresult --' + '>\n<div id=\"poll329230\" class=\"right_block_gradi…

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

  • Info Line 855, Column 98: ID "\"poll329230\"" first defined here
    …elementform --' + '>\n        <div id=\"poll329230\" class=\"right_block_gradi…
  • Error Line 861, Column 113: an attribute value must be a literal unless it contains only name characters
    …-' + '>\n<div id=\"poll329230\" class=\"right_block_gradient marginBottom\">\n…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 148: "marginBottom" is not a member of a group specified for any attribute
    …ss=\"right_block_gradient marginBottom\">\n    <div class=\"block_header\"><h2…
  • Error Line 861, Column 150: document type does not allow element "div" here
    …=\"right_block_gradient marginBottom\">\n    <div class=\"block_header\"><h2 c…

    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 861, Column 168: an attribute value must be a literal unless it contains only name characters
    …dient marginBottom\">\n    <div class=\"block_header\"><h2 class=\"blockHeader…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 195: an attribute value must be a literal unless it contains only name characters
    …<div class=\"block_header\"><h2 class=\"blockHeader\">POLL</h2></div>\n    <di…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 243: an attribute value must be a literal unless it contains only name characters
    …der\">POLL</h2></div>\n    <div class=\"block_content\">\n        <p>Wat wordt…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 362: an attribute value must be a literal unless it contains only name characters
    …noord-PSV?</p>\n        <table border=\"0\" width=\"100%\" cellpadding=\"2\" c…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 374: an attribute value must be a literal unless it contains only name characters
    …p>\n        <table border=\"0\" width=\"100%\" cellpadding=\"2\" cellspacing=\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 395: an attribute value must be a literal unless it contains only name characters
    …rder=\"0\" width=\"100%\" cellpadding=\"2\" cellspacing=\"0\">\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 413: an attribute value must be a literal unless it contains only name characters
    …"100%\" cellpadding=\"2\" cellspacing=\"0\">\n                    <tr>\n      …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 419: character data is not allowed here
    …" cellpadding=\"2\" cellspacing=\"0\">\n                    <tr>\n            …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 861, Column 445: character data is not allowed here
    …acing=\"0\">\n                    <tr>\n                        <td width=\"40…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 861, Column 481: an attribute value must be a literal unless it contains only name characters
    …r>\n                        <td width=\"40\" class=\"color_green\">50%</td>\n …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 494: an attribute value must be a literal unless it contains only name characters
    …               <td width=\"40\" class=\"color_green\">50%</td>\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 861, Column 518: character data is not allowed here
    …=\"40\" class=\"color_green\">50%</td>\n                        <td>Winst Feye…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 861, Column 568: character data is not allowed here
    …lor_green\">50%</td>\n                        <td>Winst Feyenoord</td>\n     ';

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 34: character data is not allowed here
    tmp = tmp + '               </tr>\n                    <tr>\n                  …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 60: character data is not allowed here
    …       </tr>\n                    <tr>\n                        <td></td>\n   …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 95: character data is not allowed here
    …tr>\n                        <td></td>\n                        <td>\n        …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 169: an attribute value must be a literal unless it contains only name characters
    …                        <table border=\"0\" width=\"50%\" cellpadding=\"0\" ce…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 862, Column 181: an attribute value must be a literal unless it contains only name characters
    …            <table border=\"0\" width=\"50%\" cellpadding=\"0\" cellspacing=\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 862, Column 201: an attribute value must be a literal unless it contains only name characters
    …order=\"0\" width=\"50%\" cellpadding=\"0\" cellspacing=\"0\">\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 862, Column 219: an attribute value must be a literal unless it contains only name characters
    …\"50%\" cellpadding=\"0\" cellspacing=\"0\">\n                                …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 862, Column 225: character data is not allowed here
    …" cellpadding=\"0\" cellspacing=\"0\">\n                                <tr>\n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 263: character data is not allowed here
    …\n                                <tr>\n                                    <t…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 311: an attribute value must be a literal unless it contains only name characters
    …                            <td style=\"background-color:#6ea523;\">&nbsp;</td…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 862, Column 352: character data is not allowed here
    …ackground-color:#6ea523;\">&nbsp;</td>\n                                </tr>\…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 391: character data is not allowed here
    …n                                </tr>\n                            </table>\n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 460: character data is not allowed here
    …/table>\n                        </td>\n                    </tr>\n           …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 487: character data is not allowed here
    …      </td>\n                    </tr>\n                    <tr>\n            …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 862, Column 513: character data is not allowed here
    …>\n                    </tr>\n                    <tr>\n                     ';

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 27: an attribute value must be a literal unless it contains only name characters
    tmp = tmp + '   <td width=\"40\" class=\"color_green\">33%</td>\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 40: an attribute value must be a literal unless it contains only name characters
    …mp = tmp + '   <td width=\"40\" class=\"color_green\">33%</td>\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 64: character data is not allowed here
    …=\"40\" class=\"color_green\">33%</td>\n                        <td>Winst PSV<…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 108: character data is not allowed here
    …                    <td>Winst PSV</td>\n                    </tr>\n           …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 135: character data is not allowed here
    …st PSV</td>\n                    </tr>\n                    <tr>\n            …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 161: character data is not allowed here
    …       </tr>\n                    <tr>\n                        <td></td>\n   …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 196: character data is not allowed here
    …tr>\n                        <td></td>\n                        <td>\n        …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 270: an attribute value must be a literal unless it contains only name characters
    …                        <table border=\"0\" width=\"33%\" cellpadding=\"0\" ce…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 282: an attribute value must be a literal unless it contains only name characters
    …            <table border=\"0\" width=\"33%\" cellpadding=\"0\" cellspacing=\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 302: an attribute value must be a literal unless it contains only name characters
    …order=\"0\" width=\"33%\" cellpadding=\"0\" cellspacing=\"0\">\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 320: an attribute value must be a literal unless it contains only name characters
    …\"33%\" cellpadding=\"0\" cellspacing=\"0\">\n                                …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 326: character data is not allowed here
    …" cellpadding=\"0\" cellspacing=\"0\">\n                                <tr>\n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 364: character data is not allowed here
    …\n                                <tr>\n                                    <t…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 412: an attribute value must be a literal unless it contains only name characters
    …                            <td style=\"background-color:#6ea523;\">&nbsp;</td…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 863, Column 453: character data is not allowed here
    …ackground-color:#6ea523;\">&nbsp;</td>\n                                </tr>\…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 863, Column 492: character data is not allowed here
    …n                                </tr>\n                            </table>\n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 36: character data is not allowed here
    tmp = tmp + '                 </td>\n                    </tr>\n               …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 63: character data is not allowed here
    …      </td>\n                    </tr>\n                    <tr>\n            …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 89: character data is not allowed here
    …       </tr>\n                    <tr>\n                        <td width=\"40…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 125: an attribute value must be a literal unless it contains only name characters
    …r>\n                        <td width=\"40\" class=\"color_green\">17%</td>\n …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 864, Column 138: an attribute value must be a literal unless it contains only name characters
    …               <td width=\"40\" class=\"color_green\">17%</td>\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 864, Column 162: character data is not allowed here
    …=\"40\" class=\"color_green\">17%</td>\n                        <td>Gelijkspel…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 207: character data is not allowed here
    …                   <td>Gelijkspel</td>\n                    </tr>\n           …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 234: character data is not allowed here
    …jkspel</td>\n                    </tr>\n                    <tr>\n            …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 260: character data is not allowed here
    …       </tr>\n                    <tr>\n                        <td></td>\n   …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 295: character data is not allowed here
    …tr>\n                        <td></td>\n                        <td>\n        …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 369: an attribute value must be a literal unless it contains only name characters
    …                        <table border=\"0\" width=\"17%\" cellpadding=\"0\" ce…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 864, Column 381: an attribute value must be a literal unless it contains only name characters
    …            <table border=\"0\" width=\"17%\" cellpadding=\"0\" cellspacing=\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 864, Column 401: an attribute value must be a literal unless it contains only name characters
    …order=\"0\" width=\"17%\" cellpadding=\"0\" cellspacing=\"0\">\n              …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 864, Column 419: an attribute value must be a literal unless it contains only name characters
    …\"17%\" cellpadding=\"0\" cellspacing=\"0\">\n                                …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 864, Column 425: character data is not allowed here
    …" cellpadding=\"0\" cellspacing=\"0\">\n                                <tr>\n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 463: character data is not allowed here
    …\n                                <tr>\n                                    <t…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 864, Column 511: an attribute value must be a literal unless it contains only name characters
    …r>\n                                    <td style=\"background-color:#6ea523;';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 865, Column 7: there is no attribute "tmp"
    tmp = tmp + '\">&nbsp;</td>\n                                </tr>\n           …

    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 865, Column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    tmp = tmp + '\">&nbsp;</td>\n                                </tr>\n           …
  • Error Line 865, Column 11: character "+" not allowed in attribute specification list
    tmp = tmp + '\">&nbsp;</td>\n                                </tr>\n           …
  • Error Line 865, Column 28: character data is not allowed here
    tmp = tmp + '\">&nbsp;</td>\n                                </tr>\n           …

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 865, Column 67: character data is not allowed here
    …n                                </tr>\n                            </table>\n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 865, Column 136: character data is not allowed here
    …/table>\n                        </td>\n                    </tr>\n        </t…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 865, Column 163: character data is not allowed here
    …      </td>\n                    </tr>\n        </table>\n        <p>8503 stem…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 865, Column 239: an attribute value must be a literal unless it contains only name characters
    …stemmen</p>\n    </div>\n    <div class=\"block_footer\">&nbsp;</div>\n</div>';

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 884, Column 9: element "BR" undefined
    					<BR><center><a href="/achtergronden/vanafdebank/236425/Atletico-Madrid-zet…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 885, Column 8: end tag for "BR" omitted, but OMITTAG NO was specified
    				</p>

    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 884, Column 6: start tag was here
    					<BR><center><a href="/achtergronden/vanafdebank/236425/Atletico-Madrid-zet…
  • Error Line 895, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/nieuws/236327/VI-Animatiequiz-benoem-duels-tussen-Fe…

    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 895, Column 6: start tag was here
    					<br><center><a href="/nieuws/236327/VI-Animatiequiz-benoem-duels-tussen-Fe…
  • Error Line 895, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/nieuws/236327/VI-Animatiequiz-benoem-duels-tussen-Fe…

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

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

  • Error Line 906, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/achtergronden/speler/236361/Xavi-laat-Seedorf-achter…

    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 906, Column 6: start tag was here
    					<br><center><a href="/achtergronden/speler/236361/Xavi-laat-Seedorf-achter…
  • Error Line 906, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/achtergronden/speler/236361/Xavi-laat-Seedorf-achter…

    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 918, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/achtergronden/indekantlijn/236363/Vervlogen-tijden-b…

    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 918, Column 6: start tag was here
    					<br><center><a href="/achtergronden/indekantlijn/236363/Vervlogen-tijden-b…
  • Error Line 918, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/achtergronden/indekantlijn/236363/Vervlogen-tijden-b…

    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 927, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/interactief/Foto-en-zijn-verhaal/235990/Foto-en-zn-v…

    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 927, Column 6: start tag was here
    					<br><center><a href="/interactief/Foto-en-zijn-verhaal/235990/Foto-en-zn-v…
  • Error Line 927, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/interactief/Foto-en-zijn-verhaal/235990/Foto-en-zn-v…

    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 938, Column 9: element "BR" undefined
    					<BR><center><a href="/achtergronden/club/235839/Duel-van-rentree-Stekelenb…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 939, Column 8: end tag for "BR" omitted, but OMITTAG NO was specified
    				</p>

    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 938, Column 6: start tag was here
    					<BR><center><a href="/achtergronden/club/235839/Duel-van-rentree-Stekelenb…
  • Error Line 949, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/nieuws/235517/Bezoekers-VI.nl-zetten-Van-Rhijn-en-De…

    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 949, Column 6: start tag was here
    					<br><center><a href="/nieuws/235517/Bezoekers-VI.nl-zetten-Van-Rhijn-en-De…
  • Error Line 949, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/nieuws/235517/Bezoekers-VI.nl-zetten-Van-Rhijn-en-De…

    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 960, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/nieuws/235238/Groot-aandeel-voor-AZ-in-VI-Elftal-van…

    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 960, Column 6: start tag was here
    					<br><center><a href="/nieuws/235238/Groot-aandeel-voor-AZ-in-VI-Elftal-van…
  • Error Line 960, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/nieuws/235238/Groot-aandeel-voor-AZ-in-VI-Elftal-van…

    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 971, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/achtergronden/Transferdagboek-1/235130/Transferdagbo…

    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 971, Column 6: start tag was here
    					<br><center><a href="/achtergronden/Transferdagboek-1/235130/Transferdagbo…
  • Error Line 971, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/achtergronden/Transferdagboek-1/235130/Transferdagbo…

    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 972, Column 8: end tag for "center" omitted, but OMITTAG NO was specified
    				</p>

    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 971, Column 10: start tag was here
    					<br><center><a href="/achtergronden/Transferdagboek-1/235130/Transferdagbo…
  • Error Line 982, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/interactief/t-Wereldje-overzicht.htm" class="normal"…

    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 982, Column 6: start tag was here
    					<br><center><a href="/interactief/t-Wereldje-overzicht.htm" class="normal"…
  • Error Line 982, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/interactief/t-Wereldje-overzicht.htm" class="normal"…

    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 994, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/achtergronden/DossierTransfers.htm" class="normal" t…

    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 994, Column 6: start tag was here
    					<br><center><a href="/achtergronden/DossierTransfers.htm" class="normal" t…
  • Error Line 994, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/achtergronden/DossierTransfers.htm" class="normal" t…

    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 994, Column 121: element "BR" undefined
    …al" title="Dossier Transfers">Een overzicht<BR>van de<BR>transfers</a></center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 994, Column 131: element "BR" undefined
    …al" title="Dossier Transfers">Een overzicht<BR>van de<BR>transfers</a></center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 994, Column 144: end tag for "BR" omitted, but OMITTAG NO was specified
    …al" title="Dossier Transfers">Een overzicht<BR>van de<BR>transfers</a></center>

    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 994, Column 128: start tag was here
    …al" title="Dossier Transfers">Een overzicht<BR>van de<BR>transfers</a></center>
  • Error Line 994, Column 144: end tag for "BR" omitted, but OMITTAG NO was specified
    …al" title="Dossier Transfers">Een overzicht<BR>van de<BR>transfers</a></center>

    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 994, Column 118: start tag was here
    …al" title="Dossier Transfers">Een overzicht<BR>van de<BR>transfers</a></center>
  • Error Line 1005, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/achtergronden/De-Voorbereiding-1.htm" class="normal"…

    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 1005, Column 6: start tag was here
    					<br><center><a href="/achtergronden/De-Voorbereiding-1.htm" class="normal"…
  • Error Line 1005, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/achtergronden/De-Voorbereiding-1.htm" class="normal"…

    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 1005, Column 122: element "BR" undefined
    …le="De Voorbereiding">Alles over de<BR>voorbereiding van de<BR>36 profclubs</a…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1005, Column 146: element "BR" undefined
    …orbereiding">Alles over de<BR>voorbereiding van de<BR>36 profclubs</a></center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1005, Column 162: end tag for "BR" omitted, but OMITTAG NO was specified
    …orbereiding">Alles over de<BR>voorbereiding van de<BR>36 profclubs</a></center>

    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 1005, Column 143: start tag was here
    …orbereiding">Alles over de<BR>voorbereiding van de<BR>36 profclubs</a></center>
  • Error Line 1005, Column 162: end tag for "BR" omitted, but OMITTAG NO was specified
    …orbereiding">Alles over de<BR>voorbereiding van de<BR>36 profclubs</a></center>

    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 1005, Column 119: start tag was here
    …title="De Voorbereiding">Alles over de<BR>voorbereiding van de<BR>36 profclubs…
  • Error Line 1016, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br><center><a href="/eknieuws/223766/Terugblik-Dag-19-Spaanse-furie-speel…

    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 1016, Column 6: start tag was here
    					<br><center><a href="/eknieuws/223766/Terugblik-Dag-19-Spaanse-furie-speel…
  • Error Line 1016, Column 17: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<br><center><a href="/eknieuws/223766/Terugblik-Dag-19-Spaanse-furie-speel…

    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 1030, Column 92: element "I" undefined
    …-aanvaller Jean-Paul Boëtius over zijn ouders in het <I>Feyenoord Magazine</I>.

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1073, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …://images.webads.nl/stir/vi_stir.htm" width=0 height=0 frameborder=no></iframe>
  • Error Line 1073, Column 72: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …://images.webads.nl/stir/vi_stir.htm" width=0 height=0 frameborder=no></iframe>
  • Error Line 1073, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …://images.webads.nl/stir/vi_stir.htm" width=0 height=0 frameborder=no></iframe>
  • Error Line 1073, Column 86: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    …://images.webads.nl/stir/vi_stir.htm" width=0 height=0 frameborder=no></iframe>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 1075, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
     </body>

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

  • Info Line 131, Column 3: start tag was here
      <div id="wrapper">
  • Warning Line 857, Column 59: reference to non-existent ID "\"1578698\""
    …item\" value=\"1578698\" /><label for=\"1578698\">Gelijkspel</label>\n        …

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 856, Column 283: reference to non-existent ID "\"1578696\""
    …item\" value=\"1578696\" /><label for=\"1578696\">Winst Feyenoord</label>\n   …

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 856, Column 443: reference to non-existent ID "\"1578697\""
    …item\" value=\"1578697\" /><label for=\"1578697\">Winst PSV</label>\n         …

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 19.833 visits