drogheda

I wouldn’t call this resolved, but I have a temporary goofy fix in place: through viewing source, I found out that header-img.php in the themes/default/images folder is responsible for the image overlay produced when one uses the Theme Options panel for Kubrick. (Knowing that, I still couldn’t find useful info in the codex, wp support forums, or by googling.)Since deleting header-img.php does nothing and I don’t know where the image overlay data is stored, I just removed the not(!) from the if statement at the beginning of the script, thus causing the script to die and default to my custom header image.

if ( function_exists('imagecreatefromjpeg') )
die(header("Location: placebo_wpheader.gif"));

This is obviously a kludge and if anyone has a real solution, I’d like to hear it. I’ll revisit the problem when I’m over this evil headcold and maybe it’ll make more sense then.

I was using different prefixes, e.g., lib_ and con_ and needn’t have deleted the second one as it was innocent of any offence. Ah well. It is good to hear you’ve got multiple WPs on one database. I think I’ll give it another go. (If only the electricity would stay on…) And thanks for the moral support as well!

And let this be a lesson unto all: get some sleep before you post. Heck, get some sleep before you troubleshoot.

In looking for an answer to the above problem last night, I saw that some people had fixed their blank login issue by removing untoward whitespace from the top of a .php file. Last night, in my weary daze, I thought that I’d removed any such files I’d altered.

But this morning I lurched out of bed at 8am realizing there *was* an altered file: on the quite helpful advice of this post I had uploaded a new template-functions-category.php file to facilitate the organization of my categories. I hadn’t ever doublechecked that file.

And lo, therein lay a single blank line at the top. D’oh.

Now I’m off to reload all my WP plugins and wonder if I should tempt fate again with that second blog. (Which after all, had nothing to do with the problem, save that installing it logged me out.)

Trying this reply again. First post got eaten by a db connection error. (Oh, the irony.)

It’s good to know that location doesn’t matter. I did not see that clearly elucidated elsewhere. And, since whitespace wasn’t the issues and those four things in the config file were correct in and of themselves, I deduced that the problem must be database-related. (“My, so clever!”, you’re saying.)

And lo, herein lay the fix: I created a new db_user and gave it full privileges in the new WP. When I used the new db_user in the config file, the connection error went away. Now why I can not use the same db_user for both WP databases is a mystery to me (and yes, said user had full privileges to both dbs.) If any one had thoughts on that, I’d be glad to hear’em. But otherwise, ::shrug::

Thanks for your help, podz.