Kimai maintainer since 2007
You can test the Plugin in the Plugin demo.
This bundle allows you to modify most translated contents in Kimai to your business needs.
Often companies want to change some wordings in Kimai to better match it to their industry or usage of Kimai. One of the most requested modifications in Kimai is to change “Customers” to something else (eg. “Client”, “Construction site”, “Family”). Now this is as simple as searching for the text to replace and then setting your preferred translation.
You can replace messages, form labels, menu items and many more into one or multiple language. It comes with a new “Translation” view to manage these changed translations.
Visible elements like form labels, headings, menu items, error messages, and many more can be changed.
The text from the following “domains” cannot be changed:
A tabela a seguir contém uma comparação entre o plug-in e a versão mínima exigida pelo Kimai.
|Versão do pacote||Versão mínima do Kimai|
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/TranslationBundle/) or you forgot to clear the cache (look above).