I see Leo mentions codes in the neighboring thread...
I tried to validate this page (via validator.w3.org), not sure if the report is of any interest or value but here it is:
Validation Output: 93 Errors
✉
Line 22, Column 29: character "&" is the first character of a delimiter but occurred as data
* Style: 'Diii.Net Homepage & Gallery'; Style ID: 32
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 403, Column 67: character "&" is the first character of a delimiter but occurred as data
…"application/rss+xml" title="Diablo 3 & Diablo 2 Forums @ Diablo: IncGamers RS…
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 406, Column 18: character "&" is the first character of a delimiter but occurred as data
<title>Diablo 3 & Diablo 2 Forums @ Diablo: IncGamers - Powered by vBulletin</…
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 507, Column 90: character "&" is the first character of a delimiter but occurred as data
…ttp://diablo.incgamers.com/forums/payments.php">Donate & Be a Pal</a></td></tr>
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 525, Column 33: there is no attribute "href"
<tr><td class="leftnav"><A href="http://www.diablowiki.net/Category:Interface">…
✉
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.
Line 525, Column 79: element "A" undefined
…tnav"><A href="http://www.diablowiki.net/Category:Interface">Interface</a></td>
✉
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).
Line 525, Column 92: end tag for element "a" which is not open
…tnav"><A href="http://www.diablowiki.net/Category:Interface">Interface</a></td>
✉
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.
Line 525, Column 97: end tag for "A" omitted, but OMITTAG NO was specified
…tnav"><A href="http://www.diablowiki.net/Category:Interface">Interface</a></td>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 525, Column 25: start tag was here
<tr><td class="leftnav"><A href="http://www.diablowiki.net/Category:Interface">…
Line 575, Column 214: an attribute value literal can occur in an attribute specification list only after a VI delimiter
…-%20End%20custom%20code%20--%3e%3ctr%3e%3ctd%20align=center%20class=" leftnav">
✉
Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".
Line 578, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
<br><br><center>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 578, Column 1: start tag was here
<br><br><center>
Line 578, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
<br><br><center>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 578, Column 5: start tag was here
<br><br><center>
Line 579, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
…orum perks" width="73" height="33"></a><font color="#DCDFE4" size="1" face="Ve…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 579, Column 59: start tag was here
…lo.incgamers.com/forums/payments.php"><img src="http://diablo.incgamers.com/im…
Line 579, Column 270: end tag for "br" omitted, but OMITTAG NO was specified
…" width="73" height="33"></a><font color="#DCDFE4" size="1" face="Verdana"><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 ">".
Line 579, Column 266: start tag was here
…" width="73" height="33"></a><font color="#DCDFE4" size="1" face="Verdana"><br>
Line 580, Column 57: end tag for "br" omitted, but OMITTAG NO was specified
…ze="1" face="Verdana">Help Support<br> <a href="http://diablo.incgamers.com/fo…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 580, Column 53: start tag was here
…t size="1" face="Verdana">Help Support<br> <a href="http://diablo.incgamers.co…
Line 581, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
<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 ">".
Line 581, Column 1: start tag was here
<br>
Line 583, Column 140: end tag for "img" omitted, but OMITTAG NO was specified
….png" border="0" style="margin-bottom:5px;" alt="Your Diablo 3 News Feed "></a>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 583, Column 1: start tag was here
<img src="http://diablo.incgamers.com/forums/images/icons/rss.png" border="0" s…
Line 586, Column 144: end tag for "img" omitted, but OMITTAG NO was specified
….png" border="0" style="margin-bottom:5px;" alt="Diablo: IncGamers Tweets"></a>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 586, Column 1: start tag was here
<img src="http://diablo.incgamers.com/forums/images/icons/twitter.png" border="…
Line 589, Column 147: end tag for "img" omitted, but OMITTAG NO was specified
…ng" border="0" style="margin-bottom:5px;" alt="Diablo: IncGamers Facebook"></a>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 589, Column 1: start tag was here
<img src="http://diablo.incgamers.com/forums/images/icons/facebook.png" border=…
Line 592, Column 128: character "&" is the first character of a delimiter but occurred as data
…s.png" border="0" style="margin-bottom:5px;" alt="Blizzard Posts & Tweets"></a>
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 592, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
…s.png" border="0" style="margin-bottom:5px;" alt="Blizzard Posts & Tweets"></a>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 592, Column 1: start tag was here
<img src="http://diablo.incgamers.com/forums/images/icons/blues.png" border="0"…
Line 594, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
<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 ">".
Line 594, Column 1: start tag was here
<br>
Line 597, Column 141: end tag for "img" omitted, but OMITTAG NO was specified
…ube.png" border="0" style="margin-bottom:5px;" alt="Watch Diablo 3 Videos"></a>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 597, Column 1: start tag was here
<img src="http://diablo.incgamers.com/forums/images/icons/youtube.png" border="…
Line 600, Column 143: character "&" is the first character of a delimiter but occurred as data
…der="0" style="margin-bottom:5px;" alt="Videogame News, Editorial & Video"></a>
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 600, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
…der="0" style="margin-bottom:5px;" alt="Videogame News, Editorial & Video"></a>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 600, Column 1: start tag was here
<img src="http://diablo.incgamers.com/forums/images/icons/incgamers.png" border…
Line 603, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
</td>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 580, Column 148: start tag was here
…blo.incgamers.com/forums/payments.php">Diablo: IncGamers</a></font></b><center>
Line 603, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
</td>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 578, Column 9: start tag was here
<br><br><center>
Line 651, Column 335: there is no attribute "allowTransparency"
…argin-left: 10px; color: #821E1E;" allowTransparency="true"></******></td></tr>
✉
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.
Line 665, Column 73: required attribute "alt" not specified
<td width="22" valign="top"><img src="clear.gif" border="0" width="22" />
✉
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>.
Line 671, Column 166: end tag for "br" omitted, but OMITTAG NO was specified
…embers. Please do not post links or information about hacking/warez/cheats.<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 ">".
Line 671, Column 162: start tag was here
…embers. Please do not post links or information about hacking/warez/cheats.<br>
Line 714, Column 191: character "&" is the first character of a delimiter but occurred as data
…"" border="0" /></a> <strong>Diablo 3 & Diablo 2 Forums @ Diablo: IncGamers</s…
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 984, Column 81: an attribute value must be a literal unless it contains only name characters
…<a href="member.php?u=359"><font color=#4160FF>Elly</font></a> </div></td>
✉
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.
Line 1018, Column 81: an attribute value must be a literal unless it contains only name characters
…<a href="member.php?u=476"><font color=#4160FF>Flux</font></a> </div></td>
✉
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.
Line 1076, Column 81: an attribute value must be a literal unless it contains only name characters
…<a href="member.php?u=359"><font color=#4160FF>Elly</font></a> </div></td>
✉
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.
Line 1110, Column 83: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=64392"><font color=#168A19>Dacar92</font></a> </div></…
✉
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.
Line 1144, Column 83: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=64392"><font color=#168A19>Dacar92</font></a> </div></…
✉
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.
Line 1212, Column 82: an attribute value must be a literal unless it contains only name characters
… href="member.php?u=3534"><font color=#168A19>Mad Mantis</font></a> </div…
✉
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.
Line 1348, Column 84: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=320812"><font color=#168A19>Holyknight3000</font></a> <…
✉
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.
Line 1457, Column 84: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=102560"><font color=#168A19>Orphan</font></a> </div></t…
✉
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.
Line 1491, Column 81: an attribute value must be a literal unless it contains only name characters
…<a href="member.php?u=359"><font color=#4160FF>Elly</font></a> </div></td>
✉
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.
Line 1559, Column 84: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=172198"><font color=#168A19>WarlockCC</font></a> </div>…
✉
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.
Line 1627, Column 81: an attribute value must be a literal unless it contains only name characters
…<a href="member.php?u=359"><font color=#4160FF>Elly</font></a> </div></td>
✉
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.
Line 1661, Column 83: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=86468"><font color=#168A19>Dredd</font></a>, <a href="membe…
✉
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.
Line 1661, Column 150: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=41251"><font color=#168A19>LorveN</font></a> </div></t…
✉
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.
Line 1753, Column 81: an attribute value must be a literal unless it contains only name characters
…a href="member.php?u=778"><font color=#029105>Xora</font></a>, <a href="member…
✉
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.
Line 1753, Column 147: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=42697"><font color=#029105>krischan</font></a> </div><…
✉
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.
Line 1787, Column 84: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=140565"><font color=#168A19>gorash</font></a>, <a href="memb…
✉
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.
Line 1787, Column 153: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=171898"><font color=#168A19>spiffymcbang</font></a> </d…
✉
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.
Line 1821, Column 81: an attribute value must be a literal unless it contains only name characters
…a href="member.php?u=179"><font color=#029105>Shaperla</font></a> </div><…
✉
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.
Line 1855, Column 82: an attribute value must be a literal unless it contains only name characters
… href="member.php?u=1038"><font color=#029105>ZappaFan</font></a> </div><…
✉
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.
Line 1889, Column 84: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=172655"><font color=#168A19>Thyiad</font></a> </div></t…
✉
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.
Line 2015, Column 83: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=35586"><font color=#168A19>Uncle_Mike</font></a> </div…
✉
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.
Line 2049, Column 83: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=64392"><font color=#168A19>Dacar92</font></a> </div></…
✉
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.
Line 2117, Column 83: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=64392"><font color=#168A19>Dacar92</font></a> </div></…
✉
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.
Line 2151, Column 81: an attribute value must be a literal unless it contains only name characters
…a href="member.php?u=179"><font color=#029105>Shaperla</font></a> </div><…
✉
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.
Line 2185, Column 82: an attribute value must be a literal unless it contains only name characters
… href="member.php?u=3534"><font color=#168A19>Mad Mantis</font></a> </div…
✉
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.
Line 2219, Column 81: an attribute value must be a literal unless it contains only name characters
…a href="member.php?u=455"><font color=#168A19>HeavAngel</font></a> </div>…
✉
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.
Line 2287, Column 82: an attribute value must be a literal unless it contains only name characters
… href="member.php?u=1038"><font color=#029105>ZappaFan</font></a> </div><…
✉
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.
Line 2321, Column 84: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=172655"><font color=#168A19>Thyiad</font></a> </div></t…
✉
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.
Line 2376, Column 1047: an attribute value must be a literal unless it contains only name characters
…ref="member.php?u=102560"><font color=#168A19>Orphan</font></a>, <a href="memb…
✉
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.
Line 2376, Column 2049: an attribute value must be a literal unless it contains only name characters
… href="member.php?u=3534"><font color=#168A19>Mad Mantis</font></a>, <a href="…
✉
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.
Line 2376, Column 3173: an attribute value must be a literal unless it contains only name characters
…href="member.php?u=86468"><font color=#168A19>Dredd</font></a>, <a href="membe…
✉
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.
Line 2376, Column 3966: end tag for "img" omitted, but OMITTAG NO was specified
…ages/pal.gif" alt="DIII.Net Site Pal"><font color="#8D2EEF">zarfen</font></a>,…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 2376, Column 3905: start tag was here
…me</a>, <a href="member.php?u=145288"><img border="0" src="images/pal.gif" alt…
Line 2376, Column 4445: an attribute value must be a literal unless it contains only name characters
…a href="member.php?u=476"><font color=#4160FF>Flux</font></a>, <a href="member…
✉
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.
Line 2388, Column 13: character "&" is the first character of a delimiter but occurred as data
Diablo 3 & Diablo 2 Forums @ Diablo: IncGamers Statistics
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 2394, Column 76: character "&" is the first character of a delimiter but occurred as data
…2images/misc/stats.gif" alt="Diablo 3 & Diablo 2 Forums @ Diablo: IncGamers St…
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 2489, Column 70: character "&" is the first character of a delimiter but occurred as data
…value="32" class="" selected="selected">-- Diii.Net Homepage & Gallery</option>
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 2500, Column 52: character "&" is the first character of a delimiter but occurred as data
<a href="http://diablo.incgamers.com">Diablo 3 & 2 Forums</a> -
✉
This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 2522, Column 26: end tag for "br" omitted, but OMITTAG NO was specified
<b>Game Channels</b><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 ">".
Line 2522, Column 22: start tag was here
<b>Game Channels</b><br>
Line 2526, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://blues.incgamers.com">Blue Tracker</a><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 ">".
Line 2526, Column 70: start tag was here
<a href="http://blues.incgamers.com">Blue Tracker</a><br>
Line 2527, Column 57: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://diablo.incgamers.com">Diablo 3</a><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 ">".
Line 2527, Column 53: start tag was here
<a href="http://diablo.incgamers.com">Diablo 3</a><br>
Line 2528, Column 75: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.diablowiki.net">DiabloWiki.Net</a><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 ">".
Line 2528, Column 71: start tag was here
<a href="http://www.diablowiki.net">DiabloWiki.Net</a><br>
Line 2529, Column 61: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://guildwars.incgamers.com">GuildWars</a><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 ">".
Line 2529, Column 57: start tag was here
<a href="http://guildwars.incgamers.com">GuildWars</a><br>
Line 2530, Column 59: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://hellgate.incgamers.com">Hellgate</a><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 ">".
Line 2530, Column 55: start tag was here
<a href="http://hellgate.incgamers.com">Hellgate</a><br>
Line 2531, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://rift.incgamers.com">RIFT</a><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 ">".
Line 2531, Column 47: start tag was here
<a href="http://rift.incgamers.com">RIFT</a><br>
Line 2536, Column 42: end tag for "br" omitted, but OMITTAG NO was specified
<b>Game Channels Cont...</b><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 ">".
Line 2536, Column 38: start tag was here
<b>Game Channels Cont...</b><br>
Line 2539, Column 77: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://starcraft.incgamers.com">StarCraft 2</a><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 ">".
Line 2539, Column 73: start tag was here
<a href="http://starcraft.incgamers.com">StarCraft 2</a><br>
Line 2540, Column 71: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://starcraft.incgamers.com/wiki">StarCraft Wiki</a><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 ">".
Line 2540, Column 67: start tag was here
<a href="http://starcraft.incgamers.com/wiki">StarCraft Wiki</a><br>
Line 2541, Column 67: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.vgassist.com">VGAssist</a><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 ">".
Line 2541, Column 63: start tag was here
<a href="http://www.vgassist.com">VGAssist</a><br>
Line 2542, Column 71: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://war3.incgamers.com">Warcraft 3</a><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 ">".
Line 2542, Column 67: start tag was here
<a href="http://war3.incgamers.com">Warcraft 3</a><br>
Line 2543, Column 63: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://wow.incgamers.com">World of Warcraft</a><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 ">".
Line 2543, Column 59: start tag was here
<a href="http://wow.incgamers.com">World of Warcraft</a><br>
Line 2544, Column 72: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://wowui.incgamers.com">World of Warcraft Addons</a><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 ">".
Line 2544, Column 68: start tag was here
<a href="http://wowui.incgamers.com">World of Warcraft Addons</a><br>
Line 2551, Column 36: end tag for "br" omitted, but OMITTAG NO was specified
<b>Platform/Genre Channels</b><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 ">".
Line 2551, Column 32: start tag was here
<b>Platform/Genre Channels</b><br>
Line 2554, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/pc">PC</a><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 ">".
Line 2554, Column 47: start tag was here
<a href="http://www.incgamers.com/pc">PC</a><br>
Line 2555, Column 64: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/ps3">Playstation 3</a> <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 ">".
Line 2555, Column 60: start tag was here
<a href="http://www.incgamers.com/ps3">Playstation 3</a> <br>
Line 2556, Column 60: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/xbox">Xbox 360</a> <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 ">".
Line 2556, Column 56: start tag was here
<a href="http://www.incgamers.com/xbox">Xbox 360</a> <br>
Line 2557, Column 53: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/wii">MMO</a><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 ">".
Line 2557, Column 49: start tag was here
<a href="http://www.incgamers.com/wii">MMO</a><br>
Line 2564, Column 35: end tag for "br" omitted, but OMITTAG NO was specified
<b>IncGamers Information</b><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 ">".
Line 2564, Column 31: start tag was here
<b>IncGamers Information</b><br>
Line 2566, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
…<a href="http://www.incgamers.com/Pages/5/Advertising.html">Advertising</a><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 ">".
Line 2566, Column 78: start tag was here
…<a href="http://www.incgamers.com/Pages/5/Advertising.html">Advertising</a><br>
Line 2567, Column 70: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/Pages/6/Staff.html">Staff</a><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 ">".
Line 2567, Column 66: start tag was here
<a href="http://www.incgamers.com/Pages/6/Staff.html">Staff</a><br>
Line 2568, Column 69: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/Pages/12/Jobs.html">Jobs</a><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 ">".
Line 2568, Column 65: start tag was here
<a href="http://www.incgamers.com/Pages/12/Jobs.html">Jobs</a><br>
Line 2569, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/Pages/4/About.html">About Us</a> <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 ">".
Line 2569, Column 70: start tag was here
<a href="http://www.incgamers.com/Pages/4/About.html">About Us</a> <br>
Line 2570, Column 82: end tag for "br" omitted, but OMITTAG NO was specified
…href="http://www.incgamers.com/Pages/11/Privacy.html">Privacy Policy</a><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 ">".
Line 2570, Column 78: start tag was here
…href="http://www.incgamers.com/Pages/11/Privacy.html">Privacy Policy</a><br>
Line 2578, Column 35: end tag for "br" omitted, but OMITTAG NO was specified
<b>IncGamers Connections</b><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 ">".
Line 2578, Column 31: start tag was here
<b>IncGamers Connections</b><br>
Line 2580, Column 89: end tag for "br" omitted, but OMITTAG NO was specified
…="http://www.facebook.com/pages/IncGamers/116509705864?ref=nf">Facebook</a><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 ">".
Line 2580, Column 85: start tag was here
…="http://www.facebook.com/pages/IncGamers/116509705864?ref=nf">Facebook</a><br>
Line 2581, Column 61: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.twitter.com/incgamers">Twitter</a><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 ">".
Line 2581, Column 57: start tag was here
<a href="http://www.twitter.com/incgamers">Twitter</a><br>
Line 2582, Column 64: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/Feeds/news.xml">RSS</a><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 ">".
Line 2582, Column 60: start tag was here
<a href="http://www.incgamers.com/Feeds/news.xml">RSS</a><br>
Line 2583, Column 57: end tag for element "p" which is not open
<a href="http://www.incgamers.com/forum">Forums</a></p> <br> <br>
✉
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.
Line 2583, Column 63: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/forum">Forums</a></p> <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 ">".
Line 2583, Column 59: start tag was here
<a href="http://www.incgamers.com/forum">Forums</a></p> <br> <br>
Line 2583, Column 68: end tag for "br" omitted, but OMITTAG NO was specified
<a href="http://www.incgamers.com/forum">Forums</a></p> <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 ">".
Line 2583, Column 64: start tag was here
<a href="http://www.incgamers.com/forum">Forums</a></p> <br> <br>
Line 2584, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
<b>Contact</b><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 ">".
Line 2584, Column 17: start tag was here
<b>Contact</b><br>
Line 2585, Column 65: element "A" undefined
<A href="mailto:editor@incgamers.com?subject=News Submissions">Send News</A>
✉
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).
Line 2622, Column 5: end tag for "form" omitted, but OMITTAG NO was specified
</td>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 2480, Column 1: start tag was here
<form action="index.php" method="get">
Line 2634, Column 7: 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.
Line 2703, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 419, Column 1: start tag was here
<div id="home">