28 January 2015, 8:30

Hi Kristoffer,

It sounds like the previous upgrade had only partly succeeded - hence some of the info not expected already exists.

There is no easy fix for this.

Can you check what release and version number the mahara is set to?

 SELECT * FROM config WHERE field IN ('version','release');

It sounds like these are set for an older version but the database info/structure is more current.

One thing you can do - if you know php/mysql is to work out where the previous upgrade got to before failing.

To do this you can look at htdocs/lib/db/upgrade.php file and work out what the last change in the list that exists in your database.

Each upgrade step is listed like so:

    if ($oldversion < [datestring] ) {
         ... changes being made ...
    }

Take the 'datestring' number, eg. 2010061100, and then set that number as the version number in your database. eg

 UPDATE config SET value = '2010061100' WHERE field = 'version';

So now when you try to do the upgrade it will try and start from the later point and avoid clashes with existing data/structure.

Cheers

Robert