WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

#13122 closed defect (bug) (worksforme)

upgrade process wp mu 2.9 to wp 3

Reported by: psycolor Owned by: dd32
Milestone: Priority: normal
Severity: critical Version: 3.0
Component: Upgrade/Install Keywords: upgrade mu
Focuses: Cc:

Description

i have experimented with some upgrade scenarios and i hope you will be able to look at what happens in the backend or document the process.

the first step was starting from a clean wp mu install. this worked perfectly from 2.9 to 3.0 beta 1 by overwriting the entire content of the previous mu install.
a warning came up about the salt of nonce key and the removal of the deprecated blogs.php from wp-content. then upgraded the network blogs was also fine.

up to here all was perfect, excellent work!

then i decided to upgrad to the nightly build using the beta-tester plugin and things became problematic.

the install gave me errors in the database structure; when i tried to use the 'repair' option, i've lost completely the MU features and the access to the superadmin.
tables were also corrupted making it impossible to go back.

basically the upgrade, somehow turned the installed version into a single user build. not good! trying to go back to 3.0 beta 1 also didn't work (the single user was working fine at this point), and obviously the old mu version could not recover because tables were changed by the upgrade.

Change History (1)

comment:1 nacin4 years ago

  • Milestone Unassigned deleted
  • Resolution set to worksforme
  • Status changed from new to closed

We've done a lot of changes to the MU upgrade process recently. Additionally, the development version of the beta tester plugin now supports MU -> 3.0.

Note: See TracTickets for help on using tickets.