jgpippin

nvm. i feel like an idiot; i didn’t know about $_SESSION

Be aware that some hosting providers will turn of mailing functions in PHP to prevent client spamming. Since WP uses these functions, this will disable comment notification.

I don’t get an email at all. WordPress will not send me emails, and I don’t know what script it uses to send email, so i can’t troubleshoot it.

Thanks!

I appreciate your desire to help; unfortunately, I read all of those posts before I posted this one.

At one point, someone purported to have solved the problem, but never posted the solution.

Really? No takers at all?

thank you. you, my friend, rule.

i really hate to bump, but i’m in a bad way on this.

anybody?

please help!

Here’s what’s happening; I can almost guarantee it.

You have two fixed-width<div>s (the main body and the sidebar) sitting side-by-side inside a parent fixed-width <div>.

Something is pushing one of those child <div>s wider than it’s supposed to be. FF will adjust, because FF rules, but IE just kicks the sidebar down to the bottom because IE sucks rectum.

The good news is, with a little CSS, it’s a simple fix. Pick one of the <div>s (either the main body or the sidebar div, I don’t know what the Kubric stylesheet lookslike) and cut the width back, say, 5 pixels. Or drop the padding or margins or something. Try to keep your adjustments under 5 pixels so that the difference isn’t noticable in FF.

That, and make sure to tell all of your friends how much IE blows baboons.

I second that. I really need that code to get my website working, and I’d love you if you’d come post it for us.

I’m on a roll here, if I can just figure out the rest…

There is a child_of argument in the codex that will allow you to limit the pages listed to those that are children of a specific parent.

Now, finding a way to either a) get the code to recognize which parent I’m looking at and show only its children or b) create custom sidebars for each section… that’s what’s next.

I really got to learn php.

Thanks for taking a look.
The XHTML errors are minor, nothing that would cause this kind of breakage. Some are silly – most are from MT-imported posts or bits of code from outside resources (flickr, audioblog, etc). All are negligible, though I should remove the Valid XHTML link if I don’t plan to be a nazi about XHTML validity.
The CSS error, too, was nothing: the offending line was removed without problem.
I think that I will use this as an opportunity to fuel my long-standing hate of all things Internet Explorer. Mac IE is on its way out anyway… I hope. Maybe I’ll put a “best viewed in any number of browsers that aren’t bloated with useless code and too elitist to adapt to changing technologies that don’t happen to show a high profit margin” badge or something.
Thanks, anyway.