Hallo, kann man hier etwas machen, damit sich die Fehlerausgabe reduziert? Die Domain gibt unter Seitwert bei “Technische Details” folgende Mängel aus: [quote] Die Anzahl der erkannten Probleme (41) im W3C-Validator deutet auf eine nicht W3C-konforme Programmierung der Seite hin. Details können hier abgerufen werden.[?] Die Seite benutzt veraltete Tags.[?][/quote] [quote] Validation Output: 41 Errors Error Line 95, Column 19: document type does not allow element “noscript” here; assuming missing “object” start-tag
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 95, Column 10: start tag was here
<noscript>
';
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 125, Column 154: start tag was here
…="f4956cef3264ca856236fd327216c302" /><input type="hidden" name="sMobile" valu warning line column character is the first of a delimiter but occurred as data if true usesubshop="=" this message may appear in several cases: you tried to include your page: should escape it used an unescaped ampersand be valid some contexts recommended use which always safe. another possibility that forgot close quotes previous tag. error id already defined action="" method="post"><input an is a unique identifier. each time this attribute used in document it must have different value. if you are using as hook for style sheets may be more appropriate to use classes group elements than id identify exactly one element info line column first defined here action="" method="post"><input error line column document type does not allow element here id="dynForm" action="" method="post"><input type="hidden" name="sCoreId" val 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 section instead of inside or two overlap allowed one common cause for error use xhtml syntax html documents. due to rules implicitly closed can create cascading effects. instance using tags and document may parser infer end beginning are hence reported line column tag omitted but omittag no specified><input type="hidden" name="sLanguage" value="'+ subShopID +'">';
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 130, Column 154: start tag was here
…="f4956cef3264ca856236fd327216c302" /><input type="hidden" name="sLanguage" va error line column end tag for omitted but omittag no was specified>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 407, Column 7: start tag was here
<br></p>
Error Line 416, Column 44: document type does not allow element "div" here; assuming missing "li" start-tag
<div align="center" style="padding-top:4px">
Warning Line 417, Column 64: cannot generate system identifier for general entity "L"
…http://www.iclear.de/index.phpid=314&L=0" title="" rel="nofollow"><img alt="" an entity reference was found in the document but there is no by that name defined. often this caused misspelling unencoded ampersands or leaving off trailing semicolon most common cause of error urls as described wdg references start with ampersand and end a if you want to use literal your must encode it inside be careful may get interpreted connection following text. also keep mind named are case-sensitive different characters. appears some markup generated php session handling code article has explanations solutions problem. note documents errors related will trigger up separate messages from validator. usually these all disappear when original problem fixed. line column general not defined default title="" rel="nofollow"><img alt="" this is usually a cascading error caused by an undefined entity reference or use of unencoded ampersand in url body text. see the previous message for further details. warning line column not terminated refc delimiter title="" rel="nofollow"><img alt="" if you meant to include an entity that starts with then should terminate it another reason for this error message is inadvertently created by failing escape character just before text. warning line column reference external in attribute value title="" rel="nofollow"><img alt="" this is generally the sign of an ampersand that was not properly escaped for inclusion in attribute a href example. you will need to escape all instances into error line column reference entity which no system identifier could be generated title="" rel="nofollow"><img alt="" this is usually a cascading error caused by an undefined entity reference or use of unencoded ampersand in url body text. see the previous message for further details. info line column was defined here title="" rel="nofollow"><img alt="…
Error Line 417, Column 214: an attribute specification must start with a name or name token
…s://www.domain.de/templates/domain/frontend/_resources/images/iClear.png">
An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Error Line 417, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
…s://www.domain.de/templates/domain/frontend/_resources/images/iClear.png"" />
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 417, Column 93: start tag was here
…pid=314&L=0" title="" rel="nofollow"><img alt="" border="0" width="170px" src error line column an attribute specification must start with a name or token>
An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Error Line 421, Column 208: end tag for "img" omitted, but OMITTAG NO was specified
…://www.domain.de/templates/domain/frontend/_resources/images/Billpay.png"" />
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 421, Column 85: start tag was here
…e/Endkunden/" title="" rel="nofollow"><img alt="" border="0" width="170px" src error line column end tag for omitted but omittag no was specified>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 416, Column 1: start tag was here
<div align="center" style="padding-top:4px">
Error Line 425, Column 9: ID "servicenav" already defined
<ul id="servicenav">
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).
Info Line 414, Column 9: ID "servicenav" first defined here
<ul id="servicenav" style="margin-top:0px;margin-bottom:0px">
Warning Line 428, Column 63: cannot generate system identifier for general entity "sFid"
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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.
Error Line 428, Column 63: general entity "sFid" not defined and no default entity
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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.
Warning Line 428, Column 67: reference not terminated by REFC delimiter
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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.
Warning Line 428, Column 67: reference to external entity in attribute value
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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 '&'.
Error Line 428, Column 67: reference to entity "sFid" for which no system identifier could be generated
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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.
Info Line 428, Column 62: entity was defined here
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
Error Line 478, Column 9: ID "servicenav" already defined
<ul id="servicenav">
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).
Info Line 414, Column 9: ID "servicenav" first defined here
<ul id="servicenav" style="margin-top:0px;margin-bottom:0px">
Error Line 480, Column 20: document type does not allow element "div" here; assuming missing "li" start-tag
<div align="center">
<a href=“http://www.preisroboter.de” target="_blank" rel="n…
Error Line 480, Column 232: required attribute " alt not specified title="PreisRoboter.de - Produktsuche und Preisvergleich"></a><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 type are type="text/css" for <style> and type="text/javascript" for <script>.
Error Line 481, Column 218: required attribute "alt" not specified
…o.gif" title="Geizhals.at - Produktsuche und Preisvergleich" /></a><br /></div>
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Error Line 482, Column 243: end tag for "img" omitted, but OMITTAG NO was specified
…er="0" alt="Preisvergleich" title="Schottenland.de - Preisvergleich"></a></div>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 482, Column 89: start tag was here
…nd.de" target="_blank" rel="nofollow"><img src="http://www.schottenland.de/ima…
Error Line 483, Column 16: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li class="neu"></li>
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>").
Error Line 484, Column 16: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li class="neu"></li>
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>").
Error Line 485, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
</ul>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 480, Column 1: start tag was here
<div align="center"><a href="http://www.preisroboter.de" target="_blank" rel="n…
Warning Line 491, Column 57: cannot generate system identifier for general entity "s"
…w.domain.de/sportuhren-pulsuhrenp=1&s=14" class="banner" target="_parent" ti…
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.
Error Line 491, Column 57: general entity "s" not defined and no default entity
…w.domain.de/sportuhren-pulsuhrenp=1&s=14" class="banner" target="_parent" ti…
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.
Warning Line 491, Column 58: reference not terminated by REFC delimiter
….domain.de/sportuhren-pulsuhrenp=1&s=14" class="banner" target="_parent" tit…
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.
Warning Line 491, Column 58: reference to external entity in attribute value
….domain.de/sportuhren-pulsuhrenp=1&s=14" class="banner" target="_parent" tit…
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 '&'.
Error Line 491, Column 58: reference to entity "s" for which no system identifier could be generated
….domain.de/sportuhren-pulsuhrenp=1&s=14" class="banner" target="_parent" tit…
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.
Info Line 491, Column 56: entity was defined here
…ww.domain.de/sportuhren-pulsuhrenp=1&s=14" class="banner" target="_parent" t…
Warning Line 1130, Column 67: reference not terminated by REFC delimiter
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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.
Warning Line 1130, Column 67: reference to external entity in attribute value
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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 '&'.
Error Line 1130, Column 67: reference to entity "sFid" for which no system identifier could be generated
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
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.
Info Line 428, Column 62: entity was defined here
…spo24.de/shopware.phpsViewport=support&sFid=5" title="Kontakt" target="_self">
Error Line 1171, Column 335: end tag for "hr" omitted, but OMITTAG NO was specified
…255, 0.07) inset;box-shadow: 0 0 0 1px rgba(255, 255, 255, 0.07) inset;"></div>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1171, Column 69: start tag was here
…ft;margin-top:0px;margin-right:20px;"><hr style="height:160px;width:2px;backgr…
Error Line 1193, Column 335: end tag for "hr" omitted, but OMITTAG NO was specified
…255, 0.07) inset;box-shadow: 0 0 0 1px rgba(255, 255, 255, 0.07) inset;"></div>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1193, Column 69: start tag was here
…ft;margin-top:0px;margin-right:20px;"><hr style="height:160px;width:2px;backgr…
Error Line 1197, Column 5: end tag for "ul" which is not finished
</ul>
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 require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
Error Line 1199, Column 335: end tag for "hr" omitted, but OMITTAG NO was specified
…255, 0.07) inset;box-shadow: 0 0 0 1px rgba(255, 255, 255, 0.07) inset;"></div>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1199, Column 69: start tag was here
…ft;margin-top:0px;margin-right:20px;"><hr style="height:160px;width:2px;backgr…
Error Line 1203, Column 182: document type does not allow element "div" here; assuming missing "li" start-tag
…top:10px;-moz-border-radius: 4px;-webkit-border-radius:4px;border-radius:4px;">
Error Line 1206, Column 59: value of attribute "method" cannot be "POST"; must be one of "get", "post"
…ter_form" id="letterForm" method="POST" action="http://www.domain.de/newslett…
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.
Error Line 1207, Column 58: end tag for "input" omitted, but OMITTAG NO was specified
<input type="hidden" value="newsletter" name="sViewport">
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1207, Column 1: start tag was here
<input type="hidden" value="newsletter" name="sViewport">
Error Line 1208, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
<input type="hidden" value="1" name="subscribeToNewsletter">
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1208, Column 1: start tag was here
<input type="hidden" value="1" name="subscribeToNewsletter">
Error Line 1209, Column 128: end tag for "input" omitted, but OMITTAG NO was specified
…focus="this.value='';" class="start_newsletter" id="txtmail" name="newsletter">
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1209, Column 1: start tag was here
<input type="text" value="Ihre eMail-Adresse" onfocus="this.value='';" class="s…
Error Line 1210, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
<input type="submit" value="Eintragen" class="button_newsletter">
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1210, Column 1: start tag was here
<input type="submit" value="Eintragen" class="button_newsletter">
Error Line 1213, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
</ul>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Info Line 1203, Column 1: start tag was here
<div style="background-color: #eee;height:110px;width:185px;border: 1px solid #…
[/quote]
Viele Grüße
Rainer
