| 8:40 am on Aug 12, 2004 (gmt 0)|
The first tenet of solving mysterious behaviour issues is to simplify the problem.
Gradually strip out what you think is irrelevant junk saving each time as bug1.html, bug2.html etc until the bug vanishes in bug7.html (or whatever). You can then compare bug7.html and bug6.html (i.e. compare good code and bad code) and identify the problem. This will typically require the same method as before but using finer and finer editing - it could be as simple as a non-breaking space in the wrong place.
| 11:15 am on Aug 12, 2004 (gmt 0)|
A quick glance showed me invalid code like this bit:
<!-- Side Banner -->
<table width="780" border=0>
You cannot have a <div> and a <table> immediately following a </tr>
I'd recommend you try validating the page, and fix the errors the validator throws at you.
Then see if you still have problems.
| 12:02 pm on Aug 12, 2004 (gmt 0)|
I will simplify the layout
do header colspan=3
then new TR & TD
open a table close TR and table close TD not the final TR
open a table close TR and table close TD not the final TR
open a table close TR and table close TD and final TR
and footer colspan=3
| 9:59 pm on Aug 12, 2004 (gmt 0)|
the last one with the colspan seems like a hassle. The code works I know that, but somehow in taking out code from the previous layout it messed up, or it's always been this way and i never noticed. It's just so odd that the two stick like that.
by the way... why can't u have a div and table right after a </tr>?
Oh woops just noticed i forgot to take the affilates out >.< sorry.
| 10:12 pm on Aug 12, 2004 (gmt 0)|
|why can't u have a div and table right after a </tr>? |
Because you need to close your table first.
You should also choose a doctype.
| 11:55 pm on Aug 12, 2004 (gmt 0)|
i'll choose a doctype once all this mess is cleared. I've messed with this code backwards and forwards and found nothing. and i do'nt have to close the table, i'm ending the data, then the row, then starting a new row there's nothing wrong in that. maybe witht he div part of it.
| 3:02 am on Aug 13, 2004 (gmt 0)|
|i'll choose a doctype once all this mess is cleared |
The best way to develop a page is first to make sure your mark-up is valid -- not just to see that it "works" visually in your test browser. Even if you see what you hoped to see in one browser, the HTML may well not work in another browser. This is especially true if there are errors in your mark-up and what you are seeing depends on one particular browser's error recovery routines.
I mention this because you cannot validate your HTML without a DTD beginning the document, and your work will be much smoother if you always write valid mark-up. So you are getting good advice when Reflection suggests you should add the DTD from the start.
| 3:36 pm on Aug 13, 2004 (gmt 0)|
|i do'nt have to close the table, i'm ending the data, then the row, then starting a new row there's nothing wrong in that. |
Yes there is. You cant have elements in between <tr> tags, they need to be in td or th etc.
This is not valid:
and neither is this:
| 7:59 pm on Aug 14, 2004 (gmt 0)|
Why are your paragraphs empty and then you have loads of links not inside a container?
This MUST be run through the validator. The code is not valid at present. Try: [validator.w3.org...] first.
| 8:39 pm on Aug 16, 2004 (gmt 0)|
Inside a container? what are you talking about?
And u can't tell me that's not legal to END the row, put data then open another row with TD, if u END it it's over, if u start it then YES the td ahs to come after.
| 8:44 pm on Aug 16, 2004 (gmt 0)|
And that validator is crap.
run a check on:
<Sorry, no personal URLs. See TOS [webmasterworld.com]>
and you'll see weird ass errors taht don't belong. Links that have subj in them are being read wrong. An AIM contanct code is wrong when it's perfectly right!
Saying i can't post a <p> when it's PERFECTLY legal.
[edited by: tedster at 11:59 pm (utc) on Aug. 16, 2004]
| 9:08 pm on Aug 16, 2004 (gmt 0)|
>> Inside a container? what are you talking about? <<
Your page should be made up of headings, paragraphs, lists, tables and forms.
All content on the page must be inside a heading or inside a paragraph, or inside a list, or inside a table or inside a form.
No content shoule be hanging around outside of any of those containers.
>> And that validator is crap <<
No it isn't. You have failed to understand what correct markup is.
>> run a check on: [mm.********xxxx.com...] and you'll see weird ass errors that don't belong. Links that have subj in them are being read wrong. An AIM contact code is wrong when it's perfectly right! <<
Hmmm. There are 46 reported errors. All of those errors are real errors, often caused by a problem with something a line or two above where the error is being reported as.
That code is quite messy. You need to use the heading, paragraph, table, list and form code correctly. All of those 46 errors are easy to fix. You'll learn a LOT about writing correct HTML code by fixing them all.
For example you have to close the </table> after each of these </tr> tags. That is a single table cell can contain a complete table but it cannot just contain a "floating row" such as you have now.
By the way, try to do all tags and attributes in lower case too. Using "find and replace" with a text editor can fix all that in a matter of minutes.
[edited by: g1smd at 9:14 pm (utc) on Aug. 16, 2004]
| 9:11 pm on Aug 16, 2004 (gmt 0)|
Firstly, you might want to remove that link to your site.
|And that validator is crap. |
In what way? I validated the page anyway, and every single one of the errors listed was genuine. You've got no doctype, many unquoted attributes, a ton of unescaped ampersands and a bunch of nesting problems. All the information is given as to the precise location of the problems in the source code.
Don't forget that you can get a cascade of errors - one improperly-nested tag, and it can throw out a whole load of resulting errors. Start at the top (by adding a doctype for HTML 4.01 Transitional), check the URLs in the links for ampersands and replace & by & and then you can start looking at the nesting problems.
| 8:51 pm on Aug 17, 2004 (gmt 0)|
Lol no i get most of em, and the code isn't even mine, my friend let me use it from his site. The one i'm coming up with now is alot neater and easier to read. And what elements are floating? Everything is in a table, a messy table, but it's there.
And no like aim:message etc etc that's a real code that works perfectly and used on many sites but the validator doesn't understand that (oddly).
Oh and a link I had, it said the link was wrong... it had an & in there... but it was alink! not a part of my code lol. How in the heck can that be wrong, i'm linking to a page yet it hates that when it shoudln't be my error.
And ya i'm testing my doctype right now, i have to fix alot b4 i really put that in, and like i said i understand most of them but the ones i listed below make no sense.
And sorry about the link but you had to see what i was seeing or you woulda never understood what i was saying, that and i wasn't in the best mood to be posting lol.
Oh ya and someone said to not have anything floating... so if i did
that's fine? And why not just kinda have it as was?
| 9:30 pm on Aug 17, 2004 (gmt 0)|
You'll find it easier to apply CSS styling to the elements on your page if they are in containers.
You'll find it a lot easier to understand your code in 6 months time if each part of the page is in a container.
The 1&2 errors are real errors. They can be easily fixed. The browser knows that if you put © that you want a copyright symbol and if you want a non-breaking-space you'll put in your code.
So, you have an &2 in your code, so what is the browser to do with that? It doesn't know what entity to are referring to: &2 isn't a valid entity. To be valid you have to escape the ampersand. That is, when you want to use an & on your page as an & you have to put & which makes a real ampersand in the browser.
So 1&2 should be 1&2 to be valid.
An & is used as the prefix to an entity code, like or © etc. The entity code for an ampersand to display as an & is simply & you see.
| 9:40 pm on Aug 17, 2004 (gmt 0)|
Now, 45 errors left to fix. They are ALL fixable.
| 9:42 pm on Aug 17, 2004 (gmt 0)|
Ah so i'd have to change that... well ok maybe u can explain this too b/c this is really odd.
When I validated before the validator said I needed to have something like color="#000033", now it's saying that it's not right, I think it's saying I need color=000033 (HTML strict is sayign this). so now in strict u don't use the "?
it's also saying my <center> codes are undefined?
I have a border=0 and it's saying there is no border defined... I do'nt want a border taht's the point lol.
And for the last one (i think) i have my links sometimes have a:
target=_blank and it's saying there is no target attribute. That's how I was taught to put it, it should be correct html.
| 9:46 pm on Aug 17, 2004 (gmt 0)|
Before worrying about any of that, fix all the & errors and upload the page again.
I can't look at a long list of errors like that. Fix the easy ones so I can see the wood from the trees.
Note that target does not exist in XHTML, but we will come back to that after all the & errors are fixed.
| 9:47 pm on Aug 17, 2004 (gmt 0)|
lol but i'm trying html strict, oh boy lol i'm gonna get a lesson today.
| 9:50 pm on Aug 17, 2004 (gmt 0)|
Ah, the XHTML reference was my mistake. Sorry, I'm fixing sites for 5 different people all at the same time here. I mixed you up with another site. Got it now. Fix all the & and I'll take another look.
Usually color="#000033" should be right. There must be some other problem.
| 9:56 pm on Aug 17, 2004 (gmt 0)|
After fixing all the & to be & we are down to 30 errors, so 15 were very easy, no?
Next the attribute values need to be "quoted".
That is, all the values for src and language and type all inside the script tags need to be in "quotes". Also make sure the tags are all in lower case.
The closing tag of </script> needs to be escaped. How? Easy: <\/script> - use find and replace.
| 10:00 pm on Aug 17, 2004 (gmt 0)|
Actually i fixed a few other errors lol
Why would I need \/? Isn't it just another tag and it's not a php variable or anything.
| 10:05 pm on Aug 17, 2004 (gmt 0)|
The \ escapes the / which otherwise confuses the parser when it sees a / inside a document.write statement. The \ hides the / from the parser.
Put the attribute values into quotes next, and use lower case for your tags too. That is all the block of code in and around the <script>s.
When you have time, put EVERY attribute value in quotes too, all the way down the page, and every tag in lower case. Use: "find <TR> and replace <tr>" then "find <TD> and replace <td>" in the text editor.
[edited by: g1smd at 10:09 pm (utc) on Aug. 17, 2004]
| 10:06 pm on Aug 17, 2004 (gmt 0)|
.... something very bad just happened... the entire site jsut screwed up lol.
Nvm my fault, i got it. And id din't do that \/ and it's showing up as fine.
| 10:12 pm on Aug 17, 2004 (gmt 0)|
It will probably right itself when all the errors are fixed.
You only need to escape <\/tag> on tags that are INSIDE document.write staements. You have done that just fine.
Next, to see what your table code is all about, you need to indent your code. I use a 2-space indent on the first table, then a 4-space indent on a table within that table and so on. Edit your code so you can see the nesting, then it will be clear if any tags are unclosed (or are closed in the wrong order).
Get all the tags in lower case too. It is a simple find <THIS> and replace with <this> then find </THAT> and replace with </that> for about 12 types of tags.
Get all of the attribute values inside "quotes" too; so you will then have <blah something="value"> every time.
[edited by: g1smd at 10:22 pm (utc) on Aug. 17, 2004]
| 10:16 pm on Aug 17, 2004 (gmt 0)|
Your talking about the ones on the end of the validation right?
If i delete those the entire code goes haywire, so when it says they're not open... it's lying lol b/c when i take it out, it goes nuts and makes everything screw up.
2 more ^.^
I don't understand the script one and the doc type is gonna be HTML script i beleive
[edited by: Echo_Tyme at 10:26 pm (utc) on Aug. 17, 2004]
| 10:26 pm on Aug 17, 2004 (gmt 0)|
Do the indent thing on your code, make the tags lower case, and put the attribute values inside "quotes" and then I'll take another look.
You also have double tags in some places like <small><small> -- no point opening something twice. get rid of one. Check how many closing tags you have there too!
Your final script error is missing the type="text/javscript" attribute too.
[edited by: g1smd at 10:29 pm (utc) on Aug. 17, 2004]
| 10:27 pm on Aug 17, 2004 (gmt 0)|
I fixed all that lol and the <small><small> should be a font 1 now.
Oh nvm i hit that now.
and above i meant Strict, HTML strict
I put it into strict mode to find 40 errors oddly enough.
Transitional will do for now, i'm planning a new layout as it is but i'm learning how to fix that one now.
[edited by: Echo_Tyme at 10:32 pm (utc) on Aug. 17, 2004]
| 10:31 pm on Aug 17, 2004 (gmt 0)|
You can't end with
You are masking an error with that. Do the INDENT thing on your code - make it easier to follow what is going on.
Next put your paragraph tags AROUND the paragraphs instead of BETWWEN them.
change it to
[edited by: g1smd at 10:34 pm (utc) on Aug. 17, 2004]
| This 34 message thread spans 2 pages: 34 (  2 ) > > |