I remember when I had plugin commander I was able to enable a specific plugin for just one blog by going to the backend of the (non supporter) blog as admin and activating it.
Now, since upgrading to wpmu plugin manager which can switch plugins on for supporters only, I am unable to activate a plugin just for one blog. Well, I can activate it but it doesn't stay activated.
is there a way I can activate a plugin just for one blog without having to set the plugin as supporter only? (I only want one blog to be able use that particular plugin)
I remember when I had plugin commander I was able to enable a specific plugin for just one blog by going to the backend of the (non supporter) blog as admin and activating it.
Now, since upgrading to wpmu plugin manager which can switch plugins on for supporters only, I am unable to activate a plugin just for one blog. Well, I can activate it but it doesn't stay activated.
is there a way I can activate a plugin just for one blog without having to set the plugin as supporter only? (I only want one blog to be able use that particular plugin)
I don't have the supporter-plugins.php file anywhere (didn't even knew that one existed!). All I have to do with supporter in mu-plugins are
supporter-ads
supporter-framework v1.5.5
supporter-quota v.1.5.5
supporter-themes v1.0.2
widget-supporter v1.6.2
widget-supporter-badge v1.5.5
using mp-plugin-manager v1.2
I did some peeking in mp-plugin-manager and I can see the function mp_pm_check_activated which I think is doing it as it takes effect on the
active_plugins filter and uses it's internal function to deactivate a plugin if it's not in the user_control or auto_activate or supporter_control arrays which are stored in the site options
I guess I can do some fudging to add another link to the plugin description on the plugin page list so that an admin can set the plugin to be available, clicking that will update_site_option with key name mp_pm_custom_plugins and add that array check to the mp_pm_check_activated function.
unless of course, that's a good suggestion for an update to the plugin that could save me the trouble? :-)
I re-read you post and thought of something. The plugin that you are trying to activate for a non-supporter, is it by chance enabled as a supporter only plugin in the plugin manager?
awesome Aaron thanks! I see I was on the right track with what I was thinking of doing to the source. Lucky you answered me here before I started adding chunks of code to the older version, your solution was a lot neater :-)
Yup, that is the first thing I always do however in this case my thoughts were, that this was to be something "special" because, when I attempt to "unzip" or explore the plug-in I get:
"The compressed (zipped) folder C:\users\blah\blah\downloads\94613807_mu-plugin-mamager.zip is invalid
Hence the explanation of my above procedure
Also, I never have read or heard mention that the premium plug-ins were to be handle in a special manner
I just read the instructions to make certain nothing drastic is going to happen to:
1) My database
2) This somewhat fragile platform
Does anyone have a link to a valid "compressed file"
Please note that wpmudev.org is a site where anyone can upload plugins. They're not premium plugins like on this site. So they're sometimes provided as php files instead of zip files and not all of them have instructions.
Yeah -- I'll pass on that for now, I actually have traffic on the site, it would be nice to be able to pick and choose for blog owners, but for now I simply have plug-in disabled in the options panel...
what I do to activate a plugin or theme for just one specific blog is to make it the applicable Theme/Plugin Pro Site Feature but not network activated, I then go to the blog I want the theme or plugin on and activate it there.
I then go back and change the specific plugin or theme back to "none" and as the message says something like "the theme/plugin activated on the site(s) wll not be removed"
In other words once I activated it on the target blog even deactivating in the Network admin does not remove it from the blog in which it was activated on.
because even if logged into the sub site as Super Admin and as it says:
"As a Super Admin you can activate any plugins for this site."
you cannot activate it because it does not show as a choice.
After seeing your reply I immediately tested this exact theory and found that for both plugins and themes it does not work ..... they do not show to activate them.
They are not authorized for that blog/web site in the first place.
Responses (17)
Member — 9th October 2009 11:14 #
Would you happen to have supporter-plugins.php installed in mu-plugins from the supporter package? If so, delete it.
Member — 9th October 2009 12:19 #
I don't have the supporter-plugins.php file anywhere (didn't even knew that one existed!). All I have to do with supporter in mu-plugins are
supporter-ads
supporter-framework v1.5.5
supporter-quota v.1.5.5
supporter-themes v1.0.2
widget-supporter v1.6.2
widget-supporter-badge v1.5.5
using mp-plugin-manager v1.2
I did some peeking in mp-plugin-manager and I can see the function mp_pm_check_activated which I think is doing it as it takes effect on the
active_plugins filter and uses it's internal function to deactivate a plugin if it's not in the user_control or auto_activate or supporter_control arrays which are stored in the site options
I guess I can do some fudging to add another link to the plugin description on the plugin page list so that an admin can set the plugin to be available, clicking that will update_site_option with key name mp_pm_custom_plugins and add that array check to the mp_pm_check_activated function.
unless of course, that's a good suggestion for an update to the plugin that could save me the trouble? :-)
Member — 9th October 2009 14:15 #
I re-read you post and thought of something. The plugin that you are trying to activate for a non-supporter, is it by chance enabled as a supporter only plugin in the plugin manager?
Lead Developer — 9th October 2009 17:48 #
Author here, update your wpmu plugin manager plugin. It's at version 2 now!
It will solve your problem and add new features (mark a plugin(s) to always be available to a specific blog).
http://wpmudev.org/project/wpmu-plugin-manager/notes
Member — 10th October 2009 07:08 #
awesome Aaron thanks! I see I was on the right track with what I was thinking of doing to the source. Lucky you answered me here before I started adding chunks of code to the older version, your solution was a lot neater :-)
Member — 23rd October 2009 00:54 #
I just received a "fatal error" in the zip file when I attempted to install it via upload
Incompatible archive PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature
I am doing something wrong here?
Erstwhile founder — 23rd October 2009 01:29 #
Hiya,
Please unzip the package on your local machine and follow the instructions. Our plugins should not be installed via the admin panel.
Thanks,
Andrew
Member — 23rd October 2009 01:39 #
Yup, that is the first thing I always do however in this case my thoughts were, that this was to be something "special" because, when I attempt to "unzip" or explore the plug-in I get:
"The compressed (zipped) folder C:\users\blah\blah\downloads\94613807_mu-plugin-mamager.zip is invalid
Hence the explanation of my above procedure
Also, I never have read or heard mention that the premium plug-ins were to be handle in a special manner
I just read the instructions to make certain nothing drastic is going to happen to:
1) My database
2) This somewhat fragile platform
Does anyone have a link to a valid "compressed file"
Erstwhile founder — 23rd October 2009 01:52 #
Hiya,
If you're downloading the file from the following page then it's not a zip file, it's a php file.
http://wpmudev.org/project/wpmu-plugin-manager
Please note that wpmudev.org is a site where anyone can upload plugins. They're not premium plugins like on this site. So they're sometimes provided as php files instead of zip files and not all of them have instructions.
Thanks,
Andrew
Member — 23rd October 2009 01:59 #
Yeah -- I'll pass on that for now, I actually have traffic on the site, it would be nice to be able to pick and choose for blog owners, but for now I simply have plug-in disabled in the options panel...
Will work around it I suppose
Member — 29th December 2011 12:34 #
Is it a better solution to active pro sites and use that to determine plugin access? Or use the plugin manager plugin?
Support Kangaroo — 29th December 2011 14:34 #
Greetings :-)
what I do to activate a plugin or theme for just one specific blog is to make it the applicable Theme/Plugin Pro Site Feature but not network activated, I then go to the blog I want the theme or plugin on and activate it there.
I then go back and change the specific plugin or theme back to "none" and as the message says something like "the theme/plugin activated on the site(s) wll not be removed"
In other words once I activated it on the target blog even deactivating in the Network admin does not remove it from the blog in which it was activated on.
Joe :-)
Member — 29th December 2011 18:45 #
Thanks. I will give it at try.
Member — 29th December 2011 19:43 #
Why not simply go to the blog's back end, logged in as superadmin, and activate the plugin?
Support Kangaroo — 29th December 2011 19:51 #
Greetings Anders :-)
because even if logged into the sub site as Super Admin and as it says:
"As a Super Admin you can activate any plugins for this site."
you cannot activate it because it does not show as a choice.
After seeing your reply I immediately tested this exact theory and found that for both plugins and themes it does not work ..... they do not show to activate them.
They are not authorized for that blog/web site in the first place.
Joe :-)
Member — 29th December 2011 20:04 #
I see... That's how I always do it, I suppose Supporter or somnething else complicates it in this case.
Take care
Support Kangaroo — 29th December 2011 20:37 #
Greetings anders :-)
you are absolutely correct that the Pro Sites plugin complicates the issue :-)
If you are not using the Pro Sites Plugin or formally called supporter plugin - the way you mentioned is absolutely correct and efficient :-)
Joe :-)
Become a member