id summary reporter owner description type status priority milestone component version severity resolution keywords cc focuses
22129 Plugins cannot be updated when getting updates from outside the repo griffinjt "This problem in particular is a bug in MultiSite, but it is a general annoyance outside of MultiSite as well.
WordPress can check for and offer updates to plugins that aren't activated if they are listed in the WordPress Plugin Repository. Since the update process grabs all the plugin basenames and checks them against the URL in the plugins_api function, anything found in the repo will be blessed with an update, active or not.
However, plugins that get updates outside of the repo don't get this opportunity if they are not active. I suppose this is expected since the plugin is not active (and therefore does not have the ability to filter the update_plugins transient or the plugins_api function), but it could provide for a poor user experience when they are receiving updates for some deactivated plugins and not others when updates are known to exist.
Beyond this, there is an actual bug with this regarding MultiSite that needs to be addressed. If you have a plugin that is receiving updates outside of the repo when activated on an individual site in MS, the plugin update will be shown when on that site's admin area. However, when you click to process the update (assuming you are a network admin), the update disappears on the Network Updates screen. Why? Because the plugin is not network activated, it is not run and thus no updates are filtered in. This means that there is absolutely no way of automatically updating the plugin unless you network activate it, run the update, and then network deactivate the plugin. Yuck.
I'm not sure what the best way to approach either of these scenarios would be (mainly the second issue with MS), so I wanted to get some other opinions on it." defect (bug) closed normal Multisite 3.4.2 normal wontfix dev-feedback