Tweet
Cleaning up HTML errors in templates
Hi Guys,
Well I'm starting the template cleanup project and need some advice on the best approach. At first I was going to post the errors that I found, but this would be too much of a time consumer. Here's an example of how hard that would be:
forumhome
5 The attribute value "text/css" for the TYPE attribute was not enclosed in single or double quotation marks when it must be.
in cssinclude template add quotes to (type="text/css")
112 The FONT tag must be closed but the closing tag was not found.
in forumbit template find (alt="Go to last post"></a> $lastpostdate) add (</normalfont>) after $lastpostdate
121 The ID or NAME attribute value "cat" has already been used in this document. A tag's ID or NAME attribute must be unique within the document. A tag cannot have an ID or NAME attribute that has already been used. Note that the ID values are not case sensitive (except when used to link to an anchor) and that ID and NAME attribute values share the same namespace.
Not sure how to handle this one yet
130 The closing tag for TD was found, but the tag was never opened or has been closed too many times.
130 The closing tag for TR was found, but the tag was never opened or has been closed too many times.
remove the /td /tr and leave /table in line 130
145 The FONT tag (opened in line 145) should be closed before the B tag is closed (nesting error).
find (A closed forum) swap </b></font> to </font></b>
Right now I'm thinking that I'll just do the cleanup and post the templates instead of pointing out where each error is.
Another question is how many of you use .css? For our forum I am replacing 99% of the FONT tags with CSS and am wondering if it would be better to just post the validated templates that I use. Kind of a catch22 because most of you have modified templates already. The big problem is figuring out how to let everyone know where the errors are.
By the way this whole ordeal is just because I'm a fanatic when it comes to valid HTML 4.0 code. I'm sure there are some of you who could care less as long as it works, but I'm sure there are other's like me that would prefer to have valid code.
Anyone have any input on how to go about this?
Larry "NgtCrwlr" Mingus
[Edited by NgtCrwlr on 06-14-2000 at 10:40 PM]
Well I'm starting the template cleanup project and need some advice on the best approach. At first I was going to post the errors that I found, but this would be too much of a time consumer. Here's an example of how hard that would be:
forumhome
5 The attribute value "text/css" for the TYPE attribute was not enclosed in single or double quotation marks when it must be.
in cssinclude template add quotes to (type="text/css")
112 The FONT tag must be closed but the closing tag was not found.
in forumbit template find (alt="Go to last post"></a> $lastpostdate) add (</normalfont>) after $lastpostdate
121 The ID or NAME attribute value "cat" has already been used in this document. A tag's ID or NAME attribute must be unique within the document. A tag cannot have an ID or NAME attribute that has already been used. Note that the ID values are not case sensitive (except when used to link to an anchor) and that ID and NAME attribute values share the same namespace.
Not sure how to handle this one yet
130 The closing tag for TD was found, but the tag was never opened or has been closed too many times.
130 The closing tag for TR was found, but the tag was never opened or has been closed too many times.
remove the /td /tr and leave /table in line 130
145 The FONT tag (opened in line 145) should be closed before the B tag is closed (nesting error).
find (A closed forum) swap </b></font> to </font></b>
Right now I'm thinking that I'll just do the cleanup and post the templates instead of pointing out where each error is.
Another question is how many of you use .css? For our forum I am replacing 99% of the FONT tags with CSS and am wondering if it would be better to just post the validated templates that I use. Kind of a catch22 because most of you have modified templates already. The big problem is figuring out how to let everyone know where the errors are.
By the way this whole ordeal is just because I'm a fanatic when it comes to valid HTML 4.0 code. I'm sure there are some of you who could care less as long as it works, but I'm sure there are other's like me that would prefer to have valid code.
Anyone have any input on how to go about this?
Larry "NgtCrwlr" Mingus
[Edited by NgtCrwlr on 06-14-2000 at 10:40 PM]
Comment