AutoScout24 - il mercato di auto usate, auto nuove e km 0, annunci gratuiti. Cerca l'automobile nel nostro grande database. ...

autoscout24.it
  • Domain Name
    autoscout24.it
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #2356
  • Page Size
    53.3 KB
  • Ip Address
    92.42.227.69
  • Heading
    H1: 2, H2: 2, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    AutoScout24: Il marketplace europeo delle auto usate e nuove
  • Meta Keyword
    AutoScout24, auto, vendita auto, auto usate, auto nuove, auto km0, automercato
  • Meta Description
    AutoScout24 - il mercato di auto usate, auto nuove e km 0, annunci gratuiti. Cerca l'automobile nel nostro grande database.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    92.42.227.69
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from autoscout24.it.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 4.0.30319
  • sid: LWEBITV004
  • x-powered-by: ASP.NET
  • date: Mon, 17 Jun 2013 16:10:58 GMT
  • content-length: 17505
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Domain Name: autoscout24.it
Domain Status: ok
Created: 1999-05-26 00:00:00
Updated: 2011-11-29 01:24:27
Expires: 2012-11-29
Registrant
Domain Name: AutoScout24 GmbH
Organization: AutoScout24 GmbH
ContactID: IX11176466
Address: Dingolfinger Str. 1-15
Muenchen
81673
Bayern
DE
Created: 2011-04-21 14:49:47
Updated: 2011-04-21 14:49:47
Admin Contact
Domain Name: AutoScout24 GmbH
Organization: AutoScout24 GmbH
ContactID: IX11176466
Address: Dingolfinger Str. 1-15
Muenchen
81673
Bayern
DE
Created: 2011-04-21 14:49:47
Updated: 2011-04-21 14:49:47
Technical Contacts
Domain Name: AutoScout24 GmbH
Organization: AutoScout24 GmbH
ContactID: IX11176466
Address: Dingolfinger Str. 1-15
Muenchen
81673
Bayern
DE
Created: 2011-04-21 14:49:47
Updated: 2011-04-21 14:49:47
Registrar
Organization: InterNetX GmbH
Domain Name: INTERNETXGMBH-REG
Web: http://www.internetx.com/
Name Servers: dnslbrz3.autoscout24.com
dnslbrz2.autoscout24.com

DNS Analysis


DNS servers
dnslbrz2.autoscout24.com [92.42.228.6]
dnslbrz3.autoscout24.com [92.42.224.6]

DNS Records

Answer records
autoscout24.it SOA
server: dnslbrz3.autoscout24.com
email: hostmaster@autoscout24.com
serial: 2009100754
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
900s
autoscout24.it NS  dnslbrz3.autoscout24.com 900s
autoscout24.it NS  dnslbrz2.autoscout24.com 900s
autoscout24.it A 92.42.227.69 900s
autoscout24.it MX
preference: 100
exchange: mail3.autoscout24.com
900s
autoscout24.it MX
preference: 10
exchange: mx1.autoscout24.com
900s
autoscout24.it MX
preference: 100
exchange: mail4.autoscout24.com
900s
autoscout24.it MX
preference: 10
exchange: mx0.autoscout24.com
900s

Authority records

Additional records
dnslbrz3.autoscout24.com A 92.42.224.6 900s
dnslbrz2.autoscout24.com A 92.42.228.6 900s
mx0.autoscout24.com A 92.42.225.93 900s
mail3.autoscout24.com A 92.42.225.35 900s
mx1.autoscout24.com A 92.42.225.92 900s
mail4.autoscout24.com A 92.42.225.34 900s

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 180 Errors
  • 115 Warnings
Ratio Text/Html
  • 0.6084652203414697
