My forum(www.wiizdom.com/forums) looks completely fine in every other browser than IE5 and IE6. I've attached some pictures of how it looks in IE5 and 6 below : IE5 IE6 I know that IE5 and IE6 are old but, half the people who visit the site still use them, so is there anyway I could make it look normal on IE5 and 6?
Do you mean that the menu and shoutbox don't show on IE6 and 5? You seem to be in Standards mode so IE6 should really be pretty close to everyone else. Esp since a big chunk of the page is in tables, that's pretty stable in everyone. IE5.x however, is completely broken in box model and usually I wouldn't worry about it. I'm sure your "half" who use 6 an 5 are mostly 6, right? 6 needs a few hacks but 5 needs a lot. I can't see anything else that's different. Is your IE6 and 5 javascript enabled? You've got a lot of Javascript doing who-knows-what in there.
I used browsershots.org to get these and according to them the comp that took the picture of IE6 had: Browser: MSIE 6.0 Engine: MSIE 6.0 Javascript: 1.3 Java: enabled Flash: 9 Factory: vm-fab-990 Sponsor: Andreas Krüger Hardware: VMWARE Operating system: Windows 2000 Dimensions: 1024x2353 File size: 115.2 KB Requested: 2008-04-04 09:13:34 Started: 2008-04-04 09:44:54 Page loaded: 2008-04-04 09:45:04 Uploaded: 2008-04-04 09:46:48
Hmmm, I'd need mah tools and mah Winblows machines to get any further, as I need to see the differences for myself on real machines. But it is just the top nave and shoutbox not showing, right? usually IE5 has issues with widths etc.
I'm experiencing a similar problem that I am just about to post about. Unfortunately, because I'm in the same boat, I have no help for you, but at least you can know you aren't alone in your struggle brother!
IE 5.x suffers lots of CSS flaws and isnt standards compliant. Margins, width and alignment are all buggy. Many of them dont have a cross-browser-compatible hack or fix. Better to ignore it since its slowly moving out of the browser market.
Well, if you REALLY want to fix it, you've got a LOT of work ahead of you on that template. 1) 26 Validation errors, never a good start. 2) Mootools framework - there's a fat slow bloated headache from hell 3) inlined CSS - always a sign of sloppy coding. 4) more div's and classes than the layout needs. 5) script open without a close inside a lte IE7 conditional - that by all appearances should make the entire document body not even appear. - I'll cover that in a moment as that's your culprit. 6) More presentational markup than you can shake a rattle at. 7) Comment placements AFTER closing tags instead of before in an area that has floats (at least I assume so given the use of clear) - welcome to the world of the IE double render bug and/or dissapearing content 8) bloated classitus - here's a tip, if a section inside a TR is all the same class, put the class on the TR, inherit, and save yourself a few K - see all that tcat and trow nonsense. Though as I just mentioned, it's that IE conditional that's biting you in the posterior. See this in the output: <!--[if lt IE 7]> <script type="text/javascript"> <!--//--><![CDATA[//> Code (markup): Nowhere are you CLOSING that script tag, so everything between that conditional and the next script close (way down at that crafty syntax thing) is treated as FAULTY javascript - so of course your entire header isn't rendering. That code isn't doing anything - so delete it and your content should magically appear. Though the rest of that REALLY needs to be cleaned up too - Trust me, you have my sympathies on this I'm trying to do the same thing to the default template for SMF so I have a CLEAN baseline to work with - while someone else I know is doing the same thing with myBB. It amazes me how many php developers seem to know JUST enough HTML to get themselves into trouble and churn out invalid buggy bloated nonsensical code leaving those of us deploying their softwares to pretty much rip out the guts and recode the output... AT LEAST said developers are getting better about not hardcoding in this stuff and allowing greater control over exactly WHAT is output for code through theming/skinning without diving into the code that actually makes it work.