[eGroupWare-tracker] Bugs #2507: All day events sync to Nokia 5800 as timed all-day appointment 00:00-23:59

[<tr...@eg...>]

Ticket modified by Ian Hodge at 2010/04/29 10:28
Tracking System: Bugs
Category: SyncML
Version: Trunk
Status: Open
Resolution: None
Completed: 0%
Priority: 5 - medium
Created By: Ian Hodge
Assigned to: Jörg Lehrke
Summary: #2507 - All day events sync to Nokia 5800 as timed all-day appointment 00:00-23:59
This is with 1.6.003 (and trunk?)

Syncing from egw to phone, all day events (non blocking) appear as all day appoihtments with times (00:00 - 23:59) on phone. Events on phone sync to egw as events (non blocking). I have the option ticked in syncml preferences for 'non blocking all day events'


Comment by Ian Hodge at 2010/04/29 10:28:
Logfile uploaded again, this time with '.txt' extension. I can see its contents when I look at it from the bug tracking system so I think it's ok now. Two entries were sync'd:

'Timed appointment', 29/05/2010 08:00-13:00 recurring daily until 03/05/2010
'All day event', 29/05/2010, all-day, non-blocking, recurring daily until 03/05/2010


Comment by Jörg Lehrke at 2010/04/29 06:52:
The attached log-file seems empty. Could you please do it again and let me know the exact start, end and recurrence dates of the events. Thanks!
Comment by Ian Hodge at 2010/04/28 21:48:
I updated to the latest svn then synced one timed recurring event and one all day recurring event from egw to my phone. The timed event synced correctly, the all-day event synced with an extra entry one day early as before. Logfile is attached.
Comment by Jörg Lehrke at 2010/04/26 10:01:
I tried to reproduce your problem with a recurring all-day event which started in March and lasts until 1st of July every Thursday. The vCalendar entry looks good but my Nokia 6131 was not able to process the entry. Would you please enable debug logging within the file calendar/inc/class.calendar_ical.ic.php ($log = true;) and provide my with the vCalendar data of the affected event. You will find it in the logfile. We may handled this additional issue within this ticket.
Comment by Ian Hodge at 2010/04/25 20:40:
Update: this seems to only occur for recurring events.
Comment by Ian Hodge at 2010/04/25 20:22:
Events now get sync'd correctly in both directions. Those from egw->phone now appear on phone as 'all-day events'.

However, I spotted one other problem (and this was present before the most recent update): all-day events sync'd egw->phone are sync'd one day early if they occur during summertime i.e. event on 3rd May in egw appears in phone on 2nd May.

Egw and phone are both set to Europe/London timezone. Timed events do not have this problem. Please advise if you want this raised as a separate bug. Thanks.
Comment by Jörg Lehrke at 2010/04/23 16:40:
I compared the 1.6.001 code with the current implementation and could not find a reason for different behavior. Nevertheless I get your point and export all-day events as such to Nokia now with the latest SVN versions. Please confirm that is works now.
Comment by Ian Hodge at 2010/04/23 15:28:
I don't know about 1.6.003-2 as I upgraded to trunk (svn) to try and solve my timezone issues (timezone support was basically not working with 1.6.003 using php 5.3.x). This was solved by upgrading to trunk.

Regarding this issue, yes it is still the case with trunk (svn) that all day events sync as timed all-day appointment 00:00-23:59
Comment by Jörg Lehrke at 2010/04/23 09:02:
Is this issue still open with the current version (1.6.003-2 and SVN)?
Comment by Ian Hodge at 2010/03/20 19:30:
In v1.6.001 all-day events *were* synced correctly as such to my Nokia so this behaviour has changed on the egw side since my upgrade to 1.6.003
Comment by Jörg Lehrke at 2010/03/13 06:52:
The option on EGw side is only used for event imports and enforces the 'non-blocking'. For exports of calendar data EGw set the VCalendar information appropriately, but if the client does not respect it, there is nothing we can do. Sorry


Linked entries:
http://www.egroupware.org/egroupware/index.php?menuaction=tracker.tracker_ui.edit&tr_id=2507&no_popup=1