#41233 closed enhancement (duplicate)
Plugin activation / deactivation is a pain for network.
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.9 |
Component: | Networks and Sites | Keywords: | |
Focuses: | multisite | Cc: |
Description
I think plugin activation / deactivation is a pain for network, as hooks are not correctly launched.
Even if the $network_wide
parameter passed to the activation/deactivation hook determines whatever to do, there are still cases when it's not working.
We also have to think about one though, which is when creating a new site. It's indeed tricky.
I am using this plugin to manage this, and some times I am doing it programmatically, which is the next way :
I do it by using REST API and/or cron, to iterate each sites of the network for wanted plugin activation / deactivation.
Change History (4)
Note: See
TracTickets for help on using
tickets.
Related: #37656