[Plugin: Network Plugin Auditor] Getting errors in the

The error leads back to the get_file_data() function used to read the plugin data from the plugin files. Is the error always for that plugin or is it for various plugins?

If it is just the one plugin then it looks like Random Image Widget plugin is only compatible up to 2.7. My plugin requires at least 3.2.1. I wasn’t able to replicate after installing that plugin on 3.3.1. Can you tell me a bit more about your configuration?

Also, if you turn on debugging in your wp-config.php with this code, go to the Sites page where you see the error and send me (email) the wp-content/debug.log file that would help get to the bottom of this.

define('WP_DEBUG', true); // false
if (WP_DEBUG) {
  define('WP_DEBUG_LOG', true);
  define('WP_DEBUG_DISPLAY', false);
  @ini_set('display_errors', 0);
  @ini_set('error_reporting', E_ALL & ~E_NOTICE );
  @error_reporting(E_ALL & ~E_NOTICE);
}

Hi Tevya,

Please let me know if you’re still seeing this issue in the new 1.1 version.

– Kathy

I’m sorry Kathy. I’ve just been super busy and haven’t been able to get back to you on this.

I just updated your plugin and now, instead of errors, just see paths to plugins that don’t seem to exist anymore. See here. I may have removed these plugins in my last round of auditing/merging plugin functionality on my sites… I’m not sure. But either way, it appears your plugin is showing me that these sites still have some false data about plugins that are no longer on the site.

There’s no errors, so 1.1 works great! But if you have any ideas where these “ghost” plugins are coming from, I’d like to know how to clean them out of the WP database. I like to keep things ship-shape, as I’m sure many of the people who use your plugin do.

Hi Tevya,

I’m glad the new version fixed up that issue! I was not
checking if the plugin file existed before attempting to read the data
from it. So if you had deleted a plugin that was active on other blogs and no one had disabled in in the meantime it would give the error you were seeing.

Now, instead of an error, the plugin lists the file path the child blog is attempting to include (the ghost plugin). The plugin name comes from the active_plugins entry of each blog’s options table.

The absolute safest way to handle cleaning those up would
be to visit the individual blogs’ plugin pages. They will display an
error message that the ghost plugin was deactivated because the files
were not found, and the entry will be deleted from the database.

I haven’t included any clean up features in the plugin itself, but perhaps a future version. ??

– Kathy

Awesome, thank you. I’m still getting used to a few things in Multisite.

I didn’t expect any cleanup tools, though that would be awesome if you did add some. Thanks for the excellent plugin.