Dear OJS Support - All IT Engineer (Cc; Alex_Smecher)
I have successfully upgraded my legacy OJS installation to OJS 3.3.0.22 in a Docker staging environment without any issues.
My upgrade history is as follows:
| Version | Installed |
|---|---|
| 2.4.8.0 | 2016-02-19 |
| 2.4.8.5 | 2023-05-09 |
| 3.0.2.0 | 2023-05-11 |
| 3.1.2.4 | 2023-05-11 |
| 3.2.1.4 | 2023-05-11 |
| 3.3.0.13 | 2023-05-11 |
| 3.3.0.22 | 2026-07-28 |
Database Audit
I performed a database audit before planning the next upgrade.
The database default settings are:
Database : ojs33_staging
Character Set : utf8mb4
Collation : utf8mb4_unicode_ci
However, after auditing the tables, I found that almost all tables still use the legacy collation:
latin1_swedish_ci : 150 tables
NULL (View) : 1 object (v_ref_jurnal table)
So the current situation is:
- Database default character set = utf8mb4
- Database default collation = utf8mb4_unicode_ci
- Existing tables = latin1_swedish_ci
*This appears to be inherited from the original OJS 2.4.x installation.
*
My Question
Before proceeding to OJS 3.4.x and later 3.5.x, I would like to ask:
- Is it safe to upgrade directly while the existing tables are still using latin1_swedish_ci?
- Would PKP recommend converting all existing tables to utf8mb4_unicode_ci before upgrading to OJS 3.4/3.5?
- Or is it better to complete the application upgrade first (3.3 → 3.4 → 3.5) and perform the character set/collation conversion afterward?
I would appreciate your recommendation on the safest migration strategy for a long-lived OJS installation that originated from OJS 2.4.x.
Thank you very much for your guidance.