Duplicate entries from 9.0.6.1 to 9.2

[DazzaJay]

And now in English?

:::EDIT:::
Looks like ben understood it, and he said:

9.0.6.1
9.9 (2005/06/05 12:32:54)



Table Dump:

Code::

-- Host: localhost -- Generation Time: Jul 06, 2008 at 04:58 PM -- Server version: 5.0.51 -- PHP Version: 5.2.6 -- -------------------------------------------------------- CREATE TABLE `cms_blocks` ( `bid` int(11) NOT NULL auto_increment, `bkey` varchar(15) NOT NULL default '', `title` varchar(60) NOT NULL default '', `content` text NOT NULL, `url` varchar(200) NOT NULL default '', `bposition` char(1) NOT NULL default '', `weight` int(11) NOT NULL default '1', `active` tinyint(4) NOT NULL default '1', `refresh` int(11) NOT NULL default '0', `time` varchar(14) NOT NULL default '0', `blanguage` varchar(30) NOT NULL default '', `blockfile` varchar(255) NOT NULL default '', `view` tinyint(4) NOT NULL default '0', `in_module` varchar(255) default '', PRIMARY KEY (`bid`), KEY `title` (`title`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=24 ;

[NanoCaiordo]

I've edited your post removing not needed data.

You are using a 9.1+ table structure.

[DazzaJay]

Probably from a previous Failed update attempt?

[NanoCaiordo]

DazzaJay wrote:

Nah, i restored all the Databases back to the backups before we tried updating.

DazzaJay wrote:

Probably from a previous Failed update attempt?

You know what happen there. Just remove in_module

[DazzaJay]

NanoCaiordo wrote:

You know what happen there. Just remove in_module

See, this is what's annoying, we remove that, fine, run the updater again, and the same problem happens with another table, so we fix that and start the updater again.

Now, even though we fixed the first issue, ran the updater again and fixed the second issue, when we run the updater after this, it reports the first issue again!

This just kept happening over and over again until we had to delete whole tables like cms_admins, after a few of these we just gave up....

[NanoCaiordo]

You don't have to fix a table and run the installer again. A failed upgrade should be handled in a totally different way.

### PREFERRED ###
Use our bug reporting system if you think its a core issue or use our forums if you think its caused by who helps you . . . in both cases we need more details as possible.

### ADVANCED ###
Backup the original and name it "step0", create one more copy and call it "step1". You have to run the upgrade on step1 db.

Upgrade fail: see what happen, prepare step0 to hanlde the error and note the changes.
DROP step1 and copy step0 to step1. Upgrade must run on step1 again.

When the upgrade finish get all your notes and compare the original to step0 .... etc etc. In other words you dont upgrade on the original, you always work in a copy of it. You are also invited to let us know about your saved notes.

You also MUST DROP the db before restoring a copy because of new created tables!!!

[DazzaJay]

All we have been doing is following the Instructions that came with the updater.

[NanoCaiordo]

I see from your table structure that you are not doing that.

[DazzaJay]

We followed the instructions that came with the installer for 9.1 it failed, and thats where all the sites bugs began.

So we waited for the next version, Followed the instructions that came with it, it failed also.

and so on all the way up to the version that is out now.

Either way, all its caused is More bugs.