[osCmax v2.5x] upgrade from beta 1 to beta 2

[cindyt2009]

Hi,

I have been working with 2.5x beta1. I tried to upgrade using the steps shown in the beta 3 version - 1st doing the beta1 to beta2 SQL and I get the following error message:

Error

SQL query:
#
# CHANGED TABLES
#
ALTER TABLE `languages` ADD COLUMN `meta_keywords` varchar( 255 ) COLLATE latin1_swedish_ci NULL AFTER `sort_order` ,
COMMENT = '';


MySQL said:
#1060 - Duplicate column name 'meta_keywords'

Any ideas?

(Please note this ha nothing to do with cujo's issue under the like topic. I think I confused someone by posting under his concerns)

Thanks,
C

[michael_s]

I modified the sql file to ignore duplicate columns, so it will be more fault tolerant.

Try this attached sql on your restored original database and let me know how it goes. See also cujo's thread as I posted an updated sql file for him to try. You will need that for step 2 of your upgrade process.

[cindyt2009]

Michael,

I went back and did the following: ran the install on beta3 which of course puts in a whole new database (without products that I had added). I then did a restore of the backup database I had done before the update. I then ran the file you sent me and it loaded perfectly! YEAH!

Then, after another 2 backups (better safe than sorry), I did the file you had sent to cujo....and received the following error message:

Error

SQL query:
ALTER IGNORE TABLE `orders_products_attributes` ADD COLUMN `weight_prefix` char( 1 ) NOT NULL AFTER `price_prefix` ,
ADD COLUMN `options_values_weight` decimal( 6, 3 ) NOT NULL DEFAULT '0.000' AFTER `weight_prefix` ,
COMMENT = '';


MySQL said:
#1060 - Duplicate column name 'weight_prefix'

Any ideas?

And no, I did not run either the beta1 to beta 2 upgrade or the beta2 to beta 3 that were included in the beta3 release.

[cindyt2009]

One more thing....despite the fact i reloaded my backup before the first file you sent, i have data in the admin side, but none on the catalog side. categories are there - nothing else - just a really big error message that is probably related to the above issues.
C

[michael_s]

You should not be running the installer to do this upgrade. The installer is for doing new installations.

Follow these instructions step by step:

1. You should not be loading the beta 3 database or running the installer at any point during the upgrade process. You need to start with your original unmodified beta 1 database.

2. Then run the beta1 to beta 2 sql file through phpmyadmin directly on your Beta 1 database. DO NOT RUN THE INSTALLER, just use the sql file through phpmyadmin directly on your database.

3. Then run the beta2 to beta 3 sql file through phpmyadmin directly on your Beta 1 database. DO NOT RUN THE INSTALLER, just use the sql file through phpmyadmin directly on your database.

Then overwrite all the beta 1 files on your server with the beta 3 files via ftp, omitting the install directory as it is simply not needed to upgrade.

That is all there is to it.

If you are doing anything differently than the above instructions, that is your problem. Just follow the above instructions to the letter.

[cindyt2009]

OK...thank you.

I went back and restored everything to the original beta1 db. I ran the beta1 to beta2 upgrade and it ran perfectly. Another backup and I ran the beta2 to beta3...this is the error message I received:

Error

SQL query:
ALTER TABLE `orders_products_attributes` ADD COLUMN `weight_prefix` char( 1 ) NOT NULL AFTER `price_prefix` ,
ADD COLUMN `options_values_weight` decimal( 6, 3 ) NOT NULL DEFAULT '0.000' AFTER `weight_prefix` ,
COMMENT = '';


MySQL said:
#1060 - Duplicate column name 'weight_prefix'

I did not run the 'install'....any ideas?

(and thanks for the help!)
C

[cindyt2009]

Sorry...still getting the same error message as above....when I jump from b2 to b3....

Error

SQL query:
ALTER TABLE `orders_products_attributes` ADD COLUMN `weight_prefix` char( 1 ) NOT NULL AFTER `price_prefix` ,
ADD COLUMN `options_values_weight` decimal( 6, 3 ) NOT NULL DEFAULT '0.000' AFTER `weight_prefix` ,
COMMENT = '';


MySQL said:
#1060 - Duplicate column name 'weight_prefix'

I did not run the 'install'....any ideas?

(and thanks for the help!)
C

[cindyt2009]

OK...I reviewed the upgrade issues some were having for the b2 to beta3 and followed the one that said to enter each update manually. I did that - left out the ones that were giving me "duplicate' keeps (like weight-prefix) and all went perfectly.

Thanks for the advice and all the help. Sorry for being such a pain.
Cindy

[michael_s]

You should not get that error if you are running a beta 1 stock database. Here is why:

The beta 1 database structure for the orders_products_attributes table is:

  orders_products_attributes_id int NOT NULL auto_increment,
  orders_id int NOT NULL,
  orders_products_id int NOT NULL,
  products_options varchar(32) NOT NULL,
  products_options_values varchar(32) NOT NULL,
  code_suffix varchar(16) NOT NULL,
  options_values_price decimal(15,4) NOT NULL,
  price_prefix char(1) NOT NULL,

Notice there is no field called weight_prefix in the above structure.

The beta1 to beta2 upgrade sql file does not modify the orders_products_attributes table.

So after running the beta1 to beta 2 upgrade sql, your table structure will be the following (identical to the first structure):

  orders_products_attributes_id int NOT NULL auto_increment,
  orders_id int NOT NULL,
  orders_products_id int NOT NULL,
  products_options varchar(32) NOT NULL,
  products_options_values varchar(32) NOT NULL,
  code_suffix varchar(16) NOT NULL,
  options_values_price decimal(15,4) NOT NULL,
  price_prefix char(1) NOT NULL,

Again, note there is no field called weight_prefix in the above structure.


Now you run the beta2 to beta 3 sql and that does modify the above table by adding weight_prefix. Because weight_prefix is not already present in the table, it will insert properly.

So, the conclusion I have to make is you were not running the default Beta1 table structure to begin with. At some point you added weight_prefix prior to running the upgrade sql. That is the only explanation, since beta 1 and beta 2 databases do not have the field weight_prefix in that table. Since you never posted the table schema as I requested, there is no way for me to confirm this.

I am glad you sorted it out. The problem is that you were not starting from the required beta 1 table structure.

[cindyt2009]

Thank you....I appreciate all the help and support - which is amazing!
C