shared calendar z-push timeshift

I thinknibfind a bug in webapp.

When creating a calendar item for a full day. Other devices show the appointment duration as 2 full days???

dw2412

@ckruijntjens maybe you should write this all in a way so that someone is able to reproduce.

To find out if this is really an issue please have a look for timezone definitions in your both mobile device, webapp, z-push and linux system. A missmatch in there could lead into such situations.

If they are all equal, please state what you exactly did (day, time start, time end and where original element was defined) and in which time zone your devices, z-push, webapp and linux system are.

There were in past already issues with i.e. daylight savings, with devices in different timezones, with implementation on device itself etc.

Thanks

Andreas

chrostek

Same problem as in this thread:
https://forum.kopano.io/topic/3833/calendar-all-day-events-start-02-00-end-02-00

dw2412

@chrostek

I’ve experienced such issue some years ago. It was related to daylight saving… Means that the event you have is in Summer Time and you’re still with your calendar in Winter Time. Since the thread is already much older that your post, please have a look for your timezone definition in all your PHP Mapi apps (means Z-Push and WebApp). They have to be equal. And please check what you have defined on your device and on your PC that you’re using to access the WebApp.

If it is really an issue in kopano because all time zones are propper defined, let me have a look inside my old patch set. If I remember right I’ve fixed it some years ago in the standard mapi functions related to appointments when kopano was called zarafa… Mapi.util.php has had the issue if I remember right. I will have a look inside my old patchset (I hope I will find it somewhere since it is for sure already over 7 years old…)

Andreas

chrostek

@dw2412 thanks for your reply.
All timezones are the same (Server, Client PC, Client Smartphone, php.ini, webapp, z-push, caldav).
The events in my tests were a few days in future - they where not in another daylight saving time.

My tests:
Event created in WebApp synced with z-push to android smartphone: no problem

Event created in android smartphone synced with z-push to WebApp: no problem

Event created in WebApp synced with caldav to android smartphone: event in WebApp: 16.03.2022 - event in smartphone calendar: 15.03.2022

Event created in android smartphone synced with caldav to WebApp: event in smartphone calendar: 17.03.2022 - event in WebApp: 17.03.2022 - 01:00 until 18.03.2022 - 01:00 - but if i edit it, it shows me an all-day event von 17.03.2022

so it seems a problem in ical
ical.cfg:
server_timezone = Europe/Berlin
/etc/timezone:
Europe/Berlin
webapp/config.php:
date_default_timezone_set(‘Europe/Berlin’);
php.ini:
date.timezone = ‘Europe/Berlin’

this problem only affects all-day events. normal events have the correct times on all devices!

dw2412

@chrostek

To understand you right - this what you experience is an issue related to ical/caldav and not related to Webapp since as long as you use PHP Functions (WebApp & Z-Push are PHP based) there is nothing going wrong. Just if caldav/ical is involved, you have the drift that seems to be timezone (most likely DST) related.

Andreas

chrostek

@dw2412
yes, it seems, that only ical/caldav is the problem

dw2412

@chrostek

So for this I’m off since I have no reason to use ical here at my site. My phone gets its data by Z-Push and other access by WebApp/Outlook is working without issue, too.

Which kopano-ical Version do you use?

@fbartels
Maybe someone from Kopano Support/QA can have a look into this… Seems that kopano-ical could have an issue…

chrostek

@dw2412
i use kopano-ical 11.0.2.51.76cf85b89-0+877.1

@dw2412

Hi,

I dont use ical. i also use zpush for calendar etc.

I have the same problem. when i create a calendar item (only for the full day) it reservers 2 days in the calendar)

timezone and date is correct on the server.

@ckruijntjens nevermind allredeay fixed it

dw2412

@ckruijntjens nice… so please specify some details that allow me to reproduce your issue. As stated already another thread - I’ve tried my best but without your info I’m and for sure Kopano Support/QA is unable to reproduce. Please understand that bugs can only be fixed if they can be found. To find them you need to reproduce them. To reproduce you need as much details as possible.

Let’s start with your environment. What Kopano version do you use? What timezone have you defined in WebApp/Z-Push/Php/your client(s). Which OS Distribution do you use? What did you exactly do to define the element in Kopano on your Mobile/on your desktop PC.

Andreas

dw2412

@ckruijntjens OK… So if already fixed and not a bug, please tell others what you did wrong so that they maybe find it if issue occurs and directly have an idea to what have a look for…