Feature #296
closedSelective plugin activation
Added by Matt Gold over 13 years ago. Updated over 13 years ago.
0%
Description
Hi Boone, After out meeting with the Yale team, you mentioned that you knew of several plugins that allowed plugins to be enabled selectively on a MultiSite install. Can you let me know which one you think is best and install it if possible?
Related issues
Updated by Boone Gorges over 13 years ago
- Status changed from Assigned to Reporter Feedback
Here's a rundown of what I know about.
1) http://wordpress.org/extend/plugins/restrict-multisite-plugins/ allows super admins to disable access to certain plugins from being activated by individual blog admins. Simple, but not configurable on a by-user basis - a single plugin is either available networkwide, or is not. Super admins can always override.
2) http://wordpress.org/extend/plugins/wp-manage-plugins/ allows you to hide the plugins page from users. Maybe not fine-grained enough.
Neither is perhaps exactly what you're looking for, but (1) is probably closer. What do you think?
Updated by Matt Gold over 13 years ago
Honestly, Boone, neither one of these is what I was looking for. I'm thinking specifically about the unfiltered-MU plugin, which would be great for advanced members, but dangerous to have available as a default. Maybe we should contact Ioannis about his plugin?
Updated by Boone Gorges over 13 years ago
- Target version changed from 1.1 to 1.2
I just emailed him (and forgot to cc you, sorry).
Updated by Boone Gorges over 13 years ago
- Status changed from Reporter Feedback to Assigned
- Target version changed from 1.2 to 1.1
See http://wordpress.org/extend/plugins/plugin-visibility-manager/. Might get this into 1.1 after all, pending some tests
Updated by Boone Gorges over 13 years ago
I've been playing with Yianni's plugin and it's really great. The only big downside is that it makes all plugins hidden networkwide by default, so after this plugin is activated someone will have to go down the plugin list and unhide the plugins that should be available to everyone. This should probably be done within a few days of when the upgrade happens.
On a related note, I disagree that giving access to Unfiltered MU is generally a good idea. HTML is filtered for a reason. If there is ever an instance where users can't post some tag, let me know and we'll get a plugin for that specific purpose.
Updated by Boone Gorges over 13 years ago
Updated by Matt Gold over 13 years ago
"On a related note, I disagree that giving access to Unfiltered MU is generally a good idea."
Agreed -- thought I made that point above, but maybe I left you with the mistaken impression that it should be made widely available. Just the opposite -- I'm talking about making it available, extremely selectively, to people whom the Commons dev team trusts because of long working relationships -- people like Luke, for instance, who wanted something like this on a Commons blog he ran a few years ago. Anyway, I think we're on the same page on this.
As for the plugin activation, wouldn't that have to be done at the time of upgrade? Otherwise, we risk deactivating plugins that people depend on. does the plugin just hide the menus, or does it actively deactivate (if that makes sense) the plugins? If the latter, then installing this could screw up a bunch of blogs.
Updated by Boone Gorges over 13 years ago
- Status changed from Assigned to Resolved
Truthfully, I would prefer if Unfiltered MU were unavailable to everyone. Running a blog on the Commons is importantly different from running your own WP install: here you share a space with lots of other people, and with that comes a certain amount of responsibility as well as some limitations. But I take your point.
This plugin does not deactivate any plugins. It just hides them in the UI.
Updated by Matt Gold over 13 years ago
Okay -- I understand that reasoning and agree with it.
Glad to hear about the way Yanni's plugin works.