7021 pointsLike some sort of WPMU DEV God"Mindblowingly helpful memberLifetime member
Aaron
Lead Developer
—
4th June 2009 (2 years ago)
Hey guys, I know you'll love this as a lot of you are requesting it around here.
After getting the Supporter plugin, I took a day to create a new plugin managment plugin that supports the native WPMU plugins page and the WPMUdev Premium Supporter plugin!
This is a rewrite of Plugin Commander and is intended to replace it. It uses a backend site admin options page to adjust plugin permissions. The big difference is that users can activate their plugins on the regular WP plugins page! This is the first plugin of it's kind to use the new hooks added in the WPMU 2.7 plugins page and a little creative genius to allow no hacking of core files. Also, if you use the excellent Supporter plugin from premium.wpmudev.org you will be able to choose which plugins can be accessed by supporters only!
For WPMU 2.7.1+ only! Might work for 2.7, but before that the hooks were not in plugins.php yet.
Hey guys, I know you'll love this as a lot of you are requesting it around here.
After getting the Supporter plugin, I took a day to create a new plugin managment plugin that supports the native WPMU plugins page and the WPMUdev Premium Supporter plugin!
This is a rewrite of Plugin Commander and is intended to replace it. It uses a backend site admin options page to adjust plugin permissions. The big difference is that users can activate their plugins on the regular WP plugins page! This is the first plugin of it's kind to use the new hooks added in the WPMU 2.7 plugins page and a little creative genius to allow no hacking of core files. Also, if you use the excellent Supporter plugin from premium.wpmudev.org you will be able to choose which plugins can be accessed by supporters only!
For WPMU 2.7.1+ only! Might work for 2.7, but before that the hooks were not in plugins.php yet.
- users can unfortunately decide to deactivate plugins that were set to automatically be activated at blog creation so I can't force plugin onto users, except by putting them into mu-plugins :-(
- wpmu plugin manager doesn't work with firestats, at least on my isntall, it gives me a 500 server error when trying to mass activate it for all blogs
- also some of the features from this old plugin could be implemented, i.e. the ability to see which blgo has which plugins activated: http://wpmudev.org/project/Plugin-Manager
- I'd suggest an improvement: I started autoactivating quite a few plugin, but this has to be done one-by-one, so it woudl be useful, if those plugins could be visually marked so I know where I have to continue and maybe checkboxes os I can autoactivate several plugins in one batch?
oh, one more: I haven't gottten the supporter plugin activated anywhere, can someone show me a screenshot how this plugin looks with the supporter plugi nactivated? I mean I'm curious where the integration happens :-)
Here is a screenshot of it with Supporter activated.
- users can unfortunately decide to deactivate plugins that were set to automatically be activated at blog creation so I can't force plugin onto users, except by putting them into mu-plugins :-(
That's because I didn't want to recreate the "Activate All" option found on the plugins page in 2.7.1 which emulates putting it in the mu-plugins folder.
As far as the firestats problem, I am not sure what is causing that as the mass activation code is an exact copy of Plugin Commander's. Maybe try mu-plugins instead.?
ok, thx guys for the quick responses and screenshots, still:
That's because I didn't want to recreate the "Activate All" option found on the plugins page in 2.7.1 which emulates putting it in the mu-plugins folder.
meaning that "activate all" activates plugins for all existing blogs and sets them to auto activate for new blogs too? wasn't aware of that.
As far as the firestats problem, I am not sure what is causing that as the mass activation code is an exact copy of Plugin Commander's. Maybe try mu-plugins instead.?
did you try the mass activation of firestats? is it just me with this problem?
What do you mean by try mu-plugins? meaning I should put firestats there? the reason plugin commander was written was that firestats doesn't work from mu-plugins :-)
btw. just activated and configured supporters plugin and wpmu plugin manager and now, all existing blogs I declared to be supporter blogs by extending their free demo period, lost their "active plugins" meaning they are all naked :-( or did I do something wrong?
meaning that "activate all" activates plugins for all existing blogs and sets them to auto activate for new blogs too? wasn't aware of that.
Yes
did you try the mass activation of firestats? is it just me with this problem?
What do you mean by try mu-plugins? meaning I should put firestats there? the reason plugin commander was written was that firestats doesn't work from mu-plugins :-)
No, have no experience with firestats and can't imagine what is different between this and Plugin Commander to cause a problem. Try the "Activate All" option on the plugins page.
btw. just activated and configured supporters plugin and wpmu plugin manager and now, all existing blogs I declared to be supporter blogs by extending their free demo period, lost their "active plugins" meaning they are all naked :-( or did I do something wrong?
Wpmu plugin manager may have caused that. There is no functionality to deactivate plugins when you change permissions. The only time it will deactivate plugins is when they load or reload the plugins.php page so there is no way it could deactivate current plugins for ALL users. It could also have been caused while installing the supporter plugin if you didn't leave out the plugins functionality.
this link .http://wpmudev.org/project/wpmu-plugin-manager gives me version 1.1 have you just forgotten to change the version number or is there another problem?
if we are now using the built-in site wide activation to make plugins active for all blgos and automatically activate them for new ones, then use your plugin to allow certain plugins for everyone, nobody or supporters we catually have to use your auto-activate feature to have plugins active for all users upon blog creation AND give them the chance to turn them off, right?
I noticed not even saite admins are able to deactivate a site wide activated plugin for a certain blog without deactivating it globally :-(
(I know its not really related to your plugin but I am trying to grasp hwo your plugin and the built in features work together)
Great work Aaron, this was badly needed! I'm thinking the perfect trifecta to this plugin and the supporter plugin would be......... the ability to add domain mapping as an option offered only to supporters..... which would be possible if the domain mapping plugin liked living in the plugins folder vs mu-plugins, but it doesn't. :)
I will probably be putting up an job desc on the new job board for this shortly if anyone is interested in building this capability...
I installed the modified domain mapping plugin and it seems to work perfectly.
Only one minor request if it's possible:
Can we set it so that the 'master admin/me' can use domain mapping without being a supporter?
I have a few sites already mapped that are my personal blogs on the network, thankfully the new domain mapping plugin from you did not mess with them as they still work.
I did however try to make another one of my blogs a mapped domain, but received the 'supporter message' so that I was not able to use it myself.
also, as I am a non-profit network, there will be customers that I would like to offer free domain mapping to. I am not sure how to allow it so that the master admin/me can map domains for people that I choose.
sorry to complicate the issue....
btw.. I used your contact form on your website as there seems to be no pm's on this site. We run very similar Christian networks and I was really impressed with what you have setup, very nice indeed.
I went into the plugins management and set a few to 'allow all'
I then went to one of my blogs that requires a few plugins to work, having already set them to allow all.
I then activate a plugin, it says activated, however if I leave the plugin page and then come back, the plugin is no longer activated, but shows as inactive.
Running wpmu 2.7.1/buddypress 1.0.1
Am I missing a step somewhere?
also:
As the admin I have a number of my own blogs, some custom, some not so much. Some of my blogs require custom plugins to function properly. What I can't figure out is how to allow my 'admin' blogs to use these plugins but to not present them to other users to use.
Is there a setting somewhere that I can tick to allow certain blogs to use certain plugins, and not other blogs?
I know this would probably be easy if the supporter plugin allowed multiple 'groups' as we could then assign abilities to a supporter group #1, that supporter group #2 does not have, however I don't think supporter plugin does this yet.
finally:
I have a ton of plugins installed on the server that I have set to 'supporter only' however when a 'non-supporter' blog goes to their plugin directory they still see all the plugins, which I am sure is going to confuse them. Is there a way to hide the plugins list from those that are not supporters?
sorry for so many questions, just trying to figure out the best way to handle this as there is not 'multi-level' supporter plugins available yet.
I then went to one of my blogs that requires a few plugins to work, having already set them to allow all.
I then activate a plugin, it says activated, however if I leave the plugin page and then come back, the plugin is no longer activated, but shows as inactive.
Can't understand how that would happen. Perhaps you didn't click the save options button on the plugin management page?
Is there a setting somewhere that I can tick to allow certain blogs to use certain plugins, and not other blogs?
You can go in as site admin and activate any plugin for a specific blog by going into it's dashboard.
I have a ton of plugins installed on the server that I have set to 'supporter only' however when a 'non-supporter' blog goes to their plugin directory they still see all the plugins, which I am sure is going to confuse them. Is there a way to hide the plugins list from those that are not supporters?
Not planning on changing that. That is the entire reason for the plugin as it makes the users know what they are missing until they become a supporter.
also, as I am a non-profit network, there will be customers that I would like to offer free domain mapping to. I am not sure how to allow it so that the master admin/me can map domains for people that I choose.
I have updated the plugin to always allow site admins.
I have done some more testing and here is what I have found so far.
1. If I turn a blog into a 'supporter' blog, and set the plugin to either 'allow all' or 'supporter only' I can then activate a plugin on the blog in question without problem.
2. The problem arrises if I do the following.
Set the plugin to 'allow all'
***I do not turn the blog into a supporter blog***
I then go to the blog and activate the plugin.
The plugin says activated, but If I leave the plugin page and then return later, the plugin is deactivated. Same thing happens if I try to activate more than one plugin for a non-supporter blog.
Are you sure you have the latest plugin version 1.2? Try as I might, I can't reproduce your problem. It just works. Under the management page are you sure you saved your permission preferences?
With the latest version, the only time it can possibly deactivate a plugin is when you do a bulk activate action. Do you have WPMU 2.7.1? This might not work on any other version.
under management page I have always clicked the submit button to set the changes I make.
I am running wp 2.7.1 with buddypress 1.0.1, though I'm pretty sure buddypress would not be causing any of these problems.
I'll keep digging around to see if anything else is possibly causing this.
I do have a minor suggestion though:
There are plugins that I ONLY want to run on either my blogs or very trusted friends blogs such as the plugins that allow php/javascript insertion into posts. Other plugins like buddypress for obvious reasons would never be run by a regular blog on the network *this is why I suggested being able to hide certain plugins" same goes for themes.
I have some themes on the system that require certain plugins, but if those plugins were 'accidentally' activated by other blogs using other themes it would cause conflicts, jquery etc... That is another reason to 'hide' certain plugins from users.
I would be more than interested in paying for development of the 'ultimate' vs. of this plugin if that is possible. Features like allowing admin override of any plugin for blogs whether they are supporter status or not. Ability to hide admin defined plugins from everyone. I can go on and on so I'll stop now LOL..
thanks for all your help in this. If I can provide any information that would help to solve this issue just let me know.
When you return to the plugin management page do the select boxes reflect the permissions you saved previously? Also when you recreate the plugin deactivation are you logged in as site admin or the non-supporter?
Features like allowing admin override of any plugin for blogs whether they are supporter status or not.
Site admin already can activate plugins for non-supporter blogs.
As for the other suggestions, I'll contact you via email for those changes.
I just installed the plugin manager and when I go to my admin and look in the Plugin Management there are no plugins there. Should it automatically show the plugins that I had previously in the mu-plugins file? Or am I missing a step here??
Thanks!
@Aaron: did you forget to change the version number? mine still says 1.2
besides, would it be possible/desireable to change the sort order of plugins on the plugins page? I have loads of plugins and I thought it would be better if the plugin could be changed so there are sections, i.e. right now there are links for ALL plugins, active plugins, recently active plugins, inactive ones.
Could your plugin maybe show the ones available for users on top, followed by the supporter ones? and if a user is a supporter, just show them all in one list?
I made some usefull plugin autoactivated, but when user create blog, Plugin Manager automatically set it to disabled because user is not supporter. How can I make some plugin not to be switched off by Plugin Manager?
@e.yatsik, did you set that specific plugin to be Supporter only? Because that would be your problem then (when user isn't a Supporter they don't have access to the plugins that are Supporter only).
@e.yatsik, yes you are correct. This plugin manager automatically senses the use of the supporter plugin. So the supporter-plugins.php file that comes with the supporter plugin package needs to be deleted because it will cause issues like the one you are experiencing.
When I try to adjust the plugins options in the "Plugin Management" page and click "update", the settings are not sdaved and I am directed to the dashboard page. Has any one else experienced this?
I am using the supporter plugin as well and have removed the support-plugins.php file.
7021 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Lead Developer
—
15th September 2009 (2 years ago)
#
2.0 has just been released.
NEW! Added the ability to override plugin access permissions for individual blogs via their backend edit section, just like you can do with themes. Thanks to Shawn of Anointed.net for sponsoring this plugin addition for the community.
Also, I know this plugin comes with Supporter, but that is what I want to avoid. I simply want a plugin that allows me to hide certain plugins from users on their Plugins page. I am not looking for supporter integration!
Responses (62)
Member — 5th June 2009 (2 years ago) #
Awsome that is great.
Thanks for sharing
Member — 5th June 2009 (2 years ago) #
Nice! :D
Founder & CEO — 5th June 2009 (2 years ago) #
That's truly excellent work - I'm impressed :)
Member — 5th June 2009 (2 years ago) #
WOW. I didn't see the announcement here, so I mentioned it at the default mu forums, with some questions and suggestions: http://mu.wordpress.org/forums/topic/12603?replies=5
will make a short list of them here:
Member — 5th June 2009 (2 years ago) #
oh, one more: I haven't gottten the supporter plugin activated anywhere, can someone show me a screenshot how this plugin looks with the supporter plugi nactivated? I mean I'm curious where the integration happens :-)
Member — 5th June 2009 (2 years ago) #
You just get an extra option in the select field for activation (namely "Supporters").
Lead Developer — 5th June 2009 (2 years ago) #
Here is a screenshot of it with Supporter activated.
That's because I didn't want to recreate the "Activate All" option found on the plugins page in 2.7.1 which emulates putting it in the mu-plugins folder.
As far as the firestats problem, I am not sure what is causing that as the mass activation code is an exact copy of Plugin Commander's. Maybe try mu-plugins instead.?
Lead Developer — 5th June 2009 (2 years ago) #
Here is a screenshot of the end user plugins page when they are not a supporter.
The red "Supporter Only" links take them to the supporter check-out page instead of activating plugins.
Member — 5th June 2009 (2 years ago) #
ok, thx guys for the quick responses and screenshots, still:
meaning that "activate all" activates plugins for all existing blogs and sets them to auto activate for new blogs too? wasn't aware of that.
did you try the mass activation of firestats? is it just me with this problem?
What do you mean by try mu-plugins? meaning I should put firestats there? the reason plugin commander was written was that firestats doesn't work from mu-plugins :-)
btw. just activated and configured supporters plugin and wpmu plugin manager and now, all existing blogs I declared to be supporter blogs by extending their free demo period, lost their "active plugins" meaning they are all naked :-( or did I do something wrong?
Member — 5th June 2009 (2 years ago) #
Thanks, Aaron! I've been trying to figure out how to do something like this. I'm looking forward to trying it!
Lead Developer — 5th June 2009 (2 years ago) #
Yes
No, have no experience with firestats and can't imagine what is different between this and Plugin Commander to cause a problem. Try the "Activate All" option on the plugins page.
Wpmu plugin manager may have caused that. There is no functionality to deactivate plugins when you change permissions. The only time it will deactivate plugins is when they load or reload the plugins.php page so there is no way it could deactivate current plugins for ALL users. It could also have been caused while installing the supporter plugin if you didn't leave out the plugins functionality.
I'll look into that more.
Lead Developer — 5th June 2009 (2 years ago) #
I have released a small update to the plugin in the same place FYI.
Lead Developer — 5th June 2009 (2 years ago) #
Ok, just released 1.2 (thanks to you bug testers).
Fixed bug that deactivated unallowed plugins when user visits plugins page. (preserves "grandfathering" after permission changes)
http://wpmudev.org/project/wpmu-plugin-manager
Member — 5th June 2009 (2 years ago) #
Hi Aaron,
I love what I see. I'm using buddypress 1.0 with wpmu 2.7.1 and version 1.2 of Plugin Manager. [see edit below]
When I update plugin manager i get this error:
"Cannot load wp-content/mu-plugins/mp-plugin-manager.php" and the configuration is not saved.
Is this BP compatible, I didn't see that it was not.
[edit] I am using Statspress Reloaded, I deactivated and the plugin works without error and updates.
thanks, -terry
Member — 7th June 2009 (2 years ago) #
this link .http://wpmudev.org/project/wpmu-plugin-manager gives me version 1.1 have you just forgotten to change the version number or is there another problem?
Lead Developer — 8th June 2009 (2 years ago) #
Sorry, it was 1.2, just didn't change the number in the source. Fixed now.
Member — 9th June 2009 (2 years ago) #
another question:
if we are now using the built-in site wide activation to make plugins active for all blgos and automatically activate them for new ones, then use your plugin to allow certain plugins for everyone, nobody or supporters we catually have to use your auto-activate feature to have plugins active for all users upon blog creation AND give them the chance to turn them off, right?
I noticed not even saite admins are able to deactivate a site wide activated plugin for a certain blog without deactivating it globally :-(
(I know its not really related to your plugin but I am trying to grasp hwo your plugin and the built in features work together)
Lead Developer — 9th June 2009 (2 years ago) #
Yes, that's how I designed it. I always wanted to give users the chance to deactivate a plugin in case it was giving them problems.
Member — 10th June 2009 (2 years ago) #
Great work Aaron, this was badly needed! I'm thinking the perfect trifecta to this plugin and the supporter plugin would be......... the ability to add domain mapping as an option offered only to supporters..... which would be possible if the domain mapping plugin liked living in the plugins folder vs mu-plugins, but it doesn't. :)
I will probably be putting up an job desc on the new job board for this shortly if anyone is interested in building this capability...
Member — 10th June 2009 (2 years ago) #
Thank you for the plugin, it is exactly what I have been searching for and will really help a lot
I would absolutely love to see domain mapping ability added to supporters only as well.
Lead Developer — 10th June 2009 (2 years ago) #
Domain Mapping for Supporters Only
Here you go guys. No job board posting necessary. If you appreciate it feel free to send a little donation for my time. Thanks!
Just right click and save to mu-plugins:
http://media.missionsplace.com/domain_mapping.php
It adds a little notice message and disables the form for non supporters.
Oh, and maybe get Donncha something off his wishlist as he is the amazing brains behind domain mapping.
Member — 10th June 2009 (2 years ago) #
Wow that was fast LOL
I installed the modified domain mapping plugin and it seems to work perfectly.
Only one minor request if it's possible:
Can we set it so that the 'master admin/me' can use domain mapping without being a supporter?
I have a few sites already mapped that are my personal blogs on the network, thankfully the new domain mapping plugin from you did not mess with them as they still work.
I did however try to make another one of my blogs a mapped domain, but received the 'supporter message' so that I was not able to use it myself.
also, as I am a non-profit network, there will be customers that I would like to offer free domain mapping to. I am not sure how to allow it so that the master admin/me can map domains for people that I choose.
sorry to complicate the issue....
btw.. I used your contact form on your website as there seems to be no pm's on this site. We run very similar Christian networks and I was really impressed with what you have setup, very nice indeed.
thanks again
Member — 10th June 2009 (2 years ago) #
When trying to use the plugin manager, I went in and chose a few plugins to allow for all to use.
when click submit I get
Cannot load wp-content/mu-plugins/mp-plugin-manager.php.
Member — 10th June 2009 (2 years ago) #
nm I'm an idiot LOL
I didn't rename the download file to remove the numbers before the plugin name... all is solved now
Member — 10th June 2009 (2 years ago) #
LOL. yet another question:
I went into the plugins management and set a few to 'allow all'
I then went to one of my blogs that requires a few plugins to work, having already set them to allow all.
I then activate a plugin, it says activated, however if I leave the plugin page and then come back, the plugin is no longer activated, but shows as inactive.
Running wpmu 2.7.1/buddypress 1.0.1
Am I missing a step somewhere?
also:
As the admin I have a number of my own blogs, some custom, some not so much. Some of my blogs require custom plugins to function properly. What I can't figure out is how to allow my 'admin' blogs to use these plugins but to not present them to other users to use.
Is there a setting somewhere that I can tick to allow certain blogs to use certain plugins, and not other blogs?
I know this would probably be easy if the supporter plugin allowed multiple 'groups' as we could then assign abilities to a supporter group #1, that supporter group #2 does not have, however I don't think supporter plugin does this yet.
finally:
I have a ton of plugins installed on the server that I have set to 'supporter only' however when a 'non-supporter' blog goes to their plugin directory they still see all the plugins, which I am sure is going to confuse them. Is there a way to hide the plugins list from those that are not supporters?
sorry for so many questions, just trying to figure out the best way to handle this as there is not 'multi-level' supporter plugins available yet.
Lead Developer — 11th June 2009 (2 years ago) #
Can't understand how that would happen. Perhaps you didn't click the save options button on the plugin management page?
You can go in as site admin and activate any plugin for a specific blog by going into it's dashboard.
Not planning on changing that. That is the entire reason for the plugin as it makes the users know what they are missing until they become a supporter.
Lead Developer — 11th June 2009 (2 years ago) #
I have updated the plugin to always allow site admins.
Member — 11th June 2009 (2 years ago) #
Thank you Aaron.
What is the link to the newest download?
Lead Developer — 11th June 2009 (2 years ago) #
The link is the same.
Member — 14th June 2009 (2 years ago) #
I have done some more testing and here is what I have found so far.
1. If I turn a blog into a 'supporter' blog, and set the plugin to either 'allow all' or 'supporter only' I can then activate a plugin on the blog in question without problem.
2. The problem arrises if I do the following.
Set the plugin to 'allow all'
***I do not turn the blog into a supporter blog***
I then go to the blog and activate the plugin.
The plugin says activated, but If I leave the plugin page and then return later, the plugin is deactivated. Same thing happens if I try to activate more than one plugin for a non-supporter blog.
Lead Developer — 15th June 2009 (2 years ago) #
Are you sure you have the latest plugin version 1.2? Try as I might, I can't reproduce your problem. It just works. Under the management page are you sure you saved your permission preferences?
With the latest version, the only time it can possibly deactivate a plugin is when you do a bulk activate action. Do you have WPMU 2.7.1? This might not work on any other version.
Member — 16th June 2009 (2 years ago) #
I am using the plugin from your link
http://media.missionsplace.com/domain_mapping.php
it says version 0.4.1
under management page I have always clicked the submit button to set the changes I make.
I am running wp 2.7.1 with buddypress 1.0.1, though I'm pretty sure buddypress would not be causing any of these problems.
I'll keep digging around to see if anything else is possibly causing this.
I do have a minor suggestion though:
There are plugins that I ONLY want to run on either my blogs or very trusted friends blogs such as the plugins that allow php/javascript insertion into posts. Other plugins like buddypress for obvious reasons would never be run by a regular blog on the network *this is why I suggested being able to hide certain plugins" same goes for themes.
I have some themes on the system that require certain plugins, but if those plugins were 'accidentally' activated by other blogs using other themes it would cause conflicts, jquery etc... That is another reason to 'hide' certain plugins from users.
I would be more than interested in paying for development of the 'ultimate' vs. of this plugin if that is possible. Features like allowing admin override of any plugin for blogs whether they are supporter status or not. Ability to hide admin defined plugins from everyone. I can go on and on so I'll stop now LOL..
thanks for all your help in this. If I can provide any information that would help to solve this issue just let me know.
Lead Developer — 16th June 2009 (2 years ago) #
Are you really sure you're running 1.2 (checked the source of mp-plugin-manager.php)? http://wpmudev.org/project/wpmu-plugin-manager.
When you return to the plugin management page do the select boxes reflect the permissions you saved previously? Also when you recreate the plugin deactivation are you logged in as site admin or the non-supporter?
Site admin already can activate plugins for non-supporter blogs.
As for the other suggestions, I'll contact you via email for those changes.
Member — 17th June 2009 (2 years ago) #
I just installed the plugin manager and when I go to my admin and look in the Plugin Management there are no plugins there. Should it automatically show the plugins that I had previously in the mu-plugins file? Or am I missing a step here??
Thanks!
Lead Developer — 17th June 2009 (2 years ago) #
It only manages plugins that are in the "wp-content/plugins" folder. Plugin files in mu-plugins are activated sitewide in WPMU.
Member — 17th June 2009 (2 years ago) #
ok, thanks so much Aaron!
Lead Developer — 18th July 2009 (2 years ago) #
For all who care, i've uploaded a new version to support WPMU 2.8.1.
http://wpmudev.org/project/wpmu-plugin-manager
Member — 18th July 2009 (2 years ago) #
Good work Aaron.
Member — 20th July 2009 (2 years ago) #
@Aaron: did you forget to change the version number? mine still says 1.2
besides, would it be possible/desireable to change the sort order of plugins on the plugins page? I have loads of plugins and I thought it would be better if the plugin could be changed so there are sections, i.e. right now there are links for ALL plugins, active plugins, recently active plugins, inactive ones.
Could your plugin maybe show the ones available for users on top, followed by the supporter ones? and if a user is a supporter, just show them all in one list?
does this make sense to you?
Lead Developer — 20th July 2009 (2 years ago) #
Ya, I always forget to update the number in the source. Ordering should be easy, just have to sort the array.
Member — 25th July 2009 (2 years ago) #
v. 1.3.2. working great on 2.8.2 ... thanks!
What are the chances of adding an Auto-Activate (Supporters) feature? Enabling certain plugins by default for Supporters would be just grand.
Lead Developer — 25th July 2009 (2 years ago) #
Good idea, i'll look into it.
Member — 25th July 2009 (2 years ago) #
WMPU 2.7.1 + Supporter + Plugin Manager
I made some usefull plugin autoactivated, but when user create blog, Plugin Manager automatically set it to disabled because user is not supporter. How can I make some plugin not to be switched off by Plugin Manager?
Member — 25th July 2009 (2 years ago) #
@e.yatsik, did you set that specific plugin to be Supporter only? Because that would be your problem then (when user isn't a Supporter they don't have access to the plugins that are Supporter only).
Member — 25th July 2009 (2 years ago) #
@hiranthi: No, I set some plugins to be auto-activated on blog create. But I found some mistery in supporter-plugins.php:
function supporter_plugins_disable_plugins() {if ( !is_supporter() ) {
$active_plugins = get_option('active_plugins');
if ( !empty( $active_plugins ) ) {
deactivate_plugins( $active_plugins );
}
}
}
Maybe this lines disable ALL plugins to unsupporters. I think, I need remove supporter-plugins.php in order to use Plugin Manager. Am I right?
Member — 25th July 2009 (2 years ago) #
@e.yatsik, yes you are correct. This plugin manager automatically senses the use of the supporter plugin. So the supporter-plugins.php file that comes with the supporter plugin package needs to be deleted because it will cause issues like the one you are experiencing.
Member — 28th July 2009 (2 years ago) #
When I try to adjust the plugins options in the "Plugin Management" page and click "update", the settings are not sdaved and I am directed to the dashboard page. Has any one else experienced this?
I am using the supporter plugin as well and have removed the support-plugins.php file.
Lead Developer — 29th July 2009 (2 years ago) #
Try upgrading to the latest version. A bug existed for some browsers in the post that's now fixed.
Member — 29th July 2009 (2 years ago) #
I have the most recent version (1.3.2). any other thoughts on how to fix this? thanks!
Member — 12th August 2009 (2 years ago) #
Just upgraded to 1.4.1 running on mu 2.8.3 and it seems to be still working like a charm.
If you ever get around to adding Auto-Activate (Supporters) that would be just grand! in your copious free time that is... ;-)
Thanks again.
Lead Developer — 2nd September 2009 (2 years ago) #
If someone wants to sponsor that change for the community contact me at aaron
AT
missionsplace.com
Free time is short right now ;-)
Lead Developer — 15th September 2009 (2 years ago) #
2.0 has just been released.
NEW! Added the ability to override plugin access permissions for individual blogs via their backend edit section, just like you can do with themes. Thanks to Shawn of Anointed.net for sponsoring this plugin addition for the community.
Get it here: http://wpmudev.org/project/wpmu-plugin-manager
Member — 8th July 2010 (1 year ago) #
Is this plugin still available? The link no longer works, and I would find this really helpful for my current installation...
Member — 8th July 2010 (1 year ago) #
Also, I know this plugin comes with Supporter, but that is what I want to avoid. I simply want a plugin that allows me to hide certain plugins from users on their Plugins page. I am not looking for supporter integration!
Lead Developer — 8th July 2010 (1 year ago) #
Here you go:
Member — 9th July 2010 (1 year ago) #
Thanks Aaron. You're a lifesaver!
EDIT: Tried using it and I got an issue that wpmu-admin.php could not be found in wp-admin. Where can I get that file?
Lead Developer — 9th July 2010 (1 year ago) #
It's not 3.0 ready find-replace wpmu for ms and it may work.
Developer — 9th July 2010 (1 year ago) #
@aaron - thanks, just grabbed to see if I can integrate into a rule for membership as well.
Member — 25th January 2011 (1 year ago) #
HI,
Are there plans to update this plugin for WP 3.0.4? When I click on the link to go to the plugin manager, it is no where to be found?
Thanks
Terence
Sales & Support Pro — 25th January 2011 (1 year ago) #
Hey Terence!
The current version of Supporter (that's version 2.2.7) has been tested for compatibility with 3.0.4 so should work fine!
Are you having trouble with? Let me know and we'll try to get you sorted...
Phil
Member — 6th March 2011 (1 year ago) #
For an unofficial working version, check here: http://premium.wpmudev.org/forums/topic/plugin-commander-or-plugin-manager
Lead Developer — 29th March 2011 (1 year ago) #
Hey guys, finally got around to updating it for WP 3.1 and putting it on wp.org:
http://wordpress.org/extend/plugins/multisite-plugin-manager/
Enjoy!
Become a member