Need urgent Help please. Had our journal up and running quite well and have had successful upgrades up till now. However, after copying the relevant files prior to clicking on upgrade I see screenshot 1. when attempting to proceed to upgrade from 2.4.8 to 3.0.2 had the errors in screenshot 2 with the comment “A database error has occurred: Duplicate entry ‘tinymceplugin-0-enabled’ for key 'plugin_settings_pkey”. I tried checking the database and cant seem to note any error. Unfortunately didn’t do a database previous backup and had never needed to do that in earlier versions.
Hi @revsanda,
Do you have the error message from the first time the upgrade failed?
We always recommend making a backup – even for minor upgrades, but especially for major upgrades like 2.4.8 to 3.0.2. Your database is currently in a state somewhere between the two versions, and I’m afraid this is going to be difficult to work with.
Regards,
Alec Smecher
Public Knowledge Project Team
Actually the upgrade was successful the first time but I guess my colleague turned the installed option back to off and so it reverted to the installation page. I have posted the screenshot with the errors above. I am so wrong for not doing the backup however, is there no way round it? The error it gave was “A database error has occurred: Duplicate entry ‘tinymceplugin-0-enabled’ for key 'plugin_settings_pkey” Any recommendation will be greatly appreciated please. The journal is due to publish the next issue in a week. I really need help!
Hi @revsanda,
If the upgrade was successful, you should be able to turn Installed
back to On
, I think. What happens when you do that?
Regards,
Alec Smecher
Public Knowledge Project Team
Thanks. When I change Installed back to On The webpage shows poorly formatted page with the Error DB Error: Unknown column 'a.include_in_browse' in 'where clause'
. However when I log in, everything just looks perfect. What can I do to restore the landing page. Check it kindly at www.ijavs.org
Hi @revsanda,
It sounds to me like the include_in_browse
column didn’t get added to your authors
table, as it should be during the upgrade process. This suggests to me, again, that the upgrade didn’t complete successfully.
Regards,
Alec Smecher
Public Knowledge Project Team
Thanks Alec, Ok agreed that the upgrade didn’t complete, Is there any way out of this? If I re-install from scratch is there a way of restoring all published articles and designs? I have a feeling that there was an effort when my colleague turned it off and saw the errors he tried a downgrade back to 2,4,8. However right now i still have 3,0.2 installed and the error affects even the default public page. What can I really do.
I have backed up my database now but i guess it may be too late for that. Can the backup be of help?
Hi @revsanda,
I’m afraid that without knowing exactly what happened to your database, I can only guess at what state it’s in. If it’s closer to OJS 2.x, you may be able to try it with the OJS 2.x codebase to see if it’ll allow you to access your content.
Regards,
Alec Smecher
Public Knowledge Project Team
I have been doing some research and patiently studying the problem. I came up with an idea but I really dont know how to pull it off. What if i do a clean install of OJS using a new subdomain so the old published articles retain their pages and DOI resolutions and then all new articles etc will now be on the new installation. Question: If this idea is good, how do I copy all the users to this new site and database. I am really in a big fix and need help. Sorry I really dont have a good understanding of database issues, just need the site back up and running. On the other hand, is there a way of downgrading to 2.4.8.1 if this will resolve the issues i am having. Thanks for your time.
Hi @revsanda,
That seems like it might be an option. You might also be able to get your old content out using the “Native XML” import/export plugin – if your old installation still works sufficiently to allow access to that content. Note that the XML format used by this plugin differs between OJS 2.x and 3.x, so if you export from OJS 2.x you’ll have to import into 2.x; if you export from OJS 3.x you’ll have to import into 3.x. I’m not sure which version will give you the highest likelihood of success – it’ll depend on how far through the upgrade your system went before it failed.
Regards,
Alec Smecher
Public Knowledge Project Team