La Trika Spip Team s’engage sur la qualité

Comme le savent tous ceux qui ont teste de nombreux CMS, Spip est tres fort pour faire du Valid XHTML.

De meme le squelette TMA ( TheMorning After porte sous spip ) s engage sur la validation XHTML.

Notre trikapalanet sauvage est pur bio, sans OGM ni conservateurs artificiels, c est pour cela qu il tourne sous spip svn et TMA svn, et ce concours est aussi l occasion de participer et ameliorer cet excellent squelette SPIP, qui dispose deja d une excellente validation XHTML.

Nous avons donc rajoute dans la sidebar des extraits du web un petit :

Ce qui donne dans la barre de droite :

trikapalanet gnomecorp

Commencons par le moins mauvais de nos concurrents . . . . GnomeCorp dont le site Trikapalanet affiche actuellement 8 erreurs : http://quaoar.ww7.be/gnomecorp_trik...

# Error Line 8, Column 57: end tag for "meta" omitted, but OMITTAG NO was specified … content="index, follow, noarchiv… You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". # Info Line 8, Column 1: start tag was here <meta name="robots" content="index, follow, noarchive"> # Error Line 127, Column 91: end tag for "ul" omitted, but OMITTAG NO was specified …our vos photos de vacances</li></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 124: start tag was here ><ul> # Error Line 44, Column 27: XML Parsing Error: Opening and ending tag mismatch: meta line 8 and head <!-- insert_head --></head> # Error Line 127, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 124 and div … EX FC100 pour vos photos de vacances</li></div>… # Error Line 245, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 48 and body </body> # Error Line 246, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 46 and html </html> # Error Line 246, Column 7: XML Parsing Error: Premature end of data in tag head line 5 </html> # Error Line 246, Column 7: XML Parsing Error: Premature end of data in tag html line 4 </html>

ca fait quand meme beaucoup d erreurs sur /html arf . . . . on se demande parfois quel CMs peut faire de telles erreurs . . . hum surement un joomla en fait . . . Oups non ! mince alors !!! c est un spip . . . Il doit utiliser une vieille version du squelette TMA ou l avoir bidouillé lui même . . .

trikapalanet DOT com

Signalons aussi trikapalanet "point" com , qui bien que n affichant que 9 erreurs de validation, fait de grosses erreurs, et le site s affiche particulièrement mal sous firefox (a moins que cela ne soit le design officiel ?) : voir http://quaoar.ww7.be/trikapalanet_c...

1. Error Line 38, Column 23: Attribute "role" is not a valid attribute. Did you mean "frameborder" or "scrolling"? <div id="header" role="banner"> 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. 2. Error Line 56, Column 350: Attribute "wmode" is not a valid attribute. Did you mean "code" or "frameborder"? …Screen" value="true" /><embed wmode="transparent" src="http://www.youtube.com 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. 3. Error Line 56, Column 368: Attribute "src" exists, but can not be used for this element. …e" /><embed wmode="transparent" src="http://www.youtube.com/v/JSK_EwyJmfw&amp 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. 4. Error Line 56, Column 556: Attribute "type" exists, but can not be used for this element. …oad_policy=3&showsearch=0" type="application/x-shockwave-flash" allowfull 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. 5. Error Line 56, Column 604: Attribute "allowfullscreen" is not a valid attribute …/x-shockwave-flash" allowfullscreen="true" width="425" height="355" ></embed> 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. 6. Error Line 56, Column 617: Attribute "width" exists, but can not be used for this element. …flash" allowfullscreen="true" width="425" height="355" ></embed><param name=" 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. 7. Error Line 56, Column 630: Attribute "height" exists, but can not be used for this element. …ullscreen="true" width="425" height="355" ></embed><param name="wmode" value= 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. 8. Error Line 56, Column 636: element "embed" undefined. Did you mean "meta" or "em"? …een="true" width="425" height="355" ></embed><param name="wmode" value="trans 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). 9. Error Line 72, Column 636: element "embed" undefined. Did you mean "meta" or "em"? …een="true" width="425" height="355" ></embed><param name="wmode" value="trans 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).

