Below are the results of attempting to parse this document with an SGML parser.
1. Error Line 6 column 132: document type does not allow element "META" here.
...o, mehr besucher homepage, pagerank" />
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
✉
2. Error Line 7 column 6: required attribute "TYPE" not specified.
<style>
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
✉
3. Error Line 7 column 6: document type does not allow element "STYLE" here.
<style>
✉
4. Error Line 121 column 6: 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 occured in a script section of your document, you should probably read this FAQ entry.
✉
5. Error Line 122 column 5: document type does not allow element "BODY" here.
<body>
✉
6. Warning Line 210 column 88: cannot generate system identifier for general entity "pid".
...http://filiwelt.net/klick.php?bann…=17391&prid=289" target="_top"><img s
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.
✉
7. Error Line 210 column 88: general entity "pid" not defined and no default entity.
...http://filiwelt.net/klick.php?bann…=17391&prid=289" target="_top"><img s
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
✉
8. Error Line 210 column 91: reference to entity "pid" for which no system identifier could be generated.
...http://iwelt.net/klick.php?bannerid=7820&pid=17391&prid=289" target="_top"><img src=
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
✉
9. Info Line 210 column 87: entity was defined here.
...http://ffiliwelt.net/klick.php?bann…=17391&prid=289" target="_top"><img
10. Warning Line 210 column 98: cannot generate system identifier for general entity "prid".
...et/klick.php?bannerid=7820&pid=17391&prid=289" target="_top"><img src="http:/
✉
11. Error Line 210 column 98: general entity "prid" not defined and no default entity.
...et/klick.php?bannerid=7820&pid=17391&prid=289" target="_top"><img src="http:/
✉
12. Error Line 210 column 102: reference to entity "prid" for which no system identifier could be generated.
...lick.php?bannerid=7820&pid=17391&prid=289" target="_top"><img src="http://www
✉
13. Info Line 210 column 97: entity was defined here.
...net/klick.php?bannerid=7820&pid=17391&prid=289" target="_top"><img src="http:
14. Error Line 210 column 212: required attribute "ALT" not specified.
...idth="468px" height="60px" border="0"></a></div>
✉
15. Error Line 213 column 46: required attribute "ALT" not specified.
...class="uschrift">
Willkommen </div>
✉
16. Error Line 213 column 79: required attribute "ALT" not specified.
....gif"> Willkommen </div>
