Feature #475
closedMove Critical Plugins to mu-plugins
0%
Description
Before the upgrade, we had several critical plugins activated sitewide rather than sitting in mu-plugins. We should look through and see whether there were any critical plugins that should be moved to mu-plugins. For instance, where is Askimet right now?
Related issues
Updated by Boone Gorges over 13 years ago
Akismet runs in mu-plugins on our installation, but it really shouldn't.
Moving plugins to mu-plugins that are not designed to be there is bound to break something. I'll look over the list of what's running networkwide, but I would guess that there will be few if any cases where it will be possible or desirable to move them.
Updated by Matt Gold over 13 years ago
Okay.
There are two issues here:
-- I was thinking about ticket 464 and wondering whether it might have affected any other plugins. Are all of the plugins we used to have running sitewide now running sitewide?
-- I noticed an uptick in comment spam and wondered whether it might be related.
I'm up for whatever solution works best.
Updated by Boone Gorges over 13 years ago
- Target version changed from 1.1.3 to 1.1.4
Updated by Boone Gorges over 13 years ago
- Status changed from Assigned to Rejected
I had a look at the list of network-activated plugins and none of them are appropriate for moving to mu-plugins. Most of them either are BP-dependent (in which case they are activated network-wide necessarily) or have complex folder/file structures, and thus can't run in mu-plugins.
I don't have an easy way to see which plugins were running network-wide right before upgrading to Commons 1.1, but a glance at the snapshots on cdev and on my local installation suggest that nothing has been lost. I am highly dubious that #464 was a case of WP doing something funny; more likely something is wrong with MPO that kept it from reactivating itself after the upgrade. Now that it's in mu-plugins, it's no longer relevant.