Expenses will be assigned to free configurable categories and each category has:
Each expense has the following fields:
This bundle supports data import from Kimai v1, but you need to imported the other data (like customers) first.
An example for the import command:
bin/console kimai:bundle:expenses:import-v1 "mysql://username:email@example.com:3306/database?charset=utf8" "kimai_"
You can buy this item from the developer with a regular EU-invoice or via Gumroad (platform for selling digital goods). Please create a Gumroad account during your purchase to receive software updates. Read more about the license and purchase options.
There is a Github repository, where you get support and can post bug reports, feature requests or start a discussion.
Le tableau suivant contient une comparaison entre le greffon et la version minimale requise de Kimai.
|Version groupée||Minimum Kimai version|
|1.21 - 1.24||1.15|
|1.19 - 1.19.1||1.14|
|1.16 - 1.18.1||1.12|
|1.11 - 1.13||1.9|
|1.7 - 1.10||1.7|
|1.5 - 1.6||1.6.2|
|1.1 - 1.2||1.4|
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/ExpensesBundle/) or you forgot to clear the cache (look above).
Updating the plugin works exactly like the installation: