senortim

No database caching tools, no. By “clearing out” do you mean saving blank fields? Or is there another, preferred method? (Tool? Direct in DB?)

Thanks for the quick reply!! (And yes, sure about 1.4.1. We tried 1.4.0 but were experiencing the data-corruption error that 1.4.1 corrected.)

@nickharambee — Try deleting all your PayPal cookies. I had to do this to clear up **a bunch** of problems, including deleted database entries reappearing.

For me, the problem is nothing appearing in my database at all when running in Live mode. Testing worked beautifully, but when I actually took the site live, nothing shows up in the database.

I got the same error as Nick, but don’t really know what I should do about it. I’ve diff’d my modifications to paypal.php with the original and don’t see a single thing that could cause a problem. (My mods just add a “custom” Paypal field and pass a bunch of imploded data, through to a new/modified SQL insert.)

I found it. My problem _was indeed_ with CSS. I gave #container the position:relative setting and — though I’m still not sure why — this somehow prevented sidebars from receiving clicks.

I did this because I wanted to position a sidebar that was specific to my page content (rather than via a Text Widget). To fix it, I just wrapped my sidebar in another DIV and set it’s position to relative. (It took **much longer** to find than fix; isn’t that always the way?)

@kmessinger In Screen Options, accessibility appears to be disabled. I toggled it ona dn off, with no effect. Other ideas? (PS: Sorry for misspellings, if any; since I upgraded to FF6, my fonts are totally hosed, and I’m typing half blind.)

I’m having the same — or at least a very similar — problem. The site (not public) is https://ipen.org/hgf2/ and is running WP3.2.1.

I’ve tried the things suggested above, with no success. One difference from @lankalion is that I have at least two other sites on this same server and domain that are using the same theme (TwentyTen) and are working just fine.

I thought perhaps it was a CSS thing, with a layer above my current sidebar, but I cannot locate any offending CSS. My own customizations to the CSS don’t modify the width of the #content DIV, which when I double click seems to be affected.

Thanks,
Tim