Custom content

Create custom content for stylesheets, Javascript, a global warning-message and a new page to render markdown content for company news.

Offered by

Kevin Papst

9 € excl. VAT (per year) ^*

Please provide a valid email address to access your plugin and manage your licenses.

Buy now

Available payment methods

* Can't pay? Reach out for a PPP discount.

A Kimai plugin which allows adding custom content for:

Stylesheet (embedded in all pages)
Javascript (embedded in all pages, except security screens)
A global warning message, shown to every logged-in user
An entire new page to display (markdown formatted) information for your users

Alternative

If you only want to add some custom CSS stylesheets, you can have a look at this free item instead: Custom CSS

Storage

This bundle stores contents in the directory var/data/custom-content-bundle/.

Make sure the data directory is writable by your webserver and included in your backups.

Installation

Copy files

Extract the ZIP file and upload the included directory and all files to your Kimai installation to the new directory:

var/plugins/CustomContentBundle/

The file structure needs to look like this afterwards:

var/plugins/
├── CustomContentBundle
│   ├── CustomContentBundle.php
|   └ ... more files and directories follow here ...

Clear cache

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:

How to reload Kimai cache

bin/console kimai:reload --env=prod

It is not advised, but in case the above command fails you could try:

rm -r var/cache/prod/*

You might have to set file permissions afterwards:

Adjust file permission

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:

chown -R :www-data .
chmod -R g+r .
chmod -R g+rw var/

You might not need these commands in a shared-hosting environment. And you probably need to prefix them with sudo and/or the group might be called different from www-data.

Updates

Updating the plugin works exactly like the installation:

Delete the directory var/plugins/CustomContentBundle/
Execute all installation steps again:
- Copy files
- Clear cache