Coding projects (by others)

This page lists a few projects that I've cloned from elsewhere.

Some of them still sync with the original repository, and in some cases I keep a local (private) branch with my own tweaks and additions.

> As per the OP's suggestion, moving the ticket state colors into CSS, so that they participate in the skinning process, would be a good thing to do someday. I see some problem. It would be quite easy I think to create CSS-Classes if a Variable cssclass or similar is created in the SQL-Query. That part is easy. But what CSS-Classes would a creator of a report pick? As the users can switch their skin, these would've to be supported in all available skins. We could provide some for common cases, but it would be hard to use more customized stuff. The report-creator has to make sure their CSS-Classes are added to the skins. So it is not impossible to implement I think, but as I see it the usefulness would be limited if there isn't a way to add the needed classes to all skins or add custom classes to the report window as well. Which probably would be the best way, add another input for creating CSS that is injected on the report page. But then again it is not part of the skinning.

I don't know if `tkt_ctime` was a field back when this report was made, but it exists now. So I added it to the report columns in the default text when creating new ticket reports ([](86c1910ffbd1b642)), show creation time in the default ticket view ([](814a417b4d2d1071)) and also for good measure show additionally the human readable age for both `tkt_mtime` and `tkt_ctime` ([](8b48a054edda1a17)). I think these changes should cover this ticket. As most of it is done in the default TH1 it is not instantly available on old repositories unless the tkt_view template is reverted to default. But that is better I think, because it still enables the ability for admins to configure the ticket view and reports as they like.

There is a bug if you enable reports with mutiple rows per ticket (by declaring a value name with a leading underscore), then sorttable.js breaks on these additional rows.

Not present in the current 3rd Edition text.

This was already fixed in [20201121162334Z](/info/20201121162334Z)

Theme: "Small Business" by Blackrock Digital

Background: "A beautiful day" by Jason Blackeye