Trouble and doubt in upgrading form 2.2.3 to 2.4.8.1

vagner · January 28, 2017, 10:12pm

Guys,
when click on Install System I receive the message: “Duplicate entry ‘2–filterEditor-0-0’ for key ‘user_settings_pkey’”. What should I do?

At that form of installation, shoud I mark create new database or not?

Thanks in advance!

Vilela

ctgraham · January 30, 2017, 3:52pm

With the upgrade, there is a link at the top of the installation form dedicated to the “Upgrade”, but it is small and easy to miss. You won’t fill out the installation form a second time.

github.com

pkp/ojs/blob/ojs-stable-2_4_8/docs/UPGRADE#L213-L223


2. Web

If you do not have the PHP CLI installed, you can also upgrade by running a
web-based script. To do so:

    - Edit config.inc.php and change "installed = On" to "installed = Off"
    - Open a web browser to your OJS site; you should be redirected to the
      installation and upgrade page
    - Select the "Upgrade" link and follow the on-screen instructions
    - Re-edit config.inc.php and change "installed = Off" back to
       "installed = On"

If you have access to the command line, the upgrade process there is preferred:

github.com

pkp/ojs/blob/ojs-stable-2_4_8/docs/UPGRADE#L202-L211


1. Command-line

If you have the CLI version of PHP installed (e.g., /usr/bin/php), you can
upgrade the database as follows:

    - Edit config.inc.php and change "installed = On" to "installed = Off"
    - Run the following command from the OJS directory (not including the $):
      $ php tools/upgrade.php upgrade
    - Re-edit config.inc.php and change "installed = Off" back to
       "installed = On"

If you’ve already tried reinstalling over top of your existing installation (such as indicated by the “Duplicate entry” message), be sure to start of the upgrade from a cleanly restored database from your last good backup (hopefully just before you began the upgrade of the code).

vagner · January 30, 2017, 5:56pm

I just receive the message about duplicate entry, after I fill the form at the step “-Select the “Upgrade” link and follow the on-screen instructions”.

Thanks!!

ctgraham · January 30, 2017, 7:39pm

Did the upgrade continue after that point and progress to a “Upgrade completed” message?

vagner · January 30, 2017, 7:54pm

No. It returns to the form and shows the message in a red characters!

Thanks in advance, ctgraham!

ctgraham · January 30, 2017, 8:02pm

Were you able to revert to a clean copy of the 2.2.3 database before trying the upgrade again?

vagner · January 31, 2017, 11:19am

Yes. I can do this. At this time the running version is 2.2.3, cause I can’t leave de journal off-line. Should I try the upgrade again? With some diferent step in any point?

Thanks!

ctgraham · January 31, 2017, 8:12pm

The way I would approach this would be to copy the backup of the OJS database and files to a new server (or new location on the current server), then try the upgrade there. (This allows your 2.2.3 install to continue running while you test out the upgrade.) Ideally, run the database upgrade part of the instructions from the command line, but either way, copy the output of the upgrade script and paste it here if you encounter an error message.

vagner · February 13, 2017, 7:38pm

Hi ctgraham!
I’ve done this and the problem persists!
I think I cannot upgrade directly to 2.4.8 cause the database changed and this changes were done in some version between 2.3.2 and 2.4.8.
I’ll try an upgrade to 2.3.0 and then jump to 2.4.8.
Let’s go!

ctgraham · February 13, 2017, 7:41pm

If you are able to upgrade from the command line, be sure to review the output for any error messages and for the successful completion message at the end.

You can copy the output to this forum by pasting the content between two sets of three backticks:

paste log here

vagner · February 13, 2017, 7:47pm

Oh god! I forget do run the patch from 2.3.2 to 2.4.8.1. May be this patch has the function to upgrade the database. And after the patch I run 2.4.8.1 upgrade!

ctgraham · February 13, 2017, 8:18pm

Patch based upgrading is cumulative and error prone. If you miss one patch between versions, you are likely looking at a broken installation. I strongly recommend using the “Full Package” upgrade instead.

vagner · February 14, 2017, 10:54am

Oh, yes! I found this full package at https://pkp.sfu.ca/ojs/ojs_download/. I’ll try this one!

vagner · February 20, 2017, 5:24pm

Do you have some tips on running patches? I’m new at this procedures. Should I access my servers by Putty and then run de scripts?
Thanks again!

vagner · February 21, 2017, 11:53am

Does PHP Shell works at running patches?

Thanks!

ctgraham · February 21, 2017, 3:52pm

I’m not a fan of patches, unless you are using a change management (revision control) system like Git or Subversion or Mercurial. We’re moving toward a much more rapid release cycle which will hopefully make patches obsolete for most users.

Is the a patch you are interested in particularly, or are you just following the instructions from docs/README?

vagner · February 21, 2017, 4:38pm

I’m just following the instructions from docs/readme.
But there are an alternative way to make the upgrade?

Thanks ctgraham!

ctgraham · February 28, 2017, 1:19pm

The preferred way to upgrade is via the “Full Package” upgrade. It is the first option described in the README.

The “recommended patches” section should probably just be removed from the README.

vagner · March 20, 2017, 12:03pm

Something strange happened!
I made a full update to the version just above 2.2.3 which is 2.2.4 and I received the same error message from when I tried for 2.4.8.1
I’m in trouble because I’ve already been paid to perform the upgrade!
Do you have sem aditional advice???

vagner · March 20, 2017, 12:10pm

I found something at https://pkp.sfu.ca/bugzilla/show_bug.cgi?id=4713