-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When assigning different timezone, the event duration would be wrongly changed to the time differences #1914
Comments
It automatically changed the time to 5pm, because by changing the start-timezone, you are putting the start-date after the end-date. As this is not possible, it automatically sets the end date to the start-date. (As 5pm taipei is the same as 10am Brussel)
What did you try to change the end time to? I agree as this is not optimal. There are cases where you want different timezones for start and end, e.g. an intercontinental flight, but most of the time start and end timezone is the same, so I think the default behaviour should be changing both. |
I have to change the timezone of start time first, then end time. Both timezone were set then. However after setting both timezone, when I change the end time to any time, the start time would be changed automatically too.
I'm not setting different timezone for start and end time. Just in steps I have to set the start timezone first, and at that moment the end time was changed automatically. At step 6 I missed telling you the timezone of end time was set to Brussels too. But no matter the timezone of end time was set or not, the behavior was the same. |
I think this problem goes deeper, I just tried to create an event, then change the timezone for both start & end. It's impossible to create the event with the times I want right now.
I tried to enter the time with the timepicker and to write it in manually, neither worked |
I've also hit this in a couple of different ways. The net result is always that the end timezone is changed once you click "update" and re-open the event (and the start timezone also can change). I've even hit this problem when trying to set both the start and end to be in the same timezone!. Trying to add an entry for an intercontinental flight:
Trying to create an entry in a different timezone:
Unless I'm mistaken, both of these behaviours could be explained by a bug where you are doing something like
|
Steps to reproduce
Expected behaviour
The duration shouldn't be changed. The time should be saved in the timezone I set.
Actual behaviour
A misbehavior happened to make the time differences become the duration time.
Calendar app
Calendar app version: 2.0.1
CalDAV-clients used: N/A
Client configuration
Browser: Chromium 78.0
Operating system: Debian testing
Server configuration
Operating system: Debian Buster
Web server: Apache 2.4.38
Database: MariaDB 10.3.18
PHP version: 7.3.11
Nextcloud Version: 17.0.2
Updated from an older installed version or fresh install: Updated
List of activated apps:
Nextcloud configuration:
Logs
Web server error log (e.g. /var/log/apache)
nextcloud_error.log
nextcloud_access.log
Log file (data/nextcloud.log)
nextcloud.log
Browser log
a) The javascript console log
nextcloud.slat.org-web-console.log
It was shown in the screenshot too. I didn't see too many useful information.
b) The network log
nextcloud.slat.org.har.log
The text was updated successfully, but these errors were encountered: