Light Flyff Teamsuche

Validation Output: 55 Errors

1. Error Line 10, Column 41: Attribute "language" exists, but can not be used for this element.

<script type="text/javascript" language="javascript">

✉

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

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
2. Error Line 105, Column 12: Attribute "name" exists, but can not be used for this element.

<form name="ajax_login" onsubmit="return false;">

✉

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

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

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

<form name="ajax_login" onsubmit="return false;">

✉

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

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
4. Error Line 106, Column 26: Attribute "align" exists, but can not be used for this element.

<div id="response" align="center" style="font-size:12px;color:#FF0000;font-weigh

✉

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

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
5. Error Line 107, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

…="dafb589f159e814f2991afc331329983" />

✉

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

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
6. Error Line 110, Column 74: document type does not allow element "button" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

…bmit" name="submit" onclick="ajaxlogin();">

✉

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

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
7. Error Line 152, Column 51: Attribute "border" exists, but can not be used for this element.

<td><img src="./images/status_online.jpg" border="0" alt="Online" title="Online" /></td>

✉

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

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
8. Error Line 221, Column 31: end tag for "br" omitted, but OMITTAG NO was specified

<…

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
9. Info Line 221, Column 26: start tag was here

<br>

10. Error Line 223, Column 36: Attribute "align" exists, but can not be used for this element.

<p align="center"> <a href="http://www.lightflyff.de/i

✉

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

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
11. Error Line 223, Column 177: end tag for "img" omitted, but OMITTAG NO was specified

…yff - The beginning" border="0" ></a> </p>

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
12. Info Line 223, Column 98: start tag was here

…www.lightflyff.de/index.php?p=event"><img src="./images/hero.jpg" alt="Light

13. Error Line 226, Column 32: end tag for "br" omitted, but OMITTAG NO was specified

<…

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
14. Info Line 226, Column 27: start tag was here

<br>

15. Error Line 230, Column 21: Attribute "color" exists, but can not be used for this element.

<td><font color="#000000"><u>20.01.2010</u></font></td>

✉

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

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

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

<td><font color="#000000"><u>20.01.2010</u></font></td>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
* incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
* by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
17. Error Line 230, Column 33: element "u" undefined. Did you mean "input" or "ul"?

<td><font color="#000000"><u>20.01.2010</u></font></td>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
* incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
* by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
18. Error Line 231, Column 85: end tag for "img" omitted, but OMITTAG NO was specified

…rder="0" width="270" height="1"></td>

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
19. Info Line 231, Column 8: start tag was here

<td><img src="./images/Spacer.png" alt="" border="0" width="270" height="1">

20. Error Line 232, Column 21: document type does not allow element "p" here; missing one of "th", "td" start-tag

<p align="right"><td>Von: <b><font color="#FF0000">Synaptic</font></b> </td>

✉

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

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
21. Error Line 232, Column 25: document type does not allow element "td" here

<p align="right"><td>Von: <b><font color="#FF0000">Synaptic</font></b> </td>

✉

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).
22. Error Line 232, Column 55: element "font" undefined. Did you mean "font" or "basefont"?

<p align="right"><td>Von: <b><font color="#FF0000">Synaptic</font></b> </td> </p>

✉

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
* incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
* by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
23. Error Line 236, Column 9: end tag for "br" omitted, but OMITTAG NO was specified

<…

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
24. Info Line 236, Column 4: start tag was here

<br>

25. Error Line 237, Column 20: end tag for "br" omitted, but OMITTAG NO was specified

Hallo ihr, <br><br>

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
26. Info Line 237, Column 15: start tag was here

Hallo ihr, <br><br>

27. Error Line 237, Column 24: end tag for "br" omitted, but OMITTAG NO was specified

Hallo ihr, <br><…

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
28. Info Line 237, Column 19: start tag was here

Hallo ihr, <br><br>

29. Error Line 243, Column 9: end tag for "br" omitted, but OMITTAG NO was specified

<…

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
30. Info Line 243, Column 4: start tag was here

<br>

31. Error Line 244, Column 9: end tag for "br" omitted, but OMITTAG NO was specified

<…

✉

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
32. Info Line 244, Column 4: start tag was here

<br>

