Fixed Mysql error upgrading to 2.3 beta 4

[Marcel Broekema]

Affected version

XF 2.3 beta 4

Made an exact copy of my production forum and (after disabling the Chat and Redis add-ons) see this error:
(second time running php cmd.php xf:upgrade, upgrades ends ok). Same problem when all add-ons are disabled and third try after removing all add-ons:


~/httpdocs$ php cmd.php xf:upgrade
Current version: 2021570
Upgrade target: 2030034 (2.3.0 Beta 4)
Are you sure you want to continue with the upgrade? [y/n] y

Running upgrade to 2.3.0 Alpha, step 1... done.
Running upgrade to 2.3.0 Alpha, step 2... done.
Running upgrade to 2.3.0 Alpha, step 3... done.
Running upgrade to 2.3.0 Alpha, step 4... done.
Running upgrade to 2.3.0 Alpha, step 5... done.
Running upgrade to 2.3.0 Alpha, step 6... done.
Running upgrade to 2.3.0 Alpha, step 7... done.
Running upgrade to 2.3.0 Alpha, step 8...
In AbstractStatement.php line 230:

MySQL statement prepare error [1054]: Unknown column 'priority' in 'field list'


xf:upgrade [--skip-statistics]

Exception query:

INSERT INTO xf_job (execute_class, execute_data, unique_key, manual_execute, trigger_date, priority) VALUES (?, ?, ?, ?, ?, ?) ON DUPLICATE KEY UPDATE
execute_class = VALUES(execute_class),
execute_data = VALUES(execute_data),
manual_execute = VALUES(manual_execute),
trigger_date = VALUES(trigger_date),
last_run_date = NULL,
priority = VALUES(priority)

 

[Marcel Broekema]

BTW was upgrading from 2.2.15 to 2.3 Beta 4

 

[Masetrix]

Found this...

ALTER TABLE xf_job ADD attempts TINYINT UNSIGNED NOT NULL DEFAULT '0' AFTER last_run_date, ADD priority SMALLINT UNSIGNED NOT NULL DEFAULT '100' AFTER attempts;

 

[Chris D]

I feel like we had another report of this but either way it's sorted now.

 

[Marcel Broekema]

upgrading from 2.2.15 to 2.3 Beta 6, still same issue. All addons disabled. This error:
:~/httpdocs$ php cmd.php xf:upgrade
Current version: 2021570
Upgrade target: 2030036 (2.3.0 Beta 6)
Are you sure you want to continue with the upgrade? [y/n] y

Running upgrade to 2.3.0 Alpha, step 1... done.
Running upgrade to 2.3.0 Alpha, step 2... done.
Running upgrade to 2.3.0 Alpha, step 3... done.
Running upgrade to 2.3.0 Alpha, step 4... done.
Running upgrade to 2.3.0 Alpha, step 5... done.
Running upgrade to 2.3.0 Alpha, step 6... done.
Running upgrade to 2.3.0 Alpha, step 7... done.
Running upgrade to 2.3.0 Alpha, step 8...
In AbstractStatement.php line 230:

MySQL statement prepare error [1054]: Unknown column 'priority' in 'field list'


xf:upgrade [--skip-statistics]

Exception query:

INSERT INTO xf_job (execute_class, execute_data, unique_key, manual_execute, trigger_date, priority) VALUES (?, ?, ?, ?, ?, ?) ON DUPLICATE KEY UPDATE
execute_class = VALUES(execute_class),
execute_data = VALUES(execute_data),
manual_execute = VALUES(manual_execute),
trigger_date = VALUES(trigger_date),
last_run_date = NULL,
priority = VALUES(priority)


After this error, did a php cmd.php xf:upgrade again, upgrade process ends without any error:

Current version: 2030010 (step 7)
Upgrade target: 2030036 (2.3.0 Beta 6)
Are you sure you want to continue with the upgrade? [y/n]
php cmd.php xf:upgrade
Current version: 2030010 (step 7)
Upgrade target: 2030036 (2.3.0 Beta 6)
Are you sure you want to continue with the upgrade? [y/n] y

Running upgrade to 2.3.0 Alpha, step 8... done.
Running upgrade to 2.3.0 Alpha, step 9... done.
Running upgrade to 2.3.0 Alpha, step 10... done.
Running upgrade to 2.3.0 Alpha, step 11... done.
Running upgrade to 2.3.0 Alpha, step 12... done.
Running upgrade to 2.3.0 Alpha, step 13... done.
Running upgrade to 2.3.0 Alpha, step 14... done.
Running upgrade to 2.3.0 Alpha, step 15... done.
Running upgrade to 2.3.0 Alpha, step 16... done.
Running upgrade to 2.3.0 Alpha, step 17... done.
Running upgrade to 2.3.0 Beta 1, step 1... done.
Running upgrade to 2.3.0 Beta 1, step 2... done.
Running upgrade to 2.3.0 Beta 2, step 1... done.
Running upgrade to 2.3.0 Beta 2, step 2... done.
Running upgrade to 2.3.0 Beta 3, step 1... done.
Running upgrade to 2.3.0 Beta 3, step 2... done.
Running upgrade to 2.3.0 Beta 4, step 1... done.
Running upgrade to 2.3.0 Beta 4, step 2... done.
Running upgrade to 2.3.0 Beta 4, step 3... done.
Running upgrade to 2.3.0 Beta 6, step 1... done.
All upgrade steps run up to version 2.3.0 Beta 6.

 

[duderuud]

I had the same, upgrading from 2.2.15 to 2.3b7

Running upgrade again resolved the issue.

 

[Marcel Broekema]

issue is still present, upgrading from 2.2.16 (patch2) (all add-ons disabled) to 2.3.0 Release Candidate 2.
Hope to get some tips on this from Xenforo developers....