Moin Markus
Ich habe den Block mal auf meiner Testseite (ohne den Block 100% valide) eingebaut und bei der Validierung bekomme ich das hier:
Validation Output: 5 Errors
1. Error Line 232, Column 425: end tag for "table" which is not finished
…<table border="0" width="100%"></table></td></tr></table></td><td width="50%" …
✉
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.
2. Error Line 232, Column 789: end tag for "table" which is not finished
…<table border="0" width="100%"></table></td></tr></table></td></tr></table><br…
✉
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.
3. Warning Line 232, Column 960: cannot generate system identifier for general entity "l_op"
…p;<a href="modules.php?name=Web_Links&l_op=AddLink">Neuen Link einschicken</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.
4. Error Line 232, Column 960: general entity "l_op" not defined and no default entity
…p;<a href="modules.php?name=Web_Links&l_op=AddLink">Neuen Link einschicken</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.
5. Warning Line 232, Column 964: reference not terminated by REFC delimiter
… href="modules.php?name=Web_Links&l_op=AddLink">Neuen Link einschicken</a>&nbs…
✉
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.
6. Warning Line 232, Column 964: reference to external entity in attribute value
… href="modules.php?name=Web_Links&l_op=AddLink">Neuen Link einschicken</a>&nbs…
✉
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 '&'.
7. Error Line 232, Column 964: reference to entity "l_op" for which no system identifier could be generated
… href="modules.php?name=Web_Links&l_op=AddLink">Neuen Link einschicken</a>&nbs…
✉
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. Info Line 232, Column 959: entity was defined here
…sp;<a href="modules.php?name=Web_Links&l_op=AddLink">Neuen Link einschicken</a…
9. Error Line 232, Column 80: EntityRef: expecting ';'
… cellpadding="0" cellspacing="2" width="100%"><tr><td width="50%" align="cente…
Ich hoffe du kannst damit was anfangen.
Gruß
martin b
pragmaMx Support Forum
