www.ni.dk has Alexa Rank 152.968 and Google Page Rank is 6

www.ni.dk
  • Domain Name
    www.ni.dk
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #152968
  • Page Size
    79.6 KB
  • Ip Address
    80.69.234.17
  • Heading
    H1: 40, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 4 PNG

Website Meta Analysis

  • Title
    Nyheds-Index -> Nyheder
  • Meta Keyword
  • Meta Description

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from www.ni.dk.

HTML Analysis

  • date: Fri, 22 Feb 2013 01:56:49 GMT
  • server: Apache
  • accept-ranges: bytes
  • cache-control: max-age=3600
  • expires: Fri, 22 Feb 2013 02:56:49 GMT
  • vary: User-Agent
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for www.ni.dk

DNS Analysis


DNS servers
ns.domainnetwork.se [203.27.227.61]
ns2.domainnetwork.se [202.148.152.225]
ns3.domainnetwork.com [212.81.32.109]


DNS Records

Answer records
appsec.eniro.com A 80.69.234.17 300s

Authority records

Additional records

IP 80.69.234.17 Analysis

  • Country Code
    SE
  • Country Code3
    SWE
  • Country Name
    Sweden
  • City
    EU
  • Continent Code
    62° North
  • Latitude
    15.
  • Longitude
  • No whois ip data for 80.69.234.17

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 155 Errors
  • 103 Warnings
Ratio Text/Html
  • 0.7514202628253107
