The MU forums have moved to

WPMU Plugin Commander and WPMU 2.6.5 issue (7 posts)

  1. PerS
    Posted 12 years ago #

    When I try to mass activate a plugin using plugin commander 1.1.5, it fails with "Can't load Plugin Commander".

    The url is /wp-admin/wpmu-admin.php?page=Plugin Commander&mass_activate=scissors/scissors.php

    Is this a known issue for wpmu 2.6.5 ?

  2. andrea_r
    Posted 12 years ago #

    I think it's more an issue with the plugin commander. Funnily enough, I think it actually still mass activates the plugin.

  3. PerS
    Posted 12 years ago #

    no it didn't mass activate the plugin

  4. Ovidiu
    Posted 12 years ago #

    though I use that combination, I can't comment as I haven't yet upgraded to 2.6.5

  5. PerS
    Posted 12 years ago #

    I believe I found the reason for this issue, but not a solution .. yet.

    The problem is related to using a different language than the default. My site is in Norwegian (, if I switch back to English, Plugin Commander works fine.

    the log reports:

    "GET /wp-admin/wpmu-admin.php?page=Plugin%20Commander&mass_activate=scissors/scissors.php HTTP/1.1" 500 487 "" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/2008102920 Firefox/3.0.4"

    Innstikk behandler is Norwegian for Plugin Commander

  6. cafespain
    Posted 12 years ago #

    Oh, it may be that something (WordPress or Plugin commander) is translating the menus. I haven't looked at any code so I would assume plugin commander ;p

  7. PerS
    Posted 12 years ago #

    Sure, and you're right. Plugin Commander hard codes it (on line 32):


    Changing it and moving it into function pc_textdomain() fixes this bug:

    function pc_textdomain()
    //		uncommet lines to work around wpmu 1.5.1 and 1.3.3 locale bug (
      global $locale;
      $old = $locale;
      $locale = WPLANG;
      load_plugin_textdomain('plugin-commander', 'wp-content/mu-plugins/plugin-commander-i18n');
      $locale = $old;
      define('PC_CMD_BASE',PC_HOME."?page=" . __('Plugin Commander', 'plugin-commander'));

    I moved it to pc_textdomain to make sure the translation is loaded prior to defining PC_CMD_BASE

    Not sure if I should do the same with define('PC_PLUGINS_CMD_BASE',PC_PLUGINS_HOME."?page=Plugins");

About this Topic