• Resolved gazouteast

    (@gazouteast)


    On a WP 3.1 multisite install, I am having major problems with plugin availability when logged in as network admin.

    Under WP 3.0.x and earlier, a network admin could go to any site’s admin plugins page and be shown –
    – inactive plugins (with option to activate or network activate)
    – active plugins (this site only)
    – active plugins (network activated)
    and know exactly what was up to date, needed updating, and how it was active.

    Under WP 3.1 this has all gone horribly wrong. On any individual site, it will show plugins active or inactive, but not whether they are MS-plugins, network activatable, or single site activatable.

    Going to Network Admin – Plugins will “sort-of” show what was seen under 3.0.x and earlier, but what is displayed changes depending on which site’s dashboard is being used.

    There is no single plugins page “to rule them all” where an a network admin can get a complete overview of what is happening across the whole installation – this is causing problems reactivating and updating single site plugins, and network activating them from appropriate site dashboards (e.g. BuddyPress related plugins) because on one dashboard they show as active or network activated, but on another they don’t.

    Please devs, roll this one back – it’s a nightmare to manage, the previous system was complex enough, but far easier than this system.

    [moved to Multisite forum]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Going to Network Admin – Plugins will “sort-of” show what was seen under 3.0.x and earlier, but what is displayed changes depending on which site’s dashboard is being used.

    No, Network admin is one area, based off the main iste, and show *network specfic* plguin activation.

    Single site plguisn menu shows what is available to a single site and what is activated on that site, or what can be activated on that single site.

    Network/plugins.php shows network-wide plugins activated and anything else specific to the network as a whole – like mu-plugins.

    There is no single plugins page “to rule them all” where an a network admin can get a complete overview of what is happening across the whole installation

    There are plugins to show you what plugins are singly activated on some of the sites.

    Pro tip: if they are buddypress related plugins, they almost always need to be activated network wide. like buddypress.

    Please devs, roll this one back – it’s a nightmare to manage, the previous system was complex enough, but far easier than this system.

    I doubt this will happen. It was done as a UI improvement, and to really separate the sense of the Network itself being across the whole install. Super admin menu led to a lot of confusion over what affected the network, solely because you could reach it from anywhere.

    Thread Starter gazouteast

    (@gazouteast)

    Super admin menu led to a lot of confusion over what affected the network, solely because you could reach it from anywhere.

    That was exactly why it was SUPER admin – it could be reached from anywhere. Now it’s just “poor cousin fourth removed somewhere on a half sister’s side”.

    Would roll back my sites, but I want to evaluate better what they’ve done with custom post types UI etc, hope they haven’t pigged it up the same way as the wp-stats/jetpack debacle. If they have, I’m rolling back and sticking at 3.0.5 then disabling all the call homes for core and plugins.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    There is no more Dashboard Sites, by the way. Users are treated like they are on WP.com, which means they have no per-site roles granted upon login. Simply, they are faux subscribers. So the move from Super Admin to Network Admin is a part of that. I just leave two tabs open (or use the Snack Bar plugin).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WP3.1 MS erroneous behaviour – plugins available’ is closed to new replies.