Thu, 09 Apr 2026 20:04:47 +0000 https://bugs.horde.org/ticket/8263 display of all-day events in freebusy week/month view in attendees.php broken i am running kolab with horde-webmail-1.2.3-final, but a look into GIT alludes that the problem is probably still present in Kronolith GIT. when adding attendees in kronolith's attendees.php i observed a weird display behaviour for all-day events: o create an all-day event o create another event that you want to add an attendee to o when adding an attendee notice the formerly created all-day event o especially notice the week view of all day events in week view all-day events start one day ahead in the last hour shown in freebusy view. an all-day events ends one hour early on the date of the all-day event. the day view in attendees.php looks ok. month view is also problematic... the attached patch fixes the view problems on my site but seems to work around some deeper problem. may be UTC/GMT are not considered very well or DST is not taken into consideration when viewing the freebusy periods in attendees.php. Sun, 10 May 2009 01:13:50 +0000 https://bugs.horde.org/ticket/8263#t54075 adding patch Sun, 10 May 2009 01:15:38 +0000 https://bugs.horde.org/ticket/8263#t54076 I don't see anything wrong with all-day events in the free/busy views, neither in Git or stable Kronolith. Thu, 14 May 2009 17:00:06 +0000 https://bugs.horde.org/ticket/8263#t54135 > I don't see anything wrong with all-day events in the free/busy > views, neither in Git or stable Kronolith. i'll be gone over the weekend. once i am back, i would like to send a screenshot to your mail address that might explain the problem. my questions to you: what backend do you use (esp. freebusy backend). freebusy uses unix timestamps, my server runs in UTC time and defaults to time zone Europe/Berlin. additionally we currently have DST (but i think i had this issue also with former kronolith/kolab versions throughout the whole year). thus it might also be a problem in my kolab freebusy backend on UTC server. could you check all day events in my freebusy data? do they look ok? https://mail.das-netzwerkteam.de/freebusy/m.gabriel (at) das-netzwerkteam.de.xfb if the issue is caused by kolab freebusy on my server this ticket might need a queue change... Thu, 14 May 2009 20:59:39 +0000 https://bugs.horde.org/ticket/8263#t54157 I use the SQL backend. I'm not sure what's supposed to be all-day events in your calendar, but I see May 15 - 18 correctly covered from midnight to midnight. Thu, 14 May 2009 22:22:09 +0000 https://bugs.horde.org/ticket/8263#t54159 Hi Jan, > I use the SQL backend. > I'm not sure what's supposed to be all-day events in your calendar, > but I see May 15 - 18 correctly covered from midnight to midnight. this is a kolab issue and relates to http://www.intevation.de/roundup/kolab/issue1412 in the above patch/workaround I add 3600 to the unix timestamp in freebusy. i actually replaced this now by date("Z"), but it still is a workaround... Thinking about it even more... o imagine I am a jetsetter with appointments in DE and UK o what shall the people trying to make appointments with me see in freebusy? their timezone, my timezone or the server timezone (UTC!?!)? o how do i want my events to be displayed in horde (always local time, means that when jetsetting from DE to UK my DE appointments are an hour off...)? Is there a concept in kronolith for timezone shifting resp. working cross-timezone? @kolab-people: shouldn't freebusy always be distributed completely in UTC and the timezone be added by the freebusy client??? Fri, 15 May 2009 22:16:14 +0000 https://bugs.horde.org/ticket/8263#t54206 > Is there a concept in kronolith for timezone shifting resp. working > cross-timezone? Not in the stable version. Fri, 15 May 2009 23:53:36 +0000 https://bugs.horde.org/ticket/8263#t54209