Zen Cart Logo
Forums / Upgrading to 2.x.x / upgrading from 1.5.1 to 2.1.x

upgrading from 1.5.1 to 2.1.x

Views: 2,057

Results 1 to 18 of 18
17 Dec 2025, 6:32 PM
#1
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

upgrading from 1.5.1 to 2.1.x

Opted to try the Database-only Upgrade, but it stopped saying it could not update to version 1.5.4.

Doing it on a brand new server, with PHP version: 8.2.29 MySQL version: 10.6.24-MariaDB

What can I look at to resolve this?

Attachment 21094

Thanks!

  • Rand
18 Dec 2025, 4:24 AM
#3
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

Thanks! I was able to get through a few more versions, but am now stuck at 1.5.7.

I suspect it's this one:

      - checkType: configValue
        fieldName: ADVANCED_SEARCH_INCLUDE_METATAGS
        expectedResult: 'Include meta-tags in product search?'

Is this something in the configuration table?

I added a record...

Attachment 21095

Is that the idea?

Thanks again!

18 Dec 2025, 10:21 AM
#4
swguy avatar

swguy

Administrator

Join Date:
Feb 2006
Location:
Tampa Bay, Florida
Posts:
10,682
Plugin Contributions:
56

Re: upgrading from 1.5.1 to 2.1.x

I suspect it failed on the prior one - checking this change in 1.5.7

ALTER TABLE orders ADD language_code char(2) NOT NULL default '';

Check your orders table to see if this field is present. It probably isn't because this statement failed, and the statement probably failed because of a date issue.
You can just type in the ALTER TABLE in phpMyAdmin and see the result.

18 Dec 2025, 10:25 AM
#5
swguy avatar

swguy

Administrator

Join Date:
Feb 2006
Location:
Tampa Bay, Florida
Posts:
10,682
Plugin Contributions:
56

Re: upgrading from 1.5.1 to 2.1.x

you should also be able to see the failure in the upgrade logs created in the /logs folder.

18 Dec 2025, 11:44 AM
#6
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

swguy:

I suspect it failed on the prior one - checking this change in 1.5.7

ALTER TABLE orders ADD language_code char(2) NOT NULL default '';

Check your orders table to see if this field is present. It probably isn't because this statement failed, and the statement probably failed because of a date issue.
You can just type in the ALTER TABLE in phpMyAdmin and see the result.

I added that column manually in phpMyAdmin, typing in that returns a Duplicate column name 'language code' message

18 Dec 2025, 12:06 PM
#7
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

InstallDEBUG .log file entiries are all "ALTER command denied to user" "DROP command denied..." "CREATE command denied.."

18 Dec 2025, 12:25 PM
#8
lat9 avatar

lat9

Administrator

Join Date:
Sep 2009
Location:
Stuart, FL
Posts:
14,065
Plugin Contributions:
56

Re: upgrading from 1.5.1 to 2.1.x

Randolph Hoppe:

InstallDEBUG .log file entiries are all "ALTER command denied to user" "DROP command denied..." "CREATE command denied.."
Check your cPanel Database Permissions. The DB_SERVER_USERNAME identified in the configure.php file doesn't have the required permissions to perform the database changes needed for the DB_DATABASE.

18 Dec 2025, 3:27 PM
#9
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

that helped! Thank you!

18 Dec 2025, 3:30 PM
#10
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

Am also seeing a few "Cannot execute because table paypal_testing does not exist. CHECK PREFIXES! " messages

There is not a table called paypal_testing. We use paypal. Is there an SQL statement I can use to add this table? I found the schema page, but not sure how to turn that into SQL

Also DEBUG log mentions something about duplicate key name 'idx_profile_name_zen'

18 Dec 2025, 3:42 PM
#11
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

Oh boy, I used Gemini to produce this:

