dakira / myroundcube

Automatically exported from code.google.com/p/myroundcube
0 stars 0 forks source link

[calendar_plus] - Time does not sync correctly with calDAV server. #727

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Token: 2d4eb55293a0ff24a41cc5820160e6d8 (Don't modify this token!)
Version: 3.0.49 (02-08-2014)
PHP: 5.4.32
RCMAIL: 1.0.2
Database: mysql
SERVER: Apache/2
----
I.  Issue Description:
Time synchronization is off by 4 hours.  It seems to be a timezone issue since 
my timezone is EDT which is GMT+4.  When I create an event in roundcube, the 
event is recorded correctly.  However, when later logging into OwnCloud 7.0.1 
and viewing the calendar it is recorded as Time+4hr.  So, if I set it at 2pm 
then the event shows at 6pm in Owncloud.  In Roundcube it is still showing as 
correct.

If I then open the event in Owncloud, the time is changed to the correct time 
(2pm) and then if I cancel it remains unchanged and shows me again the 6pm 
time.  However, if I open it, don't change anything, then save it, the time 
will show correct in OwnCloud.  However, after the next synchronization it will 
show in Round cube as 10am now instead of 2pm.  There is a +4 hours offset with 
OwnCloud.

Roundcube is set to AUTO under "User Interface".  I have also tried to set this 
manually.  No change.

Roundcube and OwnCloud are both configured on the same server so their 
timezones are the same.

This issue does NOT happen when creating the event with owncloud directly and 
syncing to Thunderbird or Android.  It will also not happen when created in 
Thunderbird or Android and syncing with Owncloud.  It is exclusive to Roundcube 
which would indicate to me an error in the code with how Roundcube is 
saving/tagging/reading timestamps/timezones.

II. Steps to reproduce the Issue:
1.  I created a specific user for you to test this on my OwnCloud installation.
2.  Login credentials sent privately to Roland via email.
3.  Login to the test account with owncloud and get the calDAV url for the 
calendar.
4.  Login to your Roundcube installation and enter the calDAV details.
5.  Add event in the calendar.
6.  Go back to Owncloud and see the timestamp is incorrect.
7.  Open the event and cancel it without saving changes.  The time will not 
change.
8.  Open the event, do not change anything, but this time save changes.  The 
time will be different.
9.  Got back to Roundcube and synchronize the calendar and you will see the 
time changed in Roundcube as well.

This calendar plug-in is unusable if the time does not sync correctly with 
CalDAV.

Original issue reported on code.google.com by jthornto...@gmail.com on 4 Sep 2014 at 7:09

GoogleCodeExporter commented 8 years ago
Please check your emails. My test account does syncs with correct timezones.

Original comment by myroundc...@gmail.com on 5 Sep 2014 at 3:55

GoogleCodeExporter commented 8 years ago
I have checked the emails and I have also looked at it from a different browser 
(FF & IE) and both issues are the same.  The setting for the timezone in user 
interface is set to AUTO.  

The problem still exists.

Original comment by jthornto...@gmail.com on 5 Sep 2014 at 10:59

GoogleCodeExporter commented 8 years ago
The problem does not exist for me when using the test account on YOUR server. 
So, I can't fix working things unless you tell me what should do else than 
testing things with the same plugin code as you are using and to use your 
server as backend. 

Original comment by myroundc...@gmail.com on 6 Sep 2014 at 2:42

GoogleCodeExporter commented 8 years ago
Feedback from issuer: Adjusting timezone settings in owncloud calendar fixed 
the issue.

Original comment by myroundc...@gmail.com on 6 Sep 2014 at 2:45