Custom Content plugin requires build Kimai 20100 or 20500

[foliovision]

@girish I hope you are keeping well.

We use Kimai in production and would like to add the Custom Content plugin to improve some js quickly. We thought it would be an easy job and were delighted to pay for the plugin.

Imagine our disappointment when we managed to take down our Kimai server. It turns out that
CustomContentBundle-2.2.0 requires Kimai build 20100, while
CustomContentBundle-2.3.0 requires Kimai build 20500.

The Cloudron Kimai build is back at 20031 (a.k.a. 2.0.33). We have autoupdates enabled and manually updated to make sure we have the very latest Cloudron version installed. Strangely the package version is org.kimai.cloudronapp@2.1.3 which sounds like 20130 which would be enough to allow us to install
CustomContentBundle-2.2.0.

Could you look into the Kimai package and see if we can't get the latest version down the pipe? I know there were some breaking changes with v2 but these are not major version updates (that's behind us) but just improvements to Kimai 2.x.

Thanks, Alec

[nebulon]

So the Cloudron package has Kimai v2.12.0, see https://git.cloudron.io/cloudron/kimai-app/-/blob/master/CHANGELOG.md?ref_type=heads&plain=1#L1122

This is the latest upstream release currently at https://github.com/kimai/kimai/releases/tag/2.12.0

Note that app version and package version are not the same in Cloudron.

[foliovision]

Thanks @nebulon for the quick answer. It does look like you are shipping a more recent version than the internal version number suggests. We'll have another go at it tomorrow to try to figure out why the Cloudron version reports an earlier version number than
CustomContentBundle-2.2.0 and
CustomContentBundle-2.3.0 allow.