Validation Output: 34 Errors

1. Line 16, Column 89: end tag for element "TITLE" which is not open

   …stattung.com/lkw_tische.ico"></title>

   ✉

   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.

2. Line 103, Column 27: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?

   <table width="850" height="1011" align="center" cellpadding="0" cellspacing="0" 

   ✉

   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. Line 103, Column 93: Attribute "BORDERCOLOR" is not a valid attribute

   …ing="0" cellspacing="0" bordercolor="#FFFFFF">

   ✉

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

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

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

4. Line 109, Column 51: Attribute "BACKGROUND" is not a valid attribute. Did you mean "background"?

   …d width="475" height="5" background="images/orange.gif" bgcolor="#FFFFFF"><sp

   ✉

   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. Line 117, Column 85: Attribute "BACKGROUND" is not a valid attribute. Did you mean "background"?

   …ding="0" cellspacing="0" background="images/titlebarGRADE.jpg">

   ✉

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

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

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

6. Line 126, Column 97: NET-enabling start-tag requires SHORTTAG YES

   …">lkw-zubehör.net</font> </span><br />

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

7. Line 127, Column 19: 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 HTML 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 HTML 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.

8. Line 141, Column 122: NET-enabling start-tag requires SHORTTAG YES

   …dth="150" height="125" align="left" /><img src="images/HeaderB.gif" width="69

   ✉

   The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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. Line 141, Column 122: required attribute "ALT" not specified

   …dth="150" height="125" align="left" /><img src="images/HeaderB.gif" width="69

   ✉

   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>.

10. Line 141, Column 179: NET-enabling start-tag requires SHORTTAG YES

    …aderB.gif" width="693" height="125" /></div></td>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

11. Line 141, Column 179: required attribute "ALT" not specified

    …aderB.gif" width="693" height="125" /></div></td>

    ✉

    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>.

12. Line 172, Column 149: cannot generate system identifier for general entity "aid"

    …pace-Mahagoni.html?shop_param=cid=2&aid=1101&">

    ✉

    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.

13. Line 172, Column 149: general entity "aid" not defined and no default entity

    …pace-Mahagoni.html?shop_param=cid=2&aid=1101&">

    ✉

    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.

14. Line 172, Column 152: reference to entity "aid" for which no system identifier could be generated

    …e-Mahagoni.html?shop_param=cid=2&aid=1101&">

    ✉

    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.

15. Line 172, Column 147: entity was defined here

    …-Space-Mahagoni.html?shop_param=cid=2&aid=1101&">

16. Line 173, Column 135: NET-enabling start-tag requires SHORTTAG YES

    …s MP II Mittel Tsch Ablage"></a><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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. Line 195, Column 21: 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 HTML 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 HTML 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. Line 226, Column 21: 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 HTML 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 HTML 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. Line 242, Column 65: cannot generate system identifier for general entity "site"

    …masterplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_bla

    ✉

    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.

20. Line 242, Column 65: general entity "site" not defined and no default entity

    …masterplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_bla

    ✉

    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.

21. Line 242, Column 69: reference to entity "site" for which no system identifier could be generated

    …erplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

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

22. Line 242, Column 63: entity was defined here

    …ebmasterplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_b

23. Line 242, Column 75: cannot generate system identifier for general entity "type"

    …rplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

    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.

24. Line 242, Column 75: general entity "type" not defined and no default entity

    …rplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

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

25. Line 242, Column 79: reference to entity "type" for which no system identifier could be generated

    …m/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

    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.

26. Line 242, Column 73: entity was defined here

    …asterplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

27. Line 242, Column 85: cannot generate system identifier for general entity "bnb"

    ….asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

    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.

28. Line 242, Column 85: general entity "bnb" not defined and no default entity

    ….asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

    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.

29. Line 242, Column 88: reference to entity "bnb" for which no system identifier could be generated

    …p?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

    ✉

    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.

