I get the convenience…
Yep, that’s the reason. I don’t mind removing the “network only” but we’ll need to find a good, sensible way to add some description somewhere so people know what to expect.
Hi @azaozz,
I think it’s quite clear already, the only thing i.m.o. is that it shouldn’t be available for network wide only if installed in a network.
Network admins can then choose what to do:
– Enable for network and gain access to network settings
– Or enable for each site separately and configure the plugin there.
If you want I can make a PR on GitHub.
My only concern here is to not break user expectations when first enabling the plugin. Ideally there should be a brief “explanation” shown only to network admins on the plugins page. However not seeing a good way to add that, any ideas?
-
This reply was modified 7 years, 5 months ago by
Andrew Ozz.
My user expectation was that I could activate it where I want :). I pre-configured this plugin on all sites and networks I manage pre-5.0 to make sure everything was ready to go 5.0 if needed. And now with the latest version I needed to go through all network installations again to reconfigure.
I see no point in forcing network activation only. Networks admins understand the idea of network-wide and site-specific plugins. Most plugins allow this so I don’t see the need of adding any explanation for network wide settings.
I do think that a link on the network plugins page to where the settings are (maybe even an anchor link) would be very handy.
Anyhow, that is my opinion 🙂 Thank you for this plugin!
There are few PRs that implement this. Going to work on that over the holidays and push a new beta soon (it will need some testing) 🙂
Ok thanks! Just give me a heads up and I’ll test the beta!
I’ll mark this as resolved here.
