what is the url of the site you are running this “checker thing” on?
And closing a span is not unreasonable.
Thread Starter
craigh
(@craigh)
Thnaks for looking at this.
my page is http://www.loanchecker.com.au
Also used the markup validation tool at http://validator.w3.org/ and it came back with 16 errors on the page.
I’ll fix those and see if I get a better result
Would it be normal to have so many errors when writing a page in visual?
If so wil have to make it a habit of checking code on every post I write
Thread Starter
craigh
(@craigh)
Arrgh frustrating! I must be missing something here.
I run a check using http://validator.w3.org/ and it comes back with heaps of errors. most appear to be related to closing font code, closing papargraph codes etc. If I clean these up the problem is whenever I edit or post anything I get heaps more errors again. It appears from looking at this that the code generated by wordpress when posting in visual is faulty or incomplete. The pages display OK so is it faulty code or is the code Validator having problems recognising it.
I’m new to this and don’t really understand code that well. Has anybody had the same experience?
Thread Starter
craigh
(@craigh)
Ok done a lot more reading and playing around but haven’t really progressed. With validator I can see the supposed xhtml issues on their page however I don’t see some of these peices of code when in wordpress to edit the post for example the validator tells me that </p> is missing however the > however I can’t see this code in the edit screen. Is there a setting somewhere that allows me to see all code in a post?
I don’t know. However, when you have a pile of errors like that, and fixing them just calls up more errors, it’s likely that you have a coding problem somewhere that’s throwing the checker off. Only … you have to find it.
First of all, I would use the CSS file to specify fonts because the <font> tag is deprecated (means you really shouldn’t use it nowadays). This would also mean that your font tag problems would go away.
Then, when you set an image, you need to “close” the img tag:
<img src="someimage" />
See that /> ?? That’s what it’s looking for.
Clean up some of that stuff, and your problems will likely lessen.
Thread Starter
craigh
(@craigh)
Hi Dianne, thanks heaps for your help, I’ve progressed a bit with this one and put in a new topic:
wordpress XHTML not compliant??
Looks life I have some sort of databse error throwing this up. if you get a chance please feel free to look at this other thread.
Cheers,
Craig
Which other thread. Could you post a link to it?
