body of posts pushed down

Holy crap!

400 errors!?!

That has to be some kind of record! I’m doing some slight scrolling on this *amazingly* long page of errors, and some of them are *real* doozies. *Lots* of tags that aren’t closed at all…

You’re *really* going to have to do some serious cleaning to figure this one out.

moderator: thanks for informing about pastebin. ok. next time i’ll do what you suggested.

doodlebee: i had a look at the error page and i notice something strange. lots of errors it mentioned, i checked, but they were fine. e.g. it mentioned i did not close a tag at a certain place but when i checked, it was close. guess i couldn’t understand it.

another thing i find strange is that, before yesterday when i edit that two section, everything’s fine. only when i add that two section, my blog fucked up. so i thought the cause could be due to that two sections only… errors there only but how come errors were all over!

serious cleaning? that would take lots of time. further i’m not techie/html savvy. perhaps if no choice, i should made use of the original sidebar (that comes with the template) but for that too i have to do some re-editing.

it mentioned i did not close a tag at a certain place but when i checked, it was close.

Yes, but your doctype is XHTML – therefore your code must be semantic. So if you have <p><strong>text here </p></strong>, then it won’t see the </strong> tag and say it’s unclosed because you’re writing bad markup. It has to be closed in the order it was opened – so the example above would have to be `<p>text here</p>’.

That’s why it’s throwing things off.

that would take lots of time.

Not necessarily (although you do have a lot of errors!) These errors are all related to one another. You might get lucky and find that fixing a few of them will cause the rest to fall into place (it usually works that way).

But validation *is* important – it has a lot to do with how your site is displayed. Yeah, it may have looked fine until you did this one new thing – but that *one* thing is probably what finally pushed it over the edge. Might as well clean it up and get it right so you don’t constantly run into this problem.

Can’t slap a band-aid on a severed hand and expect it to heal correctly (or function properly even if it managed to heal partway)!

I’ve just viewed your site in IE7 with a 1024×768 screen resolution, it appears to be rendering fine, the blog posts start up at the top where they should.

Usually if the sidebar or the blog posts get pushed down, it’s because some content in either of those is too larger than the section it’s been placed in.

Or you may have a problem like I do with my blog that I have been too lazy to fix yet – Perhaps the site renders correctly at the larger screen resolution, but if you look at it with a smaller screen res, like 800×600, the content gets pushed down. The fix for that would be a fluid width layout.

thanks to those who respond here. i managed to fix the problem where i can see the blog properly in firefox but in IE, it doesn’t look right. but that is beside the point now (will deal with that later or not at all as i use firefox all the while).

i fix the problem by uploading the original sidebar file first, then slowly, one by one, copy each section of links i have on the edited sidebar file on to the original sidebar file. it seems that at some places there were duplicate DIV tags.

well this fixed the problem of the posts (main body) being pushed down but of course there are still over 300 errors. so i have to be careful with my editing… in case i put it over the edge and it goes crazy again.

OTOH, as someone suggested this theme of mine is quite ‘heavy’ so i might change another theme.

“i managed to fix the problem where i can see the blog properly in firefox but in IE, it doesn’t look right. but that is beside the point now (will deal with that later or not at all as i use firefox all the while).”

Unless you plan on being the only person who views your site, you should make sure your site renders correctly in IE. Not everyone uses FF. I have both FF and IE and end up using IE most often. I’m sure if you view your stats, you’ll find most people are using IE, so you should design with those people in mind.

By the way, you can use conditional comments to fix IE. But I’d *really* suggest doing it *after* you clean up your code – you may not need to “fix” anything at all after you do that.