Validation Output: 11 Errors

1. Line 272, Column 121: document type does not allow element "em" here; assuming missing "li" start-tag

   …itle"><h3>Seminare</h3></div><ul><em>Aktuell keine Veranstaltungen</em></ul><

   ✉

2. Line 272, Column 160: end tag for "li" omitted, but OMITTAG NO was specified

   …tuell keine Veranstaltungen</em></ul></div><div id="phpbb-topics" class="widg

   ✉

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

3. Line 272, Column 117: start tag was here

   …et-title"><h3>Seminare</h3></div><ul><em>Aktuell keine Veranstaltungen</em></

4. Line 357, Column 123: cannot generate system identifier for general entity "title"

   …p%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&title=Stahl%20auf%20Stahl" title="Diggita

   ✉

   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.

5. Line 357, Column 123: general entity "title" not defined and no default entity

   …p%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&title=Stahl%20auf%20Stahl" title="Diggita

   ✉

   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 357, Column 128: reference not terminated by REFC delimiter

   …2F%2Fwww.stahlaufstahl.de%2Fwr&title=Stahl%20auf%20Stahl" title="Diggita"><im

   ✉

   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.

7. Line 357, Column 128: reference to external entity in attribute value

   …2F%2Fwww.stahlaufstahl.de%2Fwr&title=Stahl%20auf%20Stahl" title="Diggita"><im

   ✉

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

8. Line 357, Column 128: reference to entity "title" for which no system identifier could be generated

   …2F%2Fwww.stahlaufstahl.de%2Fwr&title=Stahl%20auf%20Stahl" title="Diggita"><im

   ✉

   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.

9. Line 357, Column 121: entity was defined here

   …ttp%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&title=Stahl%20auf%20Stahl" title="Diggi

10. Line 369, Column 117: cannot generate system identifier for general entity "t"

    …p%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=Stahl%20auf%20Stahl" title="MOB"><img s

    ✉

    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.

11. Line 369, Column 117: general entity "t" not defined and no default entity

    …p%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=Stahl%20auf%20Stahl" title="MOB"><img s

    ✉

    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.

12. Line 369, Column 118: reference not terminated by REFC delimiter

    …%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=Stahl%20auf%20Stahl" title="MOB"><img sr

    ✉

    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.

13. Line 369, Column 118: reference to external entity in attribute value

    …%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=Stahl%20auf%20Stahl" title="MOB"><img sr

    ✉

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

14. Line 369, Column 118: reference to entity "t" for which no system identifier could be generated

    …%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=Stahl%20auf%20Stahl" title="MOB"><img sr

    ✉

    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.

15. Line 369, Column 115: entity was defined here

    …ttp%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=Stahl%20auf%20Stahl" title="MOB"><img

16. Line 375, Column 94: cannot generate system identifier for general entity "address"

    …marks.org/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.stahlaufstahl.de

    ✉

    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.

17. Line 375, Column 94: general entity "address" not defined and no default entity

    …marks.org/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.stahlaufstahl.de

    ✉

    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.

18. Line 375, Column 101: reference not terminated by REFC delimiter

    …rg/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&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.

19. Line 375, Column 101: reference to external entity in attribute value

    …rg/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&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 '&'.

20. Line 375, Column 101: reference to entity "address" for which no system identifier could be generated

    …rg/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&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.

21. Line 375, Column 92: entity was defined here

    …timarks.org/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.stahlaufstahl.

22. Line 357, Column > 80: XML Parsing Error: EntityRef: expecting ';'

    …f="http://www.diggita.it/submit.php?url=http%3A%2F%2Fwww.stahlaufstahl.de%2Fw…

    ✉

23. Line 369, Column > 80: XML Parsing Error: EntityRef: expecting ';'

    …f="http://www.mob.com/share.php?u=http%3A%2F%2Fwww.stahlaufstahl.de%2Fwr&t=St…

    ✉

24. Line 375, Column > 80: XML Parsing Error: EntityRef: expecting ';'

    …f="http://ratimarks.org/bookmarks.php/?action=add&address=http%3A%2F%2Fwww.st…

    ✉

↑ Top