voici.fr

Tout sur les stars : les news people, les potins, vidéos et photos de stars et de célébrités ! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-06-2013 05:10:55  (update).

Overview Info

  • Domain Name
    voici.fr
  • Favicon
  • Alexa Rank
    #7091
  • Google Page Rank
    PR 5
  • Ip Address
    89.31.146.15
  • Page Size
    82.8 KB
  • Images
    0 GIF, 47 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 7 33 0 0 0

Website Meta Analysis



  • Title
    People : toutes les actualités et news people ! - Voici
  • Meta Keyword
  • Meta Description
    Tout sur les stars : les news people, les potins, vidéos et photos de stars et de célébrités !

Technical Analysis



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

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

HTML Analysis

  • expires: Mon, 17 Jun 2013 17:14:39 GMT
  • last-modified: Mon, 17 Jun 2013 17:09:39 GMT
  • cache-control: public, must-revalidate, stale-while-revalidate=10, stale-if-error=20
  • pragma:
  • served-by: www.voici.fr
  • content-language: fr-FR
  • x-d-time: 44-58-897862-00019-489
  • x-generation-time: 0.25161910057068 @ 2013-06-17T19:09:39+02:00
  • content-encoding: gzip
  • content-type: text/html; charset=utf-8
  • content-length: 17557
  • accept-ranges: bytes
  • x-varnish-cache: HIT
  • x-varnish-cache-hits: 13
  • x-varnish-server: prpcachef2
  • date: Mon, 17 Jun 2013 17:10:51 GMT
  • connection: keep-alive
  • vary: Accept-Encoding
  • 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.
%%
%% [94.46.242.2 REQUEST] >> voici.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%

domain: voici.fr
status: ACTIVE
hold: NO
holder-c: PP971-FRNIC
admin-c: MM15740-FRNIC
tech-c: VS8-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL10380-FRNIC
registrar: VEEPEE SA
anniversary: 13/02
created: 13/02/2002
last-update: 12/03/2009
source: FRNIC

ns-list: NSL10380-FRNIC
nserver: phobos.vp-dns.net
nserver: deimos.vp-dns.net
source: FRNIC

registrar: VEEPEE SA
type: Isp Option 2
address: 31 Rue Louis Pasteur
address: BOULOGNE
country: FR
phone: +33 1 73 03 85 08
fax-no: +33 1 46 05 06 54
e-mail: email
website: http://www.veepee.com
anonymous: NO
registered: 22/09/2000
source: FRNIC

nic-hdl: MM15740-FRNIC
type: PERSON
contact: Martine Mirepoix
address: PRISMA PRESSE
address: 6, rue Daru
address: 75008 Paris
country: FR
phone: +33 1 44 15 30 12
fax-no: +33 1 44 15 30 09
e-mail: email
notify: email
changed: 25/06/2004 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: VS8-FRNIC
type: ROLE
contact: Veepee SA
address: VEEPEE
address: 31, rue Louis Pasteur
address: 92100 Boulogne-Billancourt
country: FR
phone: +33 1 73 03 85 05
e-mail: email
admin-c: ER12-FRNIC
tech-c: JB1299-FRNIC
changed: 08/03/2007 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: PP971-FRNIC
type: ORGANIZATION
contact: PRISMA MEDIA
address: 13, rue Henri Barbusse
address: 92230 Gennevilliers
country: FR
phone: +33 1 44 15 30 12
e-mail: email
changed: 06/03/2012 email
anonymous: NO
obsoleted: NO
eligstatus: ok
eligsource: REGISTRY
eligdate: 06/03/2012 09:13:23
source: FRNIC

DNS Analysis


DNS servers
phobos.vp-dns.net [217.195.17.18]
deimos.vp-dns.net [217.195.18.129]

DNS Records

Answer records
voici.fr SOA
server: phobos.vp-dns.net
email: bobjones@vp-dns.net
serial: 2012121800
refresh: 14400
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
voici.fr NS  venus.vp-dns.net 3600s
voici.fr NS  deimos.vp-dns.net 3600s
voici.fr NS  phobos.vp-dns.net 3600s
voici.fr A 89.31.146.15 3600s
voici.fr MX
preference: 20
exchange: alt2.aspmx.l.google.com
3600s
voici.fr MX
preference: 20
exchange: aspmx.l.google.com
3600s
voici.fr MX
preference: 20
exchange: aspmx2.googlemail.com
3600s
voici.fr MX
preference: 20
exchange: aspmx3.googlemail.com
3600s
voici.fr MX
preference: 20
exchange: alt1.aspmx.l.google.com
3600s
voici.fr TXT v=spf1 +all 3600s
voici.fr TXT google-site-verification=bxg3oYz0FZrOJy0lDcI2CQg5TxBOcOV48bB3B9yRQzQ 3600s

