| Summary | display of all-day events in freebusy week/month view in attendees.php broken |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | m.gabriel (at) das-netzwerkteam (dot) de |
| Created | 05/10/2009 (5897 days ago) |
| Due | |
| Updated | 05/15/2009 (5892 days ago) |
| Assigned | 05/14/2009 (5893 days ago) |
| Resolved | 05/15/2009 (5892 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | Yes |
State ⇒ Not A Bug
cross-timezone?
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.
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???
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.
views, neither in Git or stable Kronolith.
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...
State ⇒ Feedback
neither in Git or stable Kronolith.
New Attachment: 20090509_Kronolith_Freebusy_AllDayEventsInWeekView.patch
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ display of all-day events in freebusy week/month view in attendees.php broken
Type ⇒ Bug
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.