3 ms·
The issue he is discussing with ownCloud and timezones is not a limitation that applies to their CalDAV implementation, it is just an issue with their web clien
by mutantmonkey 13y ago
The issue he is discussing with ownCloud and timezones is not a limitation that applies to their CalDAV implementation, it is just an issue with their web client. If you use a CalDAV client that supports time zones properly (most do), it will work fine.
- j-kidd 13y agoI am pretty sure ownCloud web client does have timezone support, but he didn't change the setting. From http://owncloud.org/support/calendars/ http://owncloud.org/support/calendars/ > The calendar needs your current position for detecting your timezone. Without the correct timezone there will be a time offset between the events in owncloud and your desktop calendar you synchronise with owncloud. You can also set the timezone manually in the personal settings. After reading the article, it seems like the author hasn't looked too hard into self-hosted solutions.
- kenkinder 13y agoYou can change the timezone on the web GUI, but that's just the offset. The issue is that CalDav PUT requests included a timezone, which the server just discards. You can try it yourself. Setup OwnCloud with Lightning or something. Create an event and specify a timezone in the event itself. Close and reopen the app, or use another app, and you'll find that OwnCloud simply truncates the data and stores it as UTC with no adjustment.