CREATE TABLE paypal_testing (
paypal_ipn_id int(11) unsigned NOT NULL AUTO_INCREMENT,
order_id int(11) unsigned NOT NULL DEFAULT '0',
custom varchar(255) NOT NULL,
txn_type varchar(40) NOT NULL,
module_name varchar(40) NOT NULL,
module_mode varchar(40) NOT NULL,
reason_code varchar(40) DEFAULT NULL,
payment_type varchar(40) NOT NULL,
payment_status varchar(32) NOT NULL,
pending_reason varchar(32) DEFAULT NULL,
invoice varchar(128) DEFAULT NULL,
mc_currency char(3) NOT NULL,
first_name varchar(32) NOT NULL,
last_name varchar(32) NOT NULL,
payer_business_name varchar(128) DEFAULT NULL,
address_name varchar(64) DEFAULT NULL,
address_street varchar(254) DEFAULT NULL,
address_city varchar(120) DEFAULT NULL,
address_state varchar(120) DEFAULT NULL,
address_zip varchar(10) DEFAULT NULL,
address_country varchar(64) DEFAULT NULL,
address_status varchar(11) DEFAULT NULL,
payer_email varchar(128) NOT NULL,
payer_id varchar(32) NOT NULL,
payer_status varchar(10) NOT NULL,
payment_date datetime NOT NULL DEFAULT '0001-01-01 00:00:00',
business varchar(128) NOT NULL,
receiver_email varchar(128) NOT NULL,
receiver_id varchar(32) NOT NULL,
txn_id varchar(20) NOT NULL,
parent_txn_id varchar(20) DEFAULT NULL,
num_cart_items tinyint(4) unsigned NOT NULL DEFAULT '1',
mc_gross decimal(7,2) NOT NULL DEFAULT '0.00',
mc_fee decimal(7,2) NOT NULL DEFAULT '0.00',
payment_gross decimal(7,2) DEFAULT NULL,
payment_fee decimal(7,2) DEFAULT NULL,
settle_amount decimal(7,2) DEFAULT NULL,
settle_currency char(3) DEFAULT NULL,
exchange_rate decimal(4,2) DEFAULT NULL,
notify_version decimal(2,1) NOT NULL DEFAULT '0.0',
verify_sign varchar(128) NOT NULL,
last_modified datetime NOT NULL DEFAULT '0001-01-01 00:00:00',
date_added datetime NOT NULL DEFAULT '0001-01-01 00:00:00',
memo text,
PRIMARY KEY (paypal_ipn_id, txn_id),
KEY idx_order_id_zen (order_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;

fair enough?

18 Dec 2025, 4:05 PM
#12
shop_suey avatar

shop_suey

Zen Follower

Join Date:
Feb 2014
Location:
Germany
Posts:
375
Plugin Contributions:
0

Re: upgrading from 1.5.1 to 2.1.x

Maybe it is, maybe not.
I don't justice on that.
But IMHO you should know what you do before you. Especially at database work.
For experiments AI is great of course. I myself wouldn't do anything like that.
YES to AI to learn how to navigate and use SQL, if you don't have those skills yet. But NO to AI to "create ABC for me".
But just my 50 cents, of course.

18 Dec 2025, 4:15 PM
#13
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

I removed the key name 'idx_profile_name_zen' from admin_profiles, so the install was able to add the key. Now there is no DEBUG being produced

Still not moving into 1.5.7 or is it 8?

7 logs being produced.

Is

Dec 18 2025 16:02 -- checkPhpVersion
FAILED
(
[version] => 8.3.0
[versionTest] => ge
)

Enough to stop it?

18 Dec 2025, 7:33 PM
#14
swguy avatar

swguy

Administrator

Join Date:
Feb 2006
Location:
Tampa Bay, Florida
Posts:
10,682
Plugin Contributions:
56

Re: upgrading from 1.5.1 to 2.1.x

Nope. This is not the problem.

18 Dec 2025, 7:35 PM
#15
swguy avatar

swguy

Administrator

Join Date:
Feb 2006
Location:
Tampa Bay, Florida
Posts:
10,682
Plugin Contributions:
56

Re: upgrading from 1.5.1 to 2.1.x

At this point I would reload your original database and start the upgrade process again. If you didn't have the ability to do various operations on the database (and it looks like you didn't), who knows what worked and what failed.

18 Dec 2025, 7:51 PM
#16
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

OK. Great idea! Thanks, again!

21 Dec 2025, 2:58 AM
#17
randolph_hoppe avatar

randolph_hoppe

Zen Follower

Join Date:
Jan 2004
Posts:
129
Plugin Contributions:
1

Re: upgrading from 1.5.1 to 2.1.x

It's been quite a ride so far! 2.1.0 is running with a bootstrap template clone. Database upgrade (eventually) went smoothly!

However, looking in my Debug warning log I see:

PHP Warning: Constant SHOW_PRODUCT_MUSIC_INFO_ARTIST already defined in /home/t.../public_html/laravel/app/Models/ProductTypeLayout.php on line 22.

Any idea what's causing that?