Tweet
Hallo,
ich habe meine Homepage Validieren lassen und das unten stehenden Ergebnis erhalten....das ist nur die erste Hälfte weil der Text für das Forum zu lang ist
Ich verstehe eigentlich nur Bahnhof , da ich nicht viel Ahnung habe.
Kann mir hier jemand weiterhelfen?
Danke im vorraus und lg
Potential Issues
The following missing or conflicting information caused the validator to perform guesswork prior to validation. If the guess or fallback is incorrect, it may make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
DOCTYPE Override in effect!
The DOCTYPE Declaration for "XHTML 1.0 Transitional" has been inserted at the start of the document, but even if no errors are shown below the document will not be Valid until you add the new DOCTYPE Declaration.
↑ Top
Validation Output: 91 Errors
Line 38, Column 79: document type does not allow element "meta" here.
…0Qm+f/O2gzFekoBGdmQVxEBZ2Kuq+UWmRs=" /> ✉
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 39, Column 6: end tag for "script" omitted, but OMITTAG NO was specified.
</head>✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 33, Column 0: start tag was here.
<script type="text/javascript"> Line 44, Column 17: there is no attribute "LANGUAGE".
<SCRIPT LANGUAGE="JavaScript"> ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 44, Column 29: element "SCRIPT" undefined.
<SCRIPT LANGUAGE="JavaScript"> ✉
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 114, Column 55: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified.
<input type="radio" name="sitesearch" value="" checked id="ss0"></input>✉
"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.
How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
Line 136, Column 49: cannot generate system identifier for general entity "http:".
…p://infopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http:/✉
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 136, Column 49: general entity "http:" not defined and no default entity.
…p://infopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http:/✉
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 136, Column 54: reference not terminated by REFC delimiter.
…nfopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http://www.✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 136, Column 54: reference to external entity in attribute value.
…nfopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http://www.✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 136, Column 54: reference to entity "http:" for which no system identifier could be generated.
…nfopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=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 136, Column 48: entity was defined here.
…tp://infopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http: Line 136, Column 117: cannot generate system identifier for general entity "schuldnerakuthilfe".
…om=http://www.schuldnerakuthilfe.com&schuldnerakuthilfe/immobilienakuthilfe=h✉
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 136, Column 117: general entity "schuldnerakuthilfe" not defined and no default entity.
…om=http://www.schuldnerakuthilfe.com&schuldnerakuthilfe/immobilienakuthilfe=h✉
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 136, Column 135: reference not terminated by REFC delimiter.
ich habe meine Homepage Validieren lassen und das unten stehenden Ergebnis erhalten....das ist nur die erste Hälfte weil der Text für das Forum zu lang ist
Ich verstehe eigentlich nur Bahnhof , da ich nicht viel Ahnung habe.
Kann mir hier jemand weiterhelfen?
Danke im vorraus und lg
Potential Issues
The following missing or conflicting information caused the validator to perform guesswork prior to validation. If the guess or fallback is incorrect, it may make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
DOCTYPE Override in effect!
The DOCTYPE Declaration for "XHTML 1.0 Transitional" has been inserted at the start of the document, but even if no errors are shown below the document will not be Valid until you add the new DOCTYPE Declaration.
↑ Top
Validation Output: 91 Errors
Line 38, Column 79: document type does not allow element "meta" here.
…0Qm+f/O2gzFekoBGdmQVxEBZ2Kuq+UWmRs=" /> ✉
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 39, Column 6: end tag for "script" omitted, but OMITTAG NO was specified.
</head>✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 33, Column 0: start tag was here.
<script type="text/javascript"> Line 44, Column 17: there is no attribute "LANGUAGE".
<SCRIPT LANGUAGE="JavaScript"> ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 44, Column 29: element "SCRIPT" undefined.
<SCRIPT LANGUAGE="JavaScript"> ✉
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 114, Column 55: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified.
<input type="radio" name="sitesearch" value="" checked id="ss0"></input>✉
"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.
How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
Line 136, Column 49: cannot generate system identifier for general entity "http:".
…p://infopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http:/✉
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 136, Column 49: general entity "http:" not defined and no default entity.
…p://infopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http:/✉
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 136, Column 54: reference not terminated by REFC delimiter.
…nfopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http://www.✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 136, Column 54: reference to external entity in attribute value.
…nfopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http://www.✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 136, Column 54: reference to entity "http:" for which no system identifier could be generated.
…nfopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=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 136, Column 48: entity was defined here.
…tp://infopirat.com/bookmark-king.php?&http://www.schuldnerakuthilfe.com=http: Line 136, Column 117: cannot generate system identifier for general entity "schuldnerakuthilfe".
…om=http://www.schuldnerakuthilfe.com&schuldnerakuthilfe/immobilienakuthilfe=h✉
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 136, Column 117: general entity "schuldnerakuthilfe" not defined and no default entity.
…om=http://www.schuldnerakuthilfe.com&schuldnerakuthilfe/immobilienakuthilfe=h✉
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 136, Column 135: reference not terminated by REFC delimiter.
Kommentar