ravedigga

I’m now on my PC at work, running XP SP2 and IE7… the fault is still present here! There’s actually parts of the pag showing up which I’ve remvoed over the weekend, but I think that’s becasue the page is being cached on the proxy server here at work… but still, this error is weird. Yet to go home and check my own PC again, but why would this have happened? I haven’t changed anything like z-index values, specifically because I don’t fully understand how to use them properly. The gallery plugin doesn’t even have a z-index attached to it in the CSS.

It’s worrying that this issue, which effects navigation, can seem to appear or not appear on identical browsers and I don’t know why.

Hi again 🙂

Ok… both of the suggested codes work, but here’s what happens…

Alchymyth

#body #content {
	float:left;
         display:inline
	width:600px;
	margin:110px 0 0 11px;
}

#body #sidebar {
	float:right;
	display:inline;
	width:321px;
	margin:110px 18px 0 0;
}

This does the trick, I just needed to cheange the ‘110px’ value to suit. I’m not sure what you mean about top-margin though, since using that instead made it all goe a bit off-skew.

KZ
#body{padding-top:140px;}

This seems to do the job in one go 🙂

So now I’ve got 2 methods, and I come back to the matter of best practise… trying to do it the ‘correct’ way and avoid any validation errors as pointed out by Songdogtech, or anything that will make it non-viewable in some browsers. At present I’ve only tested it in IE8, but I’ll install and check in Safari and Firefox next.

I’ve also re-uploaded the original CSS and validated that now – same amount of errors as when songdogtech validated it, so maybe those are nothing to do with me? I have noticed however that after my changes there’s a small error in IE in the bottom left telling me the page didn’t load correctly. Nothing looks wrong, apart from me moving things around and playing trial and errr with positioning. What I mean by that is that the errors are there even after I finally get things in the places I want them and looking correct. But I’m going to go back to the original CSS, start changing it and viewing after each change, and then see when the error appears.

Hi Songdogtech, thanks for the reply.

I’m afraid it goes a little over my head though. I’m aware of ‘validating code’, and I know ul and li are HTML list tags, but do those errors mean the theme I paid for is actually badly put together? Are you saying that the change I need to make to the layout isn’t possible without fixing those faults first?

I’m a little confused since I was worried after your reply that this might be the case and so decided to validate some other sites as a test. Sites including beatport.com, hmv.co.uk, and facebook.com all came back with more errors than my own page, and they are functional. I’m willing to fix these/get them fixed, but the main concern to me at present is getting the site up and running in a functional way, looking how it should, so that I can then get on with using it as I intend – as a platform for my music projects. Once that’s happening I’m willing to work on the site and get any glitches ironed out. So right now it’s that layout issue that I need to be the priority, unless it’s not possible.

Can you help? Any advice from anyone else?

Thanks 🙂