30. Line 242, Column 83: entity was defined here

    …ck.asp?ref=153214&site=2906&type=b445&bnb=445" target="_blank">

31. Line 243, Column 68: reference to entity "site" for which no system identifier could be generated

    …terplan.com/view.asp?ref=153214&site=2906&b=445" border="0" alt="Vodafone Zuh

    ✉

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

    …ebmasterplan.com/click.asp?ref=153214&site=2906&type=b445&bnb=445" target="_b

33. Line 243, Column 74: cannot generate system identifier for general entity "b"

    …n.com/view.asp?ref=153214&site=2906&b=445" border="0" alt="Vodafone Zuhause W

    ✉

    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. Line 243, Column 74: general entity "b" not defined and no default entity

    …n.com/view.asp?ref=153214&site=2906&b=445" border="0" alt="Vodafone Zuhause 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.

35. Line 243, Column 75: reference to entity "b" for which no system identifier could be generated

    ….com/view.asp?ref=153214&site=2906&b=445" border="0" alt="Vodafone Zuhause We

    ✉

    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.

36. Line 243, Column 72: entity was defined here

    …lan.com/view.asp?ref=153214&site=2906&b=445" border="0" alt="Vodafone Zuhause

37. Line 243, Column 147: NET-enabling start-tag requires SHORTTAG YES

    …se WebData" width="120" height="60" /></a><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

38. Line 243, Column 157: NET-enabling start-tag requires SHORTTAG YES

    …" width="120" height="60" /></a><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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. Line 246, Column 109: cannot generate system identifier for general entity "layout"

    …edtracker.de/count.php?a=1240901694&layout=./buttons/b1.jpg"></script>

    ✉

    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.

40. Line 246, Column 109: general entity "layout" not defined and no default entity

    …edtracker.de/count.php?a=1240901694&layout=./buttons/b1.jpg"></script>

    ✉

    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. Line 246, Column 115: reference to entity "layout" for which no system identifier could be generated

    …ker.de/count.php?a=1240901694&layout=./buttons/b1.jpg"></script>

    ✉

    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.

42. Line 246, Column 107: entity was defined here

    …peedtracker.de/count.php?a=1240901694&layout=./buttons/b1.jpg"></script>

43. Line 247, Column 10: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    <noscript><script type="text/javascript"><!--

    ✉

    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>").

44. Line 267, Column 52: Attribute "BORDERCOLOR" is not a valid attribute

    …         <td width="74" bordercolor="#FFFFFF"><div align="center" class="styl

    ✉

    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.

45. Line 299, Column 47: NET-enabling start-tag requires SHORTTAG YES

                        <span class="style69"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

46. Line 303, Column 79: NET-enabling start-tag requires SHORTTAG YES

    …nt> </span><span class="style73"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

47. Line 304, Column 88: end tag for "FONT" omitted, but its declaration does not permit this

    …ont face="Trebuchet MS" size="2"></p>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

48. Line 304, Column 49: start tag was here

                              &nbsp;</span></span><b><font face="Trebuchet MS" size="2"></p>

49. Line 304, Column 88: end tag for "B" omitted, but its declaration does not permit this

    …ont face="Trebuchet MS" size="2"></p>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

50. Line 304, Column 46: start tag was here

    …                 &nbsp;</span></span><b><font face="Trebuchet MS" size="2"><…

51. Line 313, Column 56: end tag for element "FONT" which is not open

                        weiteres Zubehör.</font></h1></font></b></p>

    ✉

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

52. Line 313, Column 60: end tag for element "B" which is not open

                        weiteres Zubehör.</font></h1></font></b></p>

    ✉

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

53. Line 313, Column 64: end tag for element "P" which is not open

    …         weiteres Zubehör.</font></h1></font></b></p>

    ✉

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

54. Line 318, Column 203: cannot generate system identifier for general entity "shop_param"

    …yjAYKfKCn7sfKiHOP90jIoSwDQuYYV5b7JB&shop_param=cid=&">

    ✉

    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.

