Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Time Format in Invoice #1032
in the invoice we have date and time (start/end) of the work. this is fomated with [row.date;frm='dd.mm.yyyy'] for the date and [row.start;frm='hh:nn:ss'] for start and [row.end;frm='hh:nn:ss'] endtime.
Now it comes to the stage that this is sometimes not working - have no idea why.
Current Version : v22.214.171.1249
This was working before always....
Same problem here. So far I built a workaround for that by replacing a couple of lines in kimai/extensions/ki_invoice/print.php and private_func.php.
In print.php (line 159ff)
//$model->setBeginDate($beginDate); $model->setBeginDate(date("d.m.Y",$beginDate)); //$model->setEndDate($endDate); $model->setEndDate(date("d.m.Y",$endDate)); //$model->setInvoiceDate(time());
In private_func.php (lines 241ff / version 1.19 )
// added date function to the format start and end properly // $arr['start'] = $entry['start']; $arr['start'] = date("H:i",$entry['start']); //$arr['end'] = $entry['end']; $arr['end'] = date("H:i",$entry['end']);
With that change I was able to use row.start and row.end in the odt templates again. Still, I am mising ome other vars I used before in my templates.
sorry for my late response ... we changed in the meantime the
This works for us, all the Dates/Times are correct now. Please have in mind that this may not work for all environments...
I can confirm having this bug, running Kimai v126.96.36.1994
When exporting the timesheet with a custom ODS template, some begin and end times end up being wrong times around 15 o`clock. This is not during export or anywhere else, only in the invoice, and for six out of 30 entries on that invoice.
I can't create a complete dump right now, but the following line (exported from phpMyAdmin)
where it should be
This is the template I'm using:
Because of the random nature of the bug, this is hard to spot. I almost sent out an incorrect invoice, but luckily double-checked if the template is working (I used CSV exports before, which don't have the problem)