nextcloud / nextcloud/calendar

Odd behaviour around daylight savings switch time

Open
#3,977 2 comments 2 reactions 1 assignee View on GitHub

@st3iny is already working on this.

Since Jun 11, 2025.

1. to develop bug Feature: Editor skill:frontend
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. Ensure you have English (US) locale and New York time zone ()
  2. Try to create an event at 10:00PM on March 12 2022 (Daylight savings takes effect on March 13 2022)
  3. Impossible to create event.
Expected behavior

Event should be created at 10:00PM on March 12 2022

Actual behaviour

Event does not exist. It might have been deleted, or there was a typo in a link error is displayed

https://user-images.githubusercontent.com/10747559/154983940-61c4031e-f840-451d-b7fd-76915bc1ae28.mp4

Calendar app version

3.0.6

CalDAV-clients used

No response

Browser

Firefox 97.0 (64-bit)

Client operating system

Ubunut

Server operating system

Ubuntu

Web server

Apache

Database engine version

MySQL

PHP engine version

PHP 8.0

Nextcloud version

Nextcloud Hub II (23.0.2)

Updated from an older installed version or fresh install

Updated from an older version

List of activated apps
Enabled:
  - accessibility: 1.9.0
  - activity: 2.15.0
  - appointments: 1.11.14
  - calendar: 3.0.6
  - circles: 23.0.1
  - cloud_federation_api: 1.6.0
  - comments: 1.13.0
  - contacts: 4.0.8
  - contactsinteraction: 1.4.0
  - dashboard: 7.3.0
  - dav: 1.21.0
  - federatedfilesharing: 1.13.0
  - federation: 1.13.0
  - files: 1.18.0
  - files_pdfviewer: 2.4.0
  - files_rightclick: 1.2.0
  - files_sharing: 1.15.0
  - files_trashbin: 1.13.0
  - files_versions: 1.16.0
  - files_videoplayer: 1.12.0
  - firstrunwizard: 2.12.0
  - logreader: 2.8.0
  - lookup_server_connector: 1.11.0
  - mail: 1.11.6
  - nextcloud_announcements: 1.12.0
  - notifications: 2.11.1
  - oauth2: 1.11.0
  - password_policy: 1.13.0
  - photos: 1.5.0
  - privacy: 1.7.0
  - provisioning_api: 1.13.0
  - recommendations: 1.2.0
  - richdocuments: 5.0.2
  - richdocumentscode: 21.11.103
  - serverinfo: 1.13.0
  - settings: 1.5.0
  - sharebymail: 1.13.0
  - spreed: 13.0.3
  - support: 1.6.0
  - survey_client: 1.11.0
  - systemtags: 1.13.0
  - text: 3.4.0
  - theming: 1.14.0
  - twofactor_backupcodes: 1.12.0
  - updatenotification: 1.13.0
  - user_status: 1.3.1
  - viewer: 1.7.0
  - weather_status: 1.3.0
  - workflowengine: 2.5.0
Disabled:
  - admin_audit
  - bruteforcesettings
  - encryption
  - files_external
  - user_ldap
Nextcloud configuration
{
    "system": {
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "nc23.localhost:9090"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "23.0.2.1",
        "overwrite.cli.url": "http:\/\/nc23.localhost:9090",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "mail_smtpmode": "smtp",
        "mail_sendmailmode": "smtp",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpauth": 1,
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "587",
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpsecure": "tls",
        "mail_smtpstreamoptions": {
            "ssl": {
                "allow_self_signed": true,
                "verify_peer": false
            }
        },
        "mail_smtpauthtype": "PLAIN",
        "app.mail.verify-tls-peer": false,
        "theme": "",
        "loglevel": 2,
        "maintenance": false,
        "updater.secret": "***REMOVED SENSITIVE VALUE***"
    }
}
Web server error log
NA
Log file
NA
Browser log
Might be relevant: 
TypeError: t is null
    x_ event.js:97
    n calendarObjectInstance.js:1448
    u runtime.js:63
    _invoke runtime.js:294
    v runtime.js:119
    W_ calendar-main.js:2
    o calendar-main.js:2
    promise callback*W_ calendar-main.js:2
    o calendar-main.js:2
    q_ calendar-main.js:2
    q_ calendar-main.js:2
    getCalendarObjectInstanceForNewEvent calendarObjectInstance.js:1438
    ke vuex.esm.js:851
    dispatch vuex.esm.js:516
    dispatch vuex.esm.js:406
    e EditorMixin.js:608
    u runtime.js:63
    _invoke runtime.js:294
    v runtime.js:119
    oO calendar-main.js:2
    o calendar-main.js:2
    promise callback*oO calendar-main.js:2
    o calendar-main.js:2
    sO calendar-main.js:2
    sO calendar-main.js:2
    e EditorMixin.js:598
    S vue-router.esm.js:290
    init vue-router.esm.js:392
    VueJS 19
    init vue-router.esm.js:3002
    init vue-router.esm.js:3002
    updateRoute vue-router.esm.js:2414
    transitionTo vue-router.esm.js:2263
    confirmTransition vue-router.esm.js:2401
    r vue-router.esm.js:2000
    r vue-router.esm.js:2004
    h vue-router.esm.js:2380
    confirmTransition vue-router.esm.js:2540
    e EditorMixin.js:597
    u runtime.js:63
    _invoke runtime.js:294
    v runtime.js:119
    oO calendar-main.js:2
    o calendar-main.js:2
    sO calendar-main.js:2
    sO calendar-main.js:2
    beforeRouteEnter EditorMixin.js:596
    confirmTransition vue-router.esm.js:2535
    h vue-router.esm.js:2361
    r vue-router.esm.js:2003
    St vue-router.esm.js:2008
    confirmTransition vue-router.esm.js:2397
EditorMixin.js:598:8
Additional info

This is probably a low priority edge case.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.