Multisite UX: deleting a plugin

[saracannon]

Better that current:
Change the wording form the Network Admin Plugin deletion screen from:

"Caution: This plugin may be active on other sites in the network."

to

"Caution: This plugin may be active on sites in the network."

... the current wording assumes that your action is tied to one particular website rather than the network as a whole when you are deleting a plugin. With this change, the warning is still there but does not make any assumptions about weather you are deleting it because you are thinking about one site and not the "others."

Best case scenario:
A check would be run to see if the plugin is actually active and list out which sites it is active on before deletion.

[saracannon]

Screen Shot of Current, Better, and Best scenarios

[saracannon]

diff for the wording change to remove "other"

[professor44]

@saracannon listing the sites is a great way to help users understand where that plugin is activated but listing thousands of sites on that page would be troublesome. Maybe cap it and at 10 sites and add something like "and 23,024 other sites on the network"

[saracannon]

Replying to professor44:

@saracannon listing the sites is a great way to help users understand where that plugin is activated but listing thousands of sites on that page would be troublesome. Maybe cap it and at 10 sites and add something like "and 23,024 other sites on the network"

That sounds great to me!!

[saracannon]

list five and then put "& (count) other sites"

[jeremyfelt]

I'd love to provide a list of sites the plugin is installed in. This would get heavy fast though as there is no per-plugin data. Instead, we would need to query the options for every site on the network.

Improving the message here makes sense. I could even see going stronger with the warning.

There may also be a creative path for gathering and storing per plugin data at the network level.

[SergeyBiryukov]

#53255 was marked as a duplicate.

[SergeyBiryukov]

Just noting that the warning shown on these screenshots is still in core​, but is no longer displayed, apparently due to the "Shiny Updates" changes introduced in [37714] for WordPress 4.6. See #53255.

So the UX could probably use some rethinking to make sure the warning is still displayed when appropriate.