| Home | Register | FAQ | Members List | Search | Today's Posts | Mark Forums Read |
28-05-2009, 05:59
|
#1 (permalink) |
|
Registered User
Join Date: Jul 2008
Posts: 21
|
Help me fix my W3C issues please.
Hey, I have this website: how to weld and when I run it through the W3C checker I get 3 errors only !!! But I'm lost as to how to fix the last few problems. Can someone show me what to do please. |
|
|
|
|
28-05-2009, 06:27
|
#3 (permalink) |
|
Paddy Power
Join Date: Jul 2008
Location: Marbella
Posts: 287
|
I wouldnt worry about it. If your developing your site its more important to get it working for your visitors than for W3C and if you try and meet its regulations 100% you will simply drive yourself insane. 3 errors is nothing and so long as the site functions in Firefox, IE and chrome I would just get on with more important matters. |
|
|
|
28-05-2009, 06:40
|
#4 (permalink) | |
|
Shun the non-believer
Join Date: Feb 2005
Location: Essex, UK
Posts: 1,788
 |
Quote:
|
|
|
|
|
28-05-2009, 06:47
|
#5 (permalink) | |
|
Registered User
Join Date: May 2009
Posts: 2
|
Missing a few tags
Quote:
Standards are important. Hence, using the validators to fix problems. First off: Line 216, Column 11: document type does not allow element "TR" here --Looks like you're missing a closing </tr> tag. add that to fix this problem. Secondly Line 383, Column 9: end tag for "TABLE" omitted, but its declaration does not permit this -- Another tag missing here. This time it's the </table> tag that seems to have sprouted legs and left the source code. Add it where it belongs. Should take care of the issue. Fix these two errors then run it through the W3C validator again. Any other problems send me an email. I'd be glad to help: help@burielwebwerx.com Cheers! |
|
|
|
|
28-05-2009, 07:07
|
#6 (permalink) | |
|
Paddy Power
Join Date: Jul 2008
Location: Marbella
Posts: 287
|
Quote:
Naw, Im a bit biased, I have tried my damnedest to meet those standards and have spent long nights fixing code to make it work. The more complicated the site the more errors and the more problems you may meet when fixing them according to w3c standards reports (domino effect.) I agree its important, just dont have the time or patience to deal with it currently  (that's not saying you shouldn't if you can or have more patience). |
|
|
|
|
28-05-2009, 07:46
|
#9 (permalink) |
|
has bucket
Join Date: Aug 2008
Posts: 571
|
you're missing a few closing table rows - or it appears from a quick scan of the code (hard to tell with that indenting). the validator only picked up the first instance of it tho. And, you didn't close out your table. and, Justinskie has a point in that working matters more than passing a validation test. I mean hell, validate Amazon.com sometime O_o But, as Kemp said - if you do it right from the beginning, validation should maybe...maybe take you an extra 5 minutes. |
|
|
|
28-05-2009, 21:18
|
#10 (permalink) |
|
Registered User
Join Date: Jul 2008
Posts: 21
|
Where about's do I add these codes? ------------------------------------------------ First off: Line 216, Column 11: document type does not allow element "TR" here --Looks like you're missing a closing </tr> tag. add that to fix this problem. Secondly Line 383, Column 9: end tag for "TABLE" omitted, but its declaration does not permit this -- Another tag missing here. This time it's the </table> tag that seems to have sprouted legs and left the source code. Add it where it belongs. Should take care of the issue. ----------------------------------------------------- I have tried adding the </tr> tag many times and the nav bar on the website keeps jumping from the left side to the right side of the page. |
|
|
|
29-05-2009, 06:51
|
#11 (permalink) |
|
Semantics, yay.
Join Date: Nov 2005
Location: Beverly, Massachusetts
Posts: 1,534
|
If line 216 has a <tr> tag that isn't allowed, it's because the previous table-row was not properly closed right before it ... so, you'd probably want to throw a </tr> right before it, perhaps on line 215. |
|
|
|
29-05-2009, 07:20
|
#12 (permalink) |
|
dt immigrant
Join Date: Nov 2004
Posts: 9,428
|
this validates HTML Code:
     |
|
|
|
29-05-2009, 09:32
|
#13 (permalink) |
|
Registered User
Join Date: Jul 2008
Posts: 21
|
emil, Wow awesome, thanks for that. How did you do this? Whit an automatic cleaner like HTML tidy? I see that this part of the code is different here: was this ---------------------------------------------------------- <style type="text/css"> @import url(http://www.google.com/cse/api/branding.css); </style> <style type="text/css"> @import url(http://www.google.com/cse/api/branding.css); </style> <style type="text/css"> @import url(http://www.google.com/cse/api/branding.css); </style> </head> <body> ---------------------------------------------------------- Now it is this: <style type="text/css"> div.c4 {text-align: left} div.c3 {text-align: center} div.c2 {background-color:#FFFFFF;color:#000000} img.c1 {float: middle; width: 140px; height: 104px;} </style> </head> <body> ------------------------------------------------ What have you done here, what difference does it make??? You must have used an auto cleaner as all the code is lined up nice and straight. Now for the rest of my pages what should I do? I'm thinking maybe keep copying this index page, and using it for the base of the other pages???? Peter |
|
|
|
29-05-2009, 09:40
|
#14 (permalink) |
|
dt immigrant
Join Date: Nov 2004
Posts: 9,428
|
Applied source formatting in Dreamweaver, helps a lot to maintain a clean code. You had two problems, your main table lacked an ending tag, and also one of the <tr>s also you had one word astray in an img (border which wasn't a parameter) nothing changes for the css, you still have the imprted stylesheets just above the inline styles. At this point you should worry less about validation and focus more on learning to write code, if you want my honest opinion. |
|
|
 |
|
