Allows configuration of additional (custom) fields for:
Expenses (see plugin).
You can create as many fields as you want for each data type, where each field:
The custom-field data is then available in:
You can change the “weight” of custom-fields, so they show up in the order you define.
Custom fields can be of the following type:
More about those in the documentation.
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.
The following table contains a comparison between plugin and required minimum Kimai version.
|Bundle version||Minimum Kimai version|
|1.21 - 1.24||1.17|
|1.18 - 1.20||1.15|
|1.15 - 1.16||1.11|
|1.10 - 1.13||1.9|
|1.8 - 1.9||1.7|
|1.6 - 1.7||1.6.2|
|1.3.2 - 1.4.1||1.4|
|1.1.1 - 1.2||1.1|
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/MetaFieldsBundle/) or you forgot to clear the cache (look above).
Updating the plugin works exactly like the installation: