Upgrade from 201 to 21rc2 DB failure

[guenni21]

Hi,
I have done the upgrade from 175 to 201 and it works.
Now I want to upgrade to 21rc2

I have the following problem after running the upgrade script in .../puplic/upgrade folder.

Failed to execute DB schema transformations. MySQL said: Duplicate column name 'archived_by_id'
Error upgrading to version 2.1-rc2

Any suggestions?

Tx

[moorezilla]

I'm getting this same error when trying to upgrade from 2.0.x to 2.1. Not sure how to proceed; seeing if there are some notes about this elsewhere.

I followed procedure here:

/web/wiki/doku.php/migration

[shodgman]

I am having the same problem.
I have upgraded from 1.7.4  to 1.7.4 then proceeded with the instructions for upgrading 1.x to 2.x.
After upgrading to 2.0.1 I tested the login and the GUI says I am still using version 1.7.5.  This is despite the "installed_version.php" file in the config folder saying the version is 2.0.1.

I have done Ctrl - F5 to reset cache and still seems to be the same

When I ran the public/upgrade page to go from 2.0.1 to 2.1 then it gives this duplicate record error.

So, is there a solution to this problem of  upgrading to 2.1 ?
Thanks,

[guenni21]

@morezilla: I have done exactly this before I have started the post.
But it does not work!

Any other solution?

Tx

[sinbad]

me too. seeing all these forum post one can only ask if anyone was able to actually upgrade?

[shodgman]

Not me!  No reply as yet and the bug reported about this issue has not yet been acknowledged yet.

So, I can only assume that people have NOT been able to upgrade from 1.7.5 to 2.1
---
Steve

[sinbad]

I hope someday soon the devs will find a time to tell us how to fix all those broken upgrades. It was never easy to update OG but this upgrade looks like a real disaster.

[moorezilla]

@morezilla: I have done exactly this before I have started the post.
But it does not work!

Any other solution?

Tx

Just to clarify, guenni21, I followed the instructions on the wiki, but I was not able to get the upgrade process to complete. I was not suggesting that you try the instructions, but merely documenting that I had.

[conrado]

Hi everyone. We will be looking into this today.

Are problems still occurring with Feng 2.1 final?

[jron]

I still have this exact same problem with going from 2.0.1 to 2.1 final after upgrading from 1.7.5.

[franponce87]

Hello everyone,
We have found out what the issue is, and its solution, which will be published for next release, and then yes, NO MORE problems when upgrading from 1.7.5 to 2.X IF you follow the instructions of course. Eventually it will become more user friendly though

Here is the fix:
Change all of the content of the file at FENG_ROOT/public/upgrade/templates/db_migration/2_1_molleja.php for the following one:

Code: [Select]

-- <?php echo $table_prefix ?> fo_
-- <?php echo $default_charset ?> DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
-- <?php echo $default_collation ?> collate utf8_unicode_ci
-- <?php echo $engine ?> InnoDB

INSERT INTO `<?php echo $table_prefix ?>file_types` (`id` ,`extension` ,`icon` ,`is_searchable` ,`is_image`) VALUES
 ('34', 'odt', 'doc.png', '1', '0'), ('35', 'fodt', 'doc.png', '1', '0')
ON DUPLICATE KEY UPDATE id=id;
UPDATE `<?php echo $table_prefix ?>permission_groups` SET `type` = 'roles' WHERE `id` <= 13;
UPDATE `<?php echo $table_prefix ?>permission_groups` SET `type` = 'permission_groups' WHERE `contact_id` > 0;
UPDATE `<?php echo $table_prefix ?>permission_groups` SET `type` = 'user_groups' WHERE `type` = '' OR `type` IS NULL;


The difference here is that there no longer are ALTER statements, which were actually already ran in the first process so as to keep your archived items.

Once you make this change, go to your browser and then:
FENG_ROOT/public/upgrade
Select the 2.1 version and voilá!!

We are sorry for this issue, and we thank you for patience and comprehension.

Should anyone find any further problem, please let us know about it so that we can solve it for the 2.1.1 beta version.

Best regards,
Francisco