thanks for that. i am reluctant to change i copied the page source code into Kompozer (my WYSIWYG program) and it all looks fine in there.
Has Microsoft updated IE in some way and messed it all up for me?
Some of those are pretty serious. Such as the missing ul tag that will cause all kinds of chaos.
Also are you pasting directly from word or something because there is a strange tag all over the place <o:p>. If your doing that then that’s probably the source of most problems if you must compose your posts in word before you copy them into wordpress first copy them into notepad to get rid of all the hidden formatting stuff.
i haven’t used word at all for any of these. and as i said, it’s fine in Firefox and in Kompozer.
i don’t want to go through, meticulously altering all of these, only to find that it screws up the firefox version if there’s actually another solution.
Usually valid code will display correctly in all browsers. IE7 is much better about adhering to the standards. IE6 still has some quirks.
but there was nothing wrong with it before. it was working perfectly fine in IE up til wednesday when it went spazzer for reasons completely beyond my understanding. i changed a tiny portion of the code in the L sidebar – which i’ve subsequently changed back – and that’s it. the rest of it was all there before and worked fine.
don’t mean to be a pain but i wanna get this fixed. can’t just tell everyone to switch to firefox.
Okay zip up your theme and upload it somewhere and report the link here. I need to see the code to see what’s going on.
It’s just Cutline 3-Column Split 1.1 by Chris Pearson.
http://themes.wordpress.net/columns/3-columns/4415/cutline-3-column-split-11/
Or did you want the exact version that i’m using – with everything on it?
The exact version your using because you said you modified it. If the modifications weren’t to extensive then you might just want to upload a new copy of it and be done with it. If not just zip up the one your using and give a link then I’ll look at it.
you made a post on Wednesday. Is there something in that post that may be screwing it up?
You could always back up everything before editing so if it does “screw up with firefox” then you could revert abck to only screwed up in IE
Correct the validation errors. If corrected it will NOT screw up FF. How do you think everybody else writes for many browsers including IE7?
fair enough, i will. but it’s going to be a serious hassle cos they’re on multiple different pages of the template.
what i want to know is why have these errors popped up now when they weren’t there before? i really haven’t done anything different so is it a product of an IE update or something?
Don’t kid yourself. Firefox isn’t perfect either. It displays badly rendered web pages too. BTW, the site also looks like a dog’s breakfast in Opera, which IMHO is the most unforgiving of the three browsers. If it looks good in Opera, the chances are great it will look good in the others too. At least that’s been my experience.
But when you start playing with floated divisions, especially nested floats, IE throws up all over the place.
Good luck with it.
what i want to know is why have these errors popped up
As one with who started with a TRS-80, I can say I long ago stopped asking that question and just looked for the work-around or fix. :^)
