Errors found while checking this document as HTML 4.01 Transitional!
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Unable to Determine Parse Mode!The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
-
the MIME Media Type (
text/html) can be used for XML or SGML document types - No known Document Type could be detected
- No XML declaration (e.g
<?xml version="1.0"?>) could be found at the beginning of the document. - No XML namespace (e.g
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
-
the MIME Media Type (
No DOCTYPEfound! Checking with default HTML 4.01 Transitional Document Type.No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
Validation Output: 444 Errors
-
Line 1, Column 1:
no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<HTML>The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
-
Line 16, Column 79:
NET-enabling start-tag requires SHORTTAG YES
…TdlIxUd1GPF7svV1vnqiRyTT2+wwVqCchc=" />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.
-
Line 17, Column 12:
Attribute "TYPE" is not a valid attribute. Did you mean "type"?
<meta type="" content="yhNmQc4oSLabUDyjq5zStNA2RkI"/>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.
-
Line 17, Column 52:
NET-enabling start-tag requires SHORTTAG YES
<meta type="" content="yhNmQc4oSLabUDyjq5zStNA2RkI"/>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.
-
Line 17, Column 52:
document type does not allow element "META" here
<meta type="" content="yhNmQc4oSLabUDyjq5zStNA2RkI"/>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).
-
Line 19, Column 93:
document type does not allow element "LINK" here
…nen.de/icon.ico" type="image/x-icon">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).
-
Line 20, Column 105:
document type does not allow element "LINK" here
…ss" rel="stylesheet" type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 21, Column 39:
document type does not allow element "META" here
<meta http-equiv="expires" content="0">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).
-
Line 22, Column 52:
document type does not allow element "META" here
<meta http-equiv="cache-control" content="no-cache">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).
-
Line 29, Column 23:
document type does not allow element "STYLE" here
<style type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 40, Column 7:
end tag for element "HEAD" which is not open
</head>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.
-
Line 43, Column 30:
document type does not allow element "BODY" here
<body style="margin-top:0px;">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).
-
Line 147, Column 22:
Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
<TR height="25">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.
-
Line 149, Column 176:
document type does not allow element "FORM" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME" start-tag
…l(document.getElementById('words'))">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>").
-
Line 151, Column 58:
document type does not allow element "TD" here
<TD width="550" style="white-space: nowrap"><span class="search">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).
-
Line 174, Column 22:
end tag for "SPAN" omitted, but its declaration does not permit this
</div></TD>- 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. -
Line 151, Column 58:
start tag was here
<TD width="550" style="white-space: nowrap"><span class="search"> -
Line 174, Column 22:
end tag for "FORM" omitted, but its declaration does not permit this
</div></TD>- 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. -
Line 149, Column 12:
start tag was here
<form action="http://www.teddys-auktionen.de/Search" method="get" na -
Line 174, Column 22:
end tag for "SPAN" omitted, but its declaration does not permit this
</div></TD>- 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. -
Line 148, Column 65:
start tag was here
…TD class="search" noWrap valign="middle" width="10"><span class="Stil2"> -
Line 174, Column 22:
end tag for "TABLE" omitted, but its declaration does not permit this
</div></TD>- 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. -
Line 145, Column 5:
start tag was here
<TABLE cellspacing="0" cellpadding="0" width="100%" border="0"> -
Line 174, Column 22:
end tag for "TABLE" omitted, but its declaration does not permit this
</div></TD>- 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. -
Line 138:
start tag was here
><TABLE cellSpacing=0 cellPadding=0 align = "center" width="100%" border=0> -
Line 177, Column 21:
end tag for element "FORM" which is not open
</FORM></TD>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.
-
Line 177, Column 26:
end tag for element "TD" which is not open
</FORM></TD>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.
-
Line 181, Column 9:
end tag for element "TR" which is not open
</TR>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.
-
Line 182, Column 10:
end tag for element "TBODY" which is not open
</TBODY>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.
-
Line 183, Column 8:
end tag for element "TABLE" which is not open
</TABLE>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.
-
Line 185, Column 77:
document type does not allow element "FORM" here
…tionen.de/redirect.php" method = "post">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).
-
Line 186, Column 4:
document type does not allow element "TR" here
<tr><td class = "theader2" height = "20" align="right">Hallo Gast!<a href="http: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).
-
Line 189, Column 4:
document type does not allow element "TR" here
<tr><td width="100%" align="left">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).
-
Line 201, Column 8:
ID "CURRENT" already defined
<li id=current><a href="http://www.teddys-auktionen.de/Suchanzeigen.html"><span>An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
-
Line 195, Column 7:
ID "CURRENT" first defined here
<li id=current><a href="http://www.teddys-auktionen.de/"><span>Start</span></a>< -
Line 211, Column 7:
end tag for "TABLE" omitted, but its declaration does not permit this
</form>- 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. -
Line 191:
start tag was here
i<table style="background: #E7E5E2" border="0" cellpadding="0" cellspacing="0" wi -
Line 212, Column 8:
end tag for "TABLE" which is not finished
</table>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
-
Line 213, Column 83:
required attribute "ALT" not specified
…php" width="1" height="1" border="0">The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 266, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 269, Column 37:
Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
<table width="160" height="22"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.
-
Line 289, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 297, Column 64:
required attribute "ALT" not specified
…ddys-auktionen.de//images/star6.gif"></TD><TD BGCOLOR="GAINSBORO"><span classThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 303, Column 64:
required attribute "ALT" not specified
…ddys-auktionen.de//images/star6.gif"></TD><TD><span class=text_normal><A HREFThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 309, Column 64:
required attribute "ALT" not specified
…ddys-auktionen.de//images/star6.gif"></TD><TD BGCOLOR="GAINSBORO"><span classThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 311, Column 64:
required attribute "ALT" not specified
…ddys-auktionen.de//images/star6.gif"></TD><TD><span class=text_normal><A HREFThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 325, Column 66:
required attribute "ALT" not specified
…ys-auktionen.de//images/checked.gif"></TD><TD BGCOLOR="GAINSBORO"><span classThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 327, Column 64:
required attribute "ALT" not specified
…ddys-auktionen.de//images/star6.gif"></TD><TD><span class=text_normal><A HREFThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 367, Column 75:
required attribute "ALT" not specified
…nen.de//images/smilie_oster_096.gif"></TD><TD><span class=text_normal><A HREFThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 391, Column 64:
required attribute "ALT" not specified
…ddys-auktionen.de//images/star6.gif"></TD><TD><span class=text_normal><A HREFThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 406, Column 87:
document type does not allow element "TABLE" here
…" cellspacing="0" class="table_norm">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).
-
Line 408, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 430, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 432, Column 400:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></div><br><font style="color:#FF0000;fonThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 432, Column 565:
required attribute "ALT" not specified
…nen.de/images/buynow.gif" border="0"></td></tr><tr><td style="border-left:1pxThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 432, Column 922:
required attribute "ALT" not specified
…ded/thumbs/th_902259.jpg" border="0"></a></td></tr></table></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 435, Column 27:
invalid comment declaration: found name character outside comment but inside comment declaration
<!--Ende Sonderangebote---> -
Line 435, Column 1:
comment declaration started here
<!--Ende Sonderangebote---> -
Line 435, Column 28:
character data is not allowed here
<!--Ende Sonderangebote--->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.
-
Line 437, Column 3:
document type does not allow element "P" here
<p>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).
-
Line 438, Column 87:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…" cellspacing="0" class="table_norm">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>").
-
Line 440, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 463, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 465, Column 502:
required attribute "ALT" not specified
…nen.de/images/buynow.gif" border="0"></td></tr><tr><td style="border-left:1pxThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 465, Column 871:
required attribute "ALT" not specified
…ded/thumbs/th_771781.jpg" border="0"></a></td></tr></table></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 468, Column 7:
document type does not allow element "P" here
<p>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).
-
Line 469, Column 42:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<table cellpadding="0" cellspacing="1"><tr><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>").
-
Line 471, Column 38:
Attribute "COLSPAN" is not a valid attribute. Did you mean "colspan"?
<TR height=21 colspan ="2">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.
-
Line 484, Column 18:
character ";" not allowed in attribute specification list
" target="_blank";>Plueschmamas<br>Handarbeitsforum -
Line 486, Column 18:
character ";" not allowed in attribute specification list
" target="_blank";> -
Line 486, Column 18:
document type does not allow element "A" here
" target="_blank";>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).
-
Line 487, Column 54:
required attribute "ALT" not specified
…banner.plueschpapa.de/button046.GIF"></a><br><br><!--<a href="http://www.teddThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 489, Column 113:
cannot generate system identifier for general entity "user_id"
…ID=c8c828d1414673a12d57a54d4010861e&user_id=5287c2f8fa6f8adec1d123126ad47883An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ 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.
-
Line 489, Column 113:
general entity "user_id" not defined and no default entity
…ID=c8c828d1414673a12d57a54d4010861e&user_id=5287c2f8fa6f8adec1d123126ad47883This 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.
-
Line 489, Column 120:
reference to entity "user_id" for which no system identifier could be generated
…28d1414673a12d57a54d4010861e&user_id=5287c2f8fa6f8adec1d123126ad47883This 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.
-
Line 489, Column 111:
entity was defined here
…N_ID=c8c828d1414673a12d57a54d4010861e&user_id=5287c2f8fa6f8adec1d123126ad47… -
Line 490, Column 17:
character ";" not allowed in attribute specification list
"target="_blank";> -
Line 490, Column 17:
document type does not allow element "A" here
"target="_blank";>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).
-
Line 491, Column 48:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/bas.GIF"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 492, Column 74:
character ";" not allowed in attribute specification list
…de/shops/seven-fifty"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 492, Column 74:
document type does not allow element "A" here
…de/shops/seven-fifty"target="_blank";><img src="http://banner.plueschpapa.de/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).
-
Line 492, Column 126:
required attribute "ALT" not specified
…://banner.plueschpapa.de/fifty1.GIF"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 493, Column 104:
character ";" not allowed in attribute specification list
…29724a43641e161.html"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 493, Column 104:
document type does not allow element "A" here
…29724a43641e161.html"target="_blank";><img src="http://banner.plueschpapa.de/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).
-
Line 493, Column 156:
required attribute "ALT" not specified
…://banner.plueschpapa.de/stone1.JPG"></a><br><br><a href="http://www.teddys-aThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 494, Column 17:
character ";" not allowed in attribute specification list
"target="_blank";> -
Line 494, Column 17:
document type does not allow element "A" here
"target="_blank";>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).
-
Line 495, Column 51:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/lothar.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 496, Column 105:
character ";" not allowed in attribute specification list
…8e539be7277ab2.html" target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 496, Column 105:
document type does not allow element "A" here
…8e539be7277ab2.html" target="_blank";><img src="http://banner.plueschpapa.de/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).
-
Line 496, Column 157:
required attribute "ALT" not specified
…://banner.plueschpapa.de/fossi1.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 497, Column 105:
character ";" not allowed in attribute specification list
…640b533450cc8c.html" target="_blank";> -
Line 497, Column 105:
document type does not allow element "A" here
…640b533450cc8c.html" target="_blank";>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).
-
Line 498, Column 52:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/mijuok1.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 499, Column 105:
character ";" not allowed in attribute specification list
…e2a77f605d1671.html" target="_blank";> -
Line 499, Column 105:
document type does not allow element "A" here
…e2a77f605d1671.html" target="_blank";>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).
-
Line 500, Column 56:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/bueropetra1.GIF"></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 502, Column 70:
character ";" not allowed in attribute specification list
…nen.de/shops/stoebki"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 502, Column 70:
document type does not allow element "A" here
…nen.de/shops/stoebki"target="_blank";><img src="http://banner.plueschpapa.de/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).
-
Line 504, Column 117:
reference to entity "user_id" for which no system identifier could be generated
…28d1414673a12d57a54d4010861e&user_id=5ea5e1862fcc45ad9f34d2ef8c6ad481"target=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.
-
Line 489, Column 111:
entity was defined here
…N_ID=c8c828d1414673a12d57a54d4010861e&user_id=5287c2f8fa6f8adec1d123126ad47… -
Line 504, Column 166:
character ";" not allowed in attribute specification list
…45ad9f34d2ef8c6ad481"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 504, Column 166:
document type does not allow element "A" here
…45ad9f34d2ef8c6ad481"target="_blank";><img src="http://banner.plueschpapa.de/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).
-
Line 504, Column 214:
required attribute "ALT" not specified
…http://banner.plueschpapa.de/bi.gif"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 506, Column 17:
character ";" not allowed in attribute specification list
"target="_blank";> -
Line 506, Column 17:
document type does not allow element "A" here
"target="_blank";>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).
-
Line 507, Column 50:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/moni1.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 509, Column 17:
character ";" not allowed in attribute specification list
"target="_blank";> -
Line 509, Column 17:
document type does not allow element "A" here
"target="_blank";>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).
-
Line 510, Column 54:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/weilheim1.JPG"></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 513, Column 17:
character ";" not allowed in attribute specification list
"target="_blank";> -
Line 513, Column 17:
document type does not allow element "A" here
"target="_blank";>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).
-
Line 514, Column 52:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/asearch.JPG"></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 515, Column 202:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…idth:150px;background-color:#FFFFFF">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>").
-
Line 516, Column 140:
document type does not allow element "A" here
…_blank" class="wettercomsmall231614">Wetter fuer Bedburg</a>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).
-
Line 518, Column 7:
end tag for "A" omitted, but its declaration does not permit this
</span></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. -
Line 483, Column 49:
start tag was here
… <p align="left"><span class="c6"><a href="http://www.plueschpapa.de/dim/d -
Line 537, Column 7:
"TBODY" not finished but containing element ended
</td> -
Line 537, Column 7:
end tag for "TABLE" omitted, but its declaration does not permit this
</td>- 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. -
Line 438, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 537, Column 7:
"TBODY" not finished but containing element ended
</td> -
Line 537, Column 7:
end tag for "TABLE" omitted, but its declaration does not permit this
</td>- 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. -
Line 406, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 537, Column 7:
"TBODY" not finished but containing element ended
</td> -
Line 537, Column 7:
end tag for "TABLE" omitted, but its declaration does not permit this
</td>- 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. -
Line 264, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 569, Column 216:
unclosed start-tag requires SHORTTAG YES
…teddys-auktionen.de/images/cool.png"</img><br>The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.
-
Line 569, Column 216:
required attribute "ALT" not specified
…teddys-auktionen.de/images/cool.png"</img><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 569, Column 221:
end tag for element "IMG" which is not open
…s-auktionen.de/images/cool.png"</img><br>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.
-
Line 572, Column 51:
required attribute "ALT" not specified
<img src="http://bilder.plueschpapa.de/859076.JPG"></img></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 572, Column 57:
end tag for element "IMG" which is not open
<img src="http://bilder.plueschpapa.de/859076.JPG"></img></a>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.
-
Line 573, Column 127:
required attribute "ALT" not specified
…://bilder.plueschpapa.de/901137.JPG"></img></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 573, Column 133:
end tag for element "IMG" which is not open
…der.plueschpapa.de/901137.JPG"></img></a>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.
-
Line 574, Column 148:
document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…hpapa.de/911344.JPG"></img></a>--><p><b><img src="http://bilder.plueschpapa.dThe 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>").
-
Line 574, Column 200:
required attribute "ALT" not specified
…tp://bilder.plueschpapa.de/hot1.gif"></img>jetzt geht es endlich wieder los mThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 574, Column 206:
end tag for element "IMG" which is not open
…ilder.plueschpapa.de/hot1.gif"></img>jetzt geht es endlich wieder los mit derThe 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.
-
Line 574, Column 312:
required attribute "ALT" not specified
…tp://bilder.plueschpapa.de/hot1.gif"></img><br>24 Tolle Angebote im 5 MinutenThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 574, Column 318:
end tag for element "IMG" which is not open
…ilder.plueschpapa.de/hot1.gif"></img><br>24 Tolle Angebote im 5 Minuten Takt<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.
-
Line 575, Column 69:
character ";" not allowed in attribute specification list
…uktionen.de/chatroom"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 575, Column 121:
required attribute "ALT" not specified
…://banner.plueschpapa.de/power1.jpg"></a></img><br><!--<br><b>das SchnäppchenThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 575, Column 131:
end tag for element "IMG" which is not open
…plueschpapa.de/power1.jpg"></a></img><br><!--<br><b>das Schnäppchen der WocheThe 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.
-
Line 575, Column 324:
end tag for "B" omitted, but its declaration does not permit this
…apa.de/409949.JPG"></a><br><b>--></p><center>- 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. -
Line 574, Column 148:
start tag was here
…hpapa.de/911344.JPG"></img></a>--><p><b><img src="http://bilder.plueschpapa.d -
Line 575, Column 332:
document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…09949.JPG"></a><br><b>--></p><center>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
-
Line 577, Column 86:
character ";" not allowed in attribute specification list
…/tintenshop-weilheim"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 577, Column 140:
required attribute "ALT" not specified
…/banner.plueschpapa.de/weilheim.JPG"></img></a><br><br><a href="http://www.plThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 577, Column 146:
end tag for element "IMG" which is not open
…r.plueschpapa.de/weilheim.JPG"></img></a><br><br><a href="http://www.plueschpThe 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.
-
Line 577, Column 286:
required attribute "ALT" not specified
…://banner.plueschpapa.de/werb1a.JPG"></a><p><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 579, Column 118:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…dding="0" cellspacing="0" summary="">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>").
-
Line 589, Column 146:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…CCC" cellpadding="2" cellspacing="2">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>").
-
Line 591, Column 550:
required attribute "ALT" not specified
…ded/thumbs/th_117371.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 591, Column 704:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 7.50 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 591, Column 675:
start tag was here
…ize:12;">Tierurne Urne P..</font><br><small>Versand: 7.50 EUR</td><tr><td val -
Line 592, Column 549:
required attribute "ALT" not specified
…ded/thumbs/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 592, Column 703:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 8.60 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 592, Column 674:
start tag was here
…ize:12;">Held Leder Satt..</font><br><small>Versand: 8.60 EUR</td><tr><td val -
Line 593, Column 513:
required attribute "ALT" not specified
…ded/thumbs/th_876548.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 593, Column 667:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.50 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 593, Column 638:
start tag was here
…ize:12;">Wunderschöner G..</font><br><small>Versand: 4.50 EUR</td><tr><td val -
Line 597, Column 552:
required attribute "ALT" not specified
…ded/thumbs/th_534284.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 597, Column 706:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 2.00 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 597, Column 677:
start tag was here
…ize:12;">Deutschlands gr..</font><br><small>Versand: 2.00 EUR</td><tr><td val -
Line 598, Column 523:
required attribute "ALT" not specified
…ded/thumbs/th_911917.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 598, Column 710:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></td><tr><td valign="bottom"><font styleThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 599, Column 537:
required attribute "ALT" not specified
…ded/thumbs/th_661317.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 599, Column 691:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 2.50 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 599, Column 662:
start tag was here
…ize:12;">Seidenmaltuch A..</font><br><small>Versand: 2.50 EUR</td><tr><td val -
Line 602, Column 535:
required attribute "ALT" not specified
…ded/thumbs/th_913286.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 602, Column 722:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></td><tr><td valign="bottom"><font styleThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 603, Column 518:
required attribute "ALT" not specified
…ded/thumbs/th_738341.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 603, Column 672:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.10 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 603, Column 643:
start tag was here
…ize:12;">Teddy steh Bild..</font><br><small>Versand: 4.10 EUR</td><tr><td val -
Line 604, Column 544:
required attribute "ALT" not specified
…ded/thumbs/th_907219.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 604, Column 698:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.90 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 604, Column 669:
start tag was here
…ize:12;">HDMI Kabel Full..</font><br><small>Versand: 4.90 EUR</td><tr><td val -
Line 607, Column 541:
required attribute "ALT" not specified
…ded/thumbs/th_861055.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 607, Column 728:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></td><tr><td valign="bottom"><font styleThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 608, Column 529:
required attribute "ALT" not specified
…ded/thumbs/th_748412.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 608, Column 683:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.10 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 608, Column 654:
start tag was here
…ize:12;">Behälter mit De..</font><br><small>Versand: 4.10 EUR</td><tr><td val -
Line 609, Column 517:
required attribute "ALT" not specified
…ded/thumbs/th_530738.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 609, Column 671:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 0.56 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 609, Column 642:
start tag was here
…ize:12;">AK Eaton Queens..</font><br><small>Versand: 0.56 EUR</td><tr><td val -
Line 614, Column 135:
required attribute "ALT" not specified
….de/images/bgauction.gif" border="0">=normale Auktion</small></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 615, Column 131:
required attribute "ALT" not specified
…n.de/images/bgsofort.gif" border="0">=Festpreis Auktion</small></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 616, Column 129:
required attribute "ALT" not specified
…nen.de/images/bgshop.gif" border="0">=Shop Auktion</small></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 621, Column 35:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<table width="100%" align="center">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
-
Line 624, Column 128:
required attribute "ALT" not specified
…s-auktionen.de/images/blitzkauf.png"></a><br><br>Versandkostenfreie FestpreisThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 624, Column 263:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></img>erkennbar<br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 624, Column 269:
end tag for element "IMG" which is not open
…en.de/images/versand_frei.png"></img>erkennbar<br><br>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.
-
Line 626, Column 75:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
… border="0" cellpadding=0 cellspacing="0">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>").
-
Line 633, Column 108:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…="138" cellpadding=5 cellspacing="0">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>").
-
Line 680, Column 25:
document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<div style="height:10px"> </div>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
-
Line 682, Column 108:
character ";" not allowed in attribute specification list
…7640b533450cc8c.html"target="_blank";><img src="http://banner.plueschpapa.de/ -
Line 682, Column 178:
document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…apa.de/miju.gif" alt="miju46"></a><p>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
-
Line 686, Column 30:
end tag for "B" omitted, but its declaration does not permit this
</td>- 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. -
Line 568, Column 42:
start tag was here
… <p><b>wir wünschen Allen einen gesunden und -
Line 689, Column 33:
an attribute value must be a literal unless it contains only name characters
<div style=float:left;text-align:center;margin-left:7px>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 692, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 715, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 717, Column 479:
required attribute "ALT" not specified
…en.de/images/shopart.gif" border="0"><br><img src ="http://www.teddys-auktionThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 717, Column 555:
required attribute "ALT" not specified
…nen.de/images/buynow.gif" border="0"></td></tr><tr><td style="border-left:1pxThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 717, Column 911:
required attribute "ALT" not specified
…ded/thumbs/th_892908.jpg" border="0"></a></td></tr></table></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 719, Column 22:
"TBODY" not finished but containing element ended
</table></div><div style=float:left;text-align:center;margin-left:7px> -
Line 719, Column 22:
end tag for "TABLE" omitted, but its declaration does not permit this
</table></div><div style=float:left;text-align:center;margin-left:7px>- 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. -
Line 690, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 719, Column 44:
an attribute value must be a literal unless it contains only name characters
</table></div><div style=float:left;text-align:center;margin-left:7px>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 722, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 745, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 747, Column 411:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></div><br><font style="color:#FF0000;fonThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 747, Column 576:
required attribute "ALT" not specified
…nen.de/images/buynow.gif" border="0"></td></tr><tr><td style="border-left:1pxThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 747, Column 940:
required attribute "ALT" not specified
…ded/thumbs/th_875091.jpg" border="0"></a></td></tr></table></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 749, Column 22:
"TBODY" not finished but containing element ended
</table></div><div style=float:left;text-align:center;margin-left:7px> -
Line 749, Column 22:
end tag for "TABLE" omitted, but its declaration does not permit this
</table></div><div style=float:left;text-align:center;margin-left:7px>- 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. -
Line 720, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 749, Column 44:
an attribute value must be a literal unless it contains only name characters
</table></div><div style=float:left;text-align:center;margin-left:7px>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 752, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 775, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 777, Column 497:
required attribute "ALT" not specified
…nen.de/images/buynow.gif" border="0"></td></tr><tr><td style="border-left:1pxThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 777, Column 859:
required attribute "ALT" not specified
…ded/thumbs/th_911144.jpg" border="0"></a></td></tr></table></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 779, Column 22:
"TBODY" not finished but containing element ended
</table></div><div style=float:left;text-align:center;margin-left:7px> -
Line 779, Column 22:
end tag for "TABLE" omitted, but its declaration does not permit this
</table></div><div style=float:left;text-align:center;margin-left:7px>- 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. -
Line 750, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 779, Column 44:
an attribute value must be a literal unless it contains only name characters
</table></div><div style=float:left;text-align:center;margin-left:7px>You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 782, Column 85:
document type does not allow element "TABLE" here
…="0" cellspacing="0" cellpadding="0">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).
-
Line 805, Column 48:
document type does not allow element "TABLE" here
<table class="c4" width="160" border="0">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).
-
Line 807, Column 440:
required attribute "ALT" not specified
…nen.de/images/buynow.gif" border="0"></td></tr><tr><td style="border-left:1pxThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 807, Column 775:
required attribute "ALT" not specified
…ded/thumbs/th_867067.jpg" border="0"></a></td></tr></table></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 809, Column 22:
"TBODY" not finished but containing element ended
</table></div> </td></tr> -
Line 809, Column 22:
end tag for "TABLE" omitted, but its declaration does not permit this
</table></div> </td></tr>- 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. -
Line 780, Column 6:
start tag was here
<table width="160" border="0" cellpadding="0" cellspacing="0" class="table -
Line 843, Column 414:
invalid comment declaration: found name start character outside comment but inside comment declaration
…rt-kaufen-Held-Leder-Satteltaschen--Topeka--fr-ClicksystemZZAuktionZZ911142ZZ -
Line 826, Column 16:
comment declaration started here
<!--<tr><td align="center"> -
Line 843, Column 415:
character data is not allowed here
…t-kaufen-Held-Leder-Satteltaschen--Topeka--fr-ClicksystemZZAuktionZZ911142ZZiYou 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.
-
Line 843, Column 547:
required attribute "ALT" not specified
…ded/thumbs/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 843, Column 547:
document type does not allow element "IMG" here; assuming missing "CAPTION" start-tag
…ded/thumbs/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><f -
Line 843, Column 551:
end tag for element "A" which is not open
…thumbs/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><fontThe 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.
-
Line 843, Column 556:
end tag for "CAPTION" omitted, but its declaration does not permit this
…s/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><font style- 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. -
Line 843, Column 464:
start tag was here
…cksystemZZAuktionZZ911142ZZidZZitem"><img src="http://www.teddys-auktionen.de -
Line 843, Column 556:
"TABLE" not finished but containing element ended
…s/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><font style -
Line 843, Column 556:
end tag for "TABLE" omitted, but its declaration does not permit this
…s/th_911142.jpg" border="0"></a></td><td valign="top" width="115"><font style- 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. -
Line 825, Column 11:
start tag was here
<p><table width="100%" cellpadding="0" cellspacing="1"> -
Line 843, Column 701:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 8.60 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 843, Column 672:
start tag was here
…ize:12;">Held Leder Satt..</font><br><small>Versand: 8.60 EUR</td><tr><td val -
Line 843, Column 980:
end tag for element "DIV" which is not open
…tem">mehr</a></td></tr></table></div></td>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.
-
Line 844, Column 511:
required attribute "ALT" not specified
…ded/thumbs/th_876548.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 844, Column 665:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.50 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 844, Column 636:
start tag was here
…ize:12;">Wunderschöner G..</font><br><small>Versand: 4.50 EUR</td><tr><td val -
Line 848, Column 550:
required attribute "ALT" not specified
…ded/thumbs/th_534284.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 848, Column 704:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 2.00 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 848, Column 675:
start tag was here
…ize:12;">Deutschlands gr..</font><br><small>Versand: 2.00 EUR</td><tr><td val -
Line 849, Column 521:
required attribute "ALT" not specified
…ded/thumbs/th_911917.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 849, Column 708:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></td><tr><td valign="bottom"><font styleThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 850, Column 535:
required attribute "ALT" not specified
…ded/thumbs/th_661317.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 850, Column 689:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 2.50 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 850, Column 660:
start tag was here
…ize:12;">Seidenmaltuch A..</font><br><small>Versand: 2.50 EUR</td><tr><td val -
Line 853, Column 533:
required attribute "ALT" not specified
…ded/thumbs/th_913286.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 853, Column 720:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></td><tr><td valign="bottom"><font styleThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 854, Column 516:
required attribute "ALT" not specified
…ded/thumbs/th_738341.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 854, Column 670:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.10 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 854, Column 641:
start tag was here
…ize:12;">Teddy steh Bild..</font><br><small>Versand: 4.10 EUR</td><tr><td val -
Line 855, Column 542:
required attribute "ALT" not specified
…ded/thumbs/th_907219.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 855, Column 696:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.90 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 855, Column 667:
start tag was here
…ize:12;">HDMI Kabel Full..</font><br><small>Versand: 4.90 EUR</td><tr><td val -
Line 858, Column 539:
required attribute "ALT" not specified
…ded/thumbs/th_861055.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 858, Column 726:
required attribute "ALT" not specified
…uktionen.de/images/versand_frei.png"></td><tr><td valign="bottom"><font styleThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 859, Column 527:
required attribute "ALT" not specified
…ded/thumbs/th_748412.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 859, Column 681:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.10 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 859, Column 652:
start tag was here
…ize:12;">Behälter mit De..</font><br><small>Versand: 4.10 EUR</td><tr><td val -
Line 860, Column 515:
required attribute "ALT" not specified
…ded/thumbs/th_530738.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 860, Column 669:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 0.56 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 860, Column 640:
start tag was here
…ize:12;">AK Eaton Queens..</font><br><small>Versand: 0.56 EUR</td><tr><td val -
Line 865, Column 135:
required attribute "ALT" not specified
….de/images/bgauction.gif" border="0">=normale Auktion</small></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 866, Column 131:
required attribute "ALT" not specified
…n.de/images/bgsofort.gif" border="0">=Festpreis Auktion</small></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 867, Column 129:
required attribute "ALT" not specified
…nen.de/images/bgshop.gif" border="0">=Shop Auktion</small></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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 873, Column 12:
end tag for element "TD" which is not open
</td>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.
-
Line 874, Column 15:
end tag for element "TR" which is not open
</tr>--> <!--Ende Top angebote-->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.
-
Line 875, Column 14:
document type does not allow element "TR" here
<tr>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).
-
Line 898, Column 23:
invalid comment declaration: found character "<" outside comment but inside comment declaration
<script type="text/javascript" src="welcome/ticker_last10.Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.
-
Line 879, Column 12:
comment declaration started here
<!--<table align="center" height="22" cellspacing="0" cellpadding="0 -
Line 898, Column 93:
end tag for element "SCRIPT" which is not open
…="welcome/ticker_last10.js"></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.
-
Line 904, Column 13:
end tag for element "TD" which is not open
</td>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.
-
Line 905, Column 15:
end tag for element "TR" which is not open
</tr>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.
-
Line 906, Column 14:
document type does not allow element "TR" here
<tr>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).
-
Line 926, Column 595:
end tag for "TABLE" omitted, but its declaration does not permit this
…ung,S" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 926, Column 70:
start tag was here
…nter"><div style="margin-left:100px"><table width ="217" align="left" height -
Line 926, Column 595:
end tag for "DIV" omitted, but its declaration does not permit this
…ung,S" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 926, Column 39:
start tag was here
<td align="center"><div style="margin-left:100px"><table wid -
Line 926, Column 609:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 927, Column 555:
end tag for "TABLE" omitted, but its declaration does not permit this
…ktion" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 927, Column 70:
start tag was here
…nter"><div style="margin-right:50px"><table width ="217" align="left" height -
Line 927, Column 555:
end tag for "DIV" omitted, but its declaration does not permit this
…ktion" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 927, Column 39:
start tag was here
<td align="center"><div style="margin-right:50px"><table wid -
Line 927, Column 563:
end tag for element "TABLE" which is not open
…order="0"></a></td></tr></tr></table></div></td>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.
-
Line 927, Column 569:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 927, Column 574:
end tag for element "TD" which is not open
…/a></td></tr></tr></table></div></td>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.
-
Line 928, Column 23:
end tag for element "TR" which is not open
</tr>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.
-
Line 929, Column 22:
document type does not allow element "TR" here
<tr>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).
-
Line 930, Column 547:
end tag for "TABLE" omitted, but its declaration does not permit this
…ikate" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 930, Column 61:
start tag was here
…nter"><div style="margin-left:100px"><table width ="217" align="left" height -
Line 930, Column 547:
end tag for "DIV" omitted, but its declaration does not permit this
…ikate" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 930, Column 30:
start tag was here
<td align="center"><div style="margin-left:100px"><table width ="217" -
Line 930, Column 555:
end tag for element "TABLE" which is not open
…order="0"></a></td></tr></tr></table></div></td>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.
-
Line 930, Column 561:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 930, Column 566:
end tag for element "TD" which is not open
…/a></td></tr></tr></table></div></td>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.
-
Line 931, Column 39:
document type does not allow element "TD" here
<td align="center"><div style="margin-right:50px"><table widThe 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).
-
Line 931, Column 557:
end tag for element "TR" which is not open
…en!!!" border="0"></a></td></tr></tr></table></div></td>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.
-
Line 932, Column 23:
end tag for element "TR" which is not open
</tr>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.
-
Line 933, Column 22:
document type does not allow element "TR" here
<tr>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).
-
Line 934, Column 586:
end tag for "TABLE" omitted, but its declaration does not permit this
…milie" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 934, Column 61:
start tag was here
…nter"><div style="margin-left:100px"><table width ="217" align="left" height -
Line 934, Column 586:
end tag for "DIV" omitted, but its declaration does not permit this
…milie" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 934, Column 30:
start tag was here
<td align="center"><div style="margin-left:100px"><table width ="217" -
Line 934, Column 594:
end tag for element "TABLE" which is not open
…order="0"></a></td></tr></tr></table></div></td>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.
-
Line 934, Column 600:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 934, Column 605:
end tag for element "TD" which is not open
…/a></td></tr></tr></table></div></td>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.
-
Line 935, Column 39:
document type does not allow element "TD" here
<td align="center"><div style="margin-right:50px"><table widThe 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).
-
Line 935, Column 595:
end tag for element "TR" which is not open
…um-Sc" border="0"></a></td></tr></tr></table></div></td>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.
-
Line 936, Column 23:
end tag for element "TR" which is not open
</tr>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.
-
Line 937, Column 13:
document type does not allow element "TR" here
<tr>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).
-
Line 938, Column 524:
end tag for "TABLE" omitted, but its declaration does not permit this
…liche" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 938, Column 70:
start tag was here
…nter"><div style="margin-left:100px"><table width ="217" align="left" height -
Line 938, Column 524:
end tag for "DIV" omitted, but its declaration does not permit this
…liche" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 938, Column 39:
start tag was here
<td align="center"><div style="margin-left:100px"><table wid -
Line 938, Column 532:
end tag for element "TABLE" which is not open
…order="0"></a></td></tr></tr></table></div></td>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.
-
Line 938, Column 538:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 938, Column 543:
end tag for element "TD" which is not open
…/a></td></tr></tr></table></div></td>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.
-
Line 939, Column 39:
document type does not allow element "TD" here
<td align="center"><div style="margin-right:50px"><table widThe 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).
-
Line 939, Column 570:
end tag for element "TR" which is not open
…riles" border="0"></a></td></tr></tr></table></div></td>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.
-
Line 940, Column 23:
end tag for element "TR" which is not open
</tr>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.
-
Line 941, Column 22:
document type does not allow element "TR" here
<tr>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).
-
Line 942, Column 517:
end tag for "TABLE" omitted, but its declaration does not permit this
…Nähen" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 942, Column 61:
start tag was here
…nter"><div style="margin-left:100px"><table width ="217" align="left" height -
Line 942, Column 517:
end tag for "DIV" omitted, but its declaration does not permit this
…Nähen" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 942, Column 30:
start tag was here
<td align="center"><div style="margin-left:100px"><table width ="217" -
Line 942, Column 525:
end tag for element "TABLE" which is not open
…order="0"></a></td></tr></tr></table></div></td>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.
-
Line 942, Column 531:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 942, Column 536:
end tag for element "TD" which is not open
…/a></td></tr></tr></table></div></td>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.
-
Line 943, Column 39:
document type does not allow element "TD" here
<td align="center"><div style="margin-right:50px"><table widThe 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).
-
Line 943, Column 596:
end tag for element "TR" which is not open
…erkze" border="0"></a></td></tr></tr></table></div></td>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.
-
Line 944, Column 23:
end tag for element "TR" which is not open
</tr>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.
-
Line 945, Column 22:
document type does not allow element "TR" here
<tr>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).
-
Line 946, Column 503:
end tag for "TABLE" omitted, but its declaration does not permit this
…ektro" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 946, Column 61:
start tag was here
…nter"><div style="margin-left:100px"><table width ="217" align="left" height -
Line 946, Column 503:
end tag for "DIV" omitted, but its declaration does not permit this
…ektro" border="0"></a></td></tr></tr></table></div></td>- 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. -
Line 946, Column 30:
start tag was here
<td align="center"><div style="margin-left:100px"><table width ="217" -
Line 946, Column 511:
end tag for element "TABLE" which is not open
…order="0"></a></td></tr></tr></table></div></td>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.
-
Line 946, Column 517:
end tag for element "DIV" which is not open
…"0"></a></td></tr></tr></table></div></td>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.
-
Line 946, Column 522:
end tag for element "TD" which is not open
…/a></td></tr></tr></table></div></td>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.
-
Line 947, Column 39:
document type does not allow element "TD" here
<td align="center"><div style="margin-right:50px"><table widThe 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).
-
Line 947, Column 553:
end tag for element "TR" which is not open
…eiten" border="0"></a></td></tr></tr></table></div></td>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.
-
Line 948, Column 23:
end tag for element "TR" which is not open
</tr>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.
-
Line 949, Column 13:
document type does not allow element "TR" here
<tr><td colspan="2"> </td></tr>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).
-
Line 950, Column 13:
document type does not allow element "TR" here
<tr>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).
-
Line 956, Column 15:
end tag for "DIV" omitted, but its declaration does not permit this
</td>- 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. -
Line 951, Column 42:
start tag was here
<td align="center" colspan="2"><div style="margin-right:50px"> -
Line 959, Column 25:
invalid comment declaration: found character "<" outside comment but inside comment declaration
<!--<td class="creg3"><div align="center"><table width ="217Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.
-
Line 958, Column 18:
comment declaration started here
<!--<tr><td><a href="">Alle Shops anzeigen</a></td> -
Line 959, Column 536:
required attribute "ALT" not specified
…ded/thumbs/th_748412.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 959, Column 690:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 4.10 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 959, Column 661:
start tag was here
…ize:12;">Behälter mit De..</font><br><small>Versand: 4.10 EUR</td><tr><td val -
Line 959, Column 967:
end tag for element "TD" which is not open
…mehr</a></td></tr></table></div></td>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.
-
Line 960, Column 38:
document type does not allow element "TD" here
<td class="creg3"><div align="center" class="creg3"><table wThe 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).
-
Line 960, Column 536:
required attribute "ALT" not specified
…ded/thumbs/th_530738.jpg" border="0"></a></td><td valign="top" width="115"><fThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 960, Column 690:
end tag for "SMALL" omitted, but its declaration does not permit this
…ont><br><small>Versand: 0.56 EUR</td><tr><td valign="bottom"><font style="col- 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. -
Line 960, Column 661:
start tag was here
…ize:12;">AK Eaton Queens..</font><br><small>Versand: 0.56 EUR</td><tr><td val -
Line 961, Column 14:
end tag for element "TR" which is not open
</tr>-->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.
-
Line 964, Column 24:
end tag for element "TABLE" which is not open
</table><!--ENDE SHOPS-->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.
-
Line 974, Column 86:
end tag for "B" omitted, but its declaration does not permit this
…b> Partnerlinkseite und Toplisten</a></b>- 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. -
Line 974, Column 48:
start tag was here
…tp://teddys-auktionen.de/links.html"><b> Partnerlinkseite und Toplisten</a><… -
Line 976, Column 162:
required attribute "ALT" not specified
…p://banner.plueschpapa.de/werb1.JPG"></img></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 976, Column 168:
end tag for element "IMG" which is not open
…nner.plueschpapa.de/werb1.JPG"></img></a>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.
-
Line 978, Column 147:
required attribute "ALT" not specified
…est.de/pics/spamfree.gif" border="0"></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 988, Column 17:
end tag for element "TD" which is not open
</td>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.
-
Line 989, Column 15:
end tag for element "TR" which is not open
</tr>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.
-
Line 990, Column 14:
document type does not allow element "TR" here
<tr>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).
-
Line 993, Column 16:
end tag for element "TABLE" which is not open
</table>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.
-
Line 994, Column 8:
end tag for element "TD" which is not open
</td>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.
-
Line 995, Column 33:
document type does not allow element "TD" here
<td width="160" valign="top">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).
-
Line 1034, Column 17:
end tag for "TABLE" omitted, but its declaration does not permit this
</td>- 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. -
Line 1021, Column 7:
start tag was here
<TABLE style="border:0px" height=22 cellSpacing=0 cellPadding=0 width="10 -
Line 1037, Column 13:
end tag for element "TR" which is not open
</tr>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.
-
Line 1039, Column 12:
document type does not allow element "TR" here
<tr>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).
-
Line 1071, Column 160:
end tag for "B" omitted, but its declaration does not permit this
…50,scrollbars=no')"><b>unser Team</a></td>- 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. -
Line 1071, Column 143:
start tag was here
…idth=500,height=350,scrollbars=no')"><b>unser Team</a></td> -
Line 1126, Column 166:
end tag for "B" omitted, but its declaration does not permit this
…ollbars=no')"><b>Live-Chatauktion</a></td>- 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. -
Line 1126, Column 143:
start tag was here
…idth=500,height=350,scrollbars=no')"><b>Live-Chatauktion</a></td> -
Line 1147, Column 14:
end tag for element "TABLE" which is not open
</table>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.
-
Line 1150, Column 237:
NET-enabling start-tag requires SHORTTAG YES
…Bookmark and Share" style="border:0"/></a><script type="text/javascript" src=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.
-
Line 1153, Column 8:
end tag for element "P" which is not open
</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.
-
Line 1196, Column 6:
end tag for element "P" which is not open
</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.
-
Line 1213, Column 13:
end tag for "TABLE" omitted, but its declaration does not permit this
</td>- 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. -
Line 1202, Column 4:
start tag was here
<TABLE style="border:0px" height=22 cellSpacing=0 cellPadding=0 width="100%" -
Line 1215, Column 8:
end tag for element "TD" which is not open
</td>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.
-
Line 1216, Column 9:
end tag for element "TR" which is not open
</tr>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.
-
Line 1217, Column 8:
document type does not allow element "TR" here
<tr>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).
-
Line 1222, Column 111:
character ";" not allowed in attribute specification list
…e2a77f605d1671.html" target="_blank";> -
Line 1223, Column 56:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/bueropetra1.GIF"></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1229, Column 8:
end tag for element "TABLE" which is not open
</table> </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.
-
Line 1229, Column 16:
end tag for element "P" which is not open
</table> </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.
-
Line 1235, Column 23:
document type does not allow element "STYLE" here
<style type="text/css">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
-
Line 1262, Column 13:
an attribute value must be a literal unless it contains only name characters
<tr bgcolor=#f6f6f6 height="20"><td width="20" align="left" valign="middle" ><imYou have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 493:
an attribute value must be a literal unless it contains only name characters
…e" width="30"></td></tr><tr bgcolor=#ffffff height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 1103:
required attribute "ALT" not specified
…nen.de/images/me/me.gif" border= "0"></a></td></tr><tr bgcolor=#f6f6f6 heightThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1262, Column 1130:
an attribute value must be a literal unless it contains only name characters
…rder= "0"></a></td></tr><tr bgcolor=#f6f6f6 height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 1603:
an attribute value must be a literal unless it contains only name characters
…e" width="30"></td></tr><tr bgcolor=#ffffff height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 2213:
required attribute "ALT" not specified
…nen.de/images/me/me.gif" border= "0"></a></td></tr><tr bgcolor=#f6f6f6 heightThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1262, Column 2240:
an attribute value must be a literal unless it contains only name characters
…rder= "0"></a></td></tr><tr bgcolor=#f6f6f6 height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 2713:
an attribute value must be a literal unless it contains only name characters
…e" width="30"></td></tr><tr bgcolor=#ffffff height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 3184:
an attribute value must be a literal unless it contains only name characters
…e" width="30"></td></tr><tr bgcolor=#f6f6f6 height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 3660:
an attribute value must be a literal unless it contains only name characters
…e" width="30"></td></tr><tr bgcolor=#ffffff height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 4270:
required attribute "ALT" not specified
…nen.de/images/me/me.gif" border= "0"></a></td></tr><tr bgcolor=#f6f6f6 heightThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1262, Column 4297:
an attribute value must be a literal unless it contains only name characters
…rder= "0"></a></td></tr><tr bgcolor=#f6f6f6 height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 4911:
required attribute "ALT" not specified
…nen.de/images/me/me.gif" border= "0"></a><a href= "http://www.teddys-auktioneThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1262, Column 5047:
required attribute "ALT" not specified
…de/images/shop/shop.gif" border= "0"></a></td></tr><tr bgcolor=#ffffff heightThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1262, Column 5074:
an attribute value must be a literal unless it contains only name characters
…rder= "0"></a></td></tr><tr bgcolor=#ffffff height="20"><td width="20" align=You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1262, Column 5683:
required attribute "ALT" not specified
…nen.de/images/me/me.gif" border= "0"></a></td></tr></table></td></tr></table>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1277, Column 5:
end tag for "TABLE" omitted, but its declaration does not permit this
</td></tr>- 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. -
Line 1266, Column 2:
start tag was here
<table width="170" border="0" align="center" cellpadding="0" cellspacing="1" c -
Line 1283, Column 33:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
<TD width="32%" align=middleThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1284, Column 31:
an attribute value must be a literal unless it contains only name characters
bgColor=#ffffff class="c4"><span class="text_normal">You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
-
Line 1286, Column 105:
end tag for "SPAN" omitted, but its declaration does not permit this
…gories">Registrierte User</span></TD>- 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. -
Line 1286, Column 26:
start tag was here
<TD width="22%"><span class="categories"><span class="categories">Regi -
Line 1289, Column 33:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
<TD width="32%" align=middle class="c4"><span class="text_normal">The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1291, Column 102:
end tag for "SPAN" omitted, but its declaration does not permit this
…ategories">Live Auktionen</span></TD>- 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. -
Line 1291, Column 26:
start tag was here
<TD width="22%"><span class="categories"><span class="categories">Live -
Line 1305, Column 138:
document type does not allow element "UL" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…font color="#000000"><ul class="ul1"><li><div style="text-decoration:none;curThe 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>").
-
Line 1305, Column 357:
end tag for "UL" omitted, but its declaration does not permit this
…ion:none;">tycoonct</div></li></font><!--</TD>-->- 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. -
Line 1305, Column 122:
start tag was here
…</b></u></span><font color="#000000"><ul class="ul1"><li><div style="text-dec -
Line 1306, Column 26:
end tag for element "UL" which is not open
<!--<TD>--></ul></TD>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.
-
Line 1315, Column 112:
required attribute "ALT" not specified
…4.jpg" style="border:1px solid red"></img><br>AK Wildbad... </a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1315, Column 118:
end tag for element "IMG" which is not open
… style="border:1px solid red"></img><br>AK Wildbad... </a>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.
-
Line 1321, Column 112:
required attribute "ALT" not specified
…0.jpg" style="border:1px solid red"></img><br>AK Bonndor... </a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1321, Column 118:
end tag for element "IMG" which is not open
… style="border:1px solid red"></img><br>AK Bonndor... </a>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.
-
Line 1327, Column 112:
required attribute "ALT" not specified
…5.jpg" style="border:1px solid red"></img><br>Esso Autok... </a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1327, Column 118:
end tag for element "IMG" which is not open
… style="border:1px solid red"></img><br>Esso Autok... </a>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.
-
Line 1345, Column 5:
end tag for element "TD" which is not open
</td></tr></table>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.
-
Line 1345, Column 10:
end tag for element "TR" which is not open
</td></tr></table>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.
-
Line 1345, Column 18:
end tag for element "TABLE" which is not open
</td></tr></table>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.
-
Line 1346, Column 10:
end tag for element "P" which is not open
</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.
-
Line 1377, Column 27:
invalid comment declaration: found name character outside comment but inside comment declaration
<!--Ende Sonderangebote---> -
Line 1377, Column 1:
comment declaration started here
<!--Ende Sonderangebote---> -
Line 1401, Column 101:
document type does not allow element "TABLE" here
…" cellspacing="0" class="table_norm">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).
-
Line 1407, Column 60:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
…class="c4" width="11%" align="middle"><div align="left"><span class="categoriThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1410, Column 60:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
…class="c4" width="11%" align="middle"><div align="left"><span class="categoriThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1413, Column 60:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
…class="c4" width="11%" align="middle"> <div align="left"><span class="categorThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1416, Column 60:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
…class="c4" width="11%" align="middle"><div align="left"><span class="categoriThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1419, Column 48:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
… <td class="c4" align="middle"><div align="left"><span class="categoriThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1422, Column 48:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
… <td class="c4" align="middle"><div align="left"><span class="categoriThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1425, Column 48:
value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
… <td class="c4" align="middle"><div align="left"><span class="categoriThe value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “
selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed. -
Line 1428, Column 129:
document type does not allow element "TABLE" here
…g="0" cellspacing="0" align="center">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).
-
Line 1431, Column 128:
required attribute "ALT" not specified
…xe"><img src="banners/lister1ab.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1432, Column 77:
required attribute "ALT" not specified
…="_blank"><img src="banners/faust1.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1433, Column 102:
required attribute "ALT" not specified
…p://banner.plueschpapa.de/Media.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1441, Column 92:
cannot generate system identifier for general entity "uid"
…ukte/safetrade/safetrade.asp?sid=34&uid=0" target="_blank"><img src="http://wAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ 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.
-
Line 1441, Column 92:
general entity "uid" not defined and no default entity
…ukte/safetrade/safetrade.asp?sid=34&uid=0" target="_blank"><img src="http://wThis 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.
-
Line 1441, Column 95:
reference to entity "uid" for which no system identifier could be generated
…e/safetrade/safetrade.asp?sid=34&uid=0" target="_blank"><img src="http://www.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.
-
Line 1441, Column 90:
entity was defined here
…odukte/safetrade/safetrade.asp?sid=34&uid=0" target="_blank"><img src="http:/ -
Line 1441, Column 191:
required attribute "ALT" not specified
…/images/icon_safetrade.gif" border=0></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1455, Column 14:
end tag for element "UL" which is not open
</ul>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.
-
Line 1457, Column 209:
required attribute "ALT" not specified
…s/Moneybookers_100x50.gif" border=0></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1471, Column 103:
character ";" not allowed in attribute specification list
…tueberweisungde.html"target="_blank";><img src="http://bilder.plueschpapa.de/ -
Line 1471, Column 103:
document type does not allow element "A" here
…tueberweisungde.html"target="_blank";><img src="http://bilder.plueschpapa.de/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).
-
Line 1472, Column 13:
end tag for "A" omitted, but its declaration does not permit this
</td>- 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. -
Line 1467, Column 8:
start tag was here
<a href="#" onclick="javascript:window.open('https://www.paypal.com/de/c -
Line 1479, Column 8:
end tag for element "P" which is not open
</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.
-
Line 1483, Column 9:
document type does not allow element "P" here
<p>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).
-
Line 1485, Column 59:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
<table cellpadding ="0" cellspacing ="0" width="170">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>").
-
Line 1489, Column 11:
end tag for "TABLE" omitted, but its declaration does not permit this
</td></tr></table>- 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. -
Line 1485, Column 6:
start tag was here
<table cellpadding ="0" cellspacing ="0" width="170"> -
Line 1489, Column 11:
end tag for "TABLE" omitted, but its declaration does not permit this
</td></tr></table>- 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. -
Line 1403, Column 34:
start tag was here
<td class="text_normal"><table align = "center" width="100%" border="… -
Line 1490, Column 24:
document type does not allow element "TABLE" here
<table width="170">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).
-
Line 1493, Column 105:
character ";" not allowed in attribute specification list
…373b669197b606.html" target="_blank";> -
Line 1494, Column 48:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/ma1.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1495, Column 105:
character ";" not allowed in attribute specification list
…370bbf46471178.html" target="_blank";> -
Line 1496, Column 50:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/schna.gif"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1497, Column 105:
character ";" not allowed in attribute specification list
…c9952dd55297f6.html" target="_blank";> -
Line 1498, Column 50:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/fund1.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1499, Column 109:
reference to entity "user_id" for which no system identifier could be generated
…52dc67b87996c8503e5f874f34e1&user_id=e2119e5c5b9460454dcfddd6b40f6296This 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.
-
Line 489, Column 111:
entity was defined here
…N_ID=c8c828d1414673a12d57a54d4010861e&user_id=5287c2f8fa6f8adec1d123126ad47… -
Line 1500, Column 17:
character ";" not allowed in attribute specification list
"target="_blank";> -
Line 1501, Column 48:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/ham.JPG"></a><br><br>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1502, Column 49:
required attribute "ALT" not specified
<img src="http://banner.plueschpapa.de/werb.JPG"></img>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1502, Column 55:
end tag for element "IMG" which is not open
<img src="http://banner.plueschpapa.de/werb.JPG"></img>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.
-
Line 1506, Column 42:
document type does not allow element "SPAN" here
<span style='color:#000000'>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).
-
Line 1507, Column 21:
element "O:P" undefined. Did you mean "caption" or "blockquote"?
<o:p></o: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).
-
Line 1508, Column 27:
end tag for element "TD" which is not open
</span> </td>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.
-
Line 1509, Column 13:
end tag for element "TR" which is not open
</tr>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.
-
Line 1513, Column 25:
end tag for element "TD" which is not open
<p> </p></td>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.
-
Line 1514, Column 7:
end tag for element "TR" which is not open
</tr>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.
-
Line 1515, Column 8:
end tag for element "TABLE" which is not open
</table>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.
-
Line 1519, Column 5:
end tag for element "TD" which is not open
</td></tr></table></td></tr>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.
-
Line 1519, Column 10:
end tag for element "TR" which is not open
</td></tr></table></td></tr>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.
-
Line 1519, Column 18:
end tag for element "TABLE" which is not open
</td></tr></table></td></tr>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.
-
Line 1519, Column 23:
end tag for element "TD" which is not open
</td></tr></table></td></tr>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.
-
Line 1519, Column 28:
end tag for element "TR" which is not open
</td></tr></table></td></tr>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.
-
Line 1520, Column 8:
end tag for element "TABLE" which is not open
</table>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.
-
Line 1526, Column 4:
end tag for element "P" which is not open
</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.
-
Line 1537, Column 34:
end tag for "B" omitted, but its declaration does not permit this
<font color="#000000"><b></font>- 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. -
Line 1537, Column 24:
start tag was here
<font color="#000000"><b></font> -
Line 1538, Column 4:
end tag for element "P" which is not open
</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.
-
Line 1557, Column 26:
Attribute "COLOR" is not a valid attribute. Did you mean "color"?
<hr size="1" color="#374665" width="97%">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.
-
Line 1577, Column 35:
end tag for "FONT" omitted, but its declaration does not permit this
Haftungsausschluss</span></a> an.<br><br>- 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. -
Line 1575, Column 19:
start tag was here
<a href="agb.php"><font size="1" color="#000000"><span class="categories">Nutzu -
Line 1579, Column 434:
NET-enabling start-tag requires SHORTTAG YES
…er Wong hinzufügen" border="0" /></a>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.
-
Line 1580, Column 206:
NET-enabling start-tag requires SHORTTAG YES
…chinenoptimierung mit Ranking-Hits" /></a>.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.
-
Line 1585, Column 182:
NET-enabling start-tag requires SHORTTAG YES
…" height="23" alt="XING" border="0" /></a>.<!--<a href="http://www.auktionsblThe 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.
-
Line 1589, Column 178:
NET-enabling start-tag requires SHORTTAG YES
…- Webmaster Portal" style="border:0"/></a><!--.<a href="http://www.deutscheseThe 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.
-
Line 1591, Column 168:
invalid comment declaration: found name start character outside comment but inside comment declaration
…uktionshaus Topliste vom Auktions--Agent.de" border="0" /></a>.<a href="http -
Line 1591:
comment declaration started here
n<!--<a href="http://www.auktions-agent.de/toplist/"><img src="http://www.auktion -
Line 1591, Column 194:
end tag for element "A" which is not open
…Auktions--Agent.de" border="0" /></a>.<a href="http://www.private-krankenversThe 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.
-
Line 1600, Column 114:
required attribute "ALT" not specified
…p://www.quit-submit.net/submit8.gif"></a>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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1626, Column 190:
cannot generate system identifier for general entity "title"
…encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.titleAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ 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.
-
Line 1626, Column 190:
general entity "title" not defined and no default entity
…encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.titleThis 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.
-
Line 1626, Column 195:
reference to entity "title" for which no system identifier could be generated
…eURIComponent(location.href)+'&title='+encodeURIComponent(document.title));reThis 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.
-
Line 1626, Column 188:
entity was defined here
…'+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.tit -
Line 1631, Column 151:
cannot generate system identifier for general entity "display"
…hardware.at/index.php?mod=bookmarks&display=submit');return false;" title="BoAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ 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.
-
Line 1631, Column 151:
general entity "display" not defined and no default entity
…hardware.at/index.php?mod=bookmarks&display=submit');return false;" title="BoThis 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.
-
Line 1631, Column 158:
reference to entity "display" for which no system identifier could be generated
…e.at/index.php?mod=bookmarks&display=submit');return false;" title="BookmarkThis 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.
-
Line 1631, Column 149:
entity was defined here
…w.hardware.at/index.php?mod=bookmarks&display=submit');return false;" title=" -
Line 1680, Column 35:
cannot generate system identifier for general entity "cat"
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>.An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ 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.
-
Line 1680, Column 35:
general entity "cat" not defined and no default entity
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>.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.
-
Line 1680, Column 38:
reference to entity "cat" for which no system identifier could be generated
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>.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.
-
Line 1680, Column 33:
entity was defined here
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>. -
Line 1680, Column 56:
cannot generate system identifier for general entity "pixel"
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>.An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ 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.
-
Line 1680, Column 56:
general entity "pixel" not defined and no default entity
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>.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.
-
Line 1680, Column 61:
reference to entity "pixel" for which no system identifier could be generated
…in/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>.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.
-
Line 1680, Column 54:
entity was defined here
cgi-bin/adserv/ad.cgi?action=view&cat=promo-mailtausch&pixel=468x60"></iframe>. -
Line 1683, Column 63:
document type does not allow element "A" here
…chine.net/de/site.php?details=90717"><img src="http://www.beammachine.net/de/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).
-
Line 1684, Column 58:
NET-enabling start-tag requires SHORTTAG YES
…BeamMachine.net --><script src=http://www.pucco.de/banner-0673KG429ZF643LZDnvThe 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.
-
Line 1684, Column 58:
required attribute "TYPE" not specified
…BeamMachine.net --><script src=http://www.pucco.de/banner-0673KG429ZF643LZDnvThe 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
typearetype="text/css"for<style>andtype="text/javascript"for<script>. -
Line 1684, Column 118:
end tag for element "SCRIPT" which is not open
…73KG429ZF643LZDnv600148.js> </script>.<a href="http://www.bestsubmit.de" targThe 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.
-
Line 1684, Column 170:
document type does not allow element "A" here
…//www.bestsubmit.de" target="_blank"><img src="http://www.bestsubmit.de/img/sThe 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).
-
Line 1684, Column 343:
document type does not allow element "A" here
…="http://www.webkatapult.de/aff/0/2">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).
-
Line 1685, Column 196:
NET-enabling start-tag requires SHORTTAG YES
…pult.de/images/banner/banner_01.png"/></a>.<a href="http://www.onlinepresse.iThe 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.
-
Line 1685, Column 362:
document type does not allow element "A" here
…Pressedienst mit Pressemitteilungen"><img src="http://www.onlinepresse.info/sThe 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).
-
Line 1685, Column 513:
NET-enabling start-tag requires SHORTTAG YES
…t="Autoren Siegel OnlinePresse.info"/></a><!--.<a href="http://www.seitwert.dThe 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.
-
Line 1689, Column 10:
end tag for element "DIV" which is not open
</div>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.
-
Line 1692, Column 11:
end tag for "CENTER" omitted, but its declaration does not permit this
</td>- 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. -
Line 1691, Column 1:
start tag was here
<center> -
Line 1696, Column 104:
end tag for "CENTER" omitted, but its declaration does not permit this
…" height="0" width="0"></iframe></td></tr></table></div>- 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. -
Line 1536, Column 2:
start tag was here
<center> -
Line 1696, Column 123:
end tag for element "DIV" which is not open
…"0"></iframe></td></tr></table></div>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.
![<?=$cfg['site_name']?>](/images/link-commander-logo.gif)
