mahara-contributors team mailing list archive

[Aaron Wells <1243525@xxxxxxxxxxxxxxxxxx>]

Okay, the biggest one is:   https://reviews.mahara.org/2643

I could not successfully upgrade from an installation of 1.0_STABLE, due
perhaps to the reorganization of the "textbox" block to be underneath
artefact/internal? In any case, I was stumped as to how to fix the
issue. However, I could do a direct upgrade from 1.1.0_RELEASE to
1.8_STABLE. So, I've updated the minimum upgrade from 1.0.0 to 1.1.0,
and removed the pre-1.1.0 sections of the upgrade script.

Next is this patch which squelches a warning:
https://reviews.mahara.org/2644

And this patch, which removes a bit of code incompatible with MySQL 5
and no longer in use now that we're not upgrading directly from 1.0:
https://reviews.mahara.org/2645

-- 
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