Message Error
  • Error Line 4, Column 18: there is no attribute "http-equiv"
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">

    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 4, Column 41: there is no attribute "content"
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">

    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 4, Column 67: element "META" undefined
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">

    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 5, Column 51: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="X-UA-Compatible" content="IE=8">

    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 5, Column 1: start tag was here
    <meta http-equiv="X-UA-Compatible" content="IE=8">
  • Error Line 6, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    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 6, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  • Error Line 8, Column 80: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" type="text/css" media="all" href="/ni-css/krak-ego.css">

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

  • Info Line 8, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" media="all" href="/ni-css/krak-ego.css">
  • Error Line 9, Column 71: end tag for "link" omitted, but OMITTAG NO was specified
    <link href="/ni-css/global-krak.css" rel="stylesheet" type="text/css">

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

  • Info Line 9, Column 1: start tag was here
    <link href="/ni-css/global-krak.css" rel="stylesheet" type="text/css">
  • Error Line 35, Column 97: required attribute "type" not specified
    …s.com/ajax/libs/jquery/1.4.4/jquery.js"></script><script language="javascript">

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

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

  • Error Line 35, Column 136: required attribute "type" not specified
    …s.com/ajax/libs/jquery/1.4.4/jquery.js"></script><script language="javascript">

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

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

  • Warning Line 105, Column 23: character "&" is the first character of a delimiter but occurred as data
        var regexS = '[\\?&]' + name + '=([^&#]*)';

    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 105, Column 41: character "&" is the first character of a delimiter but occurred as data
        var regexS = '[\\?&]' + name + '=([^&#]*)';

    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 128, Column 29: there is no attribute "value"
    <meta name="keywords" value="biblioteker, chat, erotik, film, fiske, fritid, ho…

    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 128, Column 324: required attribute "content" not specified
    …ex, aviser, online nyheder, webtw, s&oslash;gemaskiner, oplysning, find firma">

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

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

  • Error Line 128, Column 325: end tag for "meta" omitted, but OMITTAG NO was specified
    …ex, aviser, online nyheder, webtw, s&oslash;gemaskiner, oplysning, find firma">

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

  • Info Line 128, Column 1: start tag was here
    <meta name="keywords" value="biblioteker, chat, erotik, film, fiske, fritid, ho…
  • Error Line 129, Column 316: required attribute "content" not specified
    …er, sport, s&oslash;gemaskiner, webtv, uddannelse, vittigheder og meget mere.">

    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 129, Column 317: end tag for "meta" omitted, but OMITTAG NO was specified
    …er, sport, s&oslash;gemaskiner, webtv, uddannelse, vittigheder og meget mere.">

    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 129, Column 1: start tag was here
    <meta name="description" value="P&aring; Nyheds-Index finder du popul&aelig;re …
  • Error Line 130, Column 7: end tag for "META" 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 4, Column 1: start tag was here
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
  • Error Line 130, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 148, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …ness/common/header/limg/da-dk-krak/krak/logotype-134x37.png" alt="Krak.dk"></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 148, Column 66: start tag was here
    …tp://www.krak.dk/" class="e-logotype"><img src="http://www.krak.dk/components/…
  • Error Line 151, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" value="00062ad7-sp00000000" name="sp-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 151, Column 1: start tag was here
    <input type="hidden" value="00062ad7-sp00000000" name="sp-a">
  • Error Line 155, Column 45: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" value="cs" name="what">

    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 155, Column 1: start tag was here
    <input type="hidden" value="cs" name="what">
  • Error Line 160, Column 33: there is no attribute "autocomplete"
    <input type="text" autocomplete="off" id="e-search_word" name="search_word" val…

    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 160, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …autocomplete="off" id="e-search_word" name="search_word" value="" tabindex="1">

    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 160, Column 1: start tag was here
    <input type="text" autocomplete="off" id="e-search_word" name="search_word" val…
  • Error Line 166, Column 31: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" value="">

    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 166, Column 1: start tag was here
    <input type="hidden" value="">
  • Error Line 169, Column 107: there is no attribute "onClick"
    …tle="S&oslash;g" id="e-submit" tabindex="3" name="btn_cs" onClick="funEniro()">

    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 169, Column 120: end tag for "input" omitted, but OMITTAG NO was specified
    …tle="S&oslash;g" id="e-submit" tabindex="3" name="btn_cs" onClick="funEniro()">

    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 169, Column 9: start tag was here
    						  <input type="submit" value="" title="S&oslash;g" id="e-submit" tabindex…
  • Error Line 176, Column 111: end tag for "input" omitted, but OMITTAG NO was specified
    …lue="" title="S&oslash;g" id="ni" tabindex="3" name="btn_ni" onClick="funNi()">

    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 176, Column 9: start tag was here
    						  <input type="submit" value="" title="S&oslash;g" id="ni" tabindex="3" n…
  • Error Line 185, Column 107: required attribute "alt" not specified
    … src="http://www.ni.dk/ni-img/blank.png" width="50" height="50" border="0"></a>

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

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

  • Error Line 185, Column 111: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://www.ni.dk/ni-img/blank.png" width="50" height="50" border="0"></a>

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

  • Info Line 185, Column 29: start tag was here
    <a href="http://www.ni.dk/"><img src="http://www.ni.dk/ni-img/blank.png" width=…
  • Error Line 231, Column 41: required attribute "alt" not specified
    <img src="/ni-img/right-corner-krak.png"></li>

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

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

  • Error Line 231, Column 46: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="/ni-img/right-corner-krak.png"></li>

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

  • Info Line 231, Column 1: start tag was here
    <img src="/ni-img/right-corner-krak.png"></li>
  • Error Line 235, Column 4: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <ul>

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

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

  • Error Line 335, Column 67: required attribute "type" not specified
    <div class="box-no-border clearfixP"><script language="JavaScript">

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

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

  • Warning Line 340, Column 31: character "<" is the first character of a delimiter but occurred as data
    	return (" - "+((now.getDate()<10) ? "" : "")+ now.getDate()+". "+monthSrc[now.…

    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 344, Column 80: cannot generate system identifier for general entity "mode"
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 80: general entity "mode" not defined and no default entity
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 84: reference not terminated by REFC delimiter
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 84: reference to external entity in attribute value
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 84: reference to entity "mode" for which no system identifier could be generated
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 79: entity was defined here
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210
  • Warning Line 344, Column 90: cannot generate system identifier for general entity "submode"
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 90: general entity "submode" not defined and no default entity
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 97: reference not terminated by REFC delimiter
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 97: reference to external entity in attribute value
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 97: reference to entity "submode" for which no system identifier could be generated
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210

    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 344, Column 89: entity was defined here
    …xP"><iframe src="http://jp.dk/?service=jsfeed&mode=jpNi&submode=jp" height="210
  • Error Line 345, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>

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

  • Info Line 345, Column 55: start tag was here
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>
  • Error Line 345, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>

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

  • Info Line 345, Column 59: start tag was here
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>
  • Error Line 347, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>

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

  • Info Line 347, Column 55: start tag was here
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>
  • Error Line 347, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>

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

  • Info Line 347, Column 59: start tag was here
    " width="310" frameborder="0" scrolling="no"></iframe><br><br></div>
  • Error Line 351, Column 240: end tag for "br" omitted, but OMITTAG NO was specified
    …frameborder="0" marginheight="0" marginwidth="0"></iframe><br>&nbsp;<br/></div>

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

  • Info Line 351, Column 236: start tag was here
    …frameborder="0" marginheight="0" marginwidth="0"></iframe><br>&nbsp;<br/></div>
  • Error Line 356, Column 77: element "B" undefined
    …lg/ni/cat-7728/http:/www.aftonbladet.se/"><B>Aftonbladet</B></a> - Sverige</li>

    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 75: element "B" undefined
    …ro.dk/lg/ni/cat-7728/http:/www.dagbladet.no/"><B>Dagbladet</B></a> - Norge</li>

    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 367, Column 68: element "B" undefined
    …ro.dk/lg/ni/cat-7728/http:/www.dn.se/"><B>Dagens Nyheter</b></a> - Sverige</li>

    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 367, Column 86: end tag for element "b" which is not open
    …ro.dk/lg/ni/cat-7728/http:/www.dn.se/"><B>Dagens Nyheter</b></a> - Sverige</li>

    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 367, Column 90: end tag for "B" omitted, but OMITTAG NO was specified
    …ro.dk/lg/ni/cat-7728/http:/www.dn.se/"><B>Dagens Nyheter</b></a> - Sverige</li>

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

  • Info Line 367, Column 66: start tag was here
    …ro.dk/lg/ni/cat-7728/http:/www.dn.se/"><B>Dagens Nyheter</b></a> - Sverige</li>
  • Error Line 369, Column 13: there is no attribute "href"
    <li><A href="http://go.eniro.dk/lg/ni/cat-7728/http:/news.google.com"><B>Google…

    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 369, Column 70: element "A" undefined
    …//go.eniro.dk/lg/ni/cat-7728/http:/news.google.com"><B>Google News</B></A></li>

    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 73: element "B" undefined
    …//go.eniro.dk/lg/ni/cat-7728/http:/news.google.com"><B>Google News</B></A></li>

    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 391, Column 68: element "B" undefined
    …://go.eniro.dk/lg/ni/cat-7728/http:/www.vg.no/"><B>VG Nett</B></a> - Norge</li>

    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 405, Column 509: end tag for "img" omitted, but OMITTAG NO was specified
    …cat3=BT-16" border="0" alt="EmediateAd" width="234" height="60"></a></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 405, Column 377: start tag was here
    …?cu=1298;ty=ct;cat=;cat2=;cat3=BT-16"><img src="http://eas8.emediate.eu/eas?cu…
  • Error Line 406, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    <br></div>

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

  • Info Line 406, Column 1: start tag was here
    <br></div>
  • Error Line 437, Column 143: end tag for element "A" which is not open
    …/eas?camp=129846;ty=ct;EASLink=http://www.sas.dk?WT.mc_id=DKBA561">SAS</A></li>

    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 437, Column 148: end tag for "a" omitted, but OMITTAG NO was specified
    …/eas?camp=129846;ty=ct;EASLink=http://www.sas.dk?WT.mc_id=DKBA561">SAS</A></li>

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

  • Info Line 437, Column 5: start tag was here
    <li><a href="http://go.eniro.dk/lg/ni/cat-8061/http:/eas8.emediate.eu/eas?camp=…
  • Error Line 439, Column 99: element "A" undefined
    …/www.trafikken.dk/hovedstaden/hovedstaden.asp">Trafikken</A> - Hovedstaden</li>

    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 451, Column 153: cannot generate system identifier for general entity "no_cache"
    …OAX=*f29e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f887526468…

    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 451, Column 153: general entity "no_cache" not defined and no default entity
    …OAX=*f29e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f887526468…

    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 451, Column 161: reference not terminated by REFC delimiter
    …e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 451, Column 161: reference to external entity in attribute value
    …e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 451, Column 161: reference to entity "no_cache" for which no system identifier could be generated
    …e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 451, Column 152: entity was defined here
    …_OAX=*f29e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f88752646…
  • Error Line 637, Column 171: required attribute "type" not specified
    …b></a><b><script language="JavaScript">document.write(FUNdato())</script></b><…

    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 638, Column 128: required attribute "type" not specified
    …b></a><b><script language="JavaScript">document.write(FUNdato())</script></b><…

    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 639, Column 185: required attribute "type" not specified
    …b></a><b><script language="JavaScript">document.write(FUNdato())</script></b><…

    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 640, Column 146: cannot generate system identifier for general entity "utm_medium"
    …/www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b…

    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 640, Column 146: general entity "utm_medium" not defined and no default entity
    …/www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b…

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

  • Warning Line 640, Column 156: reference not terminated by REFC delimiter
    …xpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpre…

    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 640, Column 156: reference to external entity in attribute value
    …xpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpre…

    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 640, Column 156: reference to entity "utm_medium" for which no system identifier could be generated
    …xpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpre…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 640, Column 162: cannot generate system identifier for general entity "utm_campaign"
    ….dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b>…

    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 640, Column 162: general entity "utm_campaign" not defined and no default entity
    ….dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b>…

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

  • Warning Line 640, Column 174: reference not terminated by REFC delimiter
    …rce=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b></a><b><scri…

    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 640, Column 174: reference to external entity in attribute value
    …rce=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b></a><b><scri…

    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 640, Column 174: reference to entity "utm_campaign" for which no system identifier could be generated
    …rce=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b></a><b><scri…

    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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Error Line 640, Column 238: required attribute "type" not specified
    …b></a><b><script language="JavaScript">document.write(FUNdato())</script></b><…

    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 641, Column 180: required attribute "type" not specified
    …b></a><b><script language="JavaScript">document.write(FUNdato())</script></b><…

    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 707, Column 140: cannot generate system identifier for general entity "PageIndex"
    …/avisen.dk/listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&Articl…

    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 707, Column 140: general entity "PageIndex" not defined and no default entity
    …/avisen.dk/listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&Articl…

    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 707, Column 149: reference not terminated by REFC delimiter
    …k/listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&M…

    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 707, Column 149: reference to external entity in attribute value
    …k/listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&M…

    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 707, Column 149: reference to entity "PageIndex" for which no system identifier could be generated
    …k/listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&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.

  • Info Line 707, Column 139: entity was defined here
    …//avisen.dk/listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&Artic…
  • Warning Line 707, Column 152: cannot generate system identifier for general entity "SortType"
    …istevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu…

    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 707, Column 152: general entity "SortType" not defined and no default entity
    …istevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu…

    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 707, Column 160: reference not terminated by REFC delimiter
    …ing.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avis…

    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 707, Column 160: reference to external entity in attribute value
    …ing.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avis…

    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 707, Column 160: reference to entity "SortType" for which no system identifier could be generated
    …ing.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avis…

    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 707, Column 151: entity was defined here
    …listevisning.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Men…
  • Warning Line 707, Column 163: cannot generate system identifier for general entity "ShowType"
    ….aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.…

    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 707, Column 163: general entity "ShowType" not defined and no default entity
    ….aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.…

    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 707, Column 171: reference not terminated by REFC delimiter
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 707, Column 171: reference to external entity in attribute value
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 707, Column 171: reference to entity "ShowType" for which no system identifier could be generated
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 162: entity was defined here
    …g.aspx?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen…
  • Warning Line 707, Column 174: cannot generate system identifier for general entity "ArticleType"
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 174: general entity "ArticleType" not defined and no default entity
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 185: reference not terminated by REFC delimiter
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 707, Column 185: reference to external entity in attribute value
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 707, Column 185: reference to entity "ArticleType" for which no system identifier could be generated
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 173: entity was defined here
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>
  • Warning Line 707, Column 188: cannot generate system identifier for general entity "Menu"
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 188: general entity "Menu" not defined and no default entity
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 192: reference not terminated by REFC delimiter
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 707, Column 192: reference to external entity in attribute value
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 707, Column 192: reference to entity "Menu" for which no system identifier could be generated
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</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 707, Column 187: entity was defined here
    …?ItemID=1&PageIndex=1&SortType=1&ShowType=2&ArticleType=0&Menu=1">Avisen.dk</a>
  • Warning Line 822, Column 161: reference not terminated by REFC delimiter
    …ab71363d2b43381a8090f845a099d&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 822, Column 161: reference to external entity in attribute value
    …ab71363d2b43381a8090f845a099d&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 822, Column 161: reference to entity "no_cache" for which no system identifier could be generated
    …ab71363d2b43381a8090f845a099d&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 451, Column 152: entity was defined here
    …_OAX=*f29e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f88752646…
  • Error Line 832, Column 71: element "B" undefined
    …ttp://go.eniro.dk/lg/ni/cat-7349/http:/www.politi.dk"><B>Politi.dk</B></a></li>

    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 843, Column 509: end tag for "img" omitted, but OMITTAG NO was specified
    …cat3=BT-16" border="0" alt="EmediateAd" width="300" height="60"></a></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 843, Column 377: start tag was here
    …?cu=1301;ty=ct;cat=;cat2=;cat3=BT-16"><img src="http://eas8.emediate.eu/eas?cu…
  • Error Line 844, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br></div>

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

  • Info Line 844, Column 1: start tag was here
    <br><br></div>
  • Error Line 844, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br></div>

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

  • Info Line 844, Column 5: start tag was here
    <br><br></div>
  • Error Line 871, Column 66: an attribute specification must start with a name or name token
    …ref="http://go.eniro.dk/lg/ni/cat-8084/http:/www.arto.dk""><B>Arto</B></A></li>

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

  • Error Line 871, Column 66: element "A" undefined
    …ref="http://go.eniro.dk/lg/ni/cat-8084/http:/www.arto.dk""><B>Arto</B></A></li>

    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 871, Column 70: element "B" undefined
    …ref="http://go.eniro.dk/lg/ni/cat-8084/http:/www.arto.dk""><B>Arto</B></A></li>

    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 899, Column 157: reference not terminated by REFC delimiter
    ….dk/debat/?utm_source=eniro&utm_medium=link&utm_campaign=debat">MetroXpress</a…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 899, Column 157: reference to external entity in attribute value
    ….dk/debat/?utm_source=eniro&utm_medium=link&utm_campaign=debat">MetroXpress</a…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 899, Column 157: reference to entity "utm_medium" for which no system identifier could be generated
    ….dk/debat/?utm_source=eniro&utm_medium=link&utm_campaign=debat">MetroXpress</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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 899, Column 175: reference not terminated by REFC delimiter
    ….dk/debat/?utm_source=eniro&utm_medium=link&utm_campaign=debat">MetroXpress</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 899, Column 175: reference to external entity in attribute value
    ….dk/debat/?utm_source=eniro&utm_medium=link&utm_campaign=debat">MetroXpress</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 899, Column 175: reference to entity "utm_campaign" for which no system identifier could be generated
    ….dk/debat/?utm_source=eniro&utm_medium=link&utm_campaign=debat">MetroXpress</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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 932, Column 130: cannot generate system identifier for general entity "fsid"
    …p=136880;ty=ct;EASLink=http://k.ilius.net/?mtcmk=732397&fsid=064">Match.com</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 932, Column 130: general entity "fsid" not defined and no default entity
    …p=136880;ty=ct;EASLink=http://k.ilius.net/?mtcmk=732397&fsid=064">Match.com</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 932, Column 134: reference not terminated by REFC delimiter
    …p=136880;ty=ct;EASLink=http://k.ilius.net/?mtcmk=732397&fsid=064">Match.com</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 932, Column 134: reference to external entity in attribute value
    …p=136880;ty=ct;EASLink=http://k.ilius.net/?mtcmk=732397&fsid=064">Match.com</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 932, Column 134: reference to entity "fsid" for which no system identifier could be generated
    …p=136880;ty=ct;EASLink=http://k.ilius.net/?mtcmk=732397&fsid=064">Match.com</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 932, Column 129: entity was defined here
    …p=136880;ty=ct;EASLink=http://k.ilius.net/?mtcmk=732397&fsid=064">Match.com</a>
  • Warning Line 1040, Column 88: character "&" is the first character of a delimiter but occurred as data
    …/login.yahoo.com/config/login?.intl=dk&.done=http:/dk.mail.yahoo.com/">Yahoo M…

    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 1091, Column 161: reference not terminated by REFC delimiter
    …e4a7d66b00b748e79eaacbb8bbc39&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 1091, Column 161: reference to external entity in attribute value
    …e4a7d66b00b748e79eaacbb8bbc39&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 1091, Column 161: reference to entity "no_cache" for which no system identifier could be generated
    …e4a7d66b00b748e79eaacbb8bbc39&no_cache=1342572989098_cb7fe72f88752646832a255e1…

    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 451, Column 152: entity was defined here
    …_OAX=*f29e2e7333d611275c77b067de272dca&no_cache=1342572989098_cb7fe72f88752646…
  • Error Line 1135, Column 13: required attribute "alt" not specified
    " border="0"></a><br>&nbsp;<br/></div>

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

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

  • Error Line 1135, Column 17: end tag for "img" omitted, but OMITTAG NO was specified
    " border="0"></a><br>&nbsp;<br/></div>

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

  • Info Line 1134, Column 100: start tag was here
    ….dk/lg/ni/cat-10021/http:/www.hel.dk"><img src="http://ni.dk/aktuelt/Spot-kvin…
  • Error Line 1135, Column 22: end tag for "br" omitted, but OMITTAG NO was specified
    " border="0"></a><br>&nbsp;<br/></div>

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

  • Info Line 1135, Column 18: start tag was here
    " border="0"></a><br>&nbsp;<br/></div>
  • Error Line 1139, Column 16: there is no attribute "SIZE"
    <li><FONT SIZE=2 COLOR=#0073A5>Links til sundhed og sygdomsrelaterede hjemmesid…

    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 1139, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><FONT SIZE=2 COLOR=#0073A5>Links til sundhed og sygdomsrelaterede hjemmesid…
  • Error Line 1139, Column 24: there is no attribute "COLOR"
    <li><FONT SIZE=2 COLOR=#0073A5>Links til sundhed og sygdomsrelaterede hjemmesid…

    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 1139, Column 24: an attribute value must be a literal unless it contains only name characters
    <li><FONT SIZE=2 COLOR=#0073A5>Links til sundhed og sygdomsrelaterede hjemmesid…

    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 1139, Column 31: element "FONT" undefined
    <li><FONT SIZE=2 COLOR=#0073A5>Links til sundhed og sygdomsrelaterede hjemmesid…

    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 1139, Column 235: end tag for element "font" which is not open
    …/cat-9986/http:/www.ni.dk/sundhedogsygdom"><b>Sundhed og Sygdom</b></a>.</font>

    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 1142, Column 5: end tag for "FONT" omitted, but OMITTAG NO was specified
    </li>

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

  • Info Line 1139, Column 5: start tag was here
    <li><FONT SIZE=2 COLOR=#0073A5>Links til sundhed og sygdomsrelaterede hjemmesid…
  • Warning Line 1148, Column 392: character "&" is the first character of a delimiter but occurred as data
    …i/cat-8866/http:/kort.eniro.dk/?partnerid=linkguide"><b>Kort & Luftfoto</b></a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1166, Column 41: element "TR" undefined
    <div class="box-no-border clearfixP"><TR> 

    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 1167, Column 13: there is no attribute "bgColor"
    <TD bgColor=#ffffff>

    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 1167, Column 13: an attribute value must be a literal unless it contains only name characters
    <TD bgColor=#ffffff>

    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 1167, Column 20: element "TD" undefined
    <TD bgColor=#ffffff>

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

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

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

  • Error Line 1170, Column 31: document type does not allow element "br" here
    "Skal du leje et sommerhus?<br>Besøg Rejse-guiden",

    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 1170, Column 32: end tag for "br" omitted, but OMITTAG NO was specified
    "Skal du leje et sommerhus?<br>Besøg Rejse-guiden",

    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 1170, Column 28: start tag was here
    "Skal du leje et sommerhus?<br>Besøg Rejse-guiden",
  • Error Line 1171, Column 39: document type does not allow element "br" here
    "Er du ved at bestille sommerferie?<br>Så kan du finde inspiration på Rejse-gui…

    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 1171, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
    …Er du ved at bestille sommerferie?<br>Så kan du finde inspiration på Rejse-gui…

    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 1171, Column 36: start tag was here
    "Er du ved at bestille sommerferie?<br>Så kan du finde inspiration på Rejse-gui…
  • Error Line 1172, Column 37: document type does not allow element "br" here
    "Læs nyheder henvendt til kvinder<br>Besøg guiden Kvinder");

    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 1172, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
    "Læs nyheder henvendt til kvinder<br>Besøg guiden Kvinder");

    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 1172, Column 34: start tag was here
    "Læs nyheder henvendt til kvinder<br>Besøg guiden Kvinder");
  • Error Line 1178, Column 45: document type does not allow element "a" here
    …nt.write("<a href="+urls[randomText]+"><center><font size= -1 color = #cc0000>…

    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 1178, Column 53: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rite("<a href="+urls[randomText]+"><center><font size= -1 color = #cc0000><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 1178, Column 66: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rite("<a href="+urls[randomText]+"><center><font size= -1 color = #cc0000><b>")
  • Error Line 1178, Column 77: an attribute value must be a literal unless it contains only name characters
    …rite("<a href="+urls[randomText]+"><center><font size= -1 color = #cc0000><b>")

    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 1180, Column 24: end tag for "font" omitted, but OMITTAG NO was specified
    document.write("</b></a></font></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 1178, Column 54: start tag was here
    …rite("<a href="+urls[randomText]+"><center><font size= -1 color = #cc0000><b>")
  • Error Line 1180, Column 24: end tag for "center" omitted, but OMITTAG NO was specified
    document.write("</b></a></font></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 1178, Column 46: start tag was here
    …t.write("<a href="+urls[randomText]+"><center><font size= -1 color = #cc0000><…
  • Error Line 1180, Column 31: end tag for element "font" which is not open
    document.write("</b></a></font></center>")

    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 1180, Column 40: end tag for element "center" which is not open
    document.write("</b></a></font></center>")

    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 1181, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    </script><br>

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

  • Info Line 1181, Column 10: start tag was here
    </script><br>
  • Warning Line 1191, Column 132: cannot generate system identifier for general entity "utm_source"
    …k=http://www.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_…

    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 1191, Column 132: general entity "utm_source" not defined and no default entity
    …k=http://www.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_…

    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 1191, Column 142: reference not terminated by REFC delimiter
    …ww.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_content=Bo…

    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 1191, Column 142: reference to external entity in attribute value
    …ww.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_content=Bo…

    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 1191, Column 142: reference to entity "utm_source" for which no system identifier could be generated
    …ww.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_content=Bo…

    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 1191, Column 131: entity was defined here
    …nk=http://www.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm…
  • Warning Line 1191, Column 159: reference not terminated by REFC delimiter
    …/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEni…

    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 1191, Column 159: reference to external entity in attribute value
    …/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEni…

    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 1191, Column 159: reference to entity "utm_medium" for which no system identifier could be generated
    …/?sol=true&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEni…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1191, Column 168: cannot generate system identifier for general entity "utm_content"
    …e&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_ca…

    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 1191, Column 168: general entity "utm_content" not defined and no default entity
    …e&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_ca…

    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 1191, Column 179: reference not terminated by REFC delimiter
    …e=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_campaign=Enir…

    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 1191, Column 179: reference to external entity in attribute value
    …e=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_campaign=Enir…

    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 1191, Column 179: reference to entity "utm_content" for which no system identifier could be generated
    …e=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_campaign=Enir…

    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 1191, Column 167: entity was defined here
    …ue&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_c…
  • Warning Line 1191, Column 214: reference not terminated by REFC delimiter
    …ent=Boligside%2B-%2BEniro&utm_campaign=Eniro" style="font-weight: bold;">Bolig…

    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 1191, Column 214: reference to external entity in attribute value
    …ent=Boligside%2B-%2BEniro&utm_campaign=Eniro" style="font-weight: bold;">Bolig…

    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 1191, Column 214: reference to entity "utm_campaign" for which no system identifier could be generated
    …ent=Boligside%2B-%2BEniro&utm_campaign=Eniro" style="font-weight: bold;">Bolig…

    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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1198, Column 152: reference not terminated by REFC delimiter
    …tart.dk/?utm_source=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaig…

    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 1198, Column 152: reference to external entity in attribute value
    …tart.dk/?utm_source=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaig…

    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 1198, Column 152: reference to entity "utm_medium" for which no system identifier could be generated
    …tart.dk/?utm_source=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaig…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1198, Column 159: cannot generate system identifier for general entity "utm_term"
    …/?utm_source=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand…

    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 1198, Column 159: general entity "utm_term" not defined and no default entity
    …/?utm_source=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand…

    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 1198, Column 167: reference not terminated by REFC delimiter
    …urce=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand">Bygges…

    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 1198, Column 167: reference to external entity in attribute value
    …urce=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand">Bygges…

    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 1198, Column 167: reference to entity "utm_term" for which no system identifier could be generated
    …urce=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand">Bygges…

    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 1198, Column 158: entity was defined here
    …k/?utm_source=krak-ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=bran…
  • Warning Line 1198, Column 193: reference not terminated by REFC delimiter
    …ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand">Byggestart.dk</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1198, Column 193: reference to external entity in attribute value
    …ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand">Byggestart.dk</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1198, Column 193: reference to entity "utm_campaign" for which no system identifier could be generated
    …ni&utm_medium=link &utm_term=haandvaerker&utm_campaign=brand">Byggestart.dk</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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1215, Column 181: reference not terminated by REFC delimiter
    …koper.aspx?utm_source=eniro&utm_medium=link&utm_campaign=horoskop">Horoskop</a…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1215, Column 181: reference to external entity in attribute value
    …koper.aspx?utm_source=eniro&utm_medium=link&utm_campaign=horoskop">Horoskop</a…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1215, Column 181: reference to entity "utm_medium" for which no system identifier could be generated
    …koper.aspx?utm_source=eniro&utm_medium=link&utm_campaign=horoskop">Horoskop</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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1215, Column 199: reference not terminated by REFC delimiter
    …koper.aspx?utm_source=eniro&utm_medium=link&utm_campaign=horoskop">Horoskop</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1215, Column 199: reference to external entity in attribute value
    …koper.aspx?utm_source=eniro&utm_medium=link&utm_campaign=horoskop">Horoskop</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1215, Column 199: reference to entity "utm_campaign" for which no system identifier could be generated
    …koper.aspx?utm_source=eniro&utm_medium=link&utm_campaign=horoskop">Horoskop</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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1223, Column 142: reference not terminated by REFC delimiter
    …www.ofir.dk?utm_source=krak&utm_medium=partnerskab&utm_campaign=link" style="f…

    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 1223, Column 142: reference to external entity in attribute value
    …www.ofir.dk?utm_source=krak&utm_medium=partnerskab&utm_campaign=link" style="f…

    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 1223, Column 142: reference to entity "utm_medium" for which no system identifier could be generated
    …www.ofir.dk?utm_source=krak&utm_medium=partnerskab&utm_campaign=link" style="f…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1223, Column 167: reference not terminated by REFC delimiter
    …ak&utm_medium=partnerskab&utm_campaign=link" style="font-weight: bold;">Ofir.d…

    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 1223, Column 167: reference to external entity in attribute value
    …ak&utm_medium=partnerskab&utm_campaign=link" style="font-weight: bold;">Ofir.d…

    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 1223, Column 167: reference to entity "utm_campaign" for which no system identifier could be generated
    …ak&utm_medium=partnerskab&utm_campaign=link" style="font-weight: bold;">Ofir.d…

    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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1228, Column 143: reference not terminated by REFC delimiter
    …y=ct;EASLink=http://www.qxl.dk?utm_medium=cpc&utm_source=eniro">QXL.dk</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1228, Column 143: reference to external entity in attribute value
    …y=ct;EASLink=http://www.qxl.dk?utm_medium=cpc&utm_source=eniro">QXL.dk</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1228, Column 143: reference to entity "utm_source" for which no system identifier could be generated
    …y=ct;EASLink=http://www.qxl.dk?utm_medium=cpc&utm_source=eniro">QXL.dk</a></li>

    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 1191, Column 131: entity was defined here
    …nk=http://www.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm…
  • Warning Line 1292, Column 141: reference not terminated by REFC delimiter
    …/www.dancenter.dk/?kmg=E101&utm_source=Eniro_linkguide&utm_medium=Link&utm_cam…

    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 1292, Column 141: reference to external entity in attribute value
    …/www.dancenter.dk/?kmg=E101&utm_source=Eniro_linkguide&utm_medium=Link&utm_cam…

    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 1292, Column 141: reference to entity "utm_source" for which no system identifier could be generated
    …/www.dancenter.dk/?kmg=E101&utm_source=Eniro_linkguide&utm_medium=Link&utm_cam…

    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 1191, Column 131: entity was defined here
    …nk=http://www.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm…
  • Warning Line 1292, Column 168: reference not terminated by REFC delimiter
    …&utm_source=Eniro_linkguide&utm_medium=Link&utm_campaign=Eniro_links">DanCente…

    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 1292, Column 168: reference to external entity in attribute value
    …&utm_source=Eniro_linkguide&utm_medium=Link&utm_campaign=Eniro_links">DanCente…

    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 1292, Column 168: reference to entity "utm_medium" for which no system identifier could be generated
    …&utm_source=Eniro_linkguide&utm_medium=Link&utm_campaign=Eniro_links">DanCente…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1292, Column 186: reference not terminated by REFC delimiter
    …_source=Eniro_linkguide&utm_medium=Link&utm_campaign=Eniro_links">DanCenter</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1292, Column 186: reference to external entity in attribute value
    …_source=Eniro_linkguide&utm_medium=Link&utm_campaign=Eniro_links">DanCenter</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1292, Column 186: reference to entity "utm_campaign" for which no system identifier could be generated
    …_source=Eniro_linkguide&utm_medium=Link&utm_campaign=Eniro_links">DanCenter</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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1306, Column 231: reference not terminated by REFC delimiter
    …estinationer/?utm_source=Ni&utm_medium=Rejselink_Faergeruter_1x1&utm_content=F…

    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 1306, Column 231: reference to external entity in attribute value
    …estinationer/?utm_source=Ni&utm_medium=Rejselink_Faergeruter_1x1&utm_content=F…

    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 1306, Column 231: reference to entity "utm_medium" for which no system identifier could be generated
    …estinationer/?utm_source=Ni&utm_medium=Rejselink_Faergeruter_1x1&utm_content=F…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1306, Column 269: reference not terminated by REFC delimiter
    …=Rejselink_Faergeruter_1x1&utm_content=Faergeruter&utm_campaign=Banner_Vinter_…

    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 1306, Column 269: reference to external entity in attribute value
    …=Rejselink_Faergeruter_1x1&utm_content=Faergeruter&utm_campaign=Banner_Vinter_…

    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 1306, Column 269: reference to entity "utm_content" for which no system identifier could be generated
    …=Rejselink_Faergeruter_1x1&utm_content=Faergeruter&utm_campaign=Banner_Vinter_…

    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 1191, Column 167: entity was defined here
    …ue&utm_source=Enrio&utm_medium=Partner&utm_content=Boligside%2B-%2BEniro&utm_c…
  • Warning Line 1306, Column 294: reference not terminated by REFC delimiter
    …x1&utm_content=Faergeruter&utm_campaign=Banner_Vinter_2012_2013">Stena Line</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1306, Column 294: reference to external entity in attribute value
    …x1&utm_content=Faergeruter&utm_campaign=Banner_Vinter_2012_2013">Stena Line</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1306, Column 294: reference to entity "utm_campaign" for which no system identifier could be generated
    …x1&utm_content=Faergeruter&utm_campaign=Banner_Vinter_2012_2013">Stena Line</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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1308, Column 153: reference not terminated by REFC delimiter
    …-benns.com?utm_source=eniro&utm_medium=cpc&utm_campaign=eniro2011"><b>Team Ben…

    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 1308, Column 153: reference to external entity in attribute value
    …-benns.com?utm_source=eniro&utm_medium=cpc&utm_campaign=eniro2011"><b>Team Ben…

    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 1308, Column 153: reference to entity "utm_medium" for which no system identifier could be generated
    …-benns.com?utm_source=eniro&utm_medium=cpc&utm_campaign=eniro2011"><b>Team Ben…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1308, Column 170: reference not terminated by REFC delimiter
    …_source=eniro&utm_medium=cpc&utm_campaign=eniro2011"><b>Team Benns</b></a></li>

    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 1308, Column 170: reference to external entity in attribute value
    …_source=eniro&utm_medium=cpc&utm_campaign=eniro2011"><b>Team Benns</b></a></li>

    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 1308, Column 170: reference to entity "utm_campaign" for which no system identifier could be generated
    …_source=eniro&utm_medium=cpc&utm_campaign=eniro2011"><b>Team Benns</b></a></li>

    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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1310, Column 172: reference not terminated by REFC delimiter
    …_hotel.cfm?utm_source=Eniro&utm_medium=Rejse-guide&utm_campaign=Eniro-Rejsegui…

    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 1310, Column 172: reference to external entity in attribute value
    …_hotel.cfm?utm_source=Eniro&utm_medium=Rejse-guide&utm_campaign=Eniro-Rejsegui…

    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 1310, Column 172: reference to entity "utm_medium" for which no system identifier could be generated
    …_hotel.cfm?utm_source=Eniro&utm_medium=Rejse-guide&utm_campaign=Eniro-Rejsegui…

    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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1310, Column 197: reference not terminated by REFC delimiter
    …ce=Eniro&utm_medium=Rejse-guide&utm_campaign=Eniro-Rejseguide">Travelmarket</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1310, Column 197: reference to external entity in attribute value
    …ce=Eniro&utm_medium=Rejse-guide&utm_campaign=Eniro-Rejseguide">Travelmarket</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1310, Column 197: reference to entity "utm_campaign" for which no system identifier could be generated
    …ce=Eniro&utm_medium=Rejse-guide&utm_campaign=Eniro-Rejseguide">Travelmarket</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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Warning Line 1341, Column 127: cannot generate system identifier for general entity "partnerId"
    …793;ty=ct;EASLink=http://www.kelkoo.dk/?popup=no&partnerId=96918576">Kelkoo</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 1341, Column 127: general entity "partnerId" not defined and no default entity
    …793;ty=ct;EASLink=http://www.kelkoo.dk/?popup=no&partnerId=96918576">Kelkoo</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 1341, Column 136: reference not terminated by REFC delimiter
    …793;ty=ct;EASLink=http://www.kelkoo.dk/?popup=no&partnerId=96918576">Kelkoo</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1341, Column 136: reference to external entity in attribute value
    …793;ty=ct;EASLink=http://www.kelkoo.dk/?popup=no&partnerId=96918576">Kelkoo</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1341, Column 136: reference to entity "partnerId" for which no system identifier could be generated
    …793;ty=ct;EASLink=http://www.kelkoo.dk/?popup=no&partnerId=96918576">Kelkoo</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 1341, Column 126: entity was defined here
    …793;ty=ct;EASLink=http://www.kelkoo.dk/?popup=no&partnerId=96918576">Kelkoo</a>
  • Warning Line 1349, Column 140: reference not terminated by REFC delimiter
    …24;ty=ct;EASLink=http://www.qxl.dk/?utm_medium=cpc&utm_source=eniro">QXL.dk</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 1349, Column 140: reference to external entity in attribute value
    …24;ty=ct;EASLink=http://www.qxl.dk/?utm_medium=cpc&utm_source=eniro">QXL.dk</a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1349, Column 140: reference to entity "utm_source" for which no system identifier could be generated
    …24;ty=ct;EASLink=http://www.qxl.dk/?utm_medium=cpc&utm_source=eniro">QXL.dk</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 1191, Column 131: entity was defined here
    …nk=http://www.boligportal.dk/?sol=true&utm_source=Enrio&utm_medium=Partner&utm…
  • Warning Line 1388, Column 148: reference not terminated by REFC delimiter
    …oghoer.dk/?utm_source=enrio&utm_medium=link&utm_campaign=nyhed"><b>Se og Hø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 1388, Column 148: reference to external entity in attribute value
    …oghoer.dk/?utm_source=enrio&utm_medium=link&utm_campaign=nyhed"><b>Se og Hø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 1388, Column 148: reference to entity "utm_medium" for which no system identifier could be generated
    …oghoer.dk/?utm_source=enrio&utm_medium=link&utm_campaign=nyhed"><b>Se og Hø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 640, Column 145: entity was defined here
    …//www.metroxpress.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><…
  • Warning Line 1388, Column 166: reference not terminated by REFC delimiter
    …?utm_source=enrio&utm_medium=link&utm_campaign=nyhed"><b>Se og Hør</b></a></li>

    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 1388, Column 166: reference to external entity in attribute value
    …?utm_source=enrio&utm_medium=link&utm_campaign=nyhed"><b>Se og Hør</b></a></li>

    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 1388, Column 166: reference to entity "utm_campaign" for which no system identifier could be generated
    …?utm_source=enrio&utm_medium=link&utm_campaign=nyhed"><b>Se og Hør</b></a></li>

    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 640, Column 161: entity was defined here
    …s.dk/?utm_source=eniro&utm_medium=link&utm_campaign=nyheder"><b>MetroXpress</b…
  • Error Line 1555, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <li><br>&nbsp;<br/></li>

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

  • Info Line 1555, Column 5: start tag was here
    <li><br>&nbsp;<br/></li>
  • Warning Line 1586, Column 96: character "&" is the first character of a delimiter but occurred as data
    …ni/cat-8867/http:/www.rejse-guide.dk/rejsetider">Flytider & Færgeruter</A></li>

    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 1586, Column 111: end tag for element "A" which is not open
    …ni/cat-8867/http:/www.rejse-guide.dk/rejsetider">Flytider & Færgeruter</A></li>

    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 1586, Column 116: end tag for "a" omitted, but OMITTAG NO was specified
    …ni/cat-8867/http:/www.rejse-guide.dk/rejsetider">Flytider & Færgeruter</A></li>

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

  • Info Line 1586, Column 7: start tag was here
    <li>- <a href="http://go.eniro.dk/lg/ni/cat-8867/http:/www.rejse-guide.dk/rejse…
  • Error Line 1682, Column 509: end tag for "img" omitted, but OMITTAG NO was specified
    …cat3=BT-16" border="0" alt="EmediateAd" width="234" height="60"></a></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 1682, Column 377: start tag was here
    …?cu=1303;ty=ct;cat=;cat2=;cat3=BT-16"><img src="http://eas8.emediate.eu/eas?cu…
  • Error Line 1684, Column 509: end tag for "img" omitted, but OMITTAG NO was specified
    …cat3=BT-16" border="0" alt="EmediateAd" width="234" height="60"></a></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 1684, Column 377: start tag was here
    …?cu=1304;ty=ct;cat=;cat2=;cat3=BT-16"><img src="http://eas8.emediate.eu/eas?cu…
  • Error Line 1686, Column 509: end tag for "img" omitted, but OMITTAG NO was specified
    …cat3=BT-16" border="0" alt="EmediateAd" width="234" height="60"></a></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 1686, Column 377: start tag was here
    …?cu=1305;ty=ct;cat=;cat2=;cat3=BT-16"><img src="http://eas8.emediate.eu/eas?cu…
  • Error Line 1705, Column 10: ID "banner" already defined
    <div id="banner" class="clearfixP">

    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 191, Column 10: ID "banner" first defined here
    <div id="banner">

Visitor Analysis

Daily Visitor
  • 1.867 visits
Daily Visitor