MeredithX

That’s happened to me before. I cleared the related cookies and all was fixed. They seem to cache something in a cookie that can send you into an infinite loop.

Thanks! Now if only they would integrate mu-plugin management into WP. It’s just so wonderful to have a mu-plugin that is breaking things when I don’t have access to a shell.

The directions say to install it in mu-plugins.

I’m not clear what the difference between network install and mu-plugins is. Any pointers?

I forgot something important: I should have said that before reverting to 2.8.5, I DLed 2.8.6, and copied the relevant 2.8.6 files/folders over (a copy of) my broken copy. Same result.

I should also have noted that it made it through a few plugins before spewing PHP error code on the page. And that resetting plugins didn’t help, because widgets were whinging as well.

Mebbe its just me? Or the stars? But I think I’ll wait until the plugins I need are marked as compatible with 2.8.6 or something like that.

I was trying to set up WPMU when the dreaded phone call came…

P.S. Duh. Didn’t notice the edit post. Sorry for the two entries, although I guess it’s really clearer this way.

1. I updated to 2.8.6 a couple of days ago. Seemed to work, although it would be nice to be able to see which plugins are (possibly) incompatible first. (And, yes, I did a backup first.)
2. Updated PHP 5 today to 5.2.6.dfsg (no idea what from, but at least a few weeks old) and it killed WordPress. WP couldn’t find all sorts of WP files, like widgets.php.
3. Nothing else is broken with the new PHP version, including some 7-year-old code that I’m afraid to breathe on.
4. After tons of unbelievably painful echo debugging, I went back to 2.8.5. Copied my themes over, installed the needed plugins manually to ensure compatibility. All is now working fine.

This is on a Debian Lenny Linux box, btw, running 2.6.24-xen.

Grumble. Guess I’ll be sticking with 2.8.5 for a while.