Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 137,
Column 92:
cannot generate system identifier for general entity "seitentyp"
…t=cmp.ccc.seitenstruktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56…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 137,
Column 92:
general entity "seitentyp" not defined and no default entity
…t=cmp.ccc.seitenstruktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56…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 137,
Column 101:
reference to entity "seitentyp" for which no system identifier could be generated
….seitenstruktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら<…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 137,
Column 91:
entity was defined here
…nt=cmp.ccc.seitenstruktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=5……ruktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい…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 137,
Column 110:
general entity "pk" not defined and no default entity
…ruktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい…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 137,
Column 112:
reference to entity "pk" for which no system identifier could be generated
…ktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい]<…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 137,
Column 109:
entity was defined here
…truktur.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さ……r.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい]</li>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 137,
Column 119:
general entity "concordeid" not defined and no default entity
…r.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい]</li>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 137,
Column 129:
reference to entity "concordeid" for which no system identifier could be generated
…r.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい]</li>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 137,
Column 118:
entity was defined here
…r.detailseiten&seitentyp=produkt&pk=51171&concordeid=56004">こちら</a>をご覧下さい]</li></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.
