How to upgrade OJS 3.3 to 3.5 via cpanel?

Software Support
1

I got this problem. I have backup complete files in public html and ojs.sql.

I install the new ojs 3.5, it keep 500 errors page.

After that right now, I install totally new version of OJS 3.5 (do not upgrade). Is it anyway I can link back all the old files and user database via cpanel? As I unable to access the terminal.

Thanks .

2

Hi @cheekien,

Someone else may have to comment on teh specific issues with Cpanel. But, I will point out that we do have an upgrade guide: https://docs.pkp.sfu.ca/dev/upgrade-guide/en/

For the 500 errors, it is helpful to check your your PHP error logs and report back on error messages here on the thread.

-Roger
PKP Team

1 Like
4

I am not sure of this thread is closed or not (over 10 days now) but I am preparing to do an upgrade by way of migrating the database, configuration files, and selected file directories from the active (3.3) installation to a clean install of 3.5 LTS in a designated subdomain. This approach will allow the 6 journals using our current OJS (3.3.013) to continue their work while getting to tour the new platform (with the database and files copied from the old install) and then we cut over to 3.5 as well as the nameservers, email authentication settings (DMARC, SMTP, etc.), and delete the old site. I will be able to train the editors and others afterwards unless there is interest to do that beforehand. Has anyone tried this? cPanel features Softaculous, but I am not sure it works with OJS, so any helpful instructions that PKP could share would be helpful. I will also engage our host in the process.

5

Hi @asabhar,

Thanks for sharing your approach. We’ve heard from multiple people that Softaculous upgrades for OJS can be problematic. We have a comprehensive guide for how to go about upgrading:
https://docs.pkp.sfu.ca/dev/upgrade-guide/en/

Some people may have success using CPanel and/or Softaculous, but it’s not guaranteed. The most effective advice that our own sys admin and developers have found is captured in the upgrade guide. It may require more time and/or sys admin knowledge/expertise, but it tends to be a more sustainable approach.

-Roger
PKP Team

6

Thanks, Roger! I have watched Alec Smecher’s video demonstrating the process using a Linux Terminal, but I neither have that skill nor the level of access to the server where I could use the teminal even if I had that level of skill. We are using a hosting company with a very helpful support team but any code-level intervention is beyond the scope of their terms of service. They have once tried to upgrade to 3.4 but it failed due to a different emailing configuration (I must guess, moving from PHPMailer to the next), and I could not hold our publishers too long, so I decided to delay the upgrade until the 3.5 LTS arrives. I speculate that if I have a robust version, it will help with future upgrades using the streamlined process that Alec mentioned in his his video: https://www.youtube.com/watch?v=twTfYLVSPrI. All my best! – Arjun