The Geeklog plugins can be broadly classified into two types. One of them is the standard plugins that ship with Geeklog, and the other is the third-party plugins.
We should be handled with distinction the standard plugins and the third-party plugins.
Because the standard plugins are fully compatible with the current Geeklog system, we do not mind that they are installed automatically.
But for the third-party plugins, it will be necessary to check the compatibility with the current Geeklog system just before the system upgrade.
If not compatible, then the plugin should be automatically disabled before upgrading by install script.
To that end, we should probably add a new data to each plugin to check the compatibility.
Each plugin does have a script that is checked to see if it is compatible. The problem is it is hard to know what will change in the future which can make the current plugin incompatible (as what happened between Geeklog 1.8.x and 2.0.0).
Maybe between a major version change (ie going from 1.x to 2.x) we should have a message box come up asking the user if they would like all third party plugins disabled for the update. One of the Geeklog Core Developers.
The feature to check compatibility each plugin has is not sufficient.
Especially, about the version checking feature of the Geeklog system, it's only to check the lowest (earliest) version of the system that each plugin supports.
The feature we should add would be to check the highest (latest) version of the system that each plugin supports.
In the course of system upgrade, if the version of the system after the upgrade is later than the version the plugin supports, then it's reasonable to automatically disable the plugin. This way would prevent the trouble during the upgrade.
After the system upgrade is complete, it would be sufficient to report that some plugins have been disabled automatically by the system message (instead of the message box asking whether to disable).
After that, the site administrator will take the risk and enable some plugins step-by-step.
Since few years I run multi sites on one Geeklog code. On some sites plugins are enable and some are not, and I do not want to install all plugins on all sites. So, I need to control this action during upgrade and I would appreciate this feature in the next Geeklog version.
Ben I'm available to customise your themes or plugins for your Geeklog CMS
Good point about your situation Ben with multiple sites.
This is also where the plugin repository would help (that has been started but has yet to be finished). The install could check the repository for any new upgrades or incompatibilities. One of the Geeklog Core Developers.