comics-empire.com

comics-empire.com has Alexa Rank 802.620 and Google Page Rank is 0

Display Widget for this domain on your website. Click Here
This data was last updated from 20-03-2013 07:29:25  (update).

Overview Info

  • Domain Name
    comics-empire.com
  • Favicon
  • Alexa Rank
    #802620
  • Google Page Rank
    PR 0
  • Ip Address
    88.214.232.55
  • Page Size
    33.4 KB
  • Images
    0 GIF, 53 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 0 0 0 0 0

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    88.214.232.55
  • Domain Age
    1 Years, 8 Months, 21 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from comics-empire.com.

HTML Analysis

  • server: nginx
  • date: Wed, 20 Mar 2013 19:29:22 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for comics-empire.com

DNS Analysis


DNS servers
ns10.boysinsauna.com [88.214.232.52]
ns20.boysinsauna.com [88.214.232.52]


DNS Records

Answer records
comics-empire.com A 88.214.232.55 10800s
comics-empire.com SOA
server: ns10.boysinsauna.com
email: root@comics-empire.com
serial: 2007010105
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
10800s
comics-empire.com NS  ns10.boysinsauna.com 10800s
comics-empire.com NS  ns20.boysinsauna.com 10800s
comics-empire.com MX
preference: 10
exchange: mx2.boysinsauna.com
10800s

Authority records

Additional records

IP 88.214.232.55 Analysis

  • Country Code
    GB
  • Country Code3
    GBR
  • Country Name
    United Kingdom
  • City
    EU
  • Continent Code
    54° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 88.214.232.55

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 193 Errors
  • 139 Warnings
Ratio Text/Html
  • 0.6702211574980279
