• Resolved SooBahkDo

    (@soobahkdo)


    Hello,

    Indispensable plugin. Thanks!

    It would be helpful to add checking for Multi-Network Activation so users are advised that:

    ONLY NEEDS TO BE ACTIVE ON ONE NETWORK on MULTI-NETWORK INSTALL. YOU CANNOT ACTIVATE 2ND INSTANCE ON ANY OTHER NETWORK

    Since visibility of active plugins on each network of a multi-network is limited to one network (even using a Network Auditor plugin),

    1) Without knowledge that an instance of the plugin is already active, a user may seek to activate a 2nd instance on a different network and will encounter a FATAL ERROR (but only because the plugin is already active on a different network without the user’s awareness)

    2) The user may or may not even have privileges on the network where the plugin is active and thus could not know that it being active is the reason for the fatal error.

    3) Even if the user has privileges on the network where the plugin is active, determining I which sites on that network where the plugin is active on can be troublesome

    Perhaps the plugin could check for an already running instance of itself and report to the user with a useful message instead of a Fatal Error. Perhaps something like, “User Switching Is already active on XXsitenameXX.”

    Thanks for considering this enhancement request.

    Phil D

    • This topic was modified 6 years, 1 month ago by SooBahkDo.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the message.

    Why is activating User Switching on one network having an affect on another network? That sounds like a problem with your multi-network setup. Why is this specific to User Switching?

    Thread Starter SooBahkDo

    (@soobahkdo)

    Hi John,

    I am not sure about the answer to your inquiries, but here is what I observe and have concluded.

    Other plugins that do not deal with users and which are activated network-wide only affect the network(s) they are activated on. Those plugins’ features only appear on the network(s) where the plugin is network activated.

    I thought perhaps User Switching might be a different case since users are shared across all networks and all sites on a multi-network.

    It seemed possible that because users are common to all sites and networks on the multi-network install, that perhaps only one instance of it might be needed on the main site and the features might be available on all. ??

    When I attempt to activate User Swithing on a network where it is not displaying as activated the following error occurs.

    Plugin could not be activated because it triggered a fatal error.

    Fatal error: Cannot declare class user_switching, because the name is already in use in /home/soobahkdous/public_html/wp-content/plugins/user-switching/user-switching.php on line 36

    Upon further inspection, the User Switching feature displays on the user list page which would seem to indicate the plugin is active elsewhere on the multi-network, but its features are available on all other networks and sites on the install.

    Am I off the road and in the ditch? 🙂

    • This reply was modified 6 years, 1 month ago by SooBahkDo.
    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    I don’t know about being in the ditch 😀 but there’s nothing fundamental in User Switching which means it would cause a fatal when trying to activate it on more than one network.

    It sounds to me like it’s been globally activated, or it’s in mu-plugins, or something. I don’t think the problem is in User Switching because the fatal error your’e seeing is occurring before User Switching even has a chance to hook into WordPress.

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

The topic ‘USE ON MULTI-NETWORK INSTALL’ is closed to new replies.