Skip to content
Heiko August edited this page Jan 5, 2018 · 8 revisions

Notes beforehand the update

Please read the release message to take notice of eventual changes of the minimal system requirements.

An important note for updates from a version up to 2.3.4 to versions higher than 2.3.5

With the version 2.3.5 the PHP lib mysqli was introduced. That and further changes made the version safe for the use with PHP7. But it has also a side effect for updates from versions below 2.3.5 to versions newer than 2.3.5. An update from –let's say– 2.3.3 to 2.3.7 will fail because of the different libs for accessing MySQL. One needs a mandatory interim update to the version 2.3.5. That leads us to …

A second important note for ommiting versions

Because of a bug the list of updateable files does not contain all files, when one ommits versions in an update i.e. from 2.3.2 to 2.3.5. The update script points only to the files of the target version. In the example these are the files for version 2.3.5, but not the files of the ommited version 2.3.4. This will cause an broken installation. One solution is, to bypass this with the upload of all files of the new version after step 1 of the update. A second solution is the step by step update of every version until one reaches the target version.

This bug was solved in the version 2.3.7. Please take the important note for updates to versions higher than 2.3.5 note into account! You can find it above↑ the current note.


Check your forum for the currently installed version. Got to admin area=>update and look for the "actual version" (actual installed version). Compare your version with the actual available release. If a newer version is available, download and unzip it on your computer.

The update process in itself

  1. Please notice the changes of filenames and behaviour!
    • up to version 2.3.7: Load the files update/update_2.x_2.3.php and update/update.sql up to the server.
    • above version 2.3.7: Load the files update/update_2.3.5_2.4.php, config/VERSION and update/update.sql up to the server.
  2. Open the page admin area=>settings and disable the forum.
  3. Open the page admin area=>update. Now you should see the link to the update-file. Attention: it might be possible, that the list contains the old and the new update file (see point 1 of this list).
  4. Follow the link. The script applies in a first step the database changes.
  5. When no errors occurs, you'll see now a list of all directories and files, that have to be updated or replaced.
    1. Update the directories and files.
    2. Special case plugins: If the developers of a plugin changes the file structure of their software, it could be the case, that files got renamed or removed from the project. To prevent your plugin directories to get crowded with obsolete files over several updates, you should –when updating– delete the old directory of the plugin on the server and upload the new plugin directory from the new version to the server.
  6. Delete the content of the directory templates_c from the server. The directory contains the cached precompiled templates from the last requests with the (now) old version. These precompiled files are outdated and will be replaced one by one with the next requests for the different forum pages.
  7. Enable the forum again in the settings (admin area=>settings).


Delete the files update/update_2.x_2.3.php respectively update/update_2.3.5_2.4.php and update/update.sql from the server.

You can’t perform that action at this time.