this is not possible in (almost) every case. The plugin itself has to have support for the module and disable itself. Some plugins provide essential functions to other plugins as well, disabling these could possibly break your administrators control panel, these plugins kind cannot be removed for the same reason until all the plugins requiring it are removed.
In general it is recommended to try out any major changes in a test installation (accessible for the licensee only) or a copy of your production board.
True, I was thinking that as well. The original thought was the plugin itself would be excluded, but it's not possible. So basically it would almost have to be built-in the core, or is that out of the question too? I'm under the impression that other forum software has this ability built-in their systems. Because not everyone tests every thing ahead of time, they just see a plugin, download and install it, expecting everything to be running smoothly.
Also, not everyone's hosting configurations & etc are the same either, so testing things might not always be an option for letting them know something isn't quite right. But I surely hope there's something that can be done to help users with this issue? Just to have an option to disable all non-core plugins for debugging purposes, or one by one in core will help, of course not touching woltlab system itself nor any woltlab plugins either.
Sorry super bad code example here lol.
But an idea, all woltlab products go untouched/not disabled, whilst other non-core plugins get turned off, either all at once, or one by one. But, I'm not sure, I didn't develop the software of course lol. Just an idea. Or maybe the trouble is the fact that the plugins are requiring or having dependent plugins, is part of issue? Which makes it harder to do an option like this. I'm wondering how other software handles this built-in core feature.