Cannot upgrade 1.1.x to 1.2.x due to artefact_file_files not being upgraded in correct order
Bug #622763 reported by
Howard Miller
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
High
|
Richard Mansfield | ||
Bug Description
Two additional fields are added into the artefact_file_files table in file artefact/
2008101602 => field 'filetype' is added
2008091100 => field 'fileid' is added
Unfortunately these fields are accessed within the core upgrade script lib/db/upgrade.php. At version point 2009111012 an sql query is run on artefact_file_files accessing the filetype field.
As in an upgrade the core is always upgraded before anything else, if the starting database is old enough (any 1.1.x version I think) then core upgrade will attempt to access fields that do not (yet) exist causing a fatal error and upgrading failing.
Revision history for this message
| Richard Mansfield (richard-mansfield) wrote | #1 |
| Changed in mahara: | |
| status: | New → Fix Committed |
| importance: | Undecided → High |
| assignee: | nobody → Richard Mansfield (richard-mansfield) |
| milestone: | none → 1.2.6 |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks Howard, I'd actually noticed that one previously and fixed it by moving the core 2009111012 upgrade into the file plugin. If you pull the latest it should work.