55. Line 318, Column 203: general entity "shop_param" not defined and no default entity

    …yjAYKfKCn7sfKiHOP90jIoSwDQuYYV5b7JB&shop_param=cid=&">

    ✉

    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.

56. Line 318, Column 213: reference to entity "shop_param" for which no system identifier could be generated

    …sfKiHOP90jIoSwDQuYYV5b7JB&shop_param=cid=&">

    ✉

    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. Line 318, Column 201: entity was defined here

    …I5yjAYKfKCn7sfKiHOP90jIoSwDQuYYV5b7JB&shop_param=cid=&">

58. Line 319, Column 133: NET-enabling start-tag requires SHORTTAG YES

    … frontscheiben gardinen ab 30 euro" /></a></div><div align="center">&nbsp;</d

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

59. Line 321, Column 96: NET-enabling start-tag requires SHORTTAG YES

    …107" alt="Tisch ablage LKW MB2 MB3" /></a></div><div align="center">

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

60. Line 331, Column 84: NET-enabling start-tag requires SHORTTAG YES

    …/u></span><span class="style73"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

61. Line 340, Column 118: NET-enabling start-tag requires SHORTTAG YES

    …"style42"><span class="style73"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

62. Line 341, Column 59: 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 HTML 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 HTML 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.

63. Line 345, Column 126: NET-enabling start-tag requires SHORTTAG YES

    …nt></span><span class="style58"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

64. Line 356, Column 90: NET-enabling start-tag requires SHORTTAG YES

    …tirutsch und feuerhemend.</font><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

65. Line 357, Column 25: 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 HTML 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 HTML 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.

66. Line 358, Column 47: NET-enabling start-tag requires SHORTTAG YES

                        <span class="style68"><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

67. Line 374, Column 34: NET-enabling start-tag requires SHORTTAG YES

                        </script><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

68. Line 378, Column 223: NET-enabling start-tag requires SHORTTAG YES

    …- Webmaster Portal" style="border:0"/></a></span></p>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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. Line 393, Column 203: reference to entity "shop_param" for which no system identifier could be generated

    …sfKiHOP90jIoSwDQuYYV5b7JB&shop_param=cid=&">

    ✉

    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.

70. Line 318, Column 201: entity was defined here

    …I5yjAYKfKCn7sfKiHOP90jIoSwDQuYYV5b7JB&shop_param=cid=&">

71. Line 394, Column 120: NET-enabling start-tag requires SHORTTAG YES

    …t="vorhang gardine lkw mp3"></a><br />

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

72. Line 450, Column 21: 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 HTML 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 HTML 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.

73. Line 456, Column 131: NET-enabling start-tag requires SHORTTAG YES

    …cb.net.gif' width="128" height="128"/></a></td>

    ✉

    The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 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 HTML 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.

74. Line 456, Column 131: required attribute "ALT" not specified

    …cb.net.gif' width="128" height="128"/></a></td>

    ✉

    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>.

75. Line 460, Column 21: 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 HTML 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 HTML 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.

76. Line 464, Column 145: required attribute "TYPE" not specified

    …?c=86fc735c73cd1a18f0d325be22f44f38"></script>

    ✉

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

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

77. Line 525, Column 160: cannot generate system identifier for general entity "v"

    …12;13;14;17;19;20;26;27;33;34;38;41&v=0.9"></script></td>

    ✉

    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.

78. Line 525, Column 160: general entity "v" not defined and no default entity

    …12;13;14;17;19;20;26;27;33;34;38;41&v=0.9"></script></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. Line 525, Column 161: reference to entity "v" for which no system identifier could be generated

    …2;13;14;17;19;20;26;27;33;34;38;41&v=0.9"></script></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.

80. Line 525, Column 158: entity was defined here

    …0;12;13;14;17;19;20;26;27;33;34;38;41&v=0.9"></script></td>

↑ Top