Bug #34209
Migration Wizard broken
| Status: | Resolved | Start date: | 2012-02-23 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Migration | |||
| Target version: | 6.0 beta1 | |||
| Votes: | 0 |
Description
Starting with a clean 4.6.4 intro package installation (switching the Core files to the Incubator after the installation), I'm ending up with "Oops, an error occurred! Local default storage could not be initialized" when I try to open up the migration wizard. As people are supposed to review stuff on Saturday in Stuttgart and on Sunday in Laax I assume that this issue has high priority at the moment ... anyone other than me able to reproduce it?
History
Updated by Tolleiv Nietsch about 1 year ago
Mainly caused because within the constructor the repositories are used which rely on existing database tables (to use the Repositories) ... but that's nothing you can rely on in the migration wizards...
Workaround for now - run the "Compare database" before the upgrade wizards.
Updated by Tolleiv Nietsch about 1 year ago
- Status changed from New to Under Review
Added a third "Init" Wizard which creates all sys_file* tables. See commit 093b5a25be8ab30bd148dbd33647816ca5de3a12
Updated by Benjamin Mack about 1 year ago
- Category set to Migration
Updated by Benjamin Mack about 1 year ago
- Status changed from Under Review to Resolved
Fixed, works.