Author Topic: 3.1.1 -> 3.2.1 upgrade probs revealing after several months of live working... (Read 529 times)

myles · October 01, 2010, 04:49:01 am

It is increasingly clear that an upgrade from 3.1 to 3.2 that reported 'successful' has in fact left the database in a state somewhere between the two. This was done many long working weeks ago.

Reverting to the earlier database will, I believe, wipe our the data we currently have, and I don't think the a dump from the current database will 'fit' in the 3.1 database - this is because the upgrade was apparently successful and changed the database structure, and we now have data that fits that new structure not the 3.1 schema.

We appear to be in limbo, although strangely we have a live installation that is apparently working.

mdlueck · October 03, 2010, 01:56:31 pm

3.2.1 caught my eye, as that version for us had a nasty bug. However for us it blew up while updating the database.

3.2.2 supposedly fixed it. I custom fixed 3.2.1, and have recently upgraded to 3.2.3 - completely skipping 3.2.2 all together.

The bug we ran into:

Red error after 2.0.7 -> 3.2.1 upgrade "The second argument should be either an"
http://forum.civicrm.org/index.php/topic,15222.0.html

CiviCRM Community Forums (archive)

News:

Author Topic: 3.1.1 -> 3.2.1 upgrade probs revealing after several months of live working... (Read 529 times)

myles

3.1.1 -> 3.2.1 upgrade probs revealing after several months of live working...

mdlueck

Re: 3.1.1 -> 3.2.1 upgrade probs revealing after several months of live working...