Upgrading ojs from 3.3.0.21 to 3.5.0.1 ERROR: Upgrade failed: DB: SQLSTATE[42000]

Software Support
1

Describe the issue or problem
when upgrading from 3.3.0.21 to 3.5.0.1, the upgrade failed with error.

Steps I took leading up to the issue
run the upgrade script and then failed.

What application are you using?
OJS 3.3.0.21 to OJS3.5.0.1

Additional information
This is the log up to the error.

2025-08-10 19:30:34 [migration: APP\migration\upgrade\v3_4_0\I7191_SubmissionChecklistMigration]
2025-08-10 19:30:35 [migration: PKP\migration\upgrade\v3_4_0\I7191_SubmissionProgressType]
2025-08-10 19:30:35 [revert migration: APP\migration\upgrade\v3_4_0\I7191_SubmissionChecklistMigration]
2025-08-10 19:30:35 [downgrade for "APP\migration\upgrade\v3_4_0\I7191_SubmissionChecklistMigration" unsupported: Downgrade not supported]
ERROR: Upgrade failed: DB: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'start''' at line 1 (Connection: mysql, SQL: alter table `submissions` change `submission_progress_temp` `submission_progress` varchar(50) collate 'latin1_swedish_ci' not null default ''start'')
2

Hi @mohd_arshad,

This looks related to String column defaults are not properly escaped · Issue #56124 · laravel/framework · GitHub to me, though I’m not sure why it’s coming up for you the way it is. Have you made any modifications to the code? What DBMS and version are you using?

Regards,
Alec Smecher
Public Knowledge Project Team

3

i have the same issue and I would be grateful to know how this was solved. I am carrying out a test migration from 3.3.0.7 - 3.5.0.1 on an xampp server on Windows 10. No modifications to the code base.
mysql Ver 15.1 Distrib 10.4.32-MariaDB, for Win64 (AMD64),

and exactly the same error message.

Thank you for any assistance you can render.

4

Unfortunately i could not solve this error.

But i did do successfull upgrade to 3.5.0.1 version by version.

From 3.3.0.8 to 3.3.0.21 to 3.4.0.9 and 3.5.0.1

If i upgrade from 3.3.0.21 straight to 3.5.0.1 i got this error.

5

I just started my upgrades to 3.5 and ran into the exact same error. I’m going from 3.3.0.22 to 3.5.0.3.

I did mohd_arshad’s suggestion and it worked. Upgraded to 3.4 first and then to 3.5 without any issues, but this is a bit cumbersome across many instances :frowning:

6

Okay I think I know what the issue is. @asmecher , it looks like 3.5 is using Laravel 11, but your PR wasn’t added until version 12.

1 Like