Website Design & Development
We create stunning, user-friendly websites that drive growth.
Open Journal Systems (OJS) evolves continuously, with the Public Knowledge Project (PKP) releasing regular updates that improve functionality, security, and user experience. Understanding OJS versioning helps journal managers make informed decisions about when and how to update their installations. This guide explains the current OJS version landscape and what it means for your journal.
Current OJS Version: 3.5.0-3 #
As of December 2025, the latest OJS release is version 3.5.0-3, released on December 19, 2025. This version represents the newest iteration of OJS, incorporating bug fixes, security patches, and refinements based on community feedback since the major 3.5.0 release in June 2025.
OJS 3.5 introduced substantial changes to the platform, representing one of the most significant updates in recent years. The version includes redesigned editorial workflows, improved user management, enhanced multilingual support, and better GDPR compliance features.
Important Note: OJS 3.5.0 is not yet designated as a Long-Term Support (LTS) release. PKP has indicated LTS designation will likely happen in early 2026. Journals requiring LTS stability should consider this when planning upgrades.
Understanding OJS Version Types #
Standard Releases #
Standard releases (like 3.5.0-3) include the latest features and improvements. These versions receive ongoing updates but may see more frequent changes as PKP refines new functionality based on community feedback.
Long-Term Support (LTS) Releases #
LTS versions receive extended support with critical security fixes and bug patches over a longer period—typically until a specified end-of-life date. Journals prioritizing stability over newest features often prefer LTS releases.
The current LTS version is OJS 3.4.0-10, released November 21, 2025, with support committed until at least January 1, 2027. Many production journals run LTS versions to minimize disruption while maintaining security.
Maintenance Releases #
The third number in version strings (e.g., the "-3" in 3.5.0-3) indicates maintenance releases containing bug fixes and minor improvements without major feature changes. These updates are generally safe to apply and address issues discovered after main releases.
Key Features in OJS 3.5 #
OJS 3.5 brings significant improvements that PKP developed based on extensive community input:
Redesigned Editorial Dashboard #
The editorial interface received substantial redesign, offering cleaner navigation and more efficient workflow management. Editors can customise their views, apply new filters, and track submission status more clearly. Status icons and action buttons are more precise, reducing clicks required for common tasks.
New User Invitation System #
OJS 3.5 introduces an invitation-based workflow for adding users. Rather than creating accounts directly, administrators now send invitations allowing users to complete their own registration. This approach improves data accuracy and aligns with privacy best practices.
Note that this represents a significant workflow change from previous versions where administrators could create user accounts directly.
GDPR-Aligned Features #
Enhanced privacy controls and consent management help journals comply with data protection regulations. These features are particularly relevant for journals with European authors, reviewers, or readers.
Built-in ORCID Integration #
ORCID functionality is now integrated into OJS core rather than requiring a separate plugin. This simplifies setup and improves author identification capabilities.
ROR Integration #
Research Organization Registry (ROR) integration is now included by default, enabling standardised institutional affiliation identification without additional plugin installation.
Editorial Masthead Feature #
A new masthead feature allows automatic display of editorial team information based on assigned roles within OJS, reducing manual maintenance of editorial board pages.
Planning an OJS Upgrade?
Upgrading to OJS 3.5 involves significant changes requiring careful planning, data migration, and testing. Professional upgrade services ensure smooth transitions.
Technical Requirements for OJS 3.5 #
OJS 3.5 has updated server requirements that journals must meet before upgrading:
PHP Version: OJS 3.5 requires PHP 8.2 or higher. This is a significant change from previous versions and may require server environment updates before OJS upgrade is possible.
Database: MySQL 5.7.22+ / MariaDB 4.1+ or PostgreSQL 9.5+
Journals running on older PHP versions will need to coordinate PHP upgrades with their hosting providers before upgrading to OJS 3.5. This additional step adds complexity to the upgrade process.
Choosing Between OJS 3.5 and 3.4 LTS #
The decision between running the latest version (3.5.x) or the LTS version (3.4.x) depends on your journal's priorities:
Consider OJS 3.5 if:
- You want access to the latest features and improvements
- Your technical team can handle more frequent updates
- You're comfortable with an interface that may still see refinements
- You can meet PHP 8.2 requirements
- You're willing to help PKP improve the platform through feedback
Consider OJS 3.4 LTS if:
- Stability is your primary concern
- You prefer less frequent major changes
- Your server environment has PHP version constraints
- You want extended support guarantees
- Your editorial team prefers consistent interfaces
Why Updates Matter #
Regardless of which version branch you choose, keeping your OJS installation updated within that branch is essential:
Security Protection #
Each release addresses security vulnerabilities discovered in previous versions. Running outdated software exposes your journal to known security risks that attackers can exploit.
Bug Fixes #
Updates resolve issues affecting functionality, performance, and user experience. Problems you may be experiencing might already be fixed in newer releases.
Plugin Compatibility #
Plugin developers build for current OJS versions. Outdated installations may lose access to important plugins or find existing plugins stop working properly.
Community Support #
PKP community forums and support resources focus on current versions. Finding help for outdated installations becomes increasingly difficult.
Retired OJS Versions #
PKP officially designates older version branches as retired, meaning they no longer receive any updates—including security patches:
OJS 2.x: Fully retired. No security updates available. Journals still running OJS 2.x face significant security risks and should prioritise migration to OJS 3.x.
OJS 3.0, 3.1, 3.2: These older 3.x versions are also retired and no longer receive updates. While more recent than OJS 2.x, they should be upgraded to current supported versions.
Where to Download OJS #
OJS is free, open-source software developed and distributed by the Public Knowledge Project (PKP). The only official source for OJS downloads is PKP's website.
Official Download Page: https://pkp.sfu.ca/software/ojs/download/
PKP's download page provides:
- Latest stable release packages
- Current LTS release packages
- Links to release notes detailing changes
- Installation and upgrade documentation
- Mailing list signup for security announcements
Always download OJS directly from PKP's official website. Third-party sources may offer modified versions that could contain security vulnerabilities or unwanted modifications.
Staying Informed About OJS Releases #
PKP provides several channels for staying current with OJS developments:
PKP Community Forum: Release announcements appear in the PKP Announcements category. The forum also provides discussion space for upgrade questions and experiences.
PKP Mailing List: Subscribe through PKP's website to receive email notifications about security vulnerabilities and critical bug fixes.
PKP Documentation Hub: Updated documentation accompanies each major release, including version-specific guides for different user roles.
GitHub: Release notes and detailed changelogs are available in PKP's GitHub repositories for those wanting technical details.
Upgrade Considerations #
Upgrading OJS—particularly across major versions—involves more than simply installing new files:
Database Migration: OJS upgrades modify database structures. This process must complete successfully to preserve your data.
Theme Compatibility: Custom themes may require updates to work with new OJS versions. The 3.5 interface changes may necessitate theme modifications.
Plugin Assessment: Existing plugins need compatibility verification. Some plugins may require updates or alternatives for new OJS versions.
Testing: Upgrades should be tested in non-production environments before applying to live journals. This identifies issues before they affect operations.
Backup: Complete backups of files and database are essential before any upgrade attempt. Failed upgrades without backups can result in data loss.
Downtime Planning: Upgrades require taking the journal offline temporarily. Planning for appropriate maintenance windows minimises disruption.
Important Disclaimer #
Version information in this article reflects OJS releases as of December 2025. PKP releases new versions regularly, and the information here may become outdated. Always verify current version information directly from the official PKP website at pkp.sfu.ca/software/ojs/download before making upgrade decisions.
OJS is developed and maintained by the Public Knowledge Project (PKP). Altechmind Technologies is not affiliated with PKP. We provide this information for educational purposes based on publicly available PKP documentation and announcements.
