Find out who changed what and when: record and visualize the changes on
system configurations and
A global audit-trail page, listing all recorded changes with username, change datetime, item type and link to detail page.
Actions for each of the following items:
Introduces a new screen for each of the above items, with all recorded changes and each log entry containing the following information:
The change history will be recorded for the following fields:
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.
下表包含插件与所需的最低 Kimai 版本之间的比较。
|Bundle 版本||最低 Kimai 版本|
|1.14 - 1.15||1.16.10|
|1.12 - 1.13||1.15|
|1.11 - 1.11.1||1.14|
|1.6 - 1.8||1.7|
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/AuditTrailBundle/) or you forgot to clear the cache (look above).
Updating the plugin works exactly like the installation: