Validation Output:  174 Errors

   1. Error Line 1, Column 0: no document type declaration; will parse without validation.

      <b>[phpBB Debug] PHP Notice</b>: in file <b>/includes/functions.php</b> on line 

      ✉

      The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

      Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.
   2. Error Line 1, Column 31: character data is not allowed here.

      <b>[phpBB Debug] PHP Notice</b>: in file <b>/includes/functions.php</b> on line 

      ✉

      You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
          * putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
          * forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
          * using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
   3. Error Line 1, Column 43: document type does not allow element "B" here.

      …pBB Debug] PHP Notice</b>: in file <b>/includes/functions.php</b> on line <b>

      ✉

      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).
   4. Error Line 1, Column 72: character data is not allowed here.

      … file <b>/includes/functions.php</b> on line <b>3289</b>: <b>Undefined index:

      ✉

      You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
          * putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
          * forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
          * using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
   5. Error Line 1, Column 82: document type does not allow element "B" here.

      …includes/functions.php</b> on line <b>3289</b>: <b>Undefined index:  HIDDEN_U

      ✉

      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).
   6. Error Line 1, Column 91: character data is not allowed here.

      …functions.php</b> on line <b>3289</b>: <b>Undefined index:  HIDDEN_USERS_ZERO

      ✉

      You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
          * putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
          * forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
          * using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
   7. Error Line 1, Column 95: document type does not allow element "B" here.

      …tions.php</b> on line <b>3289</b>: <b>Undefined index:  HIDDEN_USERS_ZERO_TOT

      ✉

      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).
   8. Warning Line 1, Column 149: NET-enabling start-tag requires SHORTTAG YES.

      …  HIDDEN_USERS_ZERO_TOTAL_AND</b><br />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
   9. Error Line 1, Column 149: document type does not allow element "BR" here.

      …  HIDDEN_USERS_ZERO_TOTAL_AND</b><br />

      ✉

      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).
  10. Error Line 2, Column 2: "DOCTYPE" declaration not allowed in instance.

      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

      ✉
  11. Warning Line 7, Column 67: NET-enabling start-tag requires SHORTTAG YES.

      …"content-type" content="text/html; charset=UTF-8" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  12. Warning Line 8, Column 58: NET-enabling start-tag requires SHORTTAG YES.

      <meta http-equiv="content-language" content="fr-standard" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  13. Warning Line 9, Column 57: NET-enabling start-tag requires SHORTTAG YES.

      <meta http-equiv="content-style-type" content="text/css" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  14. Warning Line 10, Column 45: NET-enabling start-tag requires SHORTTAG YES.

      <meta http-equiv="imagetoolbar" content="no" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  15. Warning Line 11, Column 46: NET-enabling start-tag requires SHORTTAG YES.

      <meta name="resource-type" content="document" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  16. Warning Line 12, Column 43: NET-enabling start-tag requires SHORTTAG YES.

      <meta name="distribution" content="global" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  17. Warning Line 13, Column 68: NET-enabling start-tag requires SHORTTAG YES.

      …ht" content="2000, 2002, 2005, 2007 phpBB Group" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  18. Warning Line 14, Column 33: NET-enabling start-tag requires SHORTTAG YES.

      <meta name="keywords" content="" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  19. Warning Line 15, Column 36: NET-enabling start-tag requires SHORTTAG YES.

      <meta name="description" content="" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  20. Warning Line 18, Column 87: NET-enabling start-tag requires SHORTTAG YES.

      …heme/stylesheet.css" type="text/css" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  21. Warning Line 19, Column 146: NET-enabling start-tag requires SHORTTAG YES.

      …dication.php" type="application/xml" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  22. Error Line 85, Column 8: end tag for element "SCRIPT" which is not open.

      </script>

      ✉

      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.
  23. Warning Line 96, Column 194: NET-enabling start-tag requires SHORTTAG YES.

      …="1000" height="110" alt="" title="" /></a></div></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  24. Warning Line 132, Column 4: NET-enabling start-tag requires SHORTTAG YES.

      <br />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  25. Warning Line 136, Column 34: cannot generate system identifier for general entity "amp".

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

      ✉

      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.
  26. Error Line 136, Column 34: general entity "amp" not defined and no default entity.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

      ✉

      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.
  27. Error Line 136, Column 37: reference to entity "amp" for which no system identifier could be generated.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

      ✉

      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.
  28. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  29. Warning Line 136, Column 171: NET-enabling start-tag requires SHORTTAG YES.

      ….gif" width="12" height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  30. Warning Line 136, Column 188: cannot generate system identifier for general entity "nbsp".

      …height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=regi

      ✉

      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.
  31. Error Line 136, Column 188: general entity "nbsp" not defined and no default entity.

      …height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=regi

      ✉

      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.
  32. Error Line 136, Column 192: reference to entity "nbsp" for which no system identifier could be generated.

      …ht="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=register

      ✉

      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.
  33. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  34. Error Line 136, Column 199: reference to entity "nbsp" for which no system identifier could be generated.

      … alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=register&amp;si

      ✉

      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.
  35. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  36. Error Line 136, Column 236: reference to entity "amp" for which no system identifier could be generated.

      …;<a href="./ucp.php?mode=register&amp;sid=30e97dce70daef278515d130d3e41232"><

      ✉

      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.
  37. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  38. Warning Line 136, Column 373: NET-enabling start-tag requires SHORTTAG YES.

      ….gif" width="12" height="13" alt="*" /> M’enregistrer</a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  39. Warning Line 139, Column 154: NET-enabling start-tag requires SHORTTAG YES.

      ….gif" width="12" height="13" alt="*" /> FAQ</a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  40. Error Line 140, Column 9: reference to entity "nbsp" for which no system identifier could be generated.

      				&nbsp;<a href="./search.php?sid=30e97dce70daef278515d130d3e41232"><img src="

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
  41. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  42. Warning Line 140, Column 166: NET-enabling start-tag requires SHORTTAG YES.

      ….gif" width="12" height="13" alt="*" /> Rechercher</a>			</td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  43. Warning Line 149, Column 80: NET-enabling start-tag requires SHORTTAG YES.

      …sommes le Jeudi 10 Avr 2008 13:45<br /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  44. Error Line 159, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./search.php?search_id=unanswered&amp;sid=30e97dce70daef278515d130d3e41232">V

      ✉

      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.
  45. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  46. Error Line 159, Column 201: reference to entity "amp" for which no system identifier could be generated.

      …earch.php?search_id=active_topics&amp;sid=30e97dce70daef278515d130d3e41232">V

      ✉

      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.
  47. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  48. Warning Line 162, Column 26: NET-enabling start-tag requires SHORTTAG YES.

      	<br style="clear: both;" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  49. Error Line 167, Column 144: reference to entity "amp" for which no system identifier could be generated.

      …87; <a href="./viewforum.php?f=20&amp;sid=30e97dce70daef278515d130d3e41232">W

      ✉

      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.
  50. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  51. Error Line 167, Column 234: reference to entity "amp" for which no system identifier could be generated.

      …187; <a href="./viewforum.php?f=3&amp;sid=30e97dce70daef278515d130d3e41232">S

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
  52. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  53. Warning Line 172, Column 5: NET-enabling start-tag requires SHORTTAG YES.

      	<br />	<div id="pageheader">

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  54. Error Line 173, Column 53: reference to entity "amp" for which no system identifier could be generated.

      …titles" href="./viewforum.php?f=3&amp;st=0&amp;sk=t&amp;sd=d&amp;start=0&amp;

      ✉

      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.
  55. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  56. Error Line 173, Column 62: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewforum.php?f=3&amp;st=0&amp;sk=t&amp;sd=d&amp;start=0&amp;sid=30e97

      ✉

      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.
  57. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  58. Error Line 173, Column 71: reference to entity "amp" for which no system identifier could be generated.

      …ewforum.php?f=3&amp;st=0&amp;sk=t&amp;sd=d&amp;start=0&amp;sid=30e97dce70daef

      ✉

      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.
  59. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  60. Error Line 173, Column 80: reference to entity "amp" for which no system identifier could be generated.

      …hp?f=3&amp;st=0&amp;sk=t&amp;sd=d&amp;start=0&amp;sid=30e97dce70daef278515d13

      ✉

      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.
  61. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  62. Error Line 173, Column 92: reference to entity "amp" for which no system identifier could be generated.

      …t=0&amp;sk=t&amp;sd=d&amp;start=0&amp;sid=30e97dce70daef278515d130d3e41232">S

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
  63. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  64. Error Line 175, Column 85: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=3&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
  65. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  66. Error Line 175, Column 93: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=3&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
  67. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  68. Warning Line 178, Column 17: NET-enabling start-tag requires SHORTTAG YES.

      	<br clear="all" /><br />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  69. Warning Line 178, Column 23: NET-enabling start-tag requires SHORTTAG YES.

      	<br clear="all" /><br />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  70. Error Line 184, Column 76: reference to entity "amp" for which no system identifier could be generated.

      …><a href="./posting.php?mode=post&amp;f=3&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
  71. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  72. Error Line 184, Column 84: reference to entity "amp" for which no system identifier could be generated.

      …="./posting.php?mode=post&amp;f=3&amp;sid=30e97dce70daef278515d130d3e41232"><

      ✉

      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.
  73. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

  74. Warning Line 184, Column 249: NET-enabling start-tag requires SHORTTAG YES.

      …jet" title="Poster un nouveau sujet" /></a></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  75. Error Line 185, Column 60: reference to entity "nbsp" for which no system identifier could be generated.

      …valign="middle" nowrap="nowrap">&nbsp;Page <strong>1</strong> sur <strong>1</

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
  76. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  77. Warning Line 185, Column 111: NET-enabling start-tag requires SHORTTAG YES.

      …1</strong> sur <strong>1</strong><br /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
  78. Error Line 186, Column 46: reference to entity "nbsp" for which no system identifier could be generated.

      				<td class="gensmall" nowrap="nowrap">&nbsp;[ 8 sujets ]&nbsp;</td>

      ✉

      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.
  79. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  80. Error Line 186, Column 64: reference to entity "nbsp" for which no system identifier could be generated.

      …ss="gensmall" nowrap="nowrap">&nbsp;[ 8 sujets ]&nbsp;</td>

      ✉

      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.
  81. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  82. Error Line 195, Column 30: reference to entity "nbsp" for which no system identifier could be generated.

      					<td valign="middle">&nbsp;</td>

      ✉

      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.
  83. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  84. Error Line 196, Column 44: reference to entity "nbsp" for which no system identifier could be generated.

      					<td align="right" valign="middle">&nbsp;</td>

      ✉

      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.
  85. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  86. Error Line 203, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      							<th colspan="2">&nbsp;Sujets&nbsp;</th>

      ✉

      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.
  87. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  88. Error Line 203, Column 40: reference to entity "nbsp" for which no system identifier could be generated.

      							<th colspan="2">&nbsp;Sujets&nbsp;</th>

      ✉

      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.
  89. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  90. Error Line 204, Column 15: reference to entity "nbsp" for which no system identifier could be generated.

      						<th>&nbsp;Auteur&nbsp;</th>

      ✉

      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.
  91. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  92. Error Line 204, Column 27: reference to entity "nbsp" for which no system identifier could be generated.

      						<th>&nbsp;Auteur&nbsp;</th>

      ✉

      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.
  93. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  94. Error Line 205, Column 12: reference to entity "nbsp" for which no system identifier could be generated.

      			<th>&nbsp;Réponses&nbsp;</th>

      ✉

      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.
  95. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  96. Error Line 205, Column 26: reference to entity "nbsp" for which no system identifier could be generated.

      			<th>&nbsp;Réponses&nbsp;</th>

      ✉

      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.
  97. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

  98. Error Line 206, Column 12: reference to entity "nbsp" for which no system identifier could be generated.

      			<th>&nbsp;Vus&nbsp;</th>

      ✉

      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.
  99. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 100. Error Line 206, Column 21: reference to entity "nbsp" for which no system identifier could be generated.

      			<th>&nbsp;Vus&nbsp;</th>

      ✉

      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.
 101. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 102. Error Line 207, Column 12: reference to entity "nbsp" for which no system identifier could be generated.

      			<th>&nbsp;Dernier message&nbsp;</th>

      ✉

      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.
 103. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 104. Error Line 207, Column 33: reference to entity "nbsp" for which no system identifier could be generated.

      			<th>&nbsp;Dernier message&nbsp;</th>

      ✉

      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.
 105. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 106. Warning Line 215, Column 333: NET-enabling start-tag requires SHORTTAG YES.

      …ssages ou poster d’autres réponses." /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 107. Error Line 217, Column 85: reference to entity "amp" for which no system identifier could be generated.

      … 15:13" href="./viewtopic.php?f=3&amp;t=9&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 108. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 109. Error Line 217, Column 93: reference to entity "amp" for which no system identifier could be generated.

      …href="./viewtopic.php?f=3&amp;t=9&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 110. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 111. Error Line 219, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 112. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 113. Error Line 219, Column 125: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 114. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 115. Error Line 224, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 116. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 117. Error Line 224, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 118. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 119. Error Line 224, Column 220: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=9&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 120. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 121. Error Line 224, Column 228: reference to entity "amp" for which no system identifier could be generated.

      …href="./viewtopic.php?f=3&amp;t=9&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 122. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 123. Error Line 224, Column 269: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=9#p9"><img src="./styles/subsilver2/i

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 124. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 125. Warning Line 224, Column 424: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 126. Warning Line 234, Column 331: NET-enabling start-tag requires SHORTTAG YES.

      …ssages ou poster d’autres réponses." /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 127. Error Line 236, Column 82: reference to entity "amp" for which no system identifier could be generated.

      … 12:05" href="./viewtopic.php?f=3&amp;t=250&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 128. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 129. Error Line 236, Column 92: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=250&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 130. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 131. Error Line 238, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=14&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 132. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 133. Error Line 238, Column 126: reference to entity "amp" for which no system identifier could be generated.

      …ist.php?mode=viewprofile&amp;u=14&amp;sid=30e97dce70daef278515d130d3e41232">G

      ✉

      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.
 134. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 135. Error Line 243, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=14&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 136. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 137. Error Line 243, Column 84: reference to entity "amp" for which no system identifier could be generated.

      …ist.php?mode=viewprofile&amp;u=14&amp;sid=30e97dce70daef278515d130d3e41232">G

      ✉

      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.
 138. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 139. Error Line 243, Column 168: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=250&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 140. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 141. Error Line 243, Column 178: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=250&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 142. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 143. Error Line 243, Column 219: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=1293#p1293"><img src="./styles/subsil

      ✉

      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.
 144. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 145. Warning Line 243, Column 380: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 146. Warning Line 250, Column 331: NET-enabling start-tag requires SHORTTAG YES.

      …ssages ou poster d’autres réponses." /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 147. Error Line 252, Column 85: reference to entity "amp" for which no system identifier could be generated.

      … 10:03" href="./viewtopic.php?f=3&amp;t=247&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 148. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 149. Error Line 252, Column 95: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=247&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 150. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 151. Error Line 252, Column 168: reference to entity "amp" for which no system identifier could be generated.

      …2" class="topictitle">Prévention &amp; Protection</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.
 152. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 153. Error Line 254, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 154. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 155. Error Line 254, Column 125: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 156. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 157. Error Line 259, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 158. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 159. Error Line 259, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 160. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 161. Error Line 259, Column 220: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=247&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 162. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 163. Error Line 259, Column 230: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=247&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 164. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 165. Error Line 259, Column 271: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=1261#p1261"><img src="./styles/subsil

      ✉

      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.
 166. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 167. Warning Line 259, Column 432: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 168. Warning Line 266, Column 331: NET-enabling start-tag requires SHORTTAG YES.

      …ssages ou poster d’autres réponses." /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 169. Error Line 268, Column 82: reference to entity "amp" for which no system identifier could be generated.

      … 00:14" href="./viewtopic.php?f=3&amp;t=28&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 170. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 171. Error Line 268, Column 91: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=3&amp;t=28&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 172. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 173. Error Line 270, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 174. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 175. Error Line 270, Column 125: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 176. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 177. Error Line 275, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 178. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 179. Error Line 275, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 180. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 181. Error Line 275, Column 220: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=28&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 182. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 183. Error Line 275, Column 229: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=3&amp;t=28&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 184. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 185. Error Line 275, Column 270: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=30#p30"><img src="./styles/subsilver2

      ✉

      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.
 186. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 187. Warning Line 275, Column 427: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 188. Warning Line 282, Column 331: NET-enabling start-tag requires SHORTTAG YES.

      …ssages ou poster d’autres réponses." /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 189. Error Line 284, Column 85: reference to entity "amp" for which no system identifier could be generated.

      … 19:45" href="./viewtopic.php?f=3&amp;t=21&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 190. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 191. Error Line 284, Column 94: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=3&amp;t=21&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 192. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 193. Error Line 286, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 194. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 195. Error Line 286, Column 125: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 196. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 197. Error Line 291, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 198. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 199. Error Line 291, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 200. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 201. Error Line 291, Column 220: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=21&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 202. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 203. Error Line 291, Column 229: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=3&amp;t=21&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 204. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 205. Error Line 291, Column 270: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=21#p21"><img src="./styles/subsilver2

      ✉

      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.
 206. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 207. Warning Line 291, Column 427: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 208. Warning Line 298, Column 185: NET-enabling start-tag requires SHORTTAG YES.

      …sage" title="Pas de nouveau message" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 209. Error Line 300, Column 82: reference to entity "amp" for which no system identifier could be generated.

      … 16:10" href="./viewtopic.php?f=3&amp;t=243&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 210. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 211. Error Line 300, Column 92: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=243&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 212. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 213. Error Line 302, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=11&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 214. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 215. Error Line 302, Column 126: reference to entity "amp" for which no system identifier could be generated.

      …ist.php?mode=viewprofile&amp;u=11&amp;sid=30e97dce70daef278515d130d3e41232">f

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 216. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 217. Error Line 307, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=11&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 218. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 219. Error Line 307, Column 84: reference to entity "amp" for which no system identifier could be generated.

      …ist.php?mode=viewprofile&amp;u=11&amp;sid=30e97dce70daef278515d130d3e41232">f

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 220. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 221. Error Line 307, Column 175: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=243&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 222. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 223. Error Line 307, Column 185: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=243&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 224. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 225. Error Line 307, Column 226: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=1215#p1215"><img src="./styles/subsil

      ✉

      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.
 226. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 227. Warning Line 307, Column 387: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 228. Warning Line 314, Column 185: NET-enabling start-tag requires SHORTTAG YES.

      …sage" title="Pas de nouveau message" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 229. Error Line 316, Column 82: reference to entity "amp" for which no system identifier could be generated.

      … 23:39" href="./viewtopic.php?f=3&amp;t=227&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 230. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 231. Error Line 316, Column 92: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=227&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 232. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 233. Error Line 318, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=41&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 234. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 235. Error Line 318, Column 126: reference to entity "amp" for which no system identifier could be generated.

      …ist.php?mode=viewprofile&amp;u=41&amp;sid=30e97dce70daef278515d130d3e41232">J

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 236. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 237. Error Line 323, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 238. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 239. Error Line 323, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 240. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 241. Error Line 323, Column 220: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=227&amp;sid=30e97dce70daef278515d130d

      ✉

      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.
 242. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 243. Error Line 323, Column 230: reference to entity "amp" for which no system identifier could be generated.

      …ef="./viewtopic.php?f=3&amp;t=227&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 244. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 245. Error Line 323, Column 271: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=985#p985"><img src="./styles/subsilve

      ✉

      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.
 246. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 247. Warning Line 323, Column 430: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 248. Warning Line 330, Column 168: NET-enabling start-tag requires SHORTTAG YES.

      …Sujet déplacé" title="Sujet déplacé" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 249. Error Line 332, Column 102: reference to entity "amp" for which no system identifier could be generated.

      … 15:57" href="./viewtopic.php?f=4&amp;t=82&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 250. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 251. Error Line 332, Column 111: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=4&amp;t=82&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 252. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 253. Error Line 334, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=19&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 254. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 255. Error Line 334, Column 126: reference to entity "amp" for which no system identifier could be generated.

      …ist.php?mode=viewprofile&amp;u=19&amp;sid=30e97dce70daef278515d130d3e41232">D

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 256. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 257. Error Line 339, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 258. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 259. Error Line 339, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=2&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 260. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 261. Error Line 339, Column 220: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=4&amp;t=82&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 262. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 263. Error Line 339, Column 229: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=4&amp;t=82&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 264. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 265. Error Line 339, Column 270: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=267#p267"><img src="./styles/subsilve

      ✉

      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.
 266. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 267. Warning Line 339, Column 429: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 268. Warning Line 346, Column 185: NET-enabling start-tag requires SHORTTAG YES.

      …sage" title="Pas de nouveau message" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 269. Error Line 348, Column 82: reference to entity "amp" for which no system identifier could be generated.

      … 13:15" href="./viewtopic.php?f=3&amp;t=48&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 270. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 271. Error Line 348, Column 91: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=3&amp;t=48&amp;sid=30e97dce70daef278515d130d3e41232" c

      ✉

      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.
 272. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 273. Error Line 350, Column 117: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=3&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 274. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 275. Error Line 350, Column 125: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=3&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 276. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 277. Error Line 355, Column 75: reference to entity "amp" for which no system identifier could be generated.

      …./memberlist.php?mode=viewprofile&amp;u=3&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 278. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 279. Error Line 355, Column 83: reference to entity "amp" for which no system identifier could be generated.

      …list.php?mode=viewprofile&amp;u=3&amp;sid=30e97dce70daef278515d130d3e41232" s

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 280. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 281. Error Line 355, Column 221: reference to entity "amp" for which no system identifier could be generated.

      …					<a href="./viewtopic.php?f=3&amp;t=48&amp;sid=30e97dce70daef278515d130d3

      ✉

      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.
 282. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 283. Error Line 355, Column 230: reference to entity "amp" for which no system identifier could be generated.

      …ref="./viewtopic.php?f=3&amp;t=48&amp;sid=30e97dce70daef278515d130d3e41232&am

      ✉

      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.
 284. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 285. Error Line 355, Column 271: reference to entity "amp" for which no system identifier could be generated.

      …=30e97dce70daef278515d130d3e41232&amp;p=98#p98"><img src="./styles/subsilver2

      ✉

      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.
 286. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 287. Warning Line 355, Column 428: NET-enabling start-tag requires SHORTTAG YES.

      …age" title="Voir le dernier message" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 288. Error Line 363, Column 59: reference to entity "amp" for which no system identifier could be generated.

      …post" action="./viewforum.php?f=3&amp;start=0&amp;sid=30e97dce70daef278515d13

      ✉

      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.
 289. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 290. Error Line 363, Column 71: reference to entity "amp" for which no system identifier could be generated.

      …="./viewforum.php?f=3&amp;start=0&amp;sid=30e97dce70daef278515d130d3e41232"><

      ✉

      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.
 291. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 292. Error Line 363, Column 176: reference to entity "nbsp" for which no system identifier could be generated.

      …er les sujets précédents:</span>&nbsp;<select name="st" id="st"><option value

      ✉

      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.
 293. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 294. Error Line 363, Column 509: reference to entity "nbsp" for which no system identifier could be generated.

      …lue="365">1 an</option></select>&nbsp;<span class="gensmall">Trier par</span>

      ✉

      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.
 295. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 296. Error Line 363, Column 901: reference to entity "nbsp" for which no system identifier could be generated.

      …d">Décroissant</option></select>&nbsp;<input class="btnlite" type="submit" na

      ✉

      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.
 297. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 298. Warning Line 363, Column 965: NET-enabling start-tag requires SHORTTAG YES.

      …e="submit" name="sort" value="Aller" /></form>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 299. Error Line 369, Column 76: reference to entity "amp" for which no system identifier could be generated.

      …><a href="./posting.php?mode=post&amp;f=3&amp;sid=30e97dce70daef278515d130d3e

      ✉

      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.
 300. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 301. Error Line 369, Column 84: reference to entity "amp" for which no system identifier could be generated.

      …="./posting.php?mode=post&amp;f=3&amp;sid=30e97dce70daef278515d130d3e41232"><

      ✉

      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.
 302. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 303. Warning Line 369, Column 249: NET-enabling start-tag requires SHORTTAG YES.

      …jet" title="Poster un nouveau sujet" /></a></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 304. Error Line 370, Column 60: reference to entity "nbsp" for which no system identifier could be generated.

      …valign="middle" nowrap="nowrap">&nbsp;Page <strong>1</strong> sur <strong>1</

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 305. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 306. Warning Line 370, Column 111: NET-enabling start-tag requires SHORTTAG YES.

      …1</strong> sur <strong>1</strong><br /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 307. Error Line 371, Column 46: reference to entity "nbsp" for which no system identifier could be generated.

      				<td class="gensmall" nowrap="nowrap">&nbsp;[ 8 sujets ]&nbsp;</td>

      ✉

      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.
 308. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 309. Error Line 371, Column 64: reference to entity "nbsp" for which no system identifier could be generated.

      …ss="gensmall" nowrap="nowrap">&nbsp;[ 8 sujets ]&nbsp;</td>

      ✉

      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.
 310. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 311. Warning Line 376, Column 18: NET-enabling start-tag requires SHORTTAG YES.

      		<br clear="all" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 312. Error Line 382, Column 144: reference to entity "amp" for which no system identifier could be generated.

      …87; <a href="./viewforum.php?f=20&amp;sid=30e97dce70daef278515d130d3e41232">W

      ✉

      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.
 313. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 314. Error Line 382, Column 234: reference to entity "amp" for which no system identifier could be generated.

      …187; <a href="./viewforum.php?f=3&amp;sid=30e97dce70daef278515d130d3e41232">S

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 315. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 316. Warning Line 386, Column 26: NET-enabling start-tag requires SHORTTAG YES.

      	</table>	<br clear="all" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 317. Warning Line 396, Column 17: NET-enabling start-tag requires SHORTTAG YES.

      	<br clear="all" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 318. Warning Line 403, Column 177: NET-enabling start-tag requires SHORTTAG YES.

      … messages" title="Nouveaux messages" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 319. Error Line 405, Column 13: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 320. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 321. Error Line 405, Column 19: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 322. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 323. Warning Line 406, Column 185: NET-enabling start-tag requires SHORTTAG YES.

      …sage" title="Pas de nouveau message" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 324. Error Line 408, Column 13: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 325. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 326. Error Line 408, Column 19: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 327. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 328. Warning Line 409, Column 158: NET-enabling start-tag requires SHORTTAG YES.

      …t="18" alt="Annonce" title="Annonce" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 329. Warning Line 413, Column 200: NET-enabling start-tag requires SHORTTAG YES.

      …e="Nouveaux messages [ Populaires ]" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 330. Error Line 415, Column 13: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 331. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 332. Error Line 415, Column 19: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 333. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 334. Warning Line 416, Column 212: NET-enabling start-tag requires SHORTTAG YES.

      …de nouveaux messages [ Populaires ]" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 335. Error Line 418, Column 13: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 336. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 337. Error Line 418, Column 19: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 338. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 339. Warning Line 419, Column 145: NET-enabling start-tag requires SHORTTAG YES.

      …t="18" alt="Post-it" title="Post-it" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 340. Warning Line 423, Column 205: NET-enabling start-tag requires SHORTTAG YES.

      …="Nouveaux messages [ Verrouillés ]" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 341. Error Line 425, Column 13: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 342. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 343. Error Line 425, Column 19: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 344. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 345. Warning Line 426, Column 217: NET-enabling start-tag requires SHORTTAG YES.

      …e nouveaux messages [ Verrouillés ]" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 346. Error Line 428, Column 13: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 347. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 348. Error Line 428, Column 19: reference to entity "nbsp" for which no system identifier could be generated.

      				<td>&nbsp;&nbsp;</td>

      ✉

      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.
 349. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 350. Warning Line 429, Column 157: NET-enabling start-tag requires SHORTTAG YES.

      …Sujet déplacé" title="Sujet déplacé" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 351. Warning Line 434, Column 108: NET-enabling start-tag requires SHORTTAG YES.

      …strong> poster de nouveaux sujets<br />Vous <strong>ne pouvez pas</strong> ré

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 352. Warning Line 434, Column 169: NET-enabling start-tag requires SHORTTAG YES.

      … pas</strong> répondre aux sujets<br />Vous <strong>ne pouvez pas</strong> éd

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 353. Warning Line 434, Column 230: NET-enabling start-tag requires SHORTTAG YES.

      … pas</strong> éditer vos messages<br />Vous <strong>ne pouvez pas</strong> su

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 354. Warning Line 434, Column 294: NET-enabling start-tag requires SHORTTAG YES.

      …s</strong> supprimer vos messages<br />Vous <strong>ne pouvez pas</strong> jo

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 355. Warning Line 434, Column 356: NET-enabling start-tag requires SHORTTAG YES.

      …pas</strong> joindre des fichiers<br /></span></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 356. Warning Line 438, Column 16: NET-enabling start-tag requires SHORTTAG YES.

      <br clear="all" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 357. Error Line 442, Column 71: reference to entity "amp" for which no system identifier could be generated.

      …rch" action="./search.php?fid[]=3&amp;sid=30e97dce70daef278515d130d3e41232"><

      ✉

      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.
 358. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 359. Warning Line 442, Column 210: NET-enabling start-tag requires SHORTTAG YES.

      …ype="text" name="keywords" size="20" /> <input class="btnlite" type="submit" 

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 360. Warning Line 442, Column 264: NET-enabling start-tag requires SHORTTAG YES.

      …btnlite" type="submit" value="Aller" /></form></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 361. Error Line 447, Column 65: reference to entity "nbsp" for which no system identifier could be generated.

      …class="gensmall">Aller à:</span>&nbsp;<select name="f" onchange="if(this.opti

      ✉

      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.
 362. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 363. Error Line 451, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="2">&nbsp; &nbsp;La charte du forum</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 364. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 365. Error Line 451, Column 35: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="2">&nbsp; &nbsp;La charte du forum</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 366. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 367. Error Line 452, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="1">&nbsp; &nbsp;Annonces du forum</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 368. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 369. Error Line 452, Column 35: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="1">&nbsp; &nbsp;Annonces du forum</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 370. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 371. Error Line 454, Column 48: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="3" selected="selected">&nbsp; &nbsp;Sécurité</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 372. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 373. Error Line 454, Column 55: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="3" selected="selected">&nbsp; &nbsp;Sécurité</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 374. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 375. Error Line 455, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="4">&nbsp; &nbsp;Désinfection en ligne</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 376. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 377. Error Line 455, Column 35: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="4">&nbsp; &nbsp;Désinfection en ligne</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 378. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 379. Error Line 456, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="8">&nbsp; &nbsp;Optimisation</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 380. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 381. Error Line 456, Column 35: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="8">&nbsp; &nbsp;Optimisation</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 382. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 383. Error Line 457, Column 29: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="13">&nbsp; &nbsp;Question diverses sur Windows</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 384. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 385. Error Line 457, Column 36: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="13">&nbsp; &nbsp;Question diverses sur Windows</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 386. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 387. Error Line 459, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="5">&nbsp; &nbsp;Les distributions</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 388. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 389. Error Line 459, Column 35: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="5">&nbsp; &nbsp;Les distributions</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 390. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 391. Error Line 460, Column 28: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="6">&nbsp; &nbsp;Logiciels sous linux</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 392. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 393. Error Line 460, Column 35: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="6">&nbsp; &nbsp;Logiciels sous linux</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 394. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 395. Error Line 461, Column 29: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="14">&nbsp; &nbsp;Questions diverses sur Linux</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 396. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 397. Error Line 461, Column 36: reference to entity "nbsp" for which no system identifier could be generated.

      					<option value="14">&nbsp; &nbsp;Questions diverses sur Linux</option>

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 398. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 399. Error Line 463, Column 16: reference to entity "nbsp" for which no system identifier could be generated.

      		</select>&nbsp;<input class="btnlite" type="submit" value="Aller" /></td>

      ✉

      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.
 400. Info Line 136, Column 187: entity was defined here.

      … height="13" alt="*" /> Connexion</a>&nbsp; &nbsp;<a href="./ucp.php?mode=reg

 401. Warning Line 463, Column 68: NET-enabling start-tag requires SHORTTAG YES.

      …nput class="btnlite" type="submit" value="Aller" /></td>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 402. Error Line 486, Column 84: reference to entity "amp" for which no system identifier could be generated.

      …ttp://www.phpbb.com/">phpBB</a>  &amp; 2000, 2002, 2005, 2007 phpBB Group

      ✉

      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.
 403. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 404. Warning Line 487, Column 5: NET-enabling start-tag requires SHORTTAG YES.

      	<br />Traduction par: <a href="http://forums.phpbb-fr.com">phpBB-fr.com</a> &am

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 405. Error Line 487, Column 81: reference to entity "amp" for which no system identifier could be generated.

      …s.phpbb-fr.com">phpBB-fr.com</a> &amp; <a href="http://www.phpbb.biz">phpBB.b

      ✉

      This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
 406. Info Line 136, Column 33: entity was defined here.

      				<a href="./ucp.php?mode=login&amp;sid=30e97dce70daef278515d130d3e41232"><img

 407. Warning Line 487, Column 131: NET-enabling start-tag requires SHORTTAG YES.

      …tp://www.phpbb.biz">phpBB.biz</a><br /><bdo dir="ltr">[ Time : 0.056s | 11 Qu

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 408. Warning Line 493, Column 66: NET-enabling start-tag requires SHORTTAG YES.

      …lid XHTML 1.0 Transitional" height="31" width="88" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
 409. Warning Line 497, Column 48: NET-enabling start-tag requires SHORTTAG YES.

              alt="Valid CSS2" height="31" width="88" /></a>

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

↑ Top

    * Home |
    * About... |
    * News |
    * Docs |
    * Help & FAQ |
    * Feedback |

QA

Support this tool, become a
W3C Supporter

This is the W3C Markup Validator, v0.8.2.

Copyright © 1994-2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.