Skip to:
Content
Pages
Categories
Search
Top
Bottom

Plugin Error


  • jodyw1
    Participant

    @jodyw1

    Okay, I just tried installing “Plugin Commander” thinking I needed that to control plugins per mu. (I’ve since come to find that I don’t need to, that BP now takes care of that.)

    In the install, Plugin Commander crapped out, errored and failed to activate. I get this error now al over the site:

    Warning: include_once(/home/content/d/o/o/doorqtech/html/wp-content/plugins/plugin-commander-i18n/) [function.include-once]: failed to open stream: No such file or directory in /home/content/d/o/o/doorqtech/html/wp-settings.php on line 545

    Warning: include_once() [function.include]: Failed opening ‘/home/content/d/o/o/doorqtech/html/wp-content/plugins/plugin-commander-i18n/’ for inclusion (include_path=’.:/usr/local/php5/lib/php’) in /home/content/d/o/o/doorqtech/html/wp-settings.php on line 545

    I’ve deleted the plugin but that doesn’t seem to fix the problem. In fact, it makes it so that any other installs of plugins or upgrades of plugins gives a whole list of header sent errors.

    I’ve looked at line 545

    if ( get_option(‘active_plugins’) && !defined(‘WP_INSTALLING’) ) {

    $current_plugins = get_option(‘active_plugins’);

    if ( is_array($current_plugins) ) {

    foreach ($current_plugins as $plugin) {

    if ( ” != $plugin && 0 == validate_file($plugin) && file_exists(WP_PLUGIN_DIR . ‘/’ . $plugin) )

    include_once(WP_PLUGIN_DIR . ‘/’ . $plugin);

    }

    }

    }

    I can’t see a problem… though I’m no PHP expert. Is WP thinking it’s still supposed to install or use “plugin-commander-i18n?”

    I’m mentioning this here because I’m not sure if it’s directly related to BP or just to the plugin being incompatible with MU.

Viewing 3 replies - 1 through 3 (of 3 total)

  • jodyw1
    Participant

    @jodyw1

    Okay. I’m an idiot.

    I used Cyberduck to look in the plugin directory. Even though WP’s plugin panel didn’t see it, sure enough, that plugin-commander-i18n directory was sitting there, plain as day, thumbing its nose at me and eating my chips.

    I deleted it and it fixed the problem.

    Anyway, just in case this might be some kind of issue for BP, I’m leaving this up until someone else chimes in. Also, just in case someone does a search for controlling plugins per site, you can now see that BP is all you need.

    Don’t make the minor mistake I did.

    :-D


    John James Jacoby
    Keymaster

    @johnjamesjacoby

    Haha curse of the too-smart-for-your-own-good developer strikes again! :D


    jodyw1
    Participant

    @jodyw1

    You have no idea how deep the groove in my forehead is from the number of times I’ve slapped it h gone “d’oh!”

    I haven’t coded in 20 years. I’m amazed at the work Andy and Co did getting this thing to work. Tracking all of the function calls, figuring out what talks to what, etc has been very enlightening. I still haven’t figured it all out yet, so I’m sure there are more questions coming.

    And I’m sure that groove in my forehead will deepen.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin Error’ is closed to new replies.
Skip to toolbar