There are several issues with installing network-enabled-only plugins on network sites.
Currently we don't activate plugins when installing them on multi site, but it's a strange experience:
Issue 1: The install button for network-enabled-only plugins installs the plugin, but does not activate and does not provide that information
Issue 2: The install button appears on the main network site for plugins that have already been installed on the network
Steps to reproduce issue 1 & issue 2:





The steps above indicate that it's unclear what's really happening on a main site for a network. When on WordPress.com - is the main site acting as the main site or the network admin? It would be great to make that clearer the way it is clear in wp-admin by the URL and interface:
ie. example.com/wp-admin/network/plugins.php vs example.com/wp-admin/plugins.php
Right now the .org API does not provide the data to see whether a plugin is network-enabled only. The API endpoints that would need to be updated are:
https://api.wordpress.org/plugins/info/1.1/?action=query_plugins and https://api.wordpress.org/plugins/info/1.0/w3-total-cache
Tested and confirmed that a plugin installed on a Jetpack multisite parent site via https://wordpress.com/plugins/ does not show up in the plugin list on WordPress.com after it is installed and that if you click the Install button again it results in an error.
My testing steps:
Result: after installing the plugin, I see a success notice that says the plugin was activated even though it was not:
Successfully installed and activated W3 Total Cache on [sitename].

Seen at https://wordpress.com/plugins/w3-total-cache/disambiguously.com using Firefox 46.0.1 on Mac OS X 10.11.4
Result: the plugin does not appear in the list of plugins at https://wordpress.com/plugins/ for the site and the following error appears if you try to click the Install button again:
An error occurred while installing W3 Total Cache on [sitename].

Seen at https://wordpress.com/plugins/w3-total-cache/disambiguously.com using Firefox 46.0.1 on Mac OS X 10.11.4
I also noticed that the wp-admin > Plugins page lists the plugin as "Network Only":

Seen at http://disambiguously.com/wp-admin/plugins.php using Firefox 46.0.1 on Mac OS X 10.11.4
And the wp-admin > My Sites > Network Admin > Plugins page has a link to "Network Activate":

Seen at http://disambiguously.com/wp-admin/network/plugins.php using Firefox 46.0.1 on Mac OS X 10.11.4
This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 馃檹
Most helpful comment
Tested and confirmed that a plugin installed on a Jetpack multisite parent site via https://wordpress.com/plugins/ does not show up in the plugin list on WordPress.com after it is installed and that if you click the Install button again it results in an error.
My testing steps:
Result: after installing the plugin, I see a success notice that says the plugin was activated even though it was not:
Seen at https://wordpress.com/plugins/w3-total-cache/disambiguously.com using Firefox 46.0.1 on Mac OS X 10.11.4
Result: the plugin does not appear in the list of plugins at https://wordpress.com/plugins/ for the site and the following error appears if you try to click the Install button again:
Seen at https://wordpress.com/plugins/w3-total-cache/disambiguously.com using Firefox 46.0.1 on Mac OS X 10.11.4
I also noticed that the
wp-admin> Plugins page lists the plugin as "Network Only":Seen at http://disambiguously.com/wp-admin/plugins.php using Firefox 46.0.1 on Mac OS X 10.11.4
And the
wp-admin> My Sites > Network Admin > Plugins page has a link to "Network Activate":Seen at http://disambiguously.com/wp-admin/network/plugins.php using Firefox 46.0.1 on Mac OS X 10.11.4