Clansphere :: FREE Clan Content Management System

1. Error Line 14, Column 2: character data is not allowed here

{clansphere:navmeta}


You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
* putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
* forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
* using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

---

2. Warning Line 68, Column 66: cannot generate system identifier for general entity "action"

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

3. Error Line 68, Column 66: general entity "action" not defined and no default entity

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

4. Warning Line 68, Column 72: reference not terminated by REFC delimiter

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

5. Warning Line 68, Column 72: reference to external entity in attribute value

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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

---

6. Error Line 68, Column 72: reference to entity "action" for which no system identifier could be generated

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

7. Info Line 68, Column 65: entity was defined here

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>

---

8. Warning Line 68, Column 78: cannot generate system identifier for general entity "id"

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

9. Error Line 68, Column 78: general entity "id" not defined and no default entity

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

10. Warning Line 68, Column 80: reference not terminated by REFC delimiter

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

11. Warning Line 68, Column 80: reference to external entity in attribute value

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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

---

12. Error Line 68, Column 80: reference to entity "id" for which no system identifier could be generated

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>


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.

---

13. Info Line 68, Column 77: entity was defined here

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>

---

14. Warning Line 75, Column 72: reference not terminated by REFC delimiter

…left"><a class="button" href="?mod=static&action=view&id=1">BF2 Infos</a></div>


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.

---

15. Warning Line 75, Column 72: reference to external entity in attribute value

…left"><a class="button" href="?mod=static&action=view&id=1">BF2 Infos</a></div>


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

---

16. Error Line 75, Column 72: reference to entity "action" for which no system identifier could be generated

…left"><a class="button" href="?mod=static&action=view&id=1">BF2 Infos</a></div>


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.

---

17. Info Line 68, Column 65: entity was defined here

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>

---

18. Warning Line 75, Column 80: reference not terminated by REFC delimiter

…left"><a class="button" href="?mod=static&action=view&id=1">BF2 Infos</a></div>


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. Warning Line 75, Column 80: reference to external entity in attribute value

…left"><a class="button" href="?mod=static&action=view&id=1">BF2 Infos</a></div>


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. Error Line 75, Column 80: reference to entity "id" for which no system identifier could be generated

…left"><a class="button" href="?mod=static&action=view&id=1">BF2 Infos</a></div>


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. Info Line 68, Column 77: entity was defined here

…eft"><a class="button" href="?mod=static&action=view&id=2">COD4 Infos</a></div>

|

1. Error Line 14, Column 2: character data is not allowed here

{clansphere:navmeta}


You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
* putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
* forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
* using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

|

The document located at <http://epg.piripiri147.server4you.de/index.php> was successfully checked as XHTML 1.0 Transitional. This means that the resource in question identified itself as "XHTML 1.0 Transitional" and that we successfully performed a formal validation using an SGML, HTML5 and/or XML Parser(s) (depending on the markup language used).
"valid" Icon(s) on your Web page

To show your readers that you have taken the care to create an interoperable Web page, you may display this icon on any page that validates. Here is the HTML you could use to add this icon to your Web page:
Valid XHTML 1.0 Transitional

<p>
<a href="http://validator.w3.org/check?uri=referer"><img
src="http://www.w3.org/Icons/valid-xhtml10"
alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a>
</p>


A full list of icons, with links to alternate formats and colors, is available: If you like, you can download a copy of the icons to keep in your local web directory, and change the HTML fragment above to reference your local image rather than the one on this server.
Linking to this result

If you would like to create a link to this page (i.e., this validation result) to make it easier to revalidate this page in the future or to allow others to validate your page, the URI is <http://validator.w3.org/check?uri=http%3A%2F%2Fepg.piripiri147.server4you.de%2Findex.php> (or you can just add the current page to your bookmarks or hotlist).
Validating CSS Style Sheets

If you use CSS in your document, you can check it using the W3C CSS Validation Service.

|

|

|