• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Website for evolution 8.0

HappyFeet

HappyFeet

New Member
Joined
Nov 8, 2012
Messages
244
Reaction score
3
Location
Netherlands
im trying to re-up my old server again ( 6-7 years ago) I saved everything but I have same errors on the site.
server: Based on Evolutions Version 0.7.8 based on OTServ SVN Version 0.6.0
site: I really dont know anymore

w8tgrn.png

line 3 and 4:
$acc_logged = $_SESSION['account'];
$pass_logged = $_SESSION['password'];
I am sure these are good.

5exwye.png

line 76, 77 ,78 and 79:
//show source request
if($_REQUEST['action']=='source'){
highlight_file(__FILE__);
}

14mud8l.png

line 1402 :
?>

2vuek9u.png

line 456:
case "password":

Is this because of the new xampp php?
 
Sort by date Sort by votes
  1. error.png
    Line 1, Column 1: no document type declaration; will parse without validation
    <br />
    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  2. warning.png
    Line 1, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  3. warning.png
    Line 2, Column 113: NET-enabling start-tag requires SHORTTAG YES
    …count in <b>D:\xampp\htdocs\Mysticnation\top.inc.php</b> on line <b>3</b><br />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  5. warning.png
    Line 4, Column 114: NET-enabling start-tag requires SHORTTAG YES
    …sword in <b>D:\xampp\htdocs\Mysticnation\top.inc.php</b> on line <b>4</b><br />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  6. error.png
    Line 5, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
  7. warning.png
    Line 10, Column 72: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
  8. warning.png
    Line 24, Column 32: NET-enabling start-tag requires SHORTTAG YES
    <img alt="" src="img/logo.gif" />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
  9. warning.png
    Line 130, Column 168: cannot generate system identifier for general entity "amp"
    …css-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/ch…

    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 "&amp;" (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 &aelig; 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.
  10. error.png
    Line 130, Column 168: general entity "amp" not defined and no default entity
    …css-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/ch…

    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.
  11. error.png
    Line 130, Column 171: reference to entity "amp" for which no system identifier could be generated
    …-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/check…

    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. info.png
    Line 130, Column 167: entity was defined here
    …/css-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/c…
 
Upvote 0 Downvote
ricotje1 said:
  1. error.png
    Line 1, Column 1: no document type declaration; will parse without validation
    <br />
    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  2. warning.png
    Line 1, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  3. warning.png
    Line 2, Column 113: NET-enabling start-tag requires SHORTTAG YES
    …count in <b>D:\xampp\htdocs\Mysticnation\top.inc.php</b> on line <b>3</b><br />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  5. warning.png
    Line 4, Column 114: NET-enabling start-tag requires SHORTTAG YES
    …sword in <b>D:\xampp\htdocs\Mysticnation\top.inc.php</b> on line <b>4</b><br />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  6. error.png
    Line 5, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
  7. warning.png
    Line 10, Column 72: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
  8. warning.png
    Line 24, Column 32: NET-enabling start-tag requires SHORTTAG YES
    <img alt="" src="img/logo.gif" />
    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
  9. warning.png
    Line 130, Column 168: cannot generate system identifier for general entity "amp"
    …css-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/ch…

    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 "&amp;" (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 &aelig; 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.
  10. error.png
    Line 130, Column 168: general entity "amp" not defined and no default entity
    …css-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/ch…

    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.
  11. error.png
    Line 130, Column 171: reference to entity "amp" for which no system identifier could be generated
    …-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/check…

    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. info.png
    Line 130, Column 167: entity was defined here
    …/css-validator/check/referer">CSS</a> &amp; <a href="http://validator.w3.org/c…
Click to expand...

Uhm, send me your skype in PM i'll add you. We go thru each error.
 
Upvote 0 Downvote

Similar threads

tibera
  • Question
Mounts not working in Sabrehaven Base
Replies
2
Views
419
tibera
tibera
Back
Top