[pLog-svn] Site-wide control of plugins

[Jon Daley]

 	I think it is fine for admins to have full control over the blogs. 
They have control anyway, so it is just a matter of making things easier 
for them.
 	In this example from the forums, where he wants to enable auth 
image everywhere, he also has to go edit templates to make it work, 
including any user-specific templates, so it isn't just a matter of making 
the auth image plugin global.
 	I am not sure what it would look like to have plugin unspecific 
global methods - I guess the plugins have to know about it anyway, but 
perhaps the pluginbase class implements whatever function, and then 
children can override it if they need to.
 	I guess what comes next is that people want to edit most blogs, 
but not all.  One possible solution, though not feasible for the people 
who have tons of blogs, but would satisfy lots of people would be to have 
an "su" sort of function, where the site admin could become any other user 
without needing to know his password.  That would be really neat, and the 
most useful for me, as a site admin with a handful of blogs, I don't 
really need any site-wide capabilities and don't mind logging in to each 
user if I had to do some site-wide operation.

On Sun, 19 Feb 2006, Oscar Renalias wrote:
> http://forums.lifetype.net/viewtopic.php?p=23441#23441
>
> Other than allowing admins to access the contents of any blog, there is an 
> issue regarding site-wide activation of plugins. I am considering this as a 
> useful addition to 1.1but I have a couple of alternatives about how to do it. 
> Either we leave it up to plugins to code support for site-wide 
> (de)activation, or we implement support for this in the plugin framework.