1.4.2 -> 1.5 breaks installation

[Number8]

In my 1.4.2 OG site I went to Administration->Upgrades.  Selected the automatic upgrade.  Selected 1.4.2 to 1.5.

Got this error message:
-- <snip successful stuff>
-- Test query has been executed. Its safe to proceed with database migration.
-- Failed to execute DB schema transformations. MySQL said: Table 'og_template_parameters' already exists
-- Error upgrading to version 1.5

When I try to go my OG installation, I get this message:
Query failed with message 'Unknown column 'updated_by_id' in 'field list''

Any hints on how to un-break my OG installation?

[Bithunter]

I've to edit \opengoo\public\upgrade\templates\db_migration\1_5_figazza.php to fix the upgrade.

[Number8]

I've to edit \opengoo\public\upgrade\templates\db_migration\1_5_figazza.php to fix the upgrade.

Could you share what the edits are to make the upgrade work?

[Number8]

Another similar report:  http://forums.opengoo.org/index.php?topic=2282.msg8770#msg8770

[robbrandt]

Running the upgrade, I get:

Config file found and loaded. File '/config/config.php' exists and is writable Folder '/config' exists and is writable Folder '/cache' exists and is writable Folder '/tmp' exists and is writable Folder '/upload' exists and is writable Extension 'mysql' is loaded Extension 'gd' is loaded Extension 'simplexml' is loaded Upgrade script has connected to the database. Test query has been executed. Its safe to proceed with database migration. Upgrade script has connected to the database. Test query has been executed. Its safe to proceed with database migration.
Fatal error: Call to undefined method FigazzaUpgradeScript::checkColumnExists() in C:\wwwroot\opengoo\public\upgrade\scripts\FigazzaUpgradeScript.class.php on line 184

[Number8]

Can I just re-install the 1.4.2 files to get my OG site working again, or did the 'upgrade' wreck the db?

[robbrandt]

No,it looks bleak for 1.4.2.  I restored by database, but after changing all the version numbers in the obvious places to this newbie, I still can't convince opengoo that it isn't version 1.5 and that it needs to upgrade the database.

So I have moved on to looking at the upgrade scripts and applying them by hand.

[Number8]

So I have moved on to looking at the upgrade scripts and applying them by hand.

I am far from accomplished with php and sql, but that looks like several hours work, trying to figure out what was accomplished by the upgrade script before it crashed and burned, and then applying the rest of the changes individually...

Good luck, let us know how it goes.

[robbrandt]

I give up, my installation is hosed and I'm crippled.

I tried running the 1.5 sql template, substituting all the variables for their default values.  When I try to access OpenGoo I get:

We are sorry, but OpenGoo is not currently able to execute your request. An Error Report has been sent to the administrator.

I have successfully reverted to 1.4.2 though, simply by restoring the db backup I made prior to upgrading, and uploading the 1.4.2 files.

[Number8]

I give up, my installation is hosed and I'm crippled.
<snip>
I have successfully reverted to 1.4.2 though, simply by restoring the db backup I made prior to upgrading, and uploading the 1.4.2 files.

My installation is mangled, too.  
Unfortunately, I don't have a recent db backup, since I (naively) count on an upgrade script to do the right things, including not crushing a working web site.

robbrandt: How do you backup and restore your OG db?

[robbrandt]

My guess is that 1.5 was tested against 1.4 or 1.41, but not 1.42.

I suppose you could do a fresh install of 1.5 and copy your data across, or at least look where the schema might be different.  Worst case you can start comparing data for configuration differences and make them the same.

[Bithunter]

I've to edit \opengoo\public\upgrade\templates\db_migration\1_5_figazza.php to fix the upgrade.

Could you share what the edits are to make the upgrade work?

Scripts it´s not atomic, so I run it, see the error, edit the file, run again, edit again for next error, etc.
Final edit it´s not useful, you should check step by step ...

[ignacio]

Hi all,

The solution as Bithunter suggested is to repeat this procedure until you get a successful upgrade:

1) run the upgrade
2) get an error?
    a) YES: erase the line that throwed the error (or the first line if you are not sure) of 'public/upgrade/templates/db_migration/1_5_figazza.php' and go to 1)
    b) NO: You have upgraded successfully.

Of course we will try to improve this for version 1.6. There are several things we can do to improve this, one is using transactions to avoid ending with a broken installation. We would also like to split the upgrade process in smaller steps, however this conflicts with running the upgrade in one transaction. We'll have to give it some thought.

Thanks all for your patience.

[Number8]

The solution as Bithunter suggested is to repeat this procedure until you get a successful upgrade:
1) run the upgrade
2) get an error?
    a) YES: erase the line that throwed the error (or the first line if you are not sure) of 'public/upgrade/templates/db_migration/1_5_figazza.php' and go to 1)
    b) NO: You have upgraded successfully.

That's a solution?  I'll wait for 1.6 before trying to upgrade any more 1.4.2 installations...

[tuba]

hi all
I had the same problem

Running the upgrade, I get:

Config file found and loaded. File '/config/config.php' exists and is writable Folder '/config' exists and is writable Folder '/cache' exists and is writable Folder '/tmp' exists and is writable Folder '/upload' exists and is writable Extension 'mysql' is loaded Extension 'gd' is loaded Extension 'simplexml' is loaded Upgrade script has connected to the database. Test query has been executed. Its safe to proceed with database migration. Upgrade script has connected to the database. Test query has been executed. Its safe to proceed with database migration.
Fatal error: Call to undefined method FigazzaUpgradeScript::checkColumnExists() in C:\wwwroot\opengoo\public\upgrade\scripts\FigazzaUpgradeScript.class.php on line 184

• I made the query directly in mysql
  

Code: [Select]

ALTER TABLE `".TABLE_PREFIX."users` ADD COLUMN `updated_by_id` int(10) unsigned default NULL;(don't forget to change ".TABLE_PREFIX." with your prefix )

• commented the lines 184 to 188 of FigazzaUpgradeScript.class.php
• and restart the update without any problem

may be it will work for you