Yep, they would be different calls. But that would be a super helpful plugin for multisite admins.
I run two multisite installs – one with about 30 sites, and the other with more than 80. To test for plugin conflicts would mean: documenting all the plugins that are network activated (which isn’t too bad to do), but also documenting which plugins are activated in each subsite at the current moment. Then I would have to go into each subsite to deactivate all of the single site activated plugins, do my testing and go back into every site to reactivate what needs to be reactivated (or I suppose I could document all the activations in subsites, turn all the plugins off by renaming the plugins directory, and then only have to go into the subsites once to reactivate the needed plugins). I would have to check, but I don’t think the network plugin management plugins really give much help for this.
What that means in reality, is that if a multisite has more than a handful of sites, the admin is probably not really able to check for plugin conflicts.
The real advantage would be if you could give away for the network admin to be able to quickly deactivate all plugins, then just as quickly reactivate everything – hopefully, before clients notice that something is missing! ??
If you do decide to move forward with developing something, I would be glad to do some testing for you!
