Problem with IE7 on SOME pages

[bojomojo]

I am integrating:
Kayako Support Suite
WHMCS
Status2k
vBulletin

to have the same design as the main website, they all work fine on ff3 but:
Kayako and Status2k are messed up on ie7
while WHMCS and vBulletin has no problems.

I use the same files, codes, includes on all pages.

I removed all the content from the pages that cause the problem and left only the header that i add to every page, it still caused the same problem.

the URL is:
Problem solved, thanks

[Snookerman]

I noticed that you tried to self close some div tags:

<div id="theolay" style="height: 1394px; width: 1266px;"/>
That is not valid. Div tags have separate close tags:

<div id="theolay" style="height: 1394px; width: 1266px;"></div>
Fix all of those and your problem might disappear.

[bojomojo]

i cant seem to find the tags you are talking about, where exactly are they

[Snookerman]

I looked at this page: [URL Removed at user request] with firebug (http://getfirebug.com/).

[bojomojo]

these tags doesnt exist in the real code i viewed. nor does the class: "theolay" exists at all

[Snookerman]

That's strange, here is what I see:
<div id="nomain"/>
As you can see there are a few self closing div containers. Maybe someone knows if firebug does that?

[BLiZZaRD]

Start here (http://validator.w3.org/check?charset=(detect+automatically)&doctype=Inline&ss=1&group=0&user-agent=W3C_Validator%2F1.606) Missing a few tags, you have stylesheet calls in the body section, etc. etc.

[bojomojo]

this is not the error.
I removed all data, corrected all errors:
[url removed at user request]
and the error still exists

[Snookerman]

The invalid div containers are created by the box script (mybox.js). Try removing that to see if it causes the problem.

[bojomojo]

did that but its not fixed, only the bg is fixed but the naviigation is still wrong..

check to see

[Snookerman]

The self closing div containers are still there. I suggest you check all your js codes to see why you get these containers.

[Snookerman]

On the other hand, it might be firebug showing them like that when the close tag is right after the open tag. I'll take a closer look and try to find what is causing your problems.

[Snookerman]

I managed to fix it a bit, still some small faults. Add this to your .css file:

#nav_wrapper {
width: 900px;
height: 50px;
background-image: url(/images/nav_bg.gif);
position: absolute;
bottom: 0;
left:0;
}

[Snookerman]

Fixed it:

#nomain {
width: 900px;
height: 10px;
background-image: url(/images/nomain.gif);
background-repeat:no-repeat;
margin: 0 auto;
}

[bojomojo]

its fixed, thank you very much