#15826 closed enhancement (maybelater)
Updating core of a network install should go to upgrade sites
| Reported by: | defries | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Multisite | Version: | 3.1 |
| Severity: | normal | Keywords: | upgrade, network |
| Cc: | Focuses: |
Description
When using WordPress as a network I think it's a miss when updating the core you're not being redirected to /wp-admin/network/upgrade.php as this clearly is the next step.
I realize that not every update will have a db change, but I'm guessing that can be filtered?
Change History (3)
#2
@
16 years ago
- Resolution → maybelater
- Status new → closed
There has been some talk of merging upgrader.php with the unified updater. We can revisit this later if it is not addressed in 3.2.
Version 0, edited 16 years ago by
(next)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Even though this is specific to updating, changing component to Multisite so it will be on @petemall's report.