-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would recommand to have options in settings (web interface) to activate and desactivate plugins too (restricted to the user ?).
And maybe a way to install them (but with an options in the configuration for shared installations where 'simple users' shouldn't install plugins..). Regards, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: http://getfiregpg.org iEYEARECAAYFAkiW/XwACgkQjKKs5/FTCjW0ywCeOx6cSzw3THzYF62G2SYzVCY2 4uIAoJBxE83UTnJJb+sVp82G8ggD3sQU =kMB8 -----END PGP SIGNATURE----- On Mon, 4 Aug 2008 14:19:24 +0200, Cor Bosman <[EMAIL PROTECTED]> wrote: >> Yes, agree. I thought about it but someone on the list denied the use of >> configuration. >> But I think this is a must-have. >> $rcmail_config['disabled_plugins'] = 'plugin2 plugin3::mail-compose.* >> plugin3::settings.*'; >> could be a problem because a plugin could possibly rely on some actions > - >> which could be turned off (2nd and 3rd example). What about: >> $rcmail_config['enabled_plugins'] = array( 'plugin1', 'plugin2' ); >> If a plugin has parts which could be turned off and on it should have > it's >> own configuration. This is IMHO the plugin part. > > I agree with this. There should be an enabled_plugins config setting. > One reason for this would be that it will allow RC to ship with a basic > set of plugins in place without them being on by default just because > they're there. > > Cor > _______________________________________________ > List info: http://lists.roundcube.net/dev/ -- Maximilien Cuony [The_Glu] http://theglu.org _______________________________________________ List info: http://lists.roundcube.net/dev/
