Edit Source Information

[JimmiOO]

Can someone please enlighten me. When i load my forum up in IE then do a View, Source i get lots of code. I have a couple of small errors i would like to fix if possible. What template or file do i edit to put the errors right?

[glennybee]

That depends where the error is!

Copy the code that you want to find.

Go to Style Manager > Search in Templates

Paste in your code and see what template it's in.

[JimmiOO]

I went to http://validator.w3.org/ to validate my code and it came up with these errors.

I just wanted to fix them, i have found the templates that they apply to but cant seem to sort them.

1.	Line 572, Column 33: document type does not allow element "td" here.
<td align="right" valign="bottom"><img src="images/styles/channel/misc/ban_right
✉ 
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). 
2.	Line 575, Column 77: document type does not allow element "table" here.
?" border="0" width="100%" align="center">
✉ 
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). 
3.	Line 1658, Column 4: end tag for "table" 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 ">". 
4.	Line 558, Column 0: start tag was here.
<table border="0" width="100%" cellpadding="0" cellspacing="0" align="center" st
5.	Line 1658, Column 5: XML Parsing Error: Opening and ending tag mismatch: table line 558 and td.
</td>
✉ 
6.	Line 1660, Column 5: XML Parsing Error: Opening and ending tag mismatch: td line 537 and tr.
</tr>
✉ 
7.	Line 1661, Column 8: XML Parsing Error: Opening and ending tag mismatch: tr line 535 and table.
</table>
✉ 
8.	Line 1702, Column 7: XML Parsing Error: Opening and ending tag mismatch: table line 534 and body.
</body>
✉ 
9.	Line 1703, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 532 and html.
</html>
✉ 
10.	Line 1703, Column 7: XML Parsing Error: Premature end of data in tag html line 2.
</html>

[Dismounted]

Did you have a read of the "errors"? From what I can see, you have overlapping tags.

Overlapping:

<form><div>Some Text</form></div>

[JimmiOO]

Yeah it looks like i have overlapping tags, is this a big problem? and how do i fix it if it is? I use a custom skin so i think it may be causing the problem.

[Dismounted]

Originally Posted by JimmiOO

Yeah it looks like i have overlapping tags, is this a big problem?

It's a problem, maybe big, maybe not. Different browsers will render those pages differently if the code structure is not as expected.

Originally Posted by JimmiOO

how do i fix it if it is? I use a custom skin so i think it may be causing the problem.

Make them not overlap. However, before you start chasing your style's author. Disable any modifications you have running, one of them may be causing this.