Hi Hadi SOFU,
One likely reason why your version number was not updated to 2.3.4 is that the upgrade process timed out and didn't actually complete until the end.
The OCS 2.3.4 upgrade will try and 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 be timing out before it has a chance to complete this task.
The version number is updated at the end of the entire upgrade process, so if the index rebuild 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 find these in your php.ini (don't forget to restart the webserver after making changes).
Alternatively, you can remove the index rebuild 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="22.214.171.124" maxversion="126.96.36.199">
<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" />
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
Re: OCS being slow, can you please be more specific? Which pages are being slow? Is the whole site affected?