#31327 closed defect (bug) (fixed)
Shiny Updates: Plugins installed on Multisite shouldn't auto-activate on the primary site
| Reported by: | DrewAPicture | Owned by: | jeremyfelt |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.2 |
| Component: | Plugins | Version: | 4.2 |
| Severity: | normal | Keywords: | needs-testing has-patch |
| Cc: | Focuses: | multisite |
Description
In testing the installation part of the new shiny updates functionality in trunk, I discovered that installing a plugin via the Network Admin ended up installing the plugin and auto-activating it on the primary site. Probably shouldn't do that.
Steps to reproduce (multisite required):
- Navigation to Network Admin > Plugins > Add New
- Install a new plugin by clicking the "Install Now" button
- AJAX in the button should indicate the plugin is being installed
- Navigate to Primary Site > Plugins
- Note that the recently-installed plugin has been installed and is activated
Attachments (1)
Change History (5)
#3
@
10 years ago
- Keywords needs-patch added; has-patch removed
- Severity normal → blocker
I just experienced this behavior with the latest shiny updates 2-20160606 and the latest wordpress multisite. 4.5.2.
- Go to network plugins
- Add plugin
- Install plugin
- Activate plugin
-- Expected behavior: network activation, and stay on Install Plugin page
-- Actual behavior: ejected to main site of the multisite plugin page, and main site has the plugin activated, network is not activated
#4
@
10 years ago
- Keywords has-patch added; needs-patch removed
- Severity blocker → normal
@jeffmcneill Please report issues with the plugin at https://github.com/obenland/shiny-updates/issues.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
When installing a plugin via AJAX request, do not auto-activate if Multisite.