Message Error
  • Error Line 10, Column 80: required attribute "type" not specified
    …rc="https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 11, Column 86: required attribute "type" not specified
    …tps://ajax.googleapis.com/ajax/libs/jqueryui/1.8.15/jquery-ui.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 13, Column 59: required attribute "type" not specified
        <script src="/js/jquery-tooltip/jquery.tooltip.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 14, Column 33: required attribute "type" not specified
         <script src="/_inc/_inc.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 18, Column 12: there is no attribute "name"
    <META name="description" content="Comics Empire is full of all that cartoon por…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 18, Column 34: there is no attribute "content"
    <META name="description" content="Comics Empire is full of all that cartoon por…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 18, Column 172: element "META" undefined
    …toon hentai favourite heroes you always wanted to see in cartoon sex comcics"> 

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 19, Column 66: element "META" undefined
    <META name="keywords" content="cartoon sex comics, comics empire">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 25, Column 57: required attribute "type" not specified
    	<script src="http://toons-empire.com/network/script.js"></script> 

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 28, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 19, Column 1: start tag was here
    <META name="keywords" content="cartoon sex comics, comics empire">
  • Error Line 28, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 18, Column 1: start tag was here
    <META name="description" content="Comics Empire is full of all that cartoon por…
  • Error Line 28, Column 7: end tag for "head" which is not finished
    </head>

    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.

  • Error Line 32, Column 153: required attribute "alt" not specified
    …s-empire.com/network/toons-empire.png" title="Cartoon Sex Pictures" /></a></li>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 33, Column 161: required attribute "alt" not specified
    …e.com/network/celebs-empire.png" title="Naked Celebrities Pictures" /></a></li>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 34, Column 140: character "&" is the first character of a delimiter but occurred as data
    …pire.com/network/comics-empire.png" title="Cartoon & Hentai Comics" /></a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 34, Column 158: required attribute "alt" not specified
    …pire.com/network/comics-empire.png" title="Cartoon & Hentai Comics" /></a></li>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 35, Column 151: character "&" is the first character of a delimiter but occurred as data
    …etwork/dickgirls-cartoons.png" title="Futanari & DickGirl Pictures" /></a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 35, Column 173: required attribute "alt" not specified
    …etwork/dickgirls-cartoons.png" title="Futanari & DickGirl Pictures" /></a></li>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 96, Column 38: required attribute "type" not specified
            <script language="javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 146, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<form action=http://comics-empire.com/index.php?act=register&finish method=pos…
  • Error Line 146, Column 21: NET-enabling start-tag not immediately followed by null end-tag
    	<form action=http://comics-empire.com/index.php?act=register&finish method=pos…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Warning Line 146, Column 63: cannot generate system identifier for general entity "finish"
    …form action=http://comics-empire.com/index.php?act=register&finish method=post>

    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.

  • Error Line 146, Column 63: general entity "finish" not defined and no default entity
    …form action=http://comics-empire.com/index.php?act=register&finish method=post>

    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.

  • Warning Line 146, Column 69: reference not terminated by REFC delimiter
    …form action=http://comics-empire.com/index.php?act=register&finish method=post>

    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.

  • Error Line 146, Column 69: reference to entity "finish" for which no system identifier could be generated
    …form action=http://comics-empire.com/index.php?act=register&finish method=post>

    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.

  • Info Line 146, Column 62: entity was defined here
    …form action=http://comics-empire.com/index.php?act=register&finish method=post>
  • Error Line 149, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=text name=login style="width: 360px;" value=""></label><br>
  • Error Line 149, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=text name=login style="width: 360px;" value=""></label><br>
  • Error Line 149, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type=text name=login style="width: 360px;" value=""></label><br>

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

  • Info Line 149, Column 2: start tag was here
    	<input type=text name=login style="width: 360px;" value=""></label><br>
  • Error Line 149, Column 73: end tag for "br" omitted, but OMITTAG NO was specified
    	<input type=text name=login style="width: 360px;" value=""></label><br>

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

  • Info Line 149, Column 69: start tag was here
    	<input type=text name=login style="width: 360px;" value=""></label><br>
  • Error Line 151, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=password name=password style="width: 360px;" value=""></label><br>
  • Error Line 151, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=password name=password style="width: 360px;" value=""></label><br>
  • Error Line 151, Column 75: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type=password name=password style="width: 360px;" value=""></label><br>

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

  • Info Line 151, Column 2: start tag was here
    	<input type=password name=password style="width: 360px;" value=""></label><br>
  • Error Line 151, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    	<input type=password name=password style="width: 360px;" value=""></label><br>

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

  • Info Line 151, Column 76: start tag was here
    	<input type=password name=password style="width: 360px;" value=""></label><br>
  • Error Line 153, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=text name=nickname style="width: 360px;" value=""></label><br>
  • Error Line 153, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=text name=nickname style="width: 360px;" value=""></label><br>
  • Error Line 153, Column 71: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type=text name=nickname style="width: 360px;" value=""></label><br>

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

  • Info Line 153, Column 2: start tag was here
    	<input type=text name=nickname style="width: 360px;" value=""></label><br>
  • Error Line 153, Column 76: end tag for "br" omitted, but OMITTAG NO was specified
    	<input type=text name=nickname style="width: 360px;" value=""></label><br>

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

  • Info Line 153, Column 72: start tag was here
    	<input type=text name=nickname style="width: 360px;" value=""></label><br>
  • Error Line 155, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
    …checked="checked" disabled="disabled">Agree with <a href="http://comics-empire…

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

  • Info Line 155, Column 2: start tag was here
    	<input type="checkbox" name="agree" checked="checked" disabled="disabled">Agre…
  • Warning Line 155, Column 135: cannot generate system identifier for general entity "terms"
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</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 "&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.

  • Error Line 155, Column 135: general entity "terms" not defined and no default entity
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</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.

  • Warning Line 155, Column 140: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</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.

  • Warning Line 155, Column 140: reference to external entity in attribute value
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</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 '&amp;'.

  • Error Line 155, Column 140: reference to entity "terms" for which no system identifier could be generated
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</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.

  • Info Line 155, Column 134: entity was defined here
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</a>
  • Warning Line 155, Column 158: character "&" is the first character of a delimiter but occurred as data
    …"http://comics-empire.com/?act=register&terms=1" id="tc">Terms & Conditions</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 157, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<input type=submit value="Register" style="width: 360px; height: 30px;">
  • Error Line 157, Column 74: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type=submit value="Register" style="width: 360px; height: 30px;">

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

  • Info Line 157, Column 2: start tag was here
    	<input type=submit value="Register" style="width: 360px; height: 30px;">
  • Error Line 159, Column 8: end tag for element "form" which is not open
    	</form>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 167, Column 11: ID "alarm" already defined
    	<div id="alarm">Please fill the form below:</div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 144, Column 11: ID "alarm" first defined here
    	<div id="alarm">In order to access some of website functions you must be regis…
  • Error Line 168, Column 80: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …    <form action="http://comics-empire.com/?act=remind_password" method="POST">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 169, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
          E-mail: <input type="text" name="email"><br>

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

  • Info Line 169, Column 15: start tag was here
          E-mail: <input type="text" name="email"><br>
  • Error Line 169, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
          E-mail: <input type="text" name="email"><br>

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

  • Info Line 169, Column 47: start tag was here
          E-mail: <input type="text" name="email"><br>
  • Error Line 170, Column 136: end tag for "br" omitted, but OMITTAG NO was specified
    …image_show.php?sid=34e0b11d17df2733f07c41e5239154dc" alt="CAPTCHA Image" /><br>

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

  • Info Line 170, Column 132: start tag was here
    …image_show.php?sid=34e0b11d17df2733f07c41e5239154dc" alt="CAPTCHA Image" /><br>
  • Error Line 171, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
          Code: <input type="text" name="captcha_code">

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

  • Info Line 171, Column 13: start tag was here
          Code: <input type="text" name="captcha_code">
  • Error Line 173, Column 43: end tag for "input" omitted, but OMITTAG NO was specified
          <input type="submit" value="Remind">

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

  • Info Line 173, Column 7: start tag was here
          <input type="submit" value="Remind">
  • Error Line 180, Column 21: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    		<form method="POST" action="/index.php?act=search" id="search_form" class="se…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 194, Column 14: ID "content" already defined
    				<div id="content">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 192, Column 13: ID "content" first defined here
    			<div id="content">
  • Warning Line 217, Column 79: cannot generate system identifier for general entity "id"
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</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 "&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.

  • Error Line 217, Column 79: general entity "id" not defined and no default entity
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</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.

  • Warning Line 217, Column 81: reference not terminated by REFC delimiter
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</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.

  • Warning Line 217, Column 81: reference to external entity in attribute value
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</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 '&amp;'.

  • Error Line 217, Column 81: reference to entity "id" for which no system identifier could be generated
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 226, Column 81: reference not terminated by REFC delimiter
    …           <a href="http://comics-empire.com/?act=user&id=203020">Calvinkos</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.

  • Warning Line 226, Column 81: reference to external entity in attribute value
    …           <a href="http://comics-empire.com/?act=user&id=203020">Calvinkos</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 '&amp;'.

  • Error Line 226, Column 81: reference to entity "id" for which no system identifier could be generated
    …           <a href="http://comics-empire.com/?act=user&id=203020">Calvinkos</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 235, Column 81: reference not terminated by REFC delimiter
    …            <a href="http://comics-empire.com/?act=user&id=18918">omen10000</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.

  • Warning Line 235, Column 81: reference to external entity in attribute value
    …            <a href="http://comics-empire.com/?act=user&id=18918">omen10000</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 '&amp;'.

  • Error Line 235, Column 81: reference to entity "id" for which no system identifier could be generated
    …            <a href="http://comics-empire.com/?act=user&id=18918">omen10000</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 244, Column 81: reference not terminated by REFC delimiter
    …                 <a href="http://comics-empire.com/?act=user&id=22338">HOLA</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.

  • Warning Line 244, Column 81: reference to external entity in attribute value
    …                 <a href="http://comics-empire.com/?act=user&id=22338">HOLA</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 '&amp;'.

  • Error Line 244, Column 81: reference to entity "id" for which no system identifier could be generated
    …                 <a href="http://comics-empire.com/?act=user&id=22338">HOLA</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 253, Column 81: reference not terminated by REFC delimiter
    …              <a href="http://comics-empire.com/?act=user&id=754165">jabird</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.

  • Warning Line 253, Column 81: reference to external entity in attribute value
    …              <a href="http://comics-empire.com/?act=user&id=754165">jabird</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 '&amp;'.

  • Error Line 253, Column 81: reference to entity "id" for which no system identifier could be generated
    …              <a href="http://comics-empire.com/?act=user&id=754165">jabird</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 262, Column 81: reference not terminated by REFC delimiter
    …        <a href="http://comics-empire.com/?act=user&id=549355">emogirl10152</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.

  • Warning Line 262, Column 81: reference to external entity in attribute value
    …        <a href="http://comics-empire.com/?act=user&id=549355">emogirl10152</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 '&amp;'.

  • Error Line 262, Column 81: reference to entity "id" for which no system identifier could be generated
    …        <a href="http://comics-empire.com/?act=user&id=549355">emogirl10152</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 271, Column 81: reference not terminated by REFC delimiter
    …        <a href="http://comics-empire.com/?act=user&id=874477">kundan kumar</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.

  • Warning Line 271, Column 81: reference to external entity in attribute value
    …        <a href="http://comics-empire.com/?act=user&id=874477">kundan kumar</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 '&amp;'.

  • Error Line 271, Column 81: reference to entity "id" for which no system identifier could be generated
    …        <a href="http://comics-empire.com/?act=user&id=874477">kundan kumar</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 280, Column 81: reference not terminated by REFC delimiter
    …                <a href="http://comics-empire.com/?act=user&id=873518">bimo</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.

  • Warning Line 280, Column 81: reference to external entity in attribute value
    …                <a href="http://comics-empire.com/?act=user&id=873518">bimo</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 '&amp;'.

  • Error Line 280, Column 81: reference to entity "id" for which no system identifier could be generated
    …                <a href="http://comics-empire.com/?act=user&id=873518">bimo</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 294, Column 65: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                                                            <div id=chatdiv>
  • Error Line 294, Column 72: document type does not allow element "div" here; assuming missing "li" start-tag
                                                            <div id=chatdiv>
  • Error Line 296, Column 89: required attribute "type" not specified
    …         <script src="http://comics-empire.com/_inc/JsHttpRequest.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 297, Column 36: required attribute "type" not specified
                                <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 300, Column 38: document type does not allow element "li" here
                                    //<li><em class="date">'.$str[1].'</em><img src…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 393, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
    						</ul>

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

  • Info Line 294, Column 57: start tag was here
                                                            <div id=chatdiv>
  • Warning Line 415, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=936" title="View Bulma and kids (in col…

    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.

  • Warning Line 415, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=936" title="View Bulma and kids (in col…

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

  • Error Line 415, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=936" title="View Bulma and kids (in col…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 416, Column 139: required attribute "alt" not specified
    …pload/th/e/9/the948c89d69ded175ef74ddb243fdad1e.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 419, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 419, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 419, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 421, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 421, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 421, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 427, Column 69: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=comics&id=1343" title="View Full comics comics">

    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.

  • Warning Line 427, Column 69: reference to external entity in attribute value
    …"http://comics-empire.com/?act=comics&id=1343" title="View Full comics comics">

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

  • Error Line 427, Column 69: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=comics&id=1343" title="View Full comics comics">

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 428, Column 139: required attribute "alt" not specified
    …pload/th/2/c/th2cdb3ce3c92796ff32eec291d209e151.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 431, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=4226"><img src="http://comics-empire.co…

    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.

  • Warning Line 431, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=4226"><img src="http://comics-empire.co…

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

  • Error Line 431, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=4226"><img src="http://comics-empire.co…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 433, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=4226">Dragonn</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.

  • Warning Line 433, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=4226">Dragonn</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 '&amp;'.

  • Error Line 433, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=4226">Dragonn</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 439, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=913" title="View Kim highschool comics"…

    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.

  • Warning Line 439, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=913" title="View Kim highschool comics"…

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

  • Error Line 439, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=913" title="View Kim highschool comics"…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 440, Column 139: required attribute "alt" not specified
    …pload/th/2/e/th2ec60f0fae596ca595e3868534298ebd.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 443, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=24804"><img src="http://comics-empire.c…

    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.

  • Warning Line 443, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=24804"><img src="http://comics-empire.c…

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

  • Error Line 443, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=24804"><img src="http://comics-empire.c…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 445, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=24804">sexlegacy</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.

  • Warning Line 445, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=24804">sexlegacy</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 '&amp;'.

  • Error Line 445, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=24804">sexlegacy</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 451, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=870817" title="View incest family comic…

    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.

  • Warning Line 451, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=870817" title="View incest family comic…

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

  • Error Line 451, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=870817" title="View incest family comic…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 452, Column 139: required attribute "alt" not specified
    …pload/th/7/6/th762ce427bc11a1ebc255aaf329205ff0.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 455, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=689226"><img src="http://comics-empire.…

    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.

  • Warning Line 455, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=689226"><img src="http://comics-empire.…

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

  • Error Line 455, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=689226"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 457, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=689226">zarcon-95</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.

  • Warning Line 457, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=689226">zarcon-95</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 '&amp;'.

  • Error Line 457, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=689226">zarcon-95</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 463, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=685910" title="View Jimmy Neutron comic…

    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.

  • Warning Line 463, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=685910" title="View Jimmy Neutron comic…

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

  • Error Line 463, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=685910" title="View Jimmy Neutron comic…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 464, Column 139: required attribute "alt" not specified
    …pload/th/d/0/thd094ed3b48c8e7f4198fa7873c45fad6.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 467, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 467, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 467, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 469, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 469, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 469, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 475, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=759908" title="View Tsunade hentai mang…

    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.

  • Warning Line 475, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=759908" title="View Tsunade hentai mang…

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

  • Error Line 475, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=759908" title="View Tsunade hentai mang…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 476, Column 139: required attribute "alt" not specified
    …pload/th/d/7/thd7ae2b90b25f722d5896f6a3cdbe5847.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 479, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 479, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 479, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 481, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 481, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 481, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 487, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=1172" title="View Sonic XXX project 3 c…

    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.

  • Warning Line 487, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=1172" title="View Sonic XXX project 3 c…

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

  • Error Line 487, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=1172" title="View Sonic XXX project 3 c…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 488, Column 139: required attribute "alt" not specified
    …pload/th/7/e/th7ea0f7e2001680066dec235e8b501467.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 491, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 491, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 491, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 493, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 493, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 493, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 499, Column 69: reference not terminated by REFC delimiter
    …ref="http://comics-empire.com/?act=comics&id=1963" title="View Charmed comics">

    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.

  • Warning Line 499, Column 69: reference to external entity in attribute value
    …ref="http://comics-empire.com/?act=comics&id=1963" title="View Charmed comics">

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

  • Error Line 499, Column 69: reference to entity "id" for which no system identifier could be generated
    …ref="http://comics-empire.com/?act=comics&id=1963" title="View Charmed comics">

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 500, Column 139: required attribute "alt" not specified
    …pload/th/e/4/the4c01eefd1b8191b68db89e3aaf82d4a.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 503, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 503, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 503, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 505, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 505, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 505, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 511, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=734267" title="View Winx comics 9 comic…

    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.

  • Warning Line 511, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=734267" title="View Winx comics 9 comic…

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

  • Error Line 511, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=734267" title="View Winx comics 9 comic…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 512, Column 139: required attribute "alt" not specified
    …pload/th/2/f/th2f8a3cc4522ae7965cc41f0656e5b04d.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 515, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 515, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 515, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 517, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 517, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 517, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 523, Column 69: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=668069" title="View Early parole comics…

    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.

  • Warning Line 523, Column 69: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=668069" title="View Early parole comics…

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

  • Error Line 523, Column 69: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=668069" title="View Early parole comics…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 524, Column 139: required attribute "alt" not specified
    …pload/th/d/f/thdff14cc050fac9182b63ee4bdcf28110.jpg"  width="94" height="74" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 527, Column 56: reference not terminated by REFC delimiter
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Warning Line 527, Column 56: reference to external entity in attribute value
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

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

  • Error Line 527, Column 56: reference to entity "id" for which no system identifier could be generated
    …tp://comics-empire.com/?act=profile&id=497295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 529, Column 56: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Warning Line 529, Column 56: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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 '&amp;'.

  • Error Line 529, Column 56: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=profile&id=497295">Red Gre..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 545, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=890467"><img src="http://comics-empire.…

    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.

  • Warning Line 545, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=890467"><img src="http://comics-empire.…

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

  • Error Line 545, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=890467"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 547, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=882494"><img src="http://comics-empire.…

    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.

  • Warning Line 547, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=882494"><img src="http://comics-empire.…

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

  • Error Line 547, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=882494"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 549, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=882494" title="WolvieDeadred">Wolvi..</…

    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.

  • Warning Line 549, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=882494" title="WolvieDeadred">Wolvi..</…

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

  • Error Line 549, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=882494" title="WolvieDeadred">Wolvi..</…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 555, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=783961"><img src="http://comics-empire.…

    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.

  • Warning Line 555, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=783961"><img src="http://comics-empire.…

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

  • Error Line 555, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=783961"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 557, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=496601"><img src="http://comics-empire.…

    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.

  • Warning Line 557, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=496601"><img src="http://comics-empire.…

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

  • Error Line 557, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=496601"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 559, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=496601" title="narutokid144">narut..</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.

  • Warning Line 559, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=496601" title="narutokid144">narut..</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 '&amp;'.

  • Error Line 559, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=496601" title="narutokid144">narut..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 565, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=880959"><img src="http://comics-empire.…

    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.

  • Warning Line 565, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=880959"><img src="http://comics-empire.…

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

  • Error Line 565, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=880959"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 567, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=874477"><img src="http://comics-empire.…

    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.

  • Warning Line 567, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=874477"><img src="http://comics-empire.…

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

  • Error Line 567, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=874477"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 569, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=874477" title="kundan kumar">kunda..</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.

  • Warning Line 569, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=874477" title="kundan kumar">kunda..</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 '&amp;'.

  • Error Line 569, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=874477" title="kundan kumar">kunda..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 575, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=875968"><img src="http://comics-empire.…

    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.

  • Warning Line 575, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=875968"><img src="http://comics-empire.…

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

  • Error Line 575, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=875968"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 577, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=869579"><img src="http://comics-empire.…

    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.

  • Warning Line 577, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=869579"><img src="http://comics-empire.…

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

  • Error Line 577, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=869579"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 579, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=869579" title="Half Toon Guy">Half ..</…

    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.

  • Warning Line 579, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=869579" title="Half Toon Guy">Half ..</…

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

  • Error Line 579, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=869579" title="Half Toon Guy">Half ..</…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 585, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=871796"><img src="http://comics-empire.…

    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.

  • Warning Line 585, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=871796"><img src="http://comics-empire.…

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

  • Error Line 585, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=871796"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 587, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=782752"><img src="http://comics-empire.…

    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.

  • Warning Line 587, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=782752"><img src="http://comics-empire.…

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

  • Error Line 587, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=782752"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 589, Column 53: reference not terminated by REFC delimiter
    …ef="http://comics-empire.com/?act=user&id=782752" title="Akuma8282">Akuma..</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.

  • Warning Line 589, Column 53: reference to external entity in attribute value
    …ef="http://comics-empire.com/?act=user&id=782752" title="Akuma8282">Akuma..</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 '&amp;'.

  • Error Line 589, Column 53: reference to entity "id" for which no system identifier could be generated
    …ef="http://comics-empire.com/?act=user&id=782752" title="Akuma8282">Akuma..</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 595, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=869242"><img src="http://comics-empire.…

    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.

  • Warning Line 595, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=869242"><img src="http://comics-empire.…

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

  • Error Line 595, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=869242"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 597, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=519077"><img src="http://comics-empire.…

    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.

  • Warning Line 597, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=519077"><img src="http://comics-empire.…

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

  • Error Line 597, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=519077"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 599, Column 53: reference not terminated by REFC delimiter
    …a href="http://comics-empire.com/?act=user&id=519077" title="vanolt">vanolt</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.

  • Warning Line 599, Column 53: reference to external entity in attribute value
    …a href="http://comics-empire.com/?act=user&id=519077" title="vanolt">vanolt</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 '&amp;'.

  • Error Line 599, Column 53: reference to entity "id" for which no system identifier could be generated
    …a href="http://comics-empire.com/?act=user&id=519077" title="vanolt">vanolt</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 605, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=866295"><img src="http://comics-empire.…

    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.

  • Warning Line 605, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=866295"><img src="http://comics-empire.…

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

  • Error Line 605, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=866295"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 607, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=855946"><img src="http://comics-empire.…

    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.

  • Warning Line 607, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=855946"><img src="http://comics-empire.…

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

  • Error Line 607, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=855946"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 609, Column 53: reference not terminated by REFC delimiter
    						<a href="http://comics-empire.com/?act=user&id=855946" title="$@M">$@M</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.

  • Warning Line 609, Column 53: reference to external entity in attribute value
    						<a href="http://comics-empire.com/?act=user&id=855946" title="$@M">$@M</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 '&amp;'.

  • Error Line 609, Column 53: reference to entity "id" for which no system identifier could be generated
    						<a href="http://comics-empire.com/?act=user&id=855946" title="$@M">$@M</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 615, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=818027"><img src="http://comics-empire.…

    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.

  • Warning Line 615, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=818027"><img src="http://comics-empire.…

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

  • Error Line 615, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=818027"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 617, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=10085"><img src="http://comics-empire.c…

    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.

  • Warning Line 617, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=10085"><img src="http://comics-empire.c…

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

  • Error Line 617, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=10085"><img src="http://comics-empire.c…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 619, Column 53: reference not terminated by REFC delimiter
    …<a href="http://comics-empire.com/?act=user&id=10085" title="yuri23">yuri23</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.

  • Warning Line 619, Column 53: reference to external entity in attribute value
    …<a href="http://comics-empire.com/?act=user&id=10085" title="yuri23">yuri23</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 '&amp;'.

  • Error Line 619, Column 53: reference to entity "id" for which no system identifier could be generated
    …<a href="http://comics-empire.com/?act=user&id=10085" title="yuri23">yuri23</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 625, Column 74: reference not terminated by REFC delimiter
    …ttp://comics-empire.com/?act=comics&id=814439"><img src="http://comics-empire.…

    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.

  • Warning Line 625, Column 74: reference to external entity in attribute value
    …ttp://comics-empire.com/?act=comics&id=814439"><img src="http://comics-empire.…

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

  • Error Line 625, Column 74: reference to entity "id" for which no system identifier could be generated
    …ttp://comics-empire.com/?act=comics&id=814439"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 627, Column 53: reference not terminated by REFC delimiter
    …"http://comics-empire.com/?act=user&id=259797"><img src="http://comics-empire.…

    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.

  • Warning Line 627, Column 53: reference to external entity in attribute value
    …"http://comics-empire.com/?act=user&id=259797"><img src="http://comics-empire.…

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

  • Error Line 627, Column 53: reference to entity "id" for which no system identifier could be generated
    …"http://comics-empire.com/?act=user&id=259797"><img src="http://comics-empire.…

    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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Warning Line 629, Column 53: reference not terminated by REFC delimiter
    …			<a href="http://comics-empire.com/?act=user&id=259797" title="ucoz">ucoz</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.

  • Warning Line 629, Column 53: reference to external entity in attribute value
    …			<a href="http://comics-empire.com/?act=user&id=259797" title="ucoz">ucoz</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 '&amp;'.

  • Error Line 629, Column 53: reference to entity "id" for which no system identifier could be generated
    …			<a href="http://comics-empire.com/?act=user&id=259797" title="ucoz">ucoz</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.

  • Info Line 217, Column 78: entity was defined here
    …           <a href="http://comics-empire.com/?act=user&id=875569">pikamitsu</a>
  • Error Line 638, Column 27: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                <li><a target=_blank rel=nofollow href="http://xxx.famous-toons.net…
  • Error Line 638, Column 38: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                <li><a target=_blank rel=nofollow href="http://xxx.famous-toons.net…
  • Error Line 638, Column 167: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …us-toons.net/thumbs/b01056.jpg" width=120 height=160></a></li><li><a target=_b…
  • Error Line 638, Column 178: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t/thumbs/b01056.jpg" width=120 height=160></a></li><li><a target=_blank rel=no…
  • Error Line 638, Column 181: required attribute "alt" not specified
    …humbs/b01056.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofol…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 185: end tag for "img" omitted, but OMITTAG NO was specified
    …s/b01056.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofollow …

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

  • Info Line 638, Column 103: start tag was here
    …amous-toons.net?id=comics-empire.com"><img src="http://cdn1.famous-toons.net/t…
  • Error Line 638, Column 205: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …120 height=160></a></li><li><a target=_blank rel=nofollow href="http://xxx.fuc…
  • Error Line 638, Column 216: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …160></a></li><li><a target=_blank rel=nofollow href="http://xxx.fuck-toons.net…
  • Error Line 638, Column 341: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ck-toons.net/thumbs/7337b4.jpg" width=120 height=160></a></li><li><a target=_b…
  • Error Line 638, Column 352: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t/thumbs/7337b4.jpg" width=120 height=160></a></li><li><a target=_blank rel=no…
  • Error Line 638, Column 355: required attribute "alt" not specified
    …humbs/7337b4.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofol…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 359: end tag for "img" omitted, but OMITTAG NO was specified
    …s/7337b4.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofollow …

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

  • Info Line 638, Column 279: start tag was here
    ….fuck-toons.net?id=comics-empire.com"><img src="http://cdn1.fuck-toons.net/thu…
  • Error Line 638, Column 379: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …120 height=160></a></li><li><a target=_blank rel=nofollow href="http://xxx.tin…
  • Error Line 638, Column 390: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …160></a></li><li><a target=_blank rel=nofollow href="http://xxx.tiny-toons.net…
  • Error Line 638, Column 515: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ny-toons.net/thumbs/3d1fcc.jpg" width=120 height=160></a></li><li><a target=_b…
  • Error Line 638, Column 526: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t/thumbs/3d1fcc.jpg" width=120 height=160></a></li><li><a target=_blank rel=no…
  • Error Line 638, Column 529: required attribute "alt" not specified
    …humbs/3d1fcc.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofol…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 533: end tag for "img" omitted, but OMITTAG NO was specified
    …s/3d1fcc.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofollow …

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

  • Info Line 638, Column 453: start tag was here
    ….tiny-toons.net?id=comics-empire.com"><img src="http://cdn1.tiny-toons.net/thu…
  • Error Line 638, Column 553: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …120 height=160></a></li><li><a target=_blank rel=nofollow href="http://xxx.har…
  • Error Line 638, Column 564: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …160></a></li><li><a target=_blank rel=nofollow href="http://xxx.hardcore-toons…
  • Error Line 638, Column 697: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …re-toons.net/thumbs/28b75e.jpg" width=120 height=160></a></li><li><a target=_b…
  • Error Line 638, Column 708: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t/thumbs/28b75e.jpg" width=120 height=160></a></li><li><a target=_blank rel=no…
  • Error Line 638, Column 711: required attribute "alt" not specified
    …humbs/28b75e.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofol…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 715: end tag for "img" omitted, but OMITTAG NO was specified
    …s/28b75e.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofollow …

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

  • Info Line 638, Column 631: start tag was here
    …dcore-toons.net?id=comics-empire.com"><img src="http://cdn1.hardcore-toons.net…
  • Error Line 638, Column 735: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …120 height=160></a></li><li><a target=_blank rel=nofollow href="http://xxx.nud…
  • Error Line 638, Column 746: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …160></a></li><li><a target=_blank rel=nofollow href="http://xxx.nude-toons.net…
  • Error Line 638, Column 871: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …de-toons.net/thumbs/5cc8de.jpg" width=120 height=160></a></li><li><a target=_b…
  • Error Line 638, Column 882: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t/thumbs/5cc8de.jpg" width=120 height=160></a></li><li><a target=_blank rel=no…
  • Error Line 638, Column 885: required attribute "alt" not specified
    …humbs/5cc8de.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofol…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 889: end tag for "img" omitted, but OMITTAG NO was specified
    …s/5cc8de.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofollow …

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

  • Info Line 638, Column 809: start tag was here
    ….nude-toons.net?id=comics-empire.com"><img src="http://cdn1.nude-toons.net/thu…
  • Error Line 638, Column 909: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …120 height=160></a></li><li><a target=_blank rel=nofollow href="http://xxx.fre…
  • Error Line 638, Column 920: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …160></a></li><li><a target=_blank rel=nofollow href="http://xxx.fresh-toons.ne…
  • Error Line 638, Column 1047: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …sh-toons.net/thumbs/1d599d.jpg" width=120 height=160></a></li><li><a target=_b…
  • Error Line 638, Column 1058: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t/thumbs/1d599d.jpg" width=120 height=160></a></li><li><a target=_blank rel=no…
  • Error Line 638, Column 1061: required attribute "alt" not specified
    …humbs/1d599d.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofol…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 1065: end tag for "img" omitted, but OMITTAG NO was specified
    …s/1d599d.jpg" width=120 height=160></a></li><li><a target=_blank rel=nofollow …

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

  • Info Line 638, Column 984: start tag was here
    …fresh-toons.net?id=comics-empire.com"><img src="http://cdn1.fresh-toons.net/th…
  • Error Line 638, Column 1085: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …120 height=160></a></li><li><a target=_blank rel=nofollow href="http://xxx.fre…
  • Error Line 638, Column 1096: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …160></a></li><li><a target=_blank rel=nofollow href="http://xxx.fresh-toons.ne…
  • Error Line 638, Column 1223: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/cdn1.fresh-toons.net/thumbs/e51da8.jpg" width=120 height=160></a></li>			</ul>
  • Error Line 638, Column 1234: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/cdn1.fresh-toons.net/thumbs/e51da8.jpg" width=120 height=160></a></li>			</ul>
  • Error Line 638, Column 1237: required attribute "alt" not specified
    …/cdn1.fresh-toons.net/thumbs/e51da8.jpg" width=120 height=160></a></li>			</ul>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 638, Column 1241: end tag for "img" omitted, but OMITTAG NO was specified
    …/cdn1.fresh-toons.net/thumbs/e51da8.jpg" width=120 height=160></a></li>			</ul>

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

  • Info Line 638, Column 1160: start tag was here
    …fresh-toons.net?id=comics-empire.com"><img src="http://cdn1.fresh-toons.net/th…
  • Error Line 649, Column 34: required attribute "type" not specified
        <script language="javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 680, Column 22: an attribute value must be a literal unless it contains only name characters
            <form action=/?act=sm method=post>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 680, Column 38: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <form action=/?act=sm method=post>
  • Error Line 681, Column 49: end tag for "br" omitted, but OMITTAG NO was specified
            <b>Need support? Have some question?<br>

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

  • Info Line 681, Column 45: start tag was here
            <b>Need support? Have some question?<br>
  • Error Line 682, Column 79: end tag for "br" omitted, but OMITTAG NO was specified
            Want to be moderator or add new heroes, tv-show or something else?<br>

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

  • Info Line 682, Column 75: start tag was here
            Want to be moderator or add new heroes, tv-show or something else?<br>
  • Error Line 683, Column 71: end tag for "br" omitted, but OMITTAG NO was specified
    …e, please send us your working e-mail<br>if you need direct contact</b><br><br>

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

  • Info Line 683, Column 67: start tag was here
    …re, please send us your working e-mail<br>if you need direct contact</b><br><b…
  • Error Line 683, Column 105: end tag for "br" omitted, but OMITTAG NO was specified
    …e, please send us your working e-mail<br>if you need direct contact</b><br><br>

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

  • Info Line 683, Column 101: start tag was here
    …e, please send us your working e-mail<br>if you need direct contact</b><br><br>
  • Error Line 683, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …e, please send us your working e-mail<br>if you need direct contact</b><br><br>

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

  • Info Line 683, Column 105: start tag was here
    …e, please send us your working e-mail<br>if you need direct contact</b><br><br>
  • Error Line 684, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            Your email: <input size=30 type=text name="xemail"><br>
  • Error Line 684, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            Your email: <input size=30 type=text name="xemail"><br>
  • Error Line 684, Column 60: end tag for "input" omitted, but OMITTAG NO was specified
            Your email: <input size=30 type=text name="xemail"><br>

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

  • Info Line 684, Column 21: start tag was here
            Your email: <input size=30 type=text name="xemail"><br>
  • Error Line 684, Column 64: end tag for "br" omitted, but OMITTAG NO was specified
            Your email: <input size=30 type=text name="xemail"><br>

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

  • Info Line 684, Column 60: start tag was here
            Your email: <input size=30 type=text name="xemail"><br>
  • Error Line 685, Column 43: end tag for "br" omitted, but OMITTAG NO was specified
            Your message (must be filled):<br>

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

  • Info Line 685, Column 39: start tag was here
            Your message (must be filled):<br>
  • Error Line 686, Column 24: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <textarea cols=40 rows=7 name="xmsg"></textarea><br>
  • Error Line 686, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <textarea cols=40 rows=7 name="xmsg"></textarea><br>
  • Error Line 686, Column 61: end tag for "br" omitted, but OMITTAG NO was specified
            <textarea cols=40 rows=7 name="xmsg"></textarea><br>

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

  • Info Line 686, Column 57: start tag was here
            <textarea cols=40 rows=7 name="xmsg"></textarea><br>
  • Error Line 687, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                    <input type=submit value="Send">
  • Error Line 687, Column 49: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type=submit value="Send">

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

  • Info Line 687, Column 17: start tag was here
                    <input type=submit value="Send">
  • Error Line 688, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <input type=hidden name=xref value="">
  • Error Line 688, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <input type=hidden name=xref value="">
  • Error Line 688, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
            <input type=hidden name=xref value="">

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

  • Info Line 688, Column 9: start tag was here
            <input type=hidden name=xref value="">

Visitor Analysis

Daily Visitor
  • 140 visits
Daily Visitor

In Page Analysis