nextcloud / nextcloud/whiteboard

Library persistence fails if user's Templates folder was deleted

Open
#1,251 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
215
Forks
39
Avg merge
1d 3h
Merged PRs (30d)
32

Description

Whiteboard library persistence fails if the user's "Templates" folder has been deleted.

Environment

  • Nextcloud deployment: Nextcloud AIO
  • Whiteboard version: 1.5.9
  • Browser: Brave / Chromium

Steps to reproduce

  1. Remove the user's Templates/ folder from Nextcloud Files (or rename to TemplatesBackup)
  2. Open any .whiteboard file.
  3. Import a library. Library -> three dots -> Open -> select previously downloaded .excalidrawlib from a file picker
  4. Confirm the imported library appears in the current session.
  5. Reload the page and enter the .whiteboard file.
  6. Imported library disapears.

Actual behavior

The imported library disappears after reload.

In browser DevTools, the library save request fails:

PUT /apps/whiteboard/library -> 404

Expected behavior

Whiteboard should persist the imported library, even if the user deleted the default Templates/ folder.

Possible solution

  1. Ensure the user's Templates/ folder exists before reading/writing personal.excalidrawlib.
  2. Recreate Templates/ folder when importing a library.

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.

Research direction

Reproduce the deleted-Templates scenario and inspect the failing PUT /apps/whiteboard/library request, including how the personal.excalidrawlib location is handled. Done means an imported library remains available after reload even when the user's Templates folder was deleted.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.