Managing plugin and theme access for sites

  • Here’s the thing; I have a multisite setup with a bunch of sites underneath it.
    If I install plugins or themes on super-admin level, I can either network activate them or not.

    1. Network activated themes are available for all sites
    2. Not Network activated themes are not available for any site

    1. Network activated plugins are activated for all sites
    2. Not Network activated plugins are optional for all sites

    So two options for both.
    The third option I need is
    3. Optional for some sites

    I have several reasons, but the most important one is premium themes and plugins.
    If one site wants to use a premium theme or plugin, I don’t want to activate the theme/plugin – or make it optional, for all sites of the network. This of course for licence reasons.

    I have used the search option of the forum and found several topics with somehow the same question. However they all are at least two years old an most of them point to plugins which are outdated a long time ago.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Bet Hannon

    (@bethannon1)

    Try leaving the desired/premium plugin deactivated in the network dashboard, and only activate it in the single subsite dashboard.

    For themes, network activate it, go into the subsite, activate the theme, then go back to network Admin and deactivate the theme. It will stay activated in the subsite, no longer be available to all sites.

    Thread Starter Gooly

    (@gooly)

    Thanks for the tip Bet.
    That’s a good tip for the themes. However if I leave the plugins deactivated, still the owners of the subsites will be able to activate it.
    However from now my question only regards the plugins ??
    Thanks for your help.

    Moderator Bet Hannon

    (@bethannon1)

    This is why I never give the clients in our multisites a level above Editor ??

    In that case, I think I might check out the Members plugin by Justin Tadlock, to see if your premium plugins already have capabilities as a part of their code. This plugin would allow you to deny privileges for some plugins and their capabilities. You can also allowed some capabilities – for instance, I can allow a user to view and edit Gravity Forms entries, but not make any changes to the form or the GF settings.

    If the plugins that you need to control access to DON’T have capabilities written into them already, it may be possible to write some functions that would create them.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Managing plugin and theme access for sites’ is closed to new replies.