Authority records

Additional records
venus.vp-dns.net A 94.23.243.144 86400s
deimos.vp-dns.net A 217.195.18.129 86400s
deimos.vp-dns.net 28 [16 bytes] 86400s
phobos.vp-dns.net A 217.195.17.18 86400s
phobos.vp-dns.net 28 [16 bytes] 86400s

IP 89.31.146.15 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 89.31.146.15

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 68 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.6935643681143693
Message Error
  • Error Line 2, Column 77: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr" lang="fr">    <html>

    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 2, Column 72: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr" lang="fr">    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 7, Column 16: there is no attribute "property"
    <meta property="og:title" content="People : toutes les actualités et news peopl…

    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 22, Column 38: required attribute "type" not specified
            <script language="javascript">

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

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

  • Error Line 36, Column 109: character ";" not allowed in attribute specification list
    …split(";");for(i=0;i<ARRCookies.length;i++){x=ARRCookies[i].substr(0,ARRCookie…
  • Error Line 36, Column 109: element "ARRCookies.length" undefined
    …split(";");for(i=0;i<ARRCookies.length;i++){x=ARRCookies[i].substr(0,ARRCookie…

    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 38, Column 108: cannot generate system identifier for general entity "cookieName"
    …?netId='+escape(crtg_nid);crtg_url+='&cookieName='+escape(crtg_cookiename);crt…

    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 38, Column 108: general entity "cookieName" not defined and no default entity
    …?netId='+escape(crtg_nid);crtg_url+='&cookieName='+escape(crtg_cookiename);crt…

    This is usually a cascading error caused by 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 38, Column 118: reference not terminated by REFC delimiter
    …scape(crtg_nid);crtg_url+='&cookieName='+escape(crtg_cookiename);crtg_url+='&r…

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

  • Error Line 38, Column 118: reference to entity "cookieName" for which no system identifier could be generated
    …scape(crtg_nid);crtg_url+='&cookieName='+escape(crtg_cookiename);crtg_url+='&r…

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

  • Info Line 38, Column 107: entity was defined here
    …s?netId='+escape(crtg_nid);crtg_url+='&cookieName='+escape(crtg_cookiename);cr…
  • Warning Line 38, Column 157: cannot generate system identifier for general entity "rnd"
    …'+escape(crtg_cookiename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + e…

    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 38, Column 157: general entity "rnd" not defined and no default entity
    …'+escape(crtg_cookiename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + e…

    This is usually a cascading error caused by 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 38, Column 160: reference not terminated by REFC delimiter
    …scape(crtg_cookiename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + esca…

    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 38, Column 160: reference to entity "rnd" for which no system identifier could be generated
    …scape(crtg_cookiename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + esca…

    This is usually a cascading error caused by 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 38, Column 156: entity was defined here
    …='+escape(crtg_cookiename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + …
  • Warning Line 38, Column 184: cannot generate system identifier for general entity "varName"
    …ename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + escape(crtg_varname);

    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 38, Column 184: general entity "varName" not defined and no default entity
    …ename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + escape(crtg_varname);

    This is usually a cascading error caused by 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 38, Column 191: reference not terminated by REFC delimiter
    …ename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + escape(crtg_varname);

    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 38, Column 191: reference to entity "varName" for which no system identifier could be generated
    …ename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + escape(crtg_varname);

    This is usually a cascading error caused by 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 38, Column 183: entity was defined here
    …ename);crtg_url+='&rnd='+crtg_rnd;crtg_url+='&varName=' + escape(crtg_varname);
  • Error Line 41, Column 9: end tag for "ARRCookies.length" 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 36, Column 91: start tag was here
    …s=document.cookie.split(";");for(i=0;i<ARRCookies.length;i++){x=ARRCookies[i].…
  • Error Line 47, Column 29: an attribute specification must start with a name or name token
            document.write('<scr'+'ipt src="http://ad.prismamediadigital.com/call/p…

    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 47, Column 29: element "scr" undefined
            document.write('<scr'+'ipt src="http://ad.prismamediadigital.com/call/p…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 47, Column 195: delimiter "'" invalid: only S separators and TAGC allowed here
    …+ sas_master + '/' + sas_tmstp + '/' + escape(sas_target) + '?"></scr'+'ipt>');
  • Error Line 56, Column 38: document type does not allow element "div" here; assuming missing "object" start-tag
                        <div id="fb-root"></div>
  • Error Line 58, Column 86: end tag for "object" omitted, but OMITTAG NO was specified
    … type="text/javascript">FB.init("320459221314297");</script>            </head>

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

  • Info Line 56, Column 21: start tag was here
                        <div id="fb-root"></div>
  • Error Line 65, Column 138: document type does not allow element "link" here
    …ache/public/stylesheets/d5fb509f658cbee330ad1409f40d2602_1265708685_all.css" />

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

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

  • Warning Line 101, Column 62: cannot generate system identifier for general entity "redirect"
    …smashop.fr/affiliation/?code=VOIABO11&redirect=http%3A%2F%2Flogi162.xiti.com%2…

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

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

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

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

  • Error Line 101, Column 62: general entity "redirect" not defined and no default entity
    …smashop.fr/affiliation/?code=VOIABO11&redirect=http%3A%2F%2Flogi162.xiti.com%2…

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

  • Warning Line 101, Column 70: reference not terminated by REFC delimiter
    …fr/affiliation/?code=VOIABO11&redirect=http%3A%2F%2Flogi162.xiti.com%2Fgo.url%…

    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 101, Column 70: reference to external entity in attribute value
    …fr/affiliation/?code=VOIABO11&redirect=http%3A%2F%2Flogi162.xiti.com%2Fgo.url%…

    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 101, Column 70: reference to entity "redirect" for which no system identifier could be generated
    …fr/affiliation/?code=VOIABO11&redirect=http%3A%2F%2Flogi162.xiti.com%2Fgo.url%…

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

  • Info Line 101, Column 61: entity was defined here
    …ismashop.fr/affiliation/?code=VOIABO11&redirect=http%3A%2F%2Flogi162.xiti.com%…
  • Error Line 101, Column 288: there is no attribute "onClick"
    …ne%2Fabonnement-voici.html"   onClick="recordOutboundLink(this, 'Outbound Link…

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

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

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

  • Warning Line 114, Column 79: cannot generate system identifier for general entity "cid"
    …fr/content/landing-voici?channel=1397&cid=1397voicibonsplans" rel="nofollow" t…

    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 114, Column 79: general entity "cid" not defined and no default entity
    …fr/content/landing-voici?channel=1397&cid=1397voicibonsplans" rel="nofollow" t…

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

  • Warning Line 114, Column 82: reference not terminated by REFC delimiter
    …content/landing-voici?channel=1397&cid=1397voicibonsplans" rel="nofollow" targ…

    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 114, Column 82: reference to external entity in attribute value
    …content/landing-voici?channel=1397&cid=1397voicibonsplans" rel="nofollow" targ…

    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 114, Column 82: reference to entity "cid" for which no system identifier could be generated
    …content/landing-voici?channel=1397&cid=1397voicibonsplans" rel="nofollow" targ…

    This is usually a cascading error caused by 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 114, Column 78: entity was defined here
    ….fr/content/landing-voici?channel=1397&cid=1397voicibonsplans" rel="nofollow" …
  • Error Line 126, Column 30: required attribute "type" not specified
    <script language="JavaScript">

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

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

  • Error Line 134, Column 55: an attribute value must be a literal unless it contains only name characters
    …rget="_self"><img id="logo_voici" src=/extension/voi_v3/design/voi/images/logo…

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

  • Error Line 155, Column 38: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    				  			  					    							<li class=color-np>
  • Error Line 189, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-vp>
  • Error Line 199, Column 15: end tag for "ul" which is not finished
    					 				</ul>

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

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

  • Error Line 203, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-mb>
  • Error Line 233, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-tv>
  • Error Line 278, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-mu>
  • Error Line 288, Column 15: end tag for "ul" which is not finished
    					 				</ul>

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

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

  • Error Line 292, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-ci>
  • Error Line 302, Column 15: end tag for "ul" which is not finished
    					 				</ul>

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

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

  • Error Line 306, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-bp>
  • Error Line 324, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					  			  					    							<li class=color-jx>
  • Error Line 356, Column 15: end tag for "ul" which is not finished
    					 				</ul>

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

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

  • Warning Line 363, Column 52: cannot generate system identifier for general entity "fsid"
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</a>

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

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

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

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

  • Error Line 363, Column 52: general entity "fsid" not defined and no default entity
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</a>

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

  • Warning Line 363, Column 56: reference not terminated by REFC delimiter
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</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 363, Column 56: reference to external entity in attribute value
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</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 363, Column 56: reference to entity "fsid" for which no system identifier could be generated
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</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 363, Column 51: entity was defined here
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</a>
  • Error Line 368, Column 15: end tag for "ul" which is not finished
    					 				</ul>

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

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

  • Error Line 398, Column 138: document type does not allow element "link" here
    …ache/public/stylesheets/55e898090f7466f30d7df3e7f96dfe11_1351151322_all.css" />

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

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

  • Error Line 416, Column 89: there is no attribute "gname"
    …="gSearch"><gcse:searchbox-only gname="searchbox-only0" resultsUrl="/google_se…

    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 416, Column 118: there is no attribute "resultsUrl"
    …ly gname="searchbox-only0" resultsUrl="/google_search/search" queryParameterNa…

    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 416, Column 161: there is no attribute "queryParameterName"
    …gle_search/search" queryParameterName="q"></gcse:searchbox-only></div>	<div cl…

    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 416, Column 164: element "gcse:searchbox-only" undefined
    …_search/search" queryParameterName="q"></gcse:searchbox-only></div>	<div class…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 426, Column 11: ID "carrousel" already defined
    	<div id="carrousel" class="coda-slider-wrapper">

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

  • Info Line 424, Column 11: ID "carrousel" first defined here
    	<div id="carrousel">
  • Error Line 445, Column 55: end tag for element "a" which is not open
    																					<p class="title">Charlie Sheen</a></p>

    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 485, Column 54: end tag for element "a" which is not open
    																					<p class="title">Taylor Swift</a></p>

    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 519, Column 58: end tag for element "a" which is not open
    																					<p class="title">Gérard Depardieu</a></p>

    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 559, Column 49: end tag for element "a" which is not open
    																					<p class="title">Beyoncé</a></p>

    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 599, Column 56: end tag for element "a" which is not open
    																					<p class="title">Britney Spears</a></p>

    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 633, Column 14: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        						<h3>Paparazzi décédé : Charlie Sheen fait un don...</h3>

    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 643, Column 14: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        						<h3>Harry Styles a plaqué Taylor Swift car elle...</h3>

    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 653, Column 14: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        						<h3>VIDEO Gérard Depardieu surpris à Paris par une...</h3>

    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 663, Column 14: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        						<h3>PHOTO Beyoncé : les premiers pas de Blue Ivy...</h3>

    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 673, Column 14: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        						<h3>Britney Spears et son fiancé Jason Trawick se...</h3>

    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 1327, Column 24: there is no attribute "profile_id"
        <fb:fan profile_id="162135926640" stream="0" connections="10" logobar="1" w…

    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 1327, Column 46: there is no attribute "stream"
    …:fan profile_id="162135926640" stream="0" connections="10" logobar="1" width="…

    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 1327, Column 62: there is no attribute "connections"
    …id="162135926640" stream="0" connections="10" logobar="1" width="298"></fb:fan>

    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 1327, Column 75: there is no attribute "logobar"
    …id="162135926640" stream="0" connections="10" logobar="1" width="298"></fb:fan>

    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 1327, Column 85: there is no attribute "width"
    …id="162135926640" stream="0" connections="10" logobar="1" width="298"></fb:fan>

    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 1327, Column 90: element "fb:fan" undefined
    …id="162135926640" stream="0" connections="10" logobar="1" width="298"></fb:fan>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1335, Column 19: there is no attribute "LANGUAGE"
    	<SCRIPT LANGUAGE="JavaScript1.1" SRC="http://www.meetic-partners.com/call/adj/…

    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 1335, Column 39: there is no attribute "SRC"
    	<SCRIPT LANGUAGE="JavaScript1.1" SRC="http://www.meetic-partners.com/call/adj/…

    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 1335, Column 149: element "SCRIPT" undefined
    …183596/1322867/Prisma_FR.meeticcorp/300x150/[timestamp]/no?[countgo]"></SCRIPT>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1336, Column 11: element "NOSCRIPT" undefined
    	<NOSCRIPT>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1338, Column 129: required attribute "alt" not specified
    …ll/adi/183596/1322867/Prisma_FR.meeticcorp/300x150/[timestamp]/no?" border="0">

    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 1338, Column 130: end tag for "img" omitted, but OMITTAG NO was specified
    …ll/adi/183596/1322867/Prisma_FR.meeticcorp/300x150/[timestamp]/no?" border="0">

    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 1338, Column 8: start tag was here
    	      <img src="http://www.meetic-partners.com/call/adi/183596/1322867/Prisma_…
  • Error Line 1351, Column 171: there is no attribute "allowtransparency"
    …overflow:hidden; width:300px; height:250px;" allowtransparency="true"></iframe>

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

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

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

  • Warning Line 1460, Column 63: reference not terminated by REFC delimiter
    …"http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</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 1460, Column 63: reference to external entity in attribute value
    …"http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</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 1460, Column 63: reference to entity "fsid" for which no system identifier could be generated
    …"http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</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 363, Column 51: entity was defined here
    …a href="http://k.ilius.net/?mtcmk=681864&fsid=070" target="_self">Rencontre</a>
  • Error Line 1615, Column 8: "html" not finished but document ended
    </html>
  • Error Line 1615, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

    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 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr" lang="fr">    <html>

Visitor Analysis

Daily Visitor
  • 16.450 visits
Daily Visitor