Message Error
  • Warning Line 21, Column 625: cannot generate system identifier for general entity "u"
    …eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…

    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 "&" (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 æ 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 21, Column 625: general entity "u" not defined and no default entity
    …eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…

    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 21, Column 626: reference not terminated by REFC delimiter
    …optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…

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

  • Error Line 21, Column 626: reference to entity "u" for which no system identifier could be generated
    …optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…

    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 21, Column 624: entity was defined here
    …teoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Mat…
  • Warning Line 21, Column 657: cannot generate system identifier for general entity "r"
    …_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…

    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 "&" (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 æ 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 21, Column 657: general entity "r" not defined and no default entity
    …_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…

    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 21, Column 658: reference not terminated by REFC delimiter
    …id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…

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

  • Error Line 21, Column 658: reference to entity "r" for which no system identifier could be generated
    …id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…

    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 21, Column 656: entity was defined here
    …t_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElemen…
  • Warning Line 65, Column 145: cannot generate system identifier for general entity "d"
    …/as24itS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

    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 "&" (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 æ 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 65, Column 145: general entity "d" not defined and no default entity
    …/as24itS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

    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 65, Column 146: reference not terminated by REFC delimiter
    …/as24itS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

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

  • Error Line 65, Column 146: reference to entity "d" for which no system identifier could be generated
    …/as24itS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());

    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 65, Column 144: entity was defined here
    …/as24itS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());
  • Error Line 170, Column 134: end tag for element "Div" which is not open
    …tutte le funzionalità del sito devi attivare il Javascript nel tuo browse</Div>

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

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

  • Error Line 177, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
    </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 165, Column 1: start tag was here
    <div style="display:block" id="inpagemsg" class="msg-error">
  • Error Line 194, Column 92: there is no attribute "onMouseOver"
    …ass="used-car-ico-active" onMouseOver="setHoverLabelTxt(&#39;quickSearchTitle&…

    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 194, Column 173: there is no attribute "onMouseOut"
    …;, &#39;Auto usate&#39;);" onMouseOut="setHoverLabelTxt(&#39;quickSearchTitle&…

    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 221, Column 67: end tag for element "Label" which is not open
                    <label class="label-disabled model">Modello</Label>

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

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

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

  • Error Line 223, Column 60: duplicate specification of attribute "name"
                        <select name="model1" id="model1" name="model">

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

  • Error Line 228, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

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

  • Info Line 221, Column 17: start tag was here
                    <label class="label-disabled model">Modello</Label>
  • Error Line 234, Column 48: end tag for element "Label" which is not open
                    <label>Prezzo fino a (€)</Label>

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

    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 264, Column 52: end tag for element "Label" which is not open
                    <label>Chilometraggio fino a</Label>

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

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

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

  • Error Line 288, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

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

  • Info Line 264, Column 17: start tag was here
                    <label>Chilometraggio fino a</Label>
  • Error Line 288, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

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

  • Info Line 234, Column 17: start tag was here
                    <label>Prezzo fino a (€)</Label>
  • Error Line 290, Column 48: end tag for element "Label" which is not open
                    <label>Anno a partire da</Label>

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

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

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

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

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

  • Error Line 349, Column 20: end tag for "label" omitted, but OMITTAG NO was specified
                  </div>

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

  • Info Line 290, Column 17: start tag was here
                    <label>Anno a partire da</Label>
  • Error Line 364, Column 60: end tag for element "Label" which is not open
                        <label class="__radius">Distanza</Label>

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

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

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

  • Error Line 376, Column 24: end tag for "label" omitted, but OMITTAG NO was specified
                      </div>

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

  • Info Line 364, Column 21: start tag was here
                        <label class="__radius">Distanza</Label>
  • Error Line 398, Column 62: end tag for element "Span" which is not open
                  <span id="tcountLabel"><span>Auto trovate</Span></span>

    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 399, Column 18: end tag for "span" omitted, but OMITTAG NO was specified
                </div>

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

  • Info Line 398, Column 15: start tag was here
                  <span id="tcountLabel"><span>Auto trovate</Span></span>
  • Error Line 472, Column 451: there is no attribute "USEMAP"
    …24.com/it-IT/110130/0/0.jpg?timestamp=20121011154432" USEMAP='#map' ></a></div>

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

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

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

  • Error Line 472, Column 458: required attribute "alt" not specified
    …24.com/it-IT/110130/0/0.jpg?timestamp=20121011154432" USEMAP='#map' ></a></div>

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

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

  • Error Line 472, Column 462: end tag for "img" omitted, but OMITTAG NO was specified
    …24.com/it-IT/110130/0/0.jpg?timestamp=20121011154432" USEMAP='#map' ></a></div>

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

  • Info Line 472, Column 357: start tag was here
    …#038;pool=1&#038;zipc=I&#038;make=13'><img src="http://cmspic.autoscout24.com/…
  • Error Line 475, Column 49: end tag for "input" omitted, but OMITTAG NO was specified
    		<input type="button" value="Inserisci gratis">

    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 475, Column 3: start tag was here
    		<input type="button" value="Inserisci gratis">
  • Error Line 519, Column 16: syntax of attribute value does not conform to declared value
    						<div id="" style=";float: right;">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 543, Column 329: there is no attribute "allowTransparency"
    …overflow:hidden; width:329px; height:282px;" allowTransparency="true"></iframe>

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

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

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

  • Warning Line 626, Column 154: cannot generate system identifier for general entity "language"
    …t24.com/adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1">…

    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 626, Column 154: general entity "language" not defined and no default entity
    …t24.com/adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1">…

    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 626, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script…

    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 626, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script…

    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 626, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script…

    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 626, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"…
  • Warning Line 626, Column 167: cannot generate system identifier for general entity "siteid"
    …ver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></di…

    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 626, Column 167: general entity "siteid" not defined and no default entity
    …ver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></di…

    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 626, Column 173: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 173: reference to external entity in attribute value
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 166: entity was defined here
    …rver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></d…
  • Warning Line 626, Column 176: cannot generate system identifier for general entity "elementid"
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 176: general entity "elementid" not defined and no default entity
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 185: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 185: reference to external entity in attribute value
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 185: reference to entity "elementid" for which no system identifier could be generated
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>

    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 626, Column 175: entity was defined here
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>
  • Warning Line 627, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script…

    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 627, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script…

    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 627, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script…

    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 626, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"…
  • Warning Line 627, Column 173: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script></div>

    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 627, Column 173: reference to external entity in attribute value
    …er/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script></div>

    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 627, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …er/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script></div>

    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 626, Column 166: entity was defined here
    …rver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></d…
  • Warning Line 627, Column 185: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script></div>

    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 627, Column 185: reference to external entity in attribute value
    …er/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script></div>

    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 627, Column 185: reference to entity "elementid" for which no system identifier could be generated
    …er/index4.aspx?slot=386&language=ita&siteid=1&elementid=slot-2"></script></div>

    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 626, Column 175: entity was defined here
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>
  • Warning Line 628, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script…

    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 628, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script…

    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 628, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script…

    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 626, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"…
  • Warning Line 628, Column 173: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script></div>

    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 628, Column 173: reference to external entity in attribute value
    …er/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script></div>

    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 628, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …er/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script></div>

    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 626, Column 166: entity was defined here
    …rver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></d…
  • Warning Line 628, Column 185: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script></div>

    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 628, Column 185: reference to external entity in attribute value
    …er/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script></div>

    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 628, Column 185: reference to entity "elementid" for which no system identifier could be generated
    …er/index4.aspx?slot=387&language=ita&siteid=1&elementid=slot-3"></script></div>

    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 626, Column 175: entity was defined here
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>
  • Warning Line 629, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script…

    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 629, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script…

    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 629, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script…

    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 626, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"…
  • Warning Line 629, Column 173: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script></div>

    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 629, Column 173: reference to external entity in attribute value
    …er/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script></div>

    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 629, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …er/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script></div>

    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 626, Column 166: entity was defined here
    …rver/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></d…
  • Warning Line 629, Column 185: reference not terminated by REFC delimiter
    …er/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script></div>

    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 629, Column 185: reference to external entity in attribute value
    …er/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script></div>

    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 629, Column 185: reference to entity "elementid" for which no system identifier could be generated
    …er/index4.aspx?slot=388&language=ita&siteid=1&elementid=slot-4"></script></div>

    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 626, Column 175: entity was defined here
    …er/index4.aspx?slot=385&language=ita&siteid=1&elementid=slot-1"></script></div>
  • Error Line 648, Column 62: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/bmw/">BMW</li></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 648, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/bmw/">BMW</li></a>
  • Error Line 648, Column 66: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/bmw/">BMW</li></a>

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

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

  • Error Line 649, Column 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/audi/">Audi</li></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 649, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/audi/">Audi</li></a>
  • Error Line 649, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/audi/">Audi</li></a>

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

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

  • Error Line 650, Column 82: end tag for "a" omitted, but OMITTAG NO was specified
    … href="http://www.autoscout24.it/modelli/mercedes-benz/">Mercedes-Benz</li></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 650, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/mercedes-benz/">Mercedes-Benz</…
  • Error Line 650, Column 86: end tag for element "a" which is not open
    … href="http://www.autoscout24.it/modelli/mercedes-benz/">Mercedes-Benz</li></a>

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

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

  • Error Line 651, Column 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/fiat/">Fiat</li></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 651, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/fiat/">Fiat</li></a>
  • Error Line 651, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/fiat/">Fiat</li></a>

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

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

  • Error Line 652, Column 76: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/alfa-romeo/">Alfa Romeo</li></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 652, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/alfa-romeo/">Alfa Romeo</li></a>
  • Error Line 652, Column 80: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/alfa-romeo/">Alfa Romeo</li></a>

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

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

  • Error Line 653, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/porsche/">Porsche</li></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 653, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/porsche/">Porsche</li></a>
  • Error Line 653, Column 74: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/porsche/">Porsche</li></a>

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

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

  • Error Line 654, Column 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/ford/">Ford</li></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 654, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/ford/">Ford</li></a>
  • Error Line 654, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/ford/">Ford</li></a>

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

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

  • Error Line 655, Column 60: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/vw/">VW</li></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 655, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/vw/">VW</li></a>
  • Error Line 655, Column 64: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/vw/">VW</li></a>

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

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

  • Error Line 666, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/renault/">Renault</li></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 666, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/renault/">Renault</li></a>
  • Error Line 666, Column 74: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/renault/">Renault</li></a>

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

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

  • Error Line 667, Column 64: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/opel/">Opel</li></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 667, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/opel/">Opel</li></a>
  • Error Line 667, Column 68: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/opel/">Opel</li></a>

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

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

  • Error Line 668, Column 76: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/land-rover/">Land Rover</li></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 668, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/land-rover/">Land Rover</li></a>
  • Error Line 668, Column 80: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/land-rover/">Land Rover</li></a>

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

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

  • Error Line 669, Column 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/toyota/">Toyota</li></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 669, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/toyota/">Toyota</li></a>
  • Error Line 669, Column 72: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/toyota/">Toyota</li></a>

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

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

  • Error Line 670, Column 73: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/vw/vw-golf/">VW Golf</li></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 670, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/vw/vw-golf/">VW Golf</li></a>
  • Error Line 670, Column 77: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/vw/vw-golf/">VW Golf</li></a>

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

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

  • Error Line 671, Column 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a4/">Audi A4</li></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 671, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a4/">Audi A4</li></a>
  • Error Line 671, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a4/">Audi A4</li></a>

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

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

  • Error Line 672, Column 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a3/">Audi A3</li></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 672, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a3/">Audi A3</li></a>
  • Error Line 672, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a3/">Audi A3</li></a>

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

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

  • Error Line 673, Column 70: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/bmw/bmw-3/">BMW 3</li></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 673, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/bmw/bmw-3/">BMW 3</li></a>
  • Error Line 673, Column 74: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/bmw/bmw-3/">BMW 3</li></a>

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

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

  • Error Line 684, Column 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a6/">Audi A6</li></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 684, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a6/">Audi A6</li></a>
  • Error Line 684, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-a6/">Audi A6</li></a>

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

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

  • Error Line 685, Column 77: end tag for "a" omitted, but OMITTAG NO was specified
    …li><a href="http://www.autoscout24.it/modelli/vw/vw-passat/">VW Passat</li></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 685, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/vw/vw-passat/">VW Passat</li></…
  • Error Line 685, Column 81: end tag for element "a" which is not open
    …li><a href="http://www.autoscout24.it/modelli/vw/vw-passat/">VW Passat</li></a>

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

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

  • Error Line 686, Column 78: end tag for "a" omitted, but OMITTAG NO was specified
    …i><a href="http://www.autoscout24.it/modelli/bmw/bmw-x/bmw-x5/">BMW X5</li></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 686, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/bmw/bmw-x/bmw-x5/">BMW X5</li><…
  • Error Line 686, Column 82: end tag for element "a" which is not open
    …i><a href="http://www.autoscout24.it/modelli/bmw/bmw-x/bmw-x5/">BMW X5</li></a>

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

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

  • Error Line 687, Column 75: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-tt/">Audi TT</li></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 687, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-tt/">Audi TT</li></a>
  • Error Line 687, Column 79: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/audi/audi-tt/">Audi TT</li></a>

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

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

  • Error Line 688, Column 81: end tag for "a" omitted, but OMITTAG NO was specified
    …a href="http://www.autoscout24.it/modelli/fiat/fiat-punto/">Fiat Punto</li></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 688, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/fiat/fiat-punto/">Fiat Punto</l…
  • Error Line 688, Column 85: end tag for element "a" which is not open
    …a href="http://www.autoscout24.it/modelli/fiat/fiat-punto/">Fiat Punto</li></a>

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

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

  • Error Line 689, Column 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.it/modelli/alfa-romeo/alfa-romeo-147/">Alfa Romeo 147</li></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 689, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/alfa-romeo/alfa-romeo-147/">Alf…
  • Error Line 689, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.it/modelli/alfa-romeo/alfa-romeo-147/">Alfa Romeo 147</li></a>

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

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

  • Error Line 690, Column 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.it/modelli/alfa-romeo/alfa-romeo-159/">Alfa Romeo 159</li></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 690, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/alfa-romeo/alfa-romeo-159/">Alf…
  • Error Line 690, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.it/modelli/alfa-romeo/alfa-romeo-159/">Alfa Romeo 159</li></a>

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

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

  • Error Line 691, Column 81: end tag for "a" omitted, but OMITTAG NO was specified
    …a href="http://www.autoscout24.it/modelli/fiat/fiat-panda/">Fiat Panda</li></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 691, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/fiat/fiat-panda/">Fiat Panda</l…
  • Error Line 691, Column 85: end tag for element "a" which is not open
    …a href="http://www.autoscout24.it/modelli/fiat/fiat-panda/">Fiat Panda</li></a>

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

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

  • Error Line 702, Column 78: end tag for "a" omitted, but OMITTAG NO was specified
    …i><a href="http://www.autoscout24.it/modelli/fuoristrada/">Fuoristrada</li></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 702, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/fuoristrada/">Fuoristrada</li><…
  • Error Line 702, Column 82: end tag for element "a" which is not open
    …i><a href="http://www.autoscout24.it/modelli/fuoristrada/">Fuoristrada</li></a>

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

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

  • Error Line 703, Column 76: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/monovolume/">Monovolume</li></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 703, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/monovolume/">Monovolume</li></a>
  • Error Line 703, Column 80: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/monovolume/">Monovolume</li></a>

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

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

  • Error Line 704, Column 68: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/cabrio/">Cabrio</li></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 704, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/cabrio/">Cabrio</li></a>
  • Error Line 704, Column 72: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/cabrio/">Cabrio</li></a>

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

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

  • Error Line 705, Column 82: end tag for "a" omitted, but OMITTAG NO was specified
    … href="http://www.autoscout24.it/modelli/auto-sportive/">Auto sportive</li></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 705, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/auto-sportive/">Auto sportive</…
  • Error Line 705, Column 86: end tag for element "a" which is not open
    … href="http://www.autoscout24.it/modelli/auto-sportive/">Auto sportive</li></a>

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

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

  • Error Line 706, Column 73: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/coupe/">Coup&eacute;</li></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 706, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/coupe/">Coup&eacute;</li></a>
  • Error Line 706, Column 77: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/coupe/">Coup&eacute;</li></a>

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

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

  • Error Line 707, Column 82: end tag for "a" omitted, but OMITTAG NO was specified
    … href="http://www.autoscout24.it/modelli/auto-a-metano/">Auto a metano</li></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 707, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/auto-a-metano/">Auto a metano</…
  • Error Line 707, Column 86: end tag for element "a" which is not open
    … href="http://www.autoscout24.it/modelli/auto-a-metano/">Auto a metano</li></a>

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

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

  • Error Line 708, Column 78: end tag for "a" omitted, but OMITTAG NO was specified
    …i><a href="http://www.autoscout24.it/modelli/auto-ibride/">Auto Ibride</li></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 708, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/auto-ibride/">Auto Ibride</li><…
  • Error Line 708, Column 82: end tag for element "a" which is not open
    …i><a href="http://www.autoscout24.it/modelli/auto-ibride/">Auto Ibride</li></a>

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

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

  • Error Line 709, Column 62: end tag for "a" omitted, but OMITTAG NO was specified
    	<li><a href="http://www.autoscout24.it/modelli/suv/">SUV</li></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 709, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.it/modelli/suv/">SUV</li></a>
  • Error Line 709, Column 66: end tag for element "a" which is not open
    	<li><a href="http://www.autoscout24.it/modelli/suv/">SUV</li></a>

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

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

  • Error Line 745, Column 23: there is no attribute "name"
                <div name="slot_110149" id="adTagHeader">

    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 763, Column 13: there is no attribute "SRC"
    <SCRIPT SRC="http://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x25…

    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.

  • Warning Line 763, Column 49: cannot generate system identifier for general entity "size"
    …C="http://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="…

    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 763, Column 49: general entity "size" not defined and no default entity
    …C="http://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="…

    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 763, Column 53: reference not terminated by REFC delimiter
    …ttp://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text…

    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 763, Column 53: reference to external entity in attribute value
    …ttp://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text…

    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 763, Column 53: reference to entity "size" for which no system identifier could be generated
    …ttp://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text…

    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 763, Column 48: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE=…
  • Warning Line 763, Column 62: cannot generate system identifier for general entity "promo_sizes"
    …adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascri…

    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 763, Column 62: general entity "promo_sizes" not defined and no default entity
    …adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascri…

    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 763, Column 73: reference not terminated by REFC delimiter
    …tj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascript"></SCRIP…

    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 763, Column 73: reference to external entity in attribute value
    …tj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascript"></SCRIP…

    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 763, Column 73: reference to entity "promo_sizes" for which no system identifier could be generated
    …tj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascript"></SCRIP…

    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 763, Column 61: entity was defined here
    ….adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascr…
  • Error Line 763, Column 88: there is no attribute "TYPE"
    …j?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascript"></SCRIPT>

    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 763, Column 105: element "SCRIPT" undefined
    …j?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascript"></SCRIPT>

    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 797, Column 62: cannot generate system identifier for general entity "link"
    …autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit…

    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 797, Column 62: general entity "link" not defined and no default entity
    …autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit…

    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 797, Column 66: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 66: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 66: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ei…
  • Warning Line 797, Column 144: cannot generate system identifier for general entity "name"
    …agazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var…

    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 797, Column 144: general entity "name" not defined and no default entity
    …agazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var…

    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 797, Column 148: reference not terminated by REFC delimiter
    …ine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s…

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

  • Warning Line 797, Column 148: reference to external entity in attribute value
    …ine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s…

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

  • Error Line 797, Column 148: reference to entity "name" for which no system identifier could be generated
    …ine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s…

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

  • Info Line 797, Column 143: entity was defined here
    …magazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="va…
  • Warning Line 797, Column 163: cannot generate system identifier for general entity "site"
    …rs%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout2…

    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 797, Column 163: general entity "site" not defined and no default entity
    …rs%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout2…

    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 797, Column 167: reference not terminated by REFC delimiter
    …Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 797, Column 167: reference to external entity in attribute value
    …Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 797, Column 167: reference to entity "site" for which no system identifier could be generated
    …Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 797, Column 162: entity was defined here
    …ers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 797, Column 416: required attribute "alt" not specified
    …tp://cmspic.autoscout24.com/it-IT/110114/0/0.jpg?timestamp=20130301112533"></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 797, Column 420: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://cmspic.autoscout24.com/it-IT/110114/0/0.jpg?timestamp=20130301112533"></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 797, Column 330: start tag was here
    …i';s.tl(this,'o', 'Mag-HP-sw-audi');"><img src="http://cmspic.autoscout24.com/…
  • Warning Line 804, Column 69: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 804, Column 69: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 804, Column 69: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ei…
  • Warning Line 804, Column 151: reference not terminated by REFC delimiter
    …ine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s…

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

  • Warning Line 804, Column 151: reference to external entity in attribute value
    …ine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s…

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

  • Error Line 804, Column 151: reference to entity "name" for which no system identifier could be generated
    …ine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s…

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

  • Info Line 797, Column 143: entity was defined here
    …magazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="va…
  • Warning Line 804, Column 170: reference not terminated by REFC delimiter
    …Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 804, Column 170: reference to external entity in attribute value
    …Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 804, Column 170: reference to entity "site" for which no system identifier could be generated
    …Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 797, Column 162: entity was defined here
    …ers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 804, Column 351: end tag for element "nobr" which is not open
    ….eVar16='Mag-HP-sw-audi';s.tl(this,'o', 'Mag-HP-sw-audi');">Dettagli</a></nobr>

    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.

  • Warning Line 811, Column 73: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 811, Column 73: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 811, Column 73: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ei…
  • Warning Line 811, Column 166: reference not terminated by REFC delimiter
    …others%2Fsw%5Frenault%2Dselection&name=hp_tb_sw-renault&site=1" id="sw-renault…

    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 811, Column 166: reference to external entity in attribute value
    …others%2Fsw%5Frenault%2Dselection&name=hp_tb_sw-renault&site=1" id="sw-renault…

    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 811, Column 166: reference to entity "name" for which no system identifier could be generated
    …others%2Fsw%5Frenault%2Dselection&name=hp_tb_sw-renault&site=1" id="sw-renault…

    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 797, Column 143: entity was defined here
    …magazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="va…
  • Warning Line 811, Column 188: reference not terminated by REFC delimiter
    …2Dselection&name=hp_tb_sw-renault&site=1" id="sw-renault">Renault</option><opt…

    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 811, Column 188: reference to external entity in attribute value
    …2Dselection&name=hp_tb_sw-renault&site=1" id="sw-renault">Renault</option><opt…

    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 811, Column 188: reference to entity "site" for which no system identifier could be generated
    …2Dselection&name=hp_tb_sw-renault&site=1" id="sw-renault">Renault</option><opt…

    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 797, Column 162: entity was defined here
    …ers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout…
  • Warning Line 811, Column 292: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 811, Column 292: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 811, Column 292: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ei…
  • Warning Line 811, Column 373: reference not terminated by REFC delimiter
    …zine%2Fmz%5Fothers%2Fsw%5Fhyundai&name=hp_tb_sw-hyundai&site=1" id="sw-hyundai…

    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 811, Column 373: reference to external entity in attribute value
    …zine%2Fmz%5Fothers%2Fsw%5Fhyundai&name=hp_tb_sw-hyundai&site=1" id="sw-hyundai…

    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 811, Column 373: reference to entity "name" for which no system identifier could be generated
    …zine%2Fmz%5Fothers%2Fsw%5Fhyundai&name=hp_tb_sw-hyundai&site=1" id="sw-hyundai…

    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 797, Column 143: entity was defined here
    …magazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="va…
  • Warning Line 811, Column 395: reference not terminated by REFC delimiter
    …s%2Fsw%5Fhyundai&name=hp_tb_sw-hyundai&site=1" id="sw-hyundai">Hyundai</option>

    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 811, Column 395: reference to external entity in attribute value
    …s%2Fsw%5Fhyundai&name=hp_tb_sw-hyundai&site=1" id="sw-hyundai">Hyundai</option>

    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 811, Column 395: reference to entity "site" for which no system identifier could be generated
    …s%2Fsw%5Fhyundai&name=hp_tb_sw-hyundai&site=1" id="sw-hyundai">Hyundai</option>

    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 797, Column 162: entity was defined here
    …ers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout…
  • Warning Line 832, Column 66: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 832, Column 66: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 832, Column 66: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ei…
  • Warning Line 832, Column 148: reference not terminated by REFC delimiter
    …ine%2Fmz%5Fothers%2Faw%5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var…

    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 832, Column 148: reference to external entity in attribute value
    …ine%2Fmz%5Fothers%2Faw%5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var…

    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 832, Column 148: reference to entity "name" for which no system identifier could be generated
    …ine%2Fmz%5Fothers%2Faw%5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var…

    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 797, Column 143: entity was defined here
    …magazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="va…
  • Warning Line 832, Column 171: reference not terminated by REFC delimiter
    …5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 832, Column 171: reference to external entity in attribute value
    …5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 832, Column 171: reference to entity "site" for which no system identifier could be generated
    …5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 797, Column 162: entity was defined here
    …ers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 832, Column 432: required attribute "alt" not specified
    …tp://cmspic.autoscout24.com/it-IT/110115/0/0.jpg?timestamp=20130301112533"></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 832, Column 436: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://cmspic.autoscout24.com/it-IT/110115/0/0.jpg?timestamp=20130301112533"></a>

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

  • Info Line 832, Column 346: start tag was here
    ….tl(this,'o', 'Mag-HP-aw-maserati');"><img src="http://cmspic.autoscout24.com/…
  • Warning Line 839, Column 69: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

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

  • Warning Line 839, Column 69: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

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

  • Error Line 839, Column 69: reference to entity "link" for which no system identifier could be generated
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Eit%2Fm…

    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 797, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ei…
  • Warning Line 839, Column 151: reference not terminated by REFC delimiter
    …ine%2Fmz%5Fothers%2Faw%5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var…

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

  • Warning Line 839, Column 151: reference to external entity in attribute value
    …ine%2Fmz%5Fothers%2Faw%5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var…

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

  • Error Line 839, Column 151: reference to entity "name" for which no system identifier could be generated
    …ine%2Fmz%5Fothers%2Faw%5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var…

    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 797, Column 143: entity was defined here
    …magazine%2Fmz%5Fothers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="va…
  • Warning Line 839, Column 174: reference not terminated by REFC delimiter
    …5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var s=s_gi('autoscout24it'…

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

  • Warning Line 839, Column 174: reference to external entity in attribute value
    …5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var s=s_gi('autoscout24it'…

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

  • Error Line 839, Column 174: reference to entity "site" for which no system identifier could be generated
    …5Fmaserati&name=hp_tb_aw-maserati&site=1"  onclick="var s=s_gi('autoscout24it'…

    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 797, Column 162: entity was defined here
    …ers%2Fsw%5Faudiplus&name=hp_tb_sw-audi&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 839, Column 367: end tag for element "nobr" which is not open
    …'Mag-HP-aw-maserati';s.tl(this,'o', 'Mag-HP-aw-maserati');">Dettagli</a></nobr>

    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.

  • Warning Line 873, Column 81: cannot generate system identifier for general entity "c"
    …://dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 99…

    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 873, Column 81: general entity "c" not defined and no default entity
    …://dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 99…

    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 873, Column 82: reference not terminated by REFC delimiter
    …//dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 999…

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

  • Error Line 873, Column 82: reference to entity "c" for which no system identifier could be generated
    …//dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 999…

    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 873, Column 80: entity was defined here
    …p://dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 9…
  • Warning Line 873, Column 85: cannot generate system identifier for general entity "cb"
    …is.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 999999…

    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 873, Column 85: general entity "cb" not defined and no default entity
    …is.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 999999…

    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 873, Column 87: reference not terminated by REFC delimiter
    ….criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 99999999…

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

  • Error Line 873, Column 87: reference to entity "cb" for which no system identifier could be generated
    ….criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 99999999…

    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 873, Column 84: entity was defined here
    …dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 99999…
  • Warning Line 875, Column 41: cannot generate system identifier for general entity "ref"
    …                  cto_dis_im_src += '&ref=' + encodeURIComponent(document.refe…

    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 875, Column 41: general entity "ref" not defined and no default entity
    …                  cto_dis_im_src += '&ref=' + encodeURIComponent(document.refe…

    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 875, Column 44: reference not terminated by REFC delimiter
    …               cto_dis_im_src += '&ref=' + encodeURIComponent(document.referre…

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

  • Error Line 875, Column 44: reference to entity "ref" for which no system identifier could be generated
    …               cto_dis_im_src += '&ref=' + encodeURIComponent(document.referre…

    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 875, Column 40: entity was defined here
    …                   cto_dis_im_src += '&ref=' + encodeURIComponent(document.ref…
  • Warning Line 880, Column 42: character "&" is the first character of a delimiter but occurred as data
                    if (cto_dis_doc !== null &&

    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 880, Column 43: character "&" is the first character of a delimiter but occurred as data
                    if (cto_dis_doc !== null &&

    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 888, Column 61: document type does not allow element "div" here
    …iv').append('<div style="display:none"><img src="http://autoscout24.widget.cri…

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

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

  • Warning Line 888, Column 143: cannot generate system identifier for general entity "wi"
    …com/pac/display.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEven…

    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 888, Column 143: general entity "wi" not defined and no default entity
    …com/pac/display.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEven…

    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 888, Column 145: reference not terminated by REFC delimiter
    …m/pac/display.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&…

    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 888, Column 145: reference to external entity in attribute value
    …m/pac/display.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&…

    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 888, Column 145: reference to entity "wi" for which no system identifier could be generated
    …m/pac/display.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&…

    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 888, Column 142: entity was defined here
    ….com/pac/display.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEve…
  • Warning Line 888, Column 154: cannot generate system identifier for general entity "pt1"
    …play.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=…

    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 888, Column 154: general entity "pt1" not defined and no default entity
    …play.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=…

    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 888, Column 157: reference not terminated by REFC delimiter
    …y.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif…

    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 888, Column 157: reference to external entity in attribute value
    …y.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif…

    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 888, Column 157: reference to entity "pt1" for which no system identifier could be generated
    …y.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif…

    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 888, Column 153: entity was defined here
    …splay.js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype…
  • Warning Line 888, Column 160: cannot generate system identifier for general entity "pt2"
    …s?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb…

    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 888, Column 160: general entity "pt2" not defined and no default entity
    …s?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb…

    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 888, Column 163: reference not terminated by REFC delimiter
    …1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' …

    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 888, Column 163: reference to external entity in attribute value
    …1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' …

    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 888, Column 163: reference to entity "pt2" for which no system identifier could be generated
    …1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' …

    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 888, Column 159: entity was defined here
    …js?p1=' + escape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&c…
  • Warning Line 888, Column 172: cannot generate system identifier for general entity "t1"
    …ape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.fl…

    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 888, Column 172: general entity "t1" not defined and no default entity
    …ape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.fl…

    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 888, Column 174: reference not terminated by REFC delimiter
    …e('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floo…

    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 888, Column 174: reference to external entity in attribute value
    …e('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floo…

    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 888, Column 174: reference to entity "t1" for which no system identifier could be generated
    …e('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floo…

    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 888, Column 171: entity was defined here
    …cape('v=2&wi=7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.f…
  • Warning Line 888, Column 185: cannot generate system identifier for general entity "resptype"
    …709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.rand…

    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 888, Column 185: general entity "resptype" not defined and no default entity
    …709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.rand…

    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 888, Column 193: reference not terminated by REFC delimiter
    …t1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 9…

    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 888, Column 193: reference to external entity in attribute value
    …t1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 9…

    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 888, Column 193: reference to entity "resptype" for which no system identifier could be generated
    …t1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 9…

    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 888, Column 184: entity was defined here
    …7709483&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.ran…
  • Warning Line 888, Column 200: reference not terminated by REFC delimiter
    …2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999…

    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 888, Column 200: reference to external entity in attribute value
    …2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999…

    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 888, Column 200: reference to entity "cb" for which no system identifier could be generated
    …2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999…

    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 873, Column 84: entity was defined here
    …dis.criteo.com/dis/dis.aspx?p=1092&c=2&cb=' + Math.floor(Math.random() * 99999…
  • Error Line 888, Column 250: required attribute "alt" not specified
    …ent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999999) + '"/></div>');

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

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

  • Warning Line 960, Column 141: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://del.icio.us…

    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 960, Column 191: cannot generate system identifier for general entity "noui"
    …dow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent…

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

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

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

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

  • Error Line 960, Column 191: general entity "noui" not defined and no default entity
    …dow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent…

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

  • Warning Line 960, Column 195: reference not terminated by REFC delimiter
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…

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

  • Warning Line 960, Column 195: reference to external entity in attribute value
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…

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

  • Error Line 960, Column 195: reference to entity "noui" for which no system identifier could be generated
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…

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

  • Info Line 960, Column 190: entity was defined here
    …ndow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponen…
  • Warning Line 960, Column 196: cannot generate system identifier for general entity "jump"
    …pen('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loca…

    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 960, Column 196: general entity "jump" not defined and no default entity
    …pen('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loca…

    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 960, Column 200: reference not terminated by REFC delimiter
    …'http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location…

    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 960, Column 200: reference to external entity in attribute value
    …'http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location…

    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 960, Column 200: reference to entity "jump" for which no system identifier could be generated
    …'http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location…

    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 960, Column 195: entity was defined here
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…
  • Warning Line 960, Column 207: cannot generate system identifier for general entity "url"
    …/del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+s…

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

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

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

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

  • Error Line 960, Column 207: general entity "url" not defined and no default entity
    …/del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+s…

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

  • Warning Line 960, Column 210: reference not terminated by REFC delimiter
    …l.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+sb_p…

    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 960, Column 210: reference to external entity in attribute value
    …l.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+sb_p…

    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 960, Column 210: reference to entity "url" for which no system identifier could be generated
    …l.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+sb_p…

    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 960, Column 206: entity was defined here
    …//del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+…
  • Warning Line 960, Column 282: cannot generate system identifier for general entity "title"
    …f+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.titl…

    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 960, Column 282: general entity "title" not defined and no default entity
    …f+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.titl…

    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 960, Column 287: reference not terminated by REFC delimiter
    …prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.title), '…

    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 960, Column 287: reference to external entity in attribute value
    …prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.title), '…

    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 960, Column 287: reference to entity "title" for which no system identifier could be generated
    …prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.title), '…

    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 960, Column 281: entity was defined here
    …ef+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.tit…
  • Warning Line 960, Column 700: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://myweb2.sear…

    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 960, Column 854: cannot generate system identifier for general entity "t"
    …refix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'…

    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 960, Column 854: general entity "t" not defined and no default entity
    …refix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'…

    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 960, Column 855: reference not terminated by REFC delimiter
    …efix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'y…

    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 960, Column 855: reference to external entity in attribute value
    …efix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'y…

    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 960, Column 855: reference to entity "t" for which no system identifier could be generated
    …efix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),'y…

    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 960, Column 853: entity was defined here
    …prefix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),…
  • Error Line 967, Column 7: required attribute "type" not specified
    <style>

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

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

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

  • Warning Line 1030, Column 53: reference not terminated by REFC delimiter
    …ttp://ib.adnxs.com/ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/j…

    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 1030, Column 53: reference to external entity in attribute value
    …ttp://ib.adnxs.com/ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/j…

    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 1030, Column 53: reference to entity "size" for which no system identifier could be generated
    …ttp://ib.adnxs.com/ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/j…

    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 763, Column 48: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE=…
  • Warning Line 1030, Column 72: reference not terminated by REFC delimiter
    …ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/javascript"></SCRIPT…

    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 1030, Column 72: reference to external entity in attribute value
    …ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/javascript"></SCRIPT…

    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 1030, Column 72: reference to entity "promo_sizes" for which no system identifier could be generated
    …ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/javascript"></SCRIPT…

    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 763, Column 61: entity was defined here
    ….adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascr…
  • Error Line 1030, Column 103: element "SCRIPT" undefined
    …ttj?id=1115909&size=728x90&promo_sizes=822x90" TYPE="text/javascript"></SCRIPT>

    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 1035, Column 53: reference not terminated by REFC delimiter
    …ttp://ib.adnxs.com/ttj?id=1115909&size=120x600&promo_sizes=160x1000,300x600,16…

    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 1035, Column 53: reference to external entity in attribute value
    …ttp://ib.adnxs.com/ttj?id=1115909&size=120x600&promo_sizes=160x1000,300x600,16…

    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 1035, Column 53: reference to entity "size" for which no system identifier could be generated
    …ttp://ib.adnxs.com/ttj?id=1115909&size=120x600&promo_sizes=160x1000,300x600,16…

    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 763, Column 48: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE=…
  • Warning Line 1035, Column 73: reference not terminated by REFC delimiter
    …tj?id=1115909&size=120x600&promo_sizes=160x1000,300x600,160x600" TYPE="text/ja…

    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 1035, Column 73: reference to external entity in attribute value
    …tj?id=1115909&size=120x600&promo_sizes=160x1000,300x600,160x600" TYPE="text/ja…

    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 1035, Column 73: reference to entity "promo_sizes" for which no system identifier could be generated
    …tj?id=1115909&size=120x600&promo_sizes=160x1000,300x600,160x600" TYPE="text/ja…

    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 763, Column 61: entity was defined here
    ….adnxs.com/ttj?id=1115909&size=300x250&promo_sizes=320x250" TYPE="text/javascr…
  • Error Line 1035, Column 122: element "SCRIPT" undefined
    …=120x600&promo_sizes=160x1000,300x600,160x600" TYPE="text/javascript"></SCRIPT>

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

Visitor Analysis

Daily Visitor
  • 41.417 visits
Daily Visitor