Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OJS] Issue with migrating to 3.0 #1913

Closed
PedroSilvaNZ opened this issue Oct 24, 2016 · 7 comments
Closed

[OJS] Issue with migrating to 3.0 #1913

PedroSilvaNZ opened this issue Oct 24, 2016 · 7 comments

Comments

@PedroSilvaNZ
Copy link

Hello,
I'm trying to migrate to 3.0, and I got the following error:
A database error has occurred: Duplicate entry 'defaultthemeplugin-0-enabled' for key 'plugin_settings_pkey'
What could I do about this?
Thanks,
Pedro.-

@asmecher
Copy link
Member

@PedroSilvaNZ, is it possible that you're trying to run an upgrade on a copy of your database that has already experienced a failed upgrade?

@PedroSilvaNZ
Copy link
Author

Hi @asmecher,
That is possible yes. I have experiences several errors while updating the database, and I've been working through those. However, I'm unsure what is this error about.
Thanks,
Pedro.-

@asmecher
Copy link
Member

@PedroSilvaNZ, one of the last steps the upgrade process tries to accomplish is enabling the default theme. It looks like it's trying to do that on an installation that has already had this step performed, hence I suspect the upgrade has already (at least partially) been run. Make sure you're running the upgrade on a copy of 2.x that has never been partially upgraded, restoring from backup if necessary, and I think this will go away.

@PedroSilvaNZ
Copy link
Author

Hi,
Thanks for the prompt reply. What if that is not an option? How do a fix it?
Thanks,
Pedro.-

@asmecher
Copy link
Member

Do you mean that you don't have a backup previous to attempting an upgrade? If so, you can at least bypass the immediate problem by removing or commenting out the lines that enable the default theme plugin in dbscripts/xml/upgrade/3.0.0_update.xml -- but your database will be in an indeterminate state somewhere between the two releases and without any information on how it got there it'll be impossible to know whether you'll run into other problems further down the line.

@Shubash
Copy link

Shubash commented Dec 9, 2016

Hi
I have same problem with our journal. I didnot create the backup before upgrade to 2.4.8.1 to 3.0.1. So what can i do now. We have face many error with our journal. I try to bypass but it is not working. is there any other solution you have? I am not good at coding or commanding. I need a quick response.
Thanks
Shubash

@asmecher
Copy link
Member

asmecher commented Dec 9, 2016

@Shubash, could you post your question in http://forum.pkp.sfu.ca/ along with as much detail as you can include?

@NateWr NateWr closed this as completed Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants