[horde] Timeshift on ActiveSync to Horde

[Stephan Kleber]

Hi,

I'm sorry I couldn't answer earlier.

>> I have not forgotten about this. In debugging *this* issue, I
>> discovered another, more important issue that caused a 1 hour
>> timeshift from server -> client for recurring events that span a DST
>> transition (as opposed to your reported issue of client -> server).
>> The fix for *this* issue is included in the latest round of releases
>> that dropped today (including the ActiveSync and Date package) and had
>> to due with a bug parsing a date object on the exact hour of a DST
>> transition.
Thank you Mike for looking into this.

>> The issue you are reporting is due, I believe, to the fact that we
>> seem to be currently ignoring the timezone data structure that is sent
>> from the device. Part of the problem is that all of the devices I've
>> tested only send transition dates and offsets - and omit the timezone
>> identifier (this is allowed by the spec) - so we are going to need to
>> either parse these values into a timezone identifier, or otherwise
>> adjust the UTC time. This should only affected recurring events that
>> are created or edited on the device that span a DST transition.
>>
>> It is most likely a coincidence that you noticed this after a recent
>> upgrade - it is more likely the recent switch from daylight to
>> standard time is what has brought this to your users' attention.
May be an coincidence with DST. I didn't think about the more or less
recent chance.

> These issues should now be fixed in Git master. I'm not releasing
> another PEAR package at this time, because there were a good bit of
> changes made and I want some time for myself, and hopefully others, to
> test that things are working well first.
Ok. I will see if it is fixed as soon as possible. Lastest when released
as PEAR package.

cu
Stephan