33. Warning Line 355, Column 110: cannot generate system identifier for general entity "id"

…//topofgames.com/index.php?do=votes&id=7503"><img src="./images/vote/1.jpg" b

✉

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.
34. Error Line 355, Column 110: general entity "id" not defined and no default entity

…//topofgames.com/index.php?do=votes&id=7503"><img src="./images/vote/1.jpg" 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.
35. Warning Line 355, Column 112: reference not terminated by REFC delimiter

…topofgames.com/index.php?do=votes&id=7503"><img src="./images/vote/1.jpg" bor

✉

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
36. Warning Line 355, Column 112: reference to external entity in attribute value

…topofgames.com/index.php?do=votes&id=7503"><img src="./images/vote/1.jpg" bor

✉

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.
37. Error Line 355, Column 112: reference to entity "id" for which no system identifier could be generated

…topofgames.com/index.php?do=votes&id=7503"><img src="./images/vote/1.jpg" bor

✉

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

…p://topofgames.com/index.php?do=votes&id=7503"><img src="./images/vote/1.jpg"

39. Error Line 355, Column 162: required attribute "alt" not specified

…c="./images/vote/1.jpg" border="0" /></a><br /><a href=""><img src="./images/

✉

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

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
40. Error Line 355, Column 227: required attribute "alt" not specified

…c="./images/vote/2.jpg" border="0" /></a></div></div>

✉

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

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
41. Error Line 223, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 223 and a

…> <a href="http://www.lightflyff.de/index.php?p=event"><img src="./images/her…

✉
42. Error Line 223, Column > 80: XML Parsing Error: Opening and ending tag mismatch: a line 223 and p

…> <a href="http://www.lightflyff.de/index.php?p=event"><img src="./images/her…

✉
43. Error Line 224, Column 37: XML Parsing Error: Opening and ending tag mismatch: p line 223 and fieldset

</fieldset>

✉
44. Error Line 231, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 231 and td

…"" border="0" width="270" height="1"></td>…

✉
45. Error Line 234, Column 9: XML Parsing Error: Opening and ending tag mismatch: td line 231 and tr

</tr>

✉
46. Error Line 235, Column 12: XML Parsing Error: Opening and ending tag mismatch: tr line 229 and table

</table>

✉
47. Error Line 249, Column 17: XML Parsing Error: Opening and ending tag mismatch: br line 244 and fieldset

</fieldset>

✉
48. Error Line 258, Column 22: XML Parsing Error: Opening and ending tag mismatch: br line 243 and div

</div>

✉
49. Error Line 260, Column 14: XML Parsing Error: Opening and ending tag mismatch: br line 237 and div

</div>

✉
50. Error Line 271, Column 13: XML Parsing Error: Opening and ending tag mismatch: br line 237 and div

</div>

✉
51. Error Line 272, Column 12: XML Parsing Error: Opening and ending tag mismatch: br line 236 and div

</div>

✉
52. Error Line 273, Column 11: XML Parsing Error: Opening and ending tag mismatch: table line 228 and div

</div>

✉
53. Error Line 276, Column 10: XML Parsing Error: Opening and ending tag mismatch: fieldset line 227 and div

</div>

✉
54. Error Line 355, Column > 80: XML Parsing Error: EntityRef: expecting ';'

… align="center"><a href="http://topofgames.com/index.php?do=votes&id=7503"><i…

✉
55. Error Line 375, Column 9: XML Parsing Error: Opening and ending tag mismatch: br line 226 and div

</div>

✉
56. Error Line 376, Column 8: XML Parsing Error: Opening and ending tag mismatch: br line 221 and div

</div>

✉
57. Error Line 387, Column 7: XML Parsing Error: Opening and ending tag mismatch: fieldset line 220 and div

</div>

✉
58. Error Line 391, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 218 and body

</body>

✉
59. Error Line 392, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 217 and html

</html>

✉
60. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 210

</html>

✉
61. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 209

</html>

✉
62. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 208

</html>

✉
63. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 92

</html>

✉
64. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 66

</html>

✉
65. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 65

</html>

✉
66. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag div line 64

</html>

✉
67. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag body line 61

</html>

✉
68. Error Line 392, Column 7: XML Parsing Error: Premature end of data in tag html line 2

</html>