The Public Knowledge Project (PKP) has officially released Open Journal Systems 3.5 as its LTS (Long-Term Support) version. This is the moment we’ve been preparing for. As we shared earlier, our team has been tracking every 3.5 milestone and testing theme and plugin compatibility in our own staging environments. Now we can say it clearly: it is safe to upgrade to OJS 3.5.
In this post we walk through what 3.5 brings for editors and journal managers, a few things worth knowing before you upgrade, and how we handle migrations smoothly — whether you’re coming from OJS 2, an older OJS 3.x build, or OJS 3.3.
Why it’s safe to move now
Because 3.5 now carries the LTS label, it will receive long-term bug fixes and security patches. Upgrading today puts your journal on a stable, well-supported branch for years to come — ideal for journals that prioritise reliability.
One quick note on the upgrade path: per PKP’s support policy, if you’re on a version older than 3.3, you upgrade to 3.3 first, then to 3.5. Most of our clients already run 3.3, so they can move straight to 3.5. And if you’re still on a legacy OJS 2 installation, there’s nothing to worry about — we handle the full journey, from OJS 2 to OJS 3 and all the way to 3.5.
What OJS 3.5 brings to editors and managers
A redesigned editorial dashboard. Tracking submissions is far clearer now. New filtered views help you find manuscripts at any workflow stage, while refreshed status icons and action buttons reduce the number of clicks for everyday tasks. The interface looks noticeably different from 3.3, so a short adjustment period for your team is normal.
An automatic editorial board (masthead). You no longer fill in your editorial board as free text. You assign people to the relevant role and the system compiles the masthead automatically — with optional start and end dates per member. Your board list stays accurate and consistent with almost no manual upkeep.
Invitation-based user management. To grant someone a role such as editor, editorial board member, or manager, you no longer create their account directly. You send an invitation, and the person joins by accepting it. It’s a more privacy-friendly approach that also improves data accuracy.
ORCID and ROR built in. ORCID, which previously required installing a separate plugin, now ships in the core. ROR (Research Organization Registry), which links author affiliations to standardised, global identifiers, is integrated by default too.
A “Highlights” feature on your homepage. Showcase calls for papers, eye-catching visuals, or standout articles right on your homepage, with an optional rotating carousel. (Availability may vary by theme.)
Author-suggested reviewers. Authors can propose a reviewer’s name, affiliation, or email during submission, and that suggestion is passed to the editor.
Beyond these, 3.5 adds multiple author affiliations, basic JATS XML support, the ability to set a minimum number of reviewers per submission, and improved multilingual handling.
What to know before you upgrade
Let’s be candid: 3.5 isn’t a cosmetic refresh — it’s a structural release. That’s exactly why it’s worth planning the move properly.
- Some workflow habits change. The automatic editorial board and the shift to invitation-based user management will change a few steps your team is used to. A brief walkthrough after the upgrade is usually all it takes.
- Email configuration matters. Invitations and notifications are delivered by email, so your server’s email setup needs to be working reliably. We always verify this as part of the upgrade.
- Custom themes and some plugins may need updating. The infrastructure changes in 3.5 can require adapting custom themes and certain plugins, and your server environment needs to be current (a modern PHP version). We test all of this beforehand and make the necessary adjustments.
- Staging first, then live. We always run the upgrade on a copy (staging) environment first, confirm everything works, and only then move it to production. Full backups and data integrity are our standard, non-negotiable.
Whatever version you’re on, we manage the upgrade
- Full OJS 2 to OJS 3 migration
- Upgrades from OJS 3.1 / 3.2 / 3.3 to OJS 3.5
- Theme and plugin compatibility, data integrity, and zero-loss transitions
- Complete pre-upgrade backups and staging verification
Ready to upgrade? Get in touch
If you’d like to move to OJS 3.5, want advice on the best path for your current version, or have any other questions, reach out to us. Let’s plan the smoothest possible transition together — preserving your data, your theme, and your workflow.
Comments are closed