+200 000 voitures neuves et occasions, motos et utilitaires en France - 2 245 797 en Europe , acheter et vendre auto, moto, utilitaire, petites annonces auto gratuites, auto occasion et ...

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

Website Meta Analysis

  • Title
    AutoScout24: +200.000 voitures d'occasion et autos neuves
  • Meta Keyword
    voiture occasion, voitures occasion, voitures d' occasion, vendre voiture, auto occasion, vente voiture occasion, annonces voiture, occasion voiture, petite annonce gratuite
  • Meta Description
    +200 000 voitures neuves et occasions, motos et utilitaires en France - 2 245 797 en Europe , acheter et vendre auto, moto, utilitaire, petites annonces auto gratuites, auto occasion et neuve. Conseils pour l'achat et la vente de voiture d' occasion.

Technical Analysis

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

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnetmvc-version: 3.0
  • x-aspnet-version: 4.0.30319
  • sid: LWEBFRV002
  • x-powered-by: ASP.NET
  • date: Sat, 03 Aug 2013 12:03:50 GMT
  • content-length: 15173
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
%%
%% This is the AFNIC Whois server.
%%
%% complete date format : DD/MM/YYYY
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See http://www.afnic.fr/afnic/web/mentions-legales-whois_en
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [149.47.75.163 REQUEST] >> autoscout24.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%

domain: autoscout24.fr
status: ACTIVE
hold: NO
holder-c: AG7270-FRNIC
admin-c: SIMA4-FRNIC
tech-c: AG7129-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL7204-FRNIC
registrar: InterNetX GmbH
anniversary: 13/02
created: 04/11/2008
last-update: 13/02/2012
source: FRNIC

ns-list: NSL7204-FRNIC
nserver: dnslbrz3.autoscout24.com
nserver: dnslbrz2.autoscout24.com
source: FRNIC

registrar: InterNetX GmbH
type: Isp Option 1
address: Maximilianstrasse 6
address: 93047 REGENSBURG
country: DE
phone: +49 941 595 59 0
fax-no: +49 941 595 59 55
e-mail: email
website: http://www.internetx.de
anonymous: NO
registered: 02/07/2001
source: FRNIC

nic-hdl: SIMA4-FRNIC
type: ORGANIZATION
contact: Scout24 International Management AG
address: Neuhofstrasse 4
address: 6341 Baar
country: CH
phone: +41 417687776
fax-no: +41 417687885
e-mail: email
changed: 26/01/2012 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: AG7129-FRNIC
type: ORGANIZATION
contact: AutoScout24 GmbH
address: Dingolfinger Str. 1-15
address: 81673 Muenchen
country: DE
phone: +49 89444560
fax-no: +49 89444563000
e-mail: email
changed: 30/01/2012 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: AG7270-FRNIC
type: ORGANIZATION
contact: AutoScout24 GmbH
address: Dingolfinger Str. 1-15
address: 81673 Muenchen
country: DE
phone: +49 89444560
fax-no: +49 89444563000
e-mail: email
changed: 09/02/2012 email
anonymous: NO
obsoleted: NO
source: FRNIC

DNS Analysis


DNS servers
dnslbrz3.autoscout24.com
dnslbrz2.autoscout24.com


DNS Records

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

Authority records

Additional records
dnslbrz2.autoscout24.com A 92.42.228.6 900s
dnslbrz3.autoscout24.com A 92.42.224.6 900s
mx0.autoscout24.com A 92.42.225.93 900s
mx1.autoscout24.com A 92.42.225.92 900s
mail3.autoscout24.com A 92.42.225.35 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
  • 148 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.6674359017867748
