You should put “not work safe” if there’s nudity or strong language.
It looks fine in FF – it’s an IE problem.
Look at one of your last few posts for something too wide – image, uri, something. It could be something you’ve added to your sidebar, also.
That’s an awfully long page for entering a site 🙁
(but that’s just my personal hating of long web pages)
Anyway, Id’ start with validating the site; more than 160 errors is too much for anybody to try to detect what your problem is.
http://validator.w3.org/check?verbose=1&uri=http%3A//blog.pink-pistol.net/index.php%3Fm%3D200603
Samboll: Sorry about the nudity thing, I just picked a random archive link as an example, I forgot >.<
Moshu: Umm, it’s an ARCHIVE page – I only show the latest two posts on my main page… and the css is validated. I run a personal blog, not a business site so I don’t bother with xhtml validation because I really dont care and I’m lazy. The site is tested in firefox, ie, opera and avant and looks fine.
My site looked %100 fine before I upgraded, so this is a new problem, and not a problem with my “horrible coding”. And this isn’t an internet explorer issue – because I dont use internet exploiter – I use firefox.
I understand everything… except one thing: if you have that many errors don’t expect anybody to dig in to find what is causing the “slipping” of your posts.
Yes, I could see it in FF, but I never bother to look at the code with that many errors. Sorry.
But why would my errors not have made weird things happen beforehand – only after the upgrade?
It’s okay – I figured it out. It was a small thing with my old index.php file I was using. I just copied the index file from one of the default themes and worked from there. I was using my index file from wp 1.2, ha!
