danphalen

Tony,

In looking at your source code, your “primarycontent” div statement has both an id and a class declaration. Nothing in your CSS files that I could find for either one, nor for “current-content” either. Without seeing your template files, it’s hard to tell what broke.

Dan

Jim,

I have noticed some of the same behavior with the IE 7.0 implementation of CSS, although they did clean up their act.

One idiosyncrasy is IE’s sensitivity to the order in which you declare divs. You might try to move your “primary” div block up above your “entry-content” div in the html. Or something like that (it’s a big file).

I recall having to do something similar myself recently. If you think top-down, left-right, with floated div declarations, you may be matching the way Microsoft thought it out. CSS “float” isn’t supposed to care, and Firefox doesn’t, but nobody ever accused Redmond of doing things according to standard.

Those long strings look to me to be security codes, possibly string versions of 128-bit encryption, or even encryption itself.

What the originator might have done is encrypt function names and parameters so his/her code can’t be copied.

My guess is if you attempt to “clean” it, as you say, you might break something. I’d try to contact the author and get an answer there.

Also, I wouldn’t use this template until I learned for sure what those strings are all about.

Beautiful image, by the way.

Move your <form> block up inside the logo div thusly.

<div id=”logo”>
<h2>search words</h2>
<form method=”get” id=”searchform” action=”https://mdcaz.org/”&gt;
<div><input value=”” name=”s” id=”s” type=”text”>
<input id=”searchsubmit” value=”Search” type=”submit”>
</div>
</form>
</div>

If you like, you can also change the position of the search block by modifying your style.css file. My example justifies it right, but it also screws up any <h2> header text you care to add. If you exclude header text, it will appear where most people look for a search form.

#logo {
width: 754px;
height: 60px;
margin: 0 auto;
padding: 2px;
text-align: right;
}

Hope this helps.

Gabrielz’ fix may work, but I found those lines were moved to wp-settings.php, so the setting for AUTOSAVE_INTERVAL must have been made part of the Settings session. Not sure which of the two files takes precedence.

I would guess that if you had gone into your ‘Settings’ page and simply clicked “update” without any real changes, the wp-settings.php file would have been exercised and that might also have fixed this problem.

Still, if the Gabrielz fix works, use it.

Jeremy, how the heck can a rogue admin get into the database? Is this a bit of superhacking, or do we need to beef up the WP MySQL security implementation?

You’re probably testing with IE 6.0 or earlier, which is well-known to have a poor implementation of CSS–the language that controls your formatting.

There are two fixes for this: (1) get IE 7.0, or (2) modify the heck out of your style.css file in your theme package. I know how to do this because I’m a web dweeb, but the process is tedious and clutters your CSS.

Essentially, the older Microsoft browsers calculate height and width differently (wrongly) and ignore CSS rules for positioning (such as float).

Sorry, there’s no easy way out, but to your credit, it’s nothing you’ve done wrong. If you want to accommodate readers who have the old browsers, I suggest you post a caveat in your blog that they can upgrade either to IE 7.0 or FireFox at no expense.

We dumped IE 5.5 six years ago and 7.0 has been out for two years now. Personally, I’m out of patience with people who cling to past obsolete technology.