One of our objectives is to make upgrading from an earlier release as painless as possible, and we provide scripts that should bring your existing Eventum installation up-to-date.
Please note that if your database encoding is not UTF-8, you may encounter various bugs:
See 2.2 upgrade instructions how to convert database to UTF-8.
When upgrading to a new version of Eventum, please follow these instructions:
- Backup your copy of Eventum - files and data.
- Extract your new Eventum copy over your existing folder structure
- Run the upgrade scripts described in below
Upgrading to latest version
PLEASE NOTE: If you are upgrading from a version older than 3.2.0 please read the version specific notes at the bottom of this page.
- Rename your current Eventum dir to
- Extract Eventum release tarball and rename it to
- Copy all config files from old version to new version:
- If your workflow API, customer API or custom field files to were in
lib/eventumcopy them to
- Ensure your database database partition has enough disk space and run upgrade script:
upgrade/update-database.phpin older versions)
- Modify your workflow/customer classes not to require any Eventum core classes, they are autoloaded now. So you can just remove such lines:
- Update your cron jobs to point to the scripts in the new location (see INSTALL). Previously the scripts were in 'crons', now in 'bin', eg:
0 * * * * <PATH-TO-EVENTUM>/bin/download_emails.php username_here mail.domain.com INBOX
- Since 3.0.4 directory for writable data was moved:
|Old Value||New Value||Description|
||various lock and pid files|
||directory for logs|
- Since 3.2.0 MySQL extension was changed from mysql/mysqli to PDO_MySQL:
Upgrading from versions before 3.2
You need to upgrade to 3.2.0 first before you can upgrade to 3.2.x versions. #270
Upgrading from versions before 3.0
Upgrading directly to 3.1/3.2 from versions before 3.0 does not work, you have to upgrade to 3.0 series first.
Upgrading from versions before 2.2
Upgrading from these versions not supported, you have to go back and upgrade to 2.2 version first.
Since version 2.2 the database is assumed to be in UTF-8 encoding, it includes scripts to convert.
The charset convert scripts exists up to 2.4.0 version and are removed in 3.x series.
While it may work to use other encodings than UTF-8, then be aware that such configuration is not tested and you may encounter various problems.
convert-utf8.phpscript to update database to utf8 if the former encoding was proper
fix-charset.phpscript to update database to utf8 if the former encoding was improper.
you may also find this tool useful: https://packagist.org/packages/mremi/database-encoder
See scripts contents for inline comments and customization