Message Error
  • Warning Line 47, Column 145: cannot generate system identifier for general entity "d"
    …/as24frS.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 47, Column 145: general entity "d" not defined and no default entity
    …/as24frS.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 47, Column 146: reference not terminated by REFC delimiter
    …/as24frS.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 47, Column 146: reference to entity "d" for which no system identifier could be generated
    …/as24frS.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 47, Column 144: entity was defined here
    …/as24frS.html?r=" + escape(document.referrer) + "&d=" + Date.parse(new Date());
  • Error Line 157, Column 174: end tag for element "Div" which is not open
    …notre site internet veuillez autoriser Javascript dans votre navigateur. </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 164, 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 152, Column 1: start tag was here
    <div style="display:block" id="inpagemsg" class="msg-error">
  • Error Line 181, Column 98: 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 181, Column 185: there is no attribute "onMouseOut"
    …9;Voiture occasion&#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 208, Column 66: end tag for element "Label" which is not open
                    <label class="label-disabled model">Modèle</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 209, 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 210, 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 215, 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 208, Column 17: start tag was here
                    <label class="label-disabled model">Modèle</Label>
  • Error Line 221, Column 47: end tag for element "Label" which is not open
                    <label>Prix (€) jusqu'à</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 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 251, Column 50: end tag for element "Label" which is not open
                    <label>Kilométrage jusqu'à</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 252, 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 275, 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 251, Column 17: start tag was here
                    <label>Kilométrage jusqu'à</Label>
  • Error Line 275, 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>Prix (€) jusqu'à</Label>
  • Error Line 277, Column 48: end tag for element "Label" which is not open
                    <label>Année à partir de</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 278, 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 325, 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 331, 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 336, 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 277, Column 17: start tag was here
                    <label>Année à partir de</Label>
  • Error Line 352, Column 57: end tag for element "Label" which is not open
                        <label class="__radius">Rayon</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 353, 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 364, 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 352, Column 21: start tag was here
                        <label class="__radius">Rayon</Label>
  • Error Line 386, Column 59: end tag for element "Span" which is not open
                  <span id="tcountLabel"><span>en Europe</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 387, 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 386, Column 15: start tag was here
                  <span id="tcountLabel"><span>en Europe</Span></span>
  • Error Line 461, Column 302: there is no attribute "USEMAP"
    …oscout24.com/fr-FR/110130/1/20121122113547_img_0.jpg" 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 461, Column 309: required attribute "alt" not specified
    …oscout24.com/fr-FR/110130/1/20121122113547_img_0.jpg" 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 461, Column 313: end tag for "img" omitted, but OMITTAG NO was specified
    …oscout24.com/fr-FR/110130/1/20121122113547_img_0.jpg" 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 461, Column 214: start tag was here
    …rom=1000&#038;cy=F&#038;ustate=N%2CU'><img src="http://cmspic.autoscout24.com/…
  • Error Line 464, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
    		<input type="button" value="Annonce auto gratuite">

    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 464, Column 3: start tag was here
    		<input type="button" value="Annonce auto gratuite">
  • Error Line 490, Column 36: required attribute "type" not specified
    	<div class="marginTopFontM"><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 490, Column 36: document type does not allow element "style" here
    	<div class="marginTopFontM"><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 611, Column 112: cannot generate system identifier for general entity "intcidm"
    …24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag…

    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 611, Column 112: general entity "intcidm" not defined and no default entity
    …24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag…

    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 611, Column 119: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Warning Line 611, Column 119: reference to external entity in attribute value
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Error Line 611, Column 119: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Info Line 611, Column 111: entity was defined here
    …t24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 611, Column 142: cannot generate system identifier for general entity "magcid"
    …=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><i…

    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 611, Column 142: general entity "magcid" not defined and no default entity
    …=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><i…

    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 611, Column 148: reference not terminated by REFC delimiter
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><img src…

    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 611, Column 148: reference to external entity in attribute value
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><img src…

    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 611, Column 148: reference to entity "magcid" for which no system identifier could be generated
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><img src…

    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 611, Column 141: entity was defined here
    …e=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Error Line 611, Column 263: required attribute "alt" not specified
    …//cmspic.autoscout24.com/fr-FR/110118/11/20121211144458_img_0.jpg" /></a></div>

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

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

  • Warning Line 613, Column 94: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Warning Line 613, Column 94: reference to external entity in attribute value
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Error Line 613, Column 94: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Info Line 611, Column 111: entity was defined here
    …t24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 613, Column 123: reference not terminated by REFC delimiter
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">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 613, Column 123: reference to external entity in attribute value
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">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 613, Column 123: reference to entity "magcid" for which no system identifier could be generated
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">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 611, Column 141: entity was defined here
    …e=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 614, Column 172: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Warning Line 614, Column 172: reference to external entity in attribute value
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Error Line 614, Column 172: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-a…

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

  • Info Line 611, Column 111: entity was defined here
    …t24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 614, Column 201: reference not terminated by REFC delimiter
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Plus d'i…

    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 614, Column 201: reference to external entity in attribute value
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Plus d'i…

    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 614, Column 201: reference to entity "magcid" for which no system identifier could be generated
    …6&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent">Plus d'i…

    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 611, Column 141: entity was defined here
    …e=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 618, Column 119: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Warning Line 618, Column 119: reference to external entity in attribute value
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Error Line 618, Column 119: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Info Line 611, Column 111: entity was defined here
    …t24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 618, Column 148: reference not terminated by REFC delimiter
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent"><img src…

    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 618, Column 148: reference to external entity in attribute value
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent"><img src…

    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 618, Column 148: reference to entity "magcid" for which no system identifier could be generated
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent"><img src…

    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 611, Column 141: entity was defined here
    …e=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Error Line 618, Column 263: required attribute "alt" not specified
    …//cmspic.autoscout24.com/fr-FR/110118/11/20121211144458_img_1.jpg" /></a></div>

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

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

  • Warning Line 620, Column 94: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Warning Line 620, Column 94: reference to external entity in attribute value
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Error Line 620, Column 94: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Info Line 611, Column 111: entity was defined here
    …t24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 620, Column 123: reference not terminated by REFC delimiter
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Skoda Oc…

    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 620, Column 123: reference to external entity in attribute value
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Skoda Oc…

    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 620, Column 123: reference to entity "magcid" for which no system identifier could be generated
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Skoda Oc…

    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 611, Column 141: entity was defined here
    …e=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 621, Column 161: reference not terminated by REFC delimiter
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Warning Line 621, Column 161: reference to external entity in attribute value
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Error Line 621, Column 161: reference to entity "intcidm" for which no system identifier could be generated
    …nfo/magazine?toparticle=334861&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-a…

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

  • Info Line 611, Column 111: entity was defined here
    …t24.fr/info/magazine?toparticle=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=ma…
  • Warning Line 621, Column 190: reference not terminated by REFC delimiter
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Plus d'i…

    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 621, Column 190: reference to external entity in attribute value
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Plus d'i…

    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 621, Column 190: reference to entity "magcid" for which no system identifier could be generated
    …1&intcidm=HP-OCBox2-Mag-Teaser2&magcid=mag-home-art" target="_parent">Plus d'i…

    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 611, Column 141: entity was defined here
    …e=326426&intcidm=HP-OCBox2-Mag-Teaser1&magcid=mag-home-art" target="_parent"><…
  • Warning Line 640, Column 154: cannot generate system identifier for general entity "language"
    …t24.com/adserver/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 154: general entity "language" not defined and no default entity
    …t24.com/adserver/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></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 640, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></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 640, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></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 640, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1…
  • Warning Line 640, Column 167: cannot generate system identifier for general entity "siteid"
    …ver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></d…

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

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

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

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

  • Error Line 640, Column 167: general entity "siteid" not defined and no default entity
    …ver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></d…

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

  • Warning Line 640, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 166: entity was defined here
    …rver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></…
  • Warning Line 640, Column 177: cannot generate system identifier for general entity "elementid"
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 177: general entity "elementid" not defined and no default entity
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=298&language=fre&siteid=20&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 640, Column 176: entity was defined here
    …r/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></div>
  • Warning Line 641, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=299&language=fre&siteid=20&elementid=slot-2"></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 641, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=299&language=fre&siteid=20&elementid=slot-2"></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 641, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=299&language=fre&siteid=20&elementid=slot-2"></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 640, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1…
  • Warning Line 641, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=299&language=fre&siteid=20&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 641, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=299&language=fre&siteid=20&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 641, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=299&language=fre&siteid=20&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 640, Column 166: entity was defined here
    …rver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></…
  • Warning Line 641, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=299&language=fre&siteid=20&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 641, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=299&language=fre&siteid=20&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 641, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=299&language=fre&siteid=20&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 640, Column 176: entity was defined here
    …r/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></div>
  • Warning Line 642, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=300&language=fre&siteid=20&elementid=slot-3"></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 642, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=300&language=fre&siteid=20&elementid=slot-3"></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 642, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=300&language=fre&siteid=20&elementid=slot-3"></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 640, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1…
  • Warning Line 642, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=300&language=fre&siteid=20&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 642, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=300&language=fre&siteid=20&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 642, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=300&language=fre&siteid=20&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 640, Column 166: entity was defined here
    …rver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></…
  • Warning Line 642, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=300&language=fre&siteid=20&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 642, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=300&language=fre&siteid=20&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 642, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=300&language=fre&siteid=20&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 640, Column 176: entity was defined here
    …r/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></div>
  • Warning Line 643, Column 162: reference not terminated by REFC delimiter
    …adserver/index4.aspx?slot=301&language=fre&siteid=20&elementid=slot-4"></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 643, Column 162: reference to external entity in attribute value
    …adserver/index4.aspx?slot=301&language=fre&siteid=20&elementid=slot-4"></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 643, Column 162: reference to entity "language" for which no system identifier could be generated
    …adserver/index4.aspx?slot=301&language=fre&siteid=20&elementid=slot-4"></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 640, Column 153: entity was defined here
    …ut24.com/adserver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1…
  • Warning Line 643, Column 173: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=301&language=fre&siteid=20&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 643, Column 173: reference to external entity in attribute value
    …r/index4.aspx?slot=301&language=fre&siteid=20&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 643, Column 173: reference to entity "siteid" for which no system identifier could be generated
    …r/index4.aspx?slot=301&language=fre&siteid=20&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 640, Column 166: entity was defined here
    …rver/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></…
  • Warning Line 643, Column 186: reference not terminated by REFC delimiter
    …r/index4.aspx?slot=301&language=fre&siteid=20&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 643, Column 186: reference to external entity in attribute value
    …r/index4.aspx?slot=301&language=fre&siteid=20&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 643, Column 186: reference to entity "elementid" for which no system identifier could be generated
    …r/index4.aspx?slot=301&language=fre&siteid=20&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 640, Column 176: entity was defined here
    …r/index4.aspx?slot=298&language=fre&siteid=20&elementid=slot-1"></script></div>
  • Error Line 662, Column 83: end tag for "a" omitted, but OMITTAG NO was specified
    …href="http://www.autoscout24.fr/modeles/bmw/" title="BMW occasion">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 662, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/bmw/" title="BMW occasion">BMW<…
  • Error Line 662, Column 87: end tag for element "a" which is not open
    …href="http://www.autoscout24.fr/modeles/bmw/" title="BMW occasion">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 663, Column 86: end tag for "a" omitted, but OMITTAG NO was specified
    …f="http://www.autoscout24.fr/modeles/audi/" title="Audi occasion">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 663, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/audi/" title="Audi occasion">Au…
  • Error Line 663, Column 90: end tag for element "a" which is not open
    …f="http://www.autoscout24.fr/modeles/audi/" title="Audi occasion">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 664, Column 103: end tag for "a" omitted, but OMITTAG NO was specified
    …oscout24.fr/modeles/mercedes-benz/" title="Mercedes occasion">Mercedes</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 664, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/mercedes-benz/" title="Mercedes…
  • Error Line 664, Column 107: end tag for element "a" which is not open
    …oscout24.fr/modeles/mercedes-benz/" title="Mercedes occasion">Mercedes</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 665, Column 96: end tag for "a" omitted, but OMITTAG NO was specified
    …www.autoscout24.fr/modeles/vw/" title="Volkswagen occasion">Volkswagen</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 665, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/vw/" title="Volkswagen occasion…
  • Error Line 665, Column 100: end tag for element "a" which is not open
    …www.autoscout24.fr/modeles/vw/" title="Volkswagen occasion">Volkswagen</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 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.fr/modeles/renault/" title="Renault occasion">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.fr/modeles/renault/" title="Renault occasi…
  • Error Line 666, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.fr/modeles/renault/" title="Renault occasion">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 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.fr/modeles/peugeot/" title="Peugeot occasion">Peugeot</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.fr/modeles/peugeot/" title="Peugeot occasi…
  • Error Line 667, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.fr/modeles/peugeot/" title="Peugeot occasion">Peugeot</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 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.fr/modeles/citroen/" title="Citroen occasion">Citroen</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.fr/modeles/citroen/" title="Citroen occasi…
  • Error Line 668, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.fr/modeles/citroen/" title="Citroen occasion">Citroen</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 95: end tag for "a" omitted, but OMITTAG NO was specified
    …/www.autoscout24.fr/modeles/porsche/" title="Porsche occasion">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 669, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/porsche/" title="Porsche occasi…
  • Error Line 669, Column 99: end tag for element "a" which is not open
    …/www.autoscout24.fr/modeles/porsche/" title="Porsche occasion">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 680, Column 86: end tag for "a" omitted, but OMITTAG NO was specified
    …f="http://www.autoscout24.fr/modeles/ford/" title="Ford occasion">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 680, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/ford/" title="Ford occasion">Fo…
  • Error Line 680, Column 90: end tag for element "a" which is not open
    …f="http://www.autoscout24.fr/modeles/ford/" title="Ford occasion">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 681, Column 86: end tag for "a" omitted, but OMITTAG NO was specified
    …f="http://www.autoscout24.fr/modeles/opel/" title="Opel occasion">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 681, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/opel/" title="Opel occasion">Op…
  • Error Line 681, Column 90: end tag for element "a" which is not open
    …f="http://www.autoscout24.fr/modeles/opel/" title="Opel occasion">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 682, Column 92: end tag for "a" omitted, but OMITTAG NO was specified
    …p://www.autoscout24.fr/modeles/toyota/" title="Toyota occasion">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 682, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/toyota/" title="Toyota occasion…
  • Error Line 682, Column 96: end tag for element "a" which is not open
    …p://www.autoscout24.fr/modeles/toyota/" title="Toyota occasion">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 683, Column 104: end tag for "a" omitted, but OMITTAG NO was specified
    …scout24.fr/modeles/alfa-romeo/" title="Alfa Romeo occasion">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 683, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/alfa-romeo/" title="Alfa Romeo …
  • Error Line 683, Column 108: end tag for element "a" which is not open
    …scout24.fr/modeles/alfa-romeo/" title="Alfa Romeo occasion">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 684, Column 98: end tag for "a" omitted, but OMITTAG NO was specified
    …w.autoscout24.fr/modeles/vw/vw-golf/" title="VW Golf occasion">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 684, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/vw/vw-golf/" title="VW Golf occ…
  • Error Line 684, Column 102: end tag for element "a" which is not open
    …w.autoscout24.fr/modeles/vw/vw-golf/" title="VW Golf occasion">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 685, Column 100: end tag for "a" omitted, but OMITTAG NO was specified
    …autoscout24.fr/modeles/audi/audi-a4/" title="Audi A4 occasion">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 685, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/audi/audi-a4/" title="Audi A4 o…
  • Error Line 685, Column 104: end tag for element "a" which is not open
    …autoscout24.fr/modeles/audi/audi-a4/" title="Audi A4 occasion">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 686, Column 100: end tag for "a" omitted, but OMITTAG NO was specified
    …autoscout24.fr/modeles/audi/audi-a3/" title="Audi A3 occasion">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 686, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/audi/audi-a3/" title="Audi A3 o…
  • Error Line 686, Column 104: end tag for element "a" which is not open
    …autoscout24.fr/modeles/audi/audi-a3/" title="Audi A3 occasion">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 687, Column 118: end tag for "a" omitted, but OMITTAG NO was specified
    …eles/renault/renault-clio/" title="Renault Clio occasion">Renault Clio</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.fr/modeles/renault/renault-clio/" title="R…
  • Error Line 687, Column 122: end tag for element "a" which is not open
    …eles/renault/renault-clio/" title="Renault Clio occasion">Renault Clio</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 698, Column 105: end tag for "a" omitted, but OMITTAG NO was specified
    …cout24.fr/modeles/bmw/bmw-3/bmw-320/" title="BMW 320 occasion">BMW 320</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 698, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/bmw/bmw-3/bmw-320/" title="BMW …
  • Error Line 698, Column 109: end tag for element "a" which is not open
    …cout24.fr/modeles/bmw/bmw-3/bmw-320/" title="BMW 320 occasion">BMW 320</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 699, Column 124: end tag for "a" omitted, but OMITTAG NO was specified
    …enault/renault-megane/" title="Renault Megane occasion">Renault Megane</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 699, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/renault/renault-megane/" title=…
  • Error Line 699, Column 128: end tag for element "a" which is not open
    …enault/renault-megane/" title="Renault Megane occasion">Renault Megane</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 700, Column 104: end tag for "a" omitted, but OMITTAG NO was specified
    …scout24.fr/modeles/vw/vw-passat/" title="VW Passat occasion">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 700, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/vw/vw-passat/" title="VW Passat…
  • Error Line 700, Column 108: end tag for element "a" which is not open
    …scout24.fr/modeles/vw/vw-passat/" title="VW Passat occasion">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 701, Column 115: end tag for "a" omitted, but OMITTAG NO was specified
    …modeles/peugeot/peugeot-206/" title="Peugeot 206 occasion">Peugeot 206</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 701, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/peugeot/peugeot-206/" title="Pe…
  • Error Line 701, Column 119: end tag for element "a" which is not open
    …modeles/peugeot/peugeot-206/" title="Peugeot 206 occasion">Peugeot 206</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 115: end tag for "a" omitted, but OMITTAG NO was specified
    …modeles/peugeot/peugeot-307/" title="Peugeot 307 occasion">Peugeot 307</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.fr/modeles/peugeot/peugeot-307/" title="Pe…
  • Error Line 702, Column 119: end tag for element "a" which is not open
    …modeles/peugeot/peugeot-307/" title="Peugeot 307 occasion">Peugeot 307</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 100: end tag for "a" omitted, but OMITTAG NO was specified
    …autoscout24.fr/modeles/audi/audi-a6/" title="Audi A6 occasion">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 703, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/audi/audi-a6/" title="Audi A6 o…
  • Error Line 703, Column 104: end tag for element "a" which is not open
    …autoscout24.fr/modeles/audi/audi-a6/" title="Audi A6 occasion">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 704, Column 84: end tag for "a" omitted, but OMITTAG NO was specified
    …ref="http://www.autoscout24.fr/modeles/bmw/bmw-serie-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 704, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/bmw/bmw-serie-x/bmw-x5/">BMW X5…
  • Error Line 704, Column 88: end tag for element "a" which is not open
    …ref="http://www.autoscout24.fr/modeles/bmw/bmw-serie-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 705, Column 144: end tag for "a" omitted, but OMITTAG NO was specified
    …s-benz-classe-c/" title="Mercedes Classe C occasion">Mercedes Classe C</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.fr/modeles/mercedes-benz/mercedes-benz-cla…
  • Error Line 705, Column 148: end tag for element "a" which is not open
    …s-benz-classe-c/" title="Mercedes Classe C occasion">Mercedes Classe C</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 716, Column 105: end tag for "a" omitted, but OMITTAG NO was specified
    …cout24.fr/modeles/utilitaire/" title="Camionnette occasion">Utilitaire</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 716, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/utilitaire/" title="Camionnette…
  • Error Line 716, Column 109: end tag for element "a" which is not open
    …cout24.fr/modeles/utilitaire/" title="Camionnette occasion">Utilitaire</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 717, Column 83: end tag for "a" omitted, but OMITTAG NO was specified
    …href="http://www.autoscout24.fr/modeles/4x4/" title="4x4 occasion">4x4</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 717, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/4x4/" title="4x4 occasion">4x4<…
  • Error Line 717, Column 87: end tag for element "a" which is not open
    …href="http://www.autoscout24.fr/modeles/4x4/" title="4x4 occasion">4x4</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 718, Column 101: end tag for "a" omitted, but OMITTAG NO was specified
    …utoscout24.fr/modeles/monospace/" title="Monospace occasion">Monospace</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 718, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/monospace/" title="Monospace oc…
  • Error Line 718, Column 105: end tag for element "a" which is not open
    …utoscout24.fr/modeles/monospace/" title="Monospace occasion">Monospace</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 719, Column 89: end tag for "a" omitted, but OMITTAG NO was specified
    …http://www.autoscout24.fr/modeles/break/" title="Break occasion">Break</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 719, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/break/" title="Break occasion">…
  • Error Line 719, Column 93: end tag for element "a" which is not open
    …http://www.autoscout24.fr/modeles/break/" title="Break occasion">Break</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 720, Column 96: end tag for "a" omitted, but OMITTAG NO was specified
    …www.autoscout24.fr/modeles/coupe/" title="Coupé occasion">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 720, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/coupe/" title="Coupé occasion">…
  • Error Line 720, Column 100: end tag for element "a" which is not open
    …www.autoscout24.fr/modeles/coupe/" title="Coupé occasion">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 721, Column 113: end tag for "a" omitted, but OMITTAG NO was specified
    …r/modeles/voiture-ancienne/" title="Voiture Ancienne">Voiture Ancienne</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 721, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/voiture-ancienne/" title="Voitu…
  • Error Line 721, Column 117: end tag for element "a" which is not open
    …r/modeles/voiture-ancienne/" title="Voiture Ancienne">Voiture Ancienne</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 722, Column 119: end tag for "a" omitted, but OMITTAG NO was specified
    …les/voiture-accidentee/" title="Voiture Accidentée">Voiture Accidentee</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 722, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/voiture-accidentee/" title="Voi…
  • Error Line 722, Column 123: end tag for element "a" which is not open
    …les/voiture-accidentee/" title="Voiture Accidentée">Voiture Accidentee</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 723, Column 101: end tag for "a" omitted, but OMITTAG NO was specified
    …utoscout24.fr/modeles/cabriolet/" title="Cabriolet occasion">Cabriolet</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 723, Column 6: start tag was here
    	<li><a href="http://www.autoscout24.fr/modeles/cabriolet/" title="Cabriolet oc…
  • Error Line 723, Column 105: end tag for element "a" which is not open
    …utoscout24.fr/modeles/cabriolet/" title="Cabriolet occasion">Cabriolet</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 758, Column 19: 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 786, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt language="javascript" type="text/javascript" src="ht…

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

  • Error Line 786, Column 21: element "scr" undefined
    document.write('<scr'+'ipt language="javascript" type="text/javascript" src="ht…

    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 786, Column 267: character "<" is the first character of a delimiter but occurred as data
    …al+'tile='+agm_tilecat+';sz='+agm_sz+';ord='+agm_timestamp+'?"><\/scr'+'ipt>');

    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 787, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

    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 786, Column 17: start tag was here
    document.write('<scr'+'ipt language="javascript" type="text/javascript" src="ht…
  • Warning Line 820, Column 62: cannot generate system identifier for general entity "link"
    …autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr…

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

    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 820, Column 66: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr%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 820, Column 66: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr%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 820, 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%2Efr%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 820, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ef…
  • Warning Line 820, Column 143: cannot generate system identifier for general entity "name"
    …magazine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="…

    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 820, Column 143: general entity "name" not defined and no default entity
    …magazine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="…

    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 820, Column 147: reference not terminated by REFC delimiter
    …zine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 820, Column 147: reference to external entity in attribute value
    …zine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 820, Column 147: reference to entity "name" for which no system identifier could be generated
    …zine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 820, Column 142: entity was defined here
    …Fmagazine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick=…
  • Warning Line 820, Column 165: cannot generate system identifier for general entity "site"
    …%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 820, Column 165: general entity "site" not defined and no default entity
    …%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 820, Column 169: reference not terminated by REFC delimiter
    …w%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout24fr'…

    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 820, Column 169: reference to external entity in attribute value
    …w%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout24fr'…

    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 820, Column 169: reference to entity "site" for which no system identifier could be generated
    …w%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout24fr'…

    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 820, Column 164: entity was defined here
    …s%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 820, Column 421: required attribute "alt" not specified
    …rc="http://cmspic.autoscout24.com/fr-FR/110114/1/20130124160332_img_0.jpg"></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 820, Column 425: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="http://cmspic.autoscout24.com/fr-FR/110114/1/20130124160332_img_0.jpg"></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 820, Column 341: start tag was here
    …s.tl(this,'o', 'Mag-HP-sw-ferrari');"><img src="http://cmspic.autoscout24.com/…
  • Warning Line 827, Column 69: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr%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 827, Column 69: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr%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 827, 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%2Efr%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 820, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ef…
  • Warning Line 827, Column 150: reference not terminated by REFC delimiter
    …zine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 827, Column 150: reference to external entity in attribute value
    …zine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 827, Column 150: reference to entity "name" for which no system identifier could be generated
    …zine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&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 820, Column 142: entity was defined here
    …Fmagazine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick=…
  • Warning Line 827, Column 172: reference not terminated by REFC delimiter
    …w%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout24fr'…

    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 827, Column 172: reference to external entity in attribute value
    …w%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout24fr'…

    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 827, Column 172: reference to entity "site" for which no system identifier could be generated
    …w%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout24fr'…

    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 820, Column 164: entity was defined here
    …s%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout…
  • Error Line 827, Column 371: end tag for element "nobr" which is not open
    …-sw-ferrari';s.tl(this,'o', 'Mag-HP-sw-ferrari');">Plus d&#180;infos</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 834, Column 73: reference not terminated by REFC delimiter
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr%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 834, Column 73: reference to external entity in attribute value
    …scout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Efr%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 834, 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%2Efr%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 820, Column 61: entity was defined here
    ….autoscout24.de/redir.asp?language=ger&link=http%3A%2F%2Fww2%2Eautoscout24%2Ef…
  • Warning Line 834, Column 164: reference not terminated by REFC delimiter
    …5Fothers%2Feuropassistance%2Easpx&name=hp_tb_sw-garantie-panne-mecanique&site=…

    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 834, Column 164: reference to external entity in attribute value
    …5Fothers%2Feuropassistance%2Easpx&name=hp_tb_sw-garantie-panne-mecanique&site=…

    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 834, Column 164: reference to entity "name" for which no system identifier could be generated
    …5Fothers%2Feuropassistance%2Easpx&name=hp_tb_sw-garantie-panne-mecanique&site=…

    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 820, Column 142: entity was defined here
    …Fmagazine%2Fmz%5Fothers%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick=…
  • Warning Line 834, Column 203: reference not terminated by REFC delimiter
    …hp_tb_sw-garantie-panne-mecanique&site=1" id="sw-garantie-panne-mecanique">Gar…

    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 834, Column 203: reference to external entity in attribute value
    …hp_tb_sw-garantie-panne-mecanique&site=1" id="sw-garantie-panne-mecanique">Gar…

    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 834, Column 203: reference to entity "site" for which no system identifier could be generated
    …hp_tb_sw-garantie-panne-mecanique&site=1" id="sw-garantie-panne-mecanique">Gar…

    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 820, Column 164: entity was defined here
    …s%2Fsw%5Fferrari&name=hp_tb_sw-ferrari&site=1"  onclick="var s=s_gi('autoscout…
  • Warning Line 946, 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 946, 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 946, 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 946, 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 946, 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 946, 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 946, Column 190: entity was defined here
    …ndow.open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponen…
  • Warning Line 946, 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 946, 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 946, 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 946, 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 946, 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 946, Column 195: entity was defined here
    …open('http://del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(loc…
  • Warning Line 946, 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 946, 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 946, 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 946, 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 946, 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 946, Column 206: entity was defined here
    …//del.icio.us/post?v=4&noui&jump=close&url='+encodeURIComponent(location.href+…
  • Warning Line 946, 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 946, 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 946, 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 946, 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 946, 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 946, Column 281: entity was defined here
    …ef+sb_prefix+'extcidm=sb-delicious')+'&title='+encodeURIComponent(document.tit…
  • Warning Line 946, Column 694: 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 946, Column 848: 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 946, Column 848: 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 946, Column 849: 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 946, Column 849: 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 946, Column 849: 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 946, Column 847: entity was defined here
    …prefix+'extcidm=sb-bookmarks-yahoo')+'&t='+encodeURIComponent(document.title),…
  • Warning Line 946, Column 1276: character "&" is the first character of a delimiter but occurred as data
    …(location.href.search(/\?/) != -1) ? '&' : '?';window.open('http://www.mister-…

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

  • Error Line 1002, Column 97: there is no attribute "RenderEvar24"
    …_bottomArea_bottomContentArea_omniturePixel" class="pixel" RenderEvar24="true">

    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 1027, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt language="javascript" type="text/javascript" src="ht…

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

  • Error Line 1027, Column 21: element "scr" undefined
    document.write('<scr'+'ipt language="javascript" type="text/javascript" src="ht…

    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 1027, Column 267: character "<" is the first character of a delimiter but occurred as data
    …al+'tile='+agm_tilecat+';sz='+agm_sz+';ord='+agm_timestamp+'?"><\/scr'+'ipt>');

    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 1028, Column 9: end tag for "scr" omitted, but OMITTAG NO was specified
    </script>

    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 1027, Column 17: start tag was here
    document.write('<scr'+'ipt language="javascript" type="text/javascript" src="ht…
  • Error Line 1040, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript">

    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 1040, Column 30: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JavaScript">

    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
  • 5.833 visits