If you remove (via rm, or whatever) a plugin while it's enabled, the enabled setting of that plugin remains in LocalSite
.cfg, leading to a somewhat confused InstalledPlugins
page. (Well, really, the relevant variables therein.)
This is a design constraint of manually enabling/disably plugins (not true plug & play.)
A sensible fix is to silently drop a Plugin if the Plugin topic and .pm file cannot be found.
Silently dropped plugins are a nightmare for an installer to debug. There needs to be as much feedback as possible re: the plugin. If it is enabled in the cfg, then it is expected
to be present. ACTIVATEDPLUGINS and FAILEDPLUGINS should be used as advised for working out why a plugin fails.
I just tried deleting the SlideShowPlugin
, by deleting the .pm and then the plugin topic. In both cases the diagnostics on the InstalledPlugins
page are excellent.
May be we should rename the Plugin API to "plug-configure-unplug-configure API"