edwa5823

I didn’t try seeking support, it completely sidelined an active site so I had to stop everything I was doing to restore it from a backup. I evaluated the code based on the fact that it modified a slew of root wordpress files (including main.php and cache.php) and malformed them badly. My site immediately started throwing 500 errors. After I restored everything I diffed the files from after the update with my restored versions and they were completely junked. Based on my error logs from that time it looks like 10 – 12 files were changed and began throwing errors, and even the administration area began throwing 500 errors, directly after the activation.

Well, I got tired of staring at the error so I just fixed it myself.. Not sure if this is a hack, (it may be fixed in SVN or something).

What was happening is that the plugin array was being filled with both the directory path and the file path for each plugin activated.. So even though your plugin would run the include_once would also fail on the directory call.

To fix this just replace line 582 of wp-settings.php with

if ( is_file($plugin) && '' != $plugin && 0 == validate_file($plugin) && file_exists(WP_PLUGIN_DIR . '/' . $plugin) )

All that I added is the is_file() check to be sure that include_once is trying to include a file and not a directory. The array should be fixed, but this will do it for now.

I am trying to do a brand new install of WordPress MU and am having the exact same problem.. Any plugin that I attempt to install will throw warnings after activation and each time it is missing the file from the include path.

Has anyone figured this out or is it a bug in the system?

*Slaps Forehead*

Thanks for that–it was VERY obvious. I just haven’t had time to pick it apart, and to be honest I just thought it was a problem with WordPress or one of the items I installed so I didn’t bother checking the obvious.

=)

Thanks again,

Lazy Developer

I am going to bump this since nobody replied. Would someone with some WordPress experience please have a look and see if anything jumps out at them? Right now my site is useless on IE6 and IE7.

Thanks again,

Shane