Tickets :: Comment on [#12773] Horde_Timezone unable to use non-ftp scheme to access database.

* Your Email Address
* Spam protection	Enter the letters below: .__. ..___. ..___. \| \| \|[__ \|_/ \| \|__\\__\|[___\| \ \|
Comment	>> Now Kronolith internally uses UTC to represent the event. That is >> beneficial for many purposes. But the Kronolith developers seemingly >> didn't think about repeated events here. If we repeat an event with >> fixed time in UTC (every repetition is at 19:00 in UTC), this will >> mean a non-fixed time in local timezones. > > We absolutely take into account recurrence series. We explicitly > add the timezone information to the vCalendar when we are outputting > recurring series. You can see this in Kronolith_Event::toiCalendar(). > If the event is being output in UTC, then that means that either the > event's timezone was explicitly set to UTC or there was no explicit > timezone set and the default timezone for the user in question is UTC. >
Attachment
Watch this ticket