trikapalanet DOT org

Et voici enfin trikapalanet "point" org : 9 erreurs lui aussi mais au moins il s’affiche correctement sur firefox . . . voir http://quaoar.ww7.be/trikapalanet_o...

Validation Output: 9 Errors 1. Error Line 35, Column 23: Attribute "role" is not a valid attribute. Did you mean "frameborder" or "scrolling"? <div id="header" role="banner"> 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. 2. Error Line 96, Column 12: Attribute "role" is not a valid attribute. Did you mean "frameborder" or "scrolling"? <ul role="navigation"> 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. 3. Error Line 123, Column 168: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag …t de <strong>Trikapalanet</strong><p> 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>"). 4. Error Line 124, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <center><h2>100% Trikapalanet</h2></center> 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>"). 5. Error Line 126, Column 6: end tag for "p" 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 ">". 6. Info Line 122, Column 1: start tag was here <p> 7. Error Line 126, Column 6: XML Parsing Error: Opening and ending tag mismatch: p line 122 and div </div> 8. Error Line 131, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 32 and body </body> 9. Error Line 132, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 31 and html </html> 10. Error Line 132, Column 7: XML Parsing Error: Premature end of data in tag html line 2 </html>

Tiens lui aussi a plusieurs /html , peut etre est ce aussi un joomla ? ou pire ? ah non celui la c est un wordpress en fait . . .

trikapalanet bleublog DOT ch

Parmi les top concurrents de la chasse au Trikapalanet sauvage, reste le site trikapalanet de bleublog, joli site qui saffiche assez bien, mais tout de meme 8 erreurs de validation ( voir http://quaoar.ww7.be/trikapalanet_b... )

Validation Output: 8 Errors 1. Error Line 136, Column 55: document type does not allow element "style" here <style type="text/css">h3 { cursor: pointer; }</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). 2. Warning Line 142, Column 21: character "&" is the first character of a delimiter but occurred as data if (elt && elt.tagName == "H3") { 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 "&", which is always safe. * Another possibility is that you forgot to close quotes in a previous tag. 3. Warning Line 142, Column 22: character "&" is the first character of a delimiter but occurred as data if (elt && elt.tagName == "H3") { 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 "&", which is always safe. * Another possibility is that you forgot to close quotes in a previous tag. 4. Error Line 171, Column 224: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag …d="div_send165462" class="emailthis"></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>"). 5. Error Line 197, Column 43: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <div id="div_send165387" class="emailthis"></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>"). 6. Error Line 221, Column 43: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <div id="div_send165363" class="emailthis"></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>"). 7. Error Line 288, Column 30: required attribute "type" not specified <script language="Javascript">var szmvars="lematin//CP//BLEUBLOG";</script> The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element. Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>. 8. Error Line 289, Column 80: required attribute "type" not specified …ematin.wemfbox.ch/2004/01/survey.js"></script> The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element. Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>. 9. Error Line 142, Column 21: XML Parsing Error: xmlParseEntityRef: no name if (elt && elt.tagName == "H3") { 10. Error Line 142, Column 22: XML Parsing Error: xmlParseEntityRef: no name if (elt && elt.tagName == "H3") {

trikapalanet DOT eu

Enfin terminons par le bon dernier de nos concurrents plus ou moins serieux trikapalanet.eu affiche tout de meme 22 Erreurs et 10 warning(s) :

EDIT Loiseau2nuit : Papillon est toujours sérieuse et je n’ai nul doute que nous la retrouverons en page 1 avec nous à la fin de ce concours. Elle a de qui tenir :-)

voir http://quaoar.ww7.be/trikapalanet_e...

