Usually there’s no need to do this, but if you encounter any configuration problems you can reset the plugin configuration by executing a single SQL command. Make sure that you know what are you’re doing and before executing the command create a backup of your data.
Show current configuration:
SELECT * FROM kimai2_configuration WHERE name LIKE 'controlling.%';
DELETE FROM kimai2_configuration WHERE name LIKE 'controlling.%';
For a list of all requirements to make this software functional, please e-mail us to info (at) mrsoft (dot) gmbh
The following table contains a comparison between plugin and required minimum Kimai version.
|Bundle version||Minimum Kimai version|
Extract the ZIP file and upload the included directory and all files to your Kimai installation to the new directory:
The file structure needs to look like this afterwards:
After uploading the files, Kimai needs to know about the new plugin. It will be found once the cache was re-built. Call these commands from the Kimai directory:
It is not advised, but in case the above command fails you could try:
You might have to set file permissions afterwards:
You have to allow PHP (your webserver process) to write to
var/ and it subdirectories.
Here is an example for Debian/Ubuntu (to be executed inside the Kimai directory):
Test Kimai before executing these commands (they are likely not required in a shared-hosting environment).
You probably need to prefix them with
the group might be called different than
Run the following command:
This will create the required database tables and update them to the latest version.
There are no commands defined in the "kimai:bundle:XYZ" namespace., then either the directory has a wrong name (must be var/plugins/ControllingBundle/) or you forgot to clear the cache (look above).
Updating the plugin works exactly like the installation: