mahara-contributors team mailing list archive

[Mahara Bot <1243525@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2643
Committed: http://gitorious.org/mahara/mahara/commit/5b0b25425940040d37e6c8e431c0f82c413549c0
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit 5b0b25425940040d37e6c8e431c0f82c413549c0
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Wed Oct 23 16:52:51 2013 +1300

Upgrading $config->minupgradefrom to 1.1 due to failures during upgrade
tests

Bug 1243525: I found that attempting to do a direct upgrade from 1.0 to 1.8 failed in the
"$oldversion < 2008091601" code block. It would appear this has to do with the
former "textbox" block being renamed, and the solution would require that
block to be processed before the main upgrade script. Since that would be somewhat
hard to do, and there presumably aren't that many 1.0 sites still around, I've
simply updated the minupgrade to 1.1.

Change-Id: I9c8fbe06459b5e62382621b1f4308eca8f793d72

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1243525

Title:
  Issues with 1.0->1.8 upgrade path

Status in Mahara ePortfolio:
  In Progress

Bug description:
  See also https://bugs.launchpad.net/mahara/+bug/1238407 (ENGINE=INNODB)
  and https://bugs.launchpad.net/bugs/1174623 (Correct schema drift)

  Since the README still says you can upgrade from 1.0 to master, I
  tested it out prior to the 1.8.0 release. I found a couple of
  problems, which I'll track here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1243525/+subscriptions