Validation Output: 22 Errors 1. Error Line 8, Column 38: end tag for "meta" omitted, but OMITTAG NO was specified <meta name="googlebot" content="al… You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 2. Info Line 8: start tag was here ><meta name="googlebot" content="all"> 3. Error Line 9, Column 35: end tag for "meta" omitted, but OMITTAG NO was specified <meta name="robots" content="al… You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 4. Info Line 9: start tag was here ><meta name="robots" content="all"> 5. Error Line 10, Column 97: end tag for "meta" omitted, but OMITTAG NO was specified …z / Papillon, Tous droits réservé… You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 6. Info Line 10: start tag was here d<meta name="copyright" content="Copyright &copy; 2009 Webdeez / Papillon, Tous d 7. Warning Line 121, Column 52: cannot generate system identifier for general entity "cpt" src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 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 &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. 8. Error Line 121, Column 52: general entity "cpt" not defined and no default entity src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 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. 9. Warning Line 121, Column 55: reference not terminated by REFC delimiter src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 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. 10. Warning Line 121, Column 55: reference to external entity in attribute value src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 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 '&'. 11. Error Line 121, Column 55: reference to entity "cpt" for which no system identifier could be generated src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 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. 12. Info Line 121, Column 50: entity was defined here src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 13. Warning Line 121, Column 56: character "<" is the first character of a delimiter but occurred as data src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 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 "&", which is always safe. * Another possibility is that you forgot to close quotes in a previous tag. 14. Warning Line 123, Column 4: cannot generate system identifier for general entity "data" ?>&data=site&option=invisible"> 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 &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. 15. Error Line 123, Column 4: general entity "data" not defined and no default entity ?>&data=site&option=invisible"> 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. 16. Warning Line 123, Column 8: reference not terminated by REFC delimiter ?>&data=site&option=invisible"> 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. 17. Warning Line 123, Column 8: reference to external entity in attribute value ?>&data=site&option=invisible"> 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 '&'. 18. Error Line 123, Column 8: reference to entity "data" for which no system identifier could be generated ?>&data=site&option=invisible"> 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. 19. Info Line 123, Column 2: entity was defined here ?>&data=site&option=invisible"> 20. Warning Line 123, Column 14: cannot generate system identifier for general entity "option" ?>&data=site&option=invisible"> 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 &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. 21. Error Line 123, Column 14: general entity "option" not defined and no default entity ?>&data=site&option=invisible"> 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. 22. Warning Line 123, Column 20: reference not terminated by REFC delimiter ?>&data=site&option=invisible"> 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. 23. Warning Line 123, Column 20: reference to external entity in attribute value ?>&data=site&option=invisible"> 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 '&'. 24. Error Line 123, Column 20: reference to entity "option" for which no system identifier could be generated ?>&data=site&option=invisible"> 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. 25. Info Line 123, Column 12: entity was defined here ?>&data=site&option=invisible"> 26. Error Line 19, Column 7: XML Parsing Error: Opening and ending tag mismatch: meta line 10 and head </head> 27. Error Line 121, Column 54: XML Parsing Error: EntityRef: expecting ';' src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 28. Error Line 121, Column 55: XML Parsing Error: Unescaped '<' not allowed in attributes values src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 29. Error Line 121, Column 55: XML Parsing Error: attributes construct error src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 30. Error Line 121, Column 55: XML Parsing Error: Couldn't find end of Start Tag script line 120 src="http://m3.moostik.net/js/?pseudo=trikapalanet&cpt=<?php 31. Error Line 123, Column 7: XML Parsing Error: EntityRef: expecting ';' ?>&data=site&option=invisible"> 32. Error Line 123, Column 19: XML Parsing Error: EntityRef: expecting ';' ?>&data=site&option=invisible"> 33. Error Line 124, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 118 and script </script></div><script type="text/javascript"> 34. Error Line 135, Column 6: XML Parsing Error: Opening and ending tag mismatch: body line 20 and div </div> <!-- end of container --> 35. Error Line 136, Column 7: XML Parsing Error: Opening and ending tag mismatch: meta line 9 and body </body> 36. Error Line 137, Column 7: XML Parsing Error: Opening and ending tag mismatch: meta line 8 and html </html> 37. Error Line 137, Column 7: XML Parsing Error: Premature end of data in tag head line 3 </html> 38. Error Line 137, Column 7: XML Parsing Error: Premature end of data in tag html line 2 </html>

Bien evidement les conseils pour corriger ces erreurs de validation sont offerts a nos concurrents en échange d’un petit backlink ;)