nextcloud / calendar

📆 Calendar app for Nextcloud
https://apps.nextcloud.com/apps/calendar
GNU Affero General Public License v3.0
981 stars 241 forks source link

Calender not working in version 2.0.4 #2662

Closed alexharvard closed 3 years ago

alexharvard commented 4 years ago

Steps to reproduce

Just using the calender app.

Expected behaviour

Adding new calender entries.

Actual behaviour

It's not possible to add a calender event. When clicking "Neuer Termin" or just clicking into the calender is is showing up "von Invalid date um Invalid date bis Invalid date um Invalid date" instead of the date selected as it was in all previous versions. grafik

Calendar app

Calendar app version: 2.0.4

CalDAV-clients used: None

Client configuration

Browser: Firefox 78.3.0esr, Vivaldi 3.4.2066.76

Operating system: Debian 10

Server configuration

Operating system: Debian 10 with latest stable OS updates

Web server: Apache

Database: MariaDB 10.3.23

PHP version: 7.4.10

Nextcloud Version: 19.0.4

Updated from an older installed version or fresh install: Fresh install, issue since calender app update to 2.0.4

List of activated apps:

Enabled:

Disabled:

Nextcloud configuration: { "system": { "instanceid": "REMOVED SENSITIVE VALUE", "passwordsalt": "REMOVED SENSITIVE VALUE", "secret": "REMOVED SENSITIVE VALUE", "trusted_domains": [ "REMOVED SENSITIVE VALUE" ], "datadirectory": "REMOVED SENSITIVE VALUE", "filesystem_checkchanges": 1, "dbtype": "mysql", "version": "19.0.4.2", "overwrite.cli.url": "https:\/\/REMOVED SENSITIVE VALUE\/nextcloud", "dbname": "REMOVED SENSITIVE VALUE", "dbhost": "REMOVED SENSITIVE VALUE", "dbport": "", "dbtableprefix": "oc", "mysql.utf8mb4": true, "dbuser": "REMOVED SENSITIVE VALUE", "dbpassword": "REMOVED SENSITIVE VALUE", "installed": true, "maintenance": false, "memcache.local": "\OC\Memcache\APCu", "memcache.locking": "\OC\Memcache\Redis", "redis": { "host": "REMOVED SENSITIVE VALUE", "port": 0, "timeout": 0, "password": "REMOVED SENSITIVE VALUE", "dbindex": 0 }, "app_install_overwrite": [ "radio" ], "theme": "", "loglevel": 2 } }

Browser log

No error output generated in the js console

mlchai commented 4 years ago

I'm seeing the same error on MacOS Catalina using Chrome. I do have some console output:

Screen Shot 2020-10-27 at 9 56 35 AM
Digitale-Substanz commented 3 years ago

I confirm having the same issue on Firefox 82.0 on Ubuntu 18.04. Possible duplicate, already described here: https://github.com/nextcloud/calendar/issues/2647

tcitworld commented 3 years ago

@Digitale-Substanz @mlchai @Leprazoriy Can you share the URL path before and after you click?

Please also post your own browser logs (just the ones added when clicking once).

Digitale-Substanz commented 3 years ago

URL path before I click: /index.php/apps/calendar/dayGridMonth/now URL path after I click: /index.php/apps/calendar/dayGridMonth/now/new/popover/0/1605978002/1605981602

Console logs after clicking 'Add new' button ('Neuer Termin' in German)

TypeError: e.getters.sortedCalendars[0] is undefined
    createNewEvent calendarObjects.js:339
    g vuex.esm.js:847
    dispatch vuex.esm.js:512
    dispatch vuex.esm.js:402
    n calendarObjectInstance.js:1416
    l runtime.js:63
    _invoke runtime.js:293
    v runtime.js:118
    EE calendar.js:2
    s calendar.js:2
    SE calendar.js:2
    SE calendar.js:2
    getCalendarObjectInstanceForNewEvent calendarObjectInstance.js:1416
    g vuex.esm.js:847
    dispatch vuex.esm.js:512
    dispatch vuex.esm.js:402
    t EditorMixin.js:654
    l runtime.js:63
    _invoke runtime.js:293
    v runtime.js:118
    dg calendar.js:2
    s calendar.js:2
    Ag calendar.js:2
    Ag calendar.js:2
    t EditorMixin.js:645
    e vue-router.esm.js:2452
    confirmTransition vue-router.esm.js:2434
    confirmTransition vue-router.esm.js:2298
    confirmTransition vue-router.esm.js:2297
    VueJS 8
    init vue-router.esm.js:2919
    init vue-router.esm.js:2918
    updateRoute vue-router.esm.js:2308
    transitionTo vue-router.esm.js:2156
    confirmTransition vue-router.esm.js:2294
    r vue-router.esm.js:1895
    r vue-router.esm.js:1899
    f vue-router.esm.js:2274
    confirmTransition vue-router.esm.js:2437
    t EditorMixin.js:644
    l runtime.js:63
    _invoke runtime.js:293
    v runtime.js:118
    dg calendar.js:2
    s calendar.js:2
    Ag calendar.js:2
    Ag calendar.js:2
    beforeRouteEnter EditorMixin.js:643
    confirmTransition vue-router.esm.js:2426
    f vue-router.esm.js:2252
    r vue-router.esm.js:1898
    Ee vue-router.esm.js:1906
    confirmTransition vue-router.esm.js:2404
    r vue-router.esm.js:1895
    r vue-router.esm.js:1899
    f vue-router.esm.js:2274
    Ie vue-router.esm.js:2055
    f vue-router.esm.js:2252
    r vue-router.esm.js:1898
    r vue-router.esm.js:1902
    r vue-router.esm.js:1899
    f vue-router.esm.js:2274
    beforeRouteUpdate Calendar.vue:265
    je vue-router.esm.js:2399
    f vue-router.esm.js:2252
    r vue-router.esm.js:1898
    r vue-router.esm.js:1899
    f vue-router.esm.js:2274
    <anonymous> windowTitleService.js:62
    f vue-router.esm.js:2252
    r vue-router.esm.js:1898
    Ee vue-router.esm.js:1906
    confirmTransition vue-router.esm.js:2282
    transitionTo vue-router.esm.js:2152
    push vue-router.esm.js:2519
    push vue-router.esm.js:2950
    push vue-router.esm.js:2949
    newEvent AppNavigationHeaderNewEvent.vue:70
    VueJS 3
EditorMixin.js:657:5

1

no-response[bot] commented 3 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Digitale-Substanz commented 3 years ago

What does that mean 'no response to our request'? I did reply and share the requested data to the best of my abilities. What else would be needed to finally fix this issue?