You are viewing the PKP Support Forum | PKP Home Wiki

Upgrading to OCS 2.3.4? Please read

Are you responsible for making OCS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, michael, John

Forum rules
What to do if you have a technical problem with OCS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved. Please note that this FAQ is OJS-centric, but most issues are applicable to both platforms.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OCS Conference Support and Discussion subforum; if you have a development question, try the OCS Development subforum.

Upgrading to OCS 2.3.4? Please read

Postby michael » Tue Oct 18, 2011 10:51 am

If you are upgrading an older version of OCS to the 2.3.4 release, please ensure that the version number is being correctly reported as 2.3.4 following the upgrade:

* As Site Administrator, you can check the version number by going to Site Administration => System Information
* Following a successful upgrade, the current version should be displayed as

If the current version is being displayed as the old, pre-upgrade version, it is likely that the upgrade process did not fully complete until the end and timed out before it had a chance to upgrade the version number.

The OCS 2.3.4 upgrade will try to re-index all of your conference content as part of a bug fix included in the release. If you have a lot of content, this may take some time to finish and PHP may time out before it has a chance to complete this task.

The version number is updated at the end of the upgrade process, so if the re-index times out, your version number will not be updated correctly.

You can modify your server settings and ensure that PHP's execution and memory limits are sufficiently high:

Code: Select all
    max_execution_time = 450     ; Maximum execution time of each script, in seconds (30)
    max_input_time = 90 ; Maximum amount of time each script may spend parsing request data (60)
    memory_limit = 256M      ; Maximum amount of memory a script may consume (128MB)

You can temporarily set max_execution_time = 0 (unlimited), complete the upgrade, and then reset the value back to your previous limit.

You will find these settings in your php.ini (don't forget to restart the webserver after making changes).

Alternatively, you can remove the re-index step from the upgrade process, complete the upgrade without it, and then try to manually rebuild the index after the upgrade is complete:

1) After unzipping the OCS 2.3.4 source or patching your old install with the OCS 2.3.4 upgrade patch, go to the bottom of dbscripts/xml/upgrade.xml.

You will find the following:
Code: Select all
   <upgrade minversion="" maxversion="">
      <data file="dbscripts/xml/upgrade/2.3.4_update.xml" />
      <code function="rebuildSearchIndex" />
      <note file="docs/release-notes/README-2.3.4" />

2) Remove the line: <code function="rebuildSearchIndex" /> (and save the file).

3) Run the upgrade.

4) Once the upgrade is complete and you can verify the correct version number, manually rebuild the search index from the command line: php tools/rebuildSearchIndex.php

5) Add the line removed in step 2) back to upgrade.xml (and save the file).
Posts: 408
Joined: Thu Mar 29, 2007 2:09 pm

Return to OCS Technical Support

Who is online

Users browsing this forum: No registered users and 1 guest