Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Deck calendar integration breaks calendar delegation

Aperta
  • Qualcosa non va?
#8,275 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
javascript
Ambito
api, backend

Direzione di ricerca

Inizia riproducendo il problema con l’integrazione calendario/attività di Deck abilitata e ispeziona la risposta DAV durante il caricamento dei calendari delegati per individuare il nodo mancante app-generated--deck--board-105 generato dall’applicazione. Confronta il comportamento con l’integrazione disabilitata; il lavoro è completato quando le board Deck esistenti vengono esposte correttamente e un nodo Deck non risolto non impedisce più il caricamento dei calendari delegati non correlati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Steps to reproduce
  1. Enable Deck calendar/tasks integration for a user.
  2. The user owns active Deck boards.
  3. Configure calendar delegation between two Nextcloud users.
  4. Open/reload the Calendar app as the user who receives the delegated calendar.
  5. Calendar fails to load the delegated calendars.
  6. DAV debugging shows an error for a Deck-generated calendar node, for example:
    Sabre\DAV\Exception\NotFound
    Node with name 'app-generated--deck--board-105' could not be found
    The referenced Deck board exists and is neither deleted nor archived.
  7. Disable Deck calendar/tasks integration for the affected user.
  8. Reload the Calendar app.

The delegated calendars now load correctly.

The issue is reproducible: enabling the Deck calendar integration causes the problem again; disabling it immediately resolves it.

Expected behavior

Deck calendar integration should not interfere with Calendar delegation.

Existing Deck boards should be correctly exposed as app-generated CalDAV calendar nodes. If a Deck-generated calendar node cannot be resolved, this should not prevent unrelated delegated calendars from being loaded.

Calendar delegation should work regardless of whether Deck calendar/tasks integration is enabled.

Actual behavior

With Deck calendar/tasks integration enabled, Calendar delegation fails and the Calendar app displays:

Delegated calendars could not be loaded.
Make sure the server supports calendar delegation.

The server does support calendar delegation. The delegation itself is correctly stored in oc_dav_cal_proxy, and normal CalDAV requests work.

During the failing request, SabreDAV reports:

<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DAV\Exception\NotFound</s:exception>
<s:message>Node with name 'app-generated--deck--board-105' could not be found</s:message>
</d:error>

The referenced Deck board exists in oc_deck_boards, is active, and is not deleted or archived.

Other Deck-generated calendar nodes for the same environment can be accessed successfully.

As soon as Deck calendar/tasks integration is disabled for the affected user, calendar delegation works immediately. Re-enabling the integration reproduces the issue.

Calendar app version

6.5.3

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

34.0.3

Updated from an older installed version or fresh install

None

List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info

The troubleshooting and analysis of this issue was assisted by AI. All described behavior, reproduction steps, database queries, DAV responses, and test results were verified against the actual Nextcloud environment before submitting this issue.

Lingua principale
JavaScript
Stelle
1.4k
Fork
358
Merge medio
2g 18h
PR unite (30g)
83

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/deck

Tutte le issue di nextcloud/deck

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.