Validation Output: 10 Errors

1. Line 877, Column 144: cannot generate system identifier for general entity "size"

   …%20Recht%20Kanzlei%20Update-Mandant&size=l" alt=""></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.

2. Line 877, Column 144: general entity "size" not defined and no default entity

   …%20Recht%20Kanzlei%20Update-Mandant&size=l" alt=""></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.

3. Line 877, Column 148: reference not terminated by REFC delimiter

   …echt%20Kanzlei%20Update-Mandant&size=l" alt=""></a>

   ✉

   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.

4. Line 877, Column 148: reference to external entity in attribute value

   …echt%20Kanzlei%20Update-Mandant&size=l" alt=""></a>

   ✉

   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 '&'.

5. Line 877, Column 148: reference to entity "size" for which no system identifier could be generated

   …echt%20Kanzlei%20Update-Mandant&size=l" alt=""></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.

6. Line 877, Column 142: entity was defined here

   …IT%20Recht%20Kanzlei%20Update-Mandant&size=l" alt=""></a>

7. Line 877, Column 162: end tag for "img" omitted, but OMITTAG NO was specified

   …%20Update-Mandant&size=l" alt=""></a>

   ✉

   You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

8. Line 877, Column 51: start tag was here

   …//www.fair-e-com.de" target="_blank"><img src="http://www.fair-e-com.de/logo/

9. Line 1376, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

   <p>&nbsp;</p>

   ✉

   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>").

10. Line 877, Column > 80: XML Parsing Error: EntityRef: expecting ';'

    …_blank"><img src="http://www.fair-e-com.de/logo/logo.php?name=IT%20Recht%20Ka…

    ✉

11. Line 877, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 877 and a

    …_blank"><img src="http://www.fair-e-com.de/logo/logo.php?name=IT%20Recht%20Ka…

    ✉

12. Line 975, Column 6: XML Parsing Error: Opening and ending tag mismatch: a line 877 and div

    </div>

    ✉

13. Line 2034, Column 25: XML Parsing Error: Opening and ending tag mismatch: div line 340 and body

    </div></div></div></body></html>

    ✉

14. Line 2034, Column 32: XML Parsing Error: Opening and ending tag mismatch: body line 293 and html

    </div></div></div></body></html>

    ✉

15. Line 2034, Column 32: XML Parsing Error: Premature end of data in tag html line 5

    </div></div></div></body></html>

    ✉

↑ Top