nextcloud / nextcloud/text

Internal links in Rich Workspace README.md break after target file rename (persistent across browsers, fixed only by renaming back)

Open
#8,555 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: folder description
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Describe the bug
When a Rich Workspace README.md contains an internal link to a file in the same folder, clicking the link from the rendered preview at the top of the folder view fails with "Datei existiert nicht mehr" / "File does not exist anymore" after the linked file has been renamed.
The link only breaks in this specific click path. The same link works correctly when:

The README.md is opened in the Text editor and the link is clicked from there
The file is opened via its icon in the file list

This indicates the Rich Workspace renderer resolves internal links by stored path/filename rather than by fileId, while the editor and file list use fileId-based resolution.

To Reproduce
Steps to reproduce the behavior:

  1. In a folder, create README.md with Rich Workspace and add an internal link to another file in the same folder (e.g. target.md)
  2. Verify the link works when clicked from the Rich Workspace preview
  3. Rename target.md to target-new.md
  4. Reload the folder view (or open in another browser)
  5. Click the link in the Rich Workspace preview → "Datei existiert nicht mehr"
  6. Click the link from inside the Text editor (open README.md) → works correctly
  7. Rename the file back to target.md → link in Rich Workspace works again

Expected behavior
Internal links should resolve by fileId and continue to work across renames, consistent with how internal links behave when clicked from inside the Text editor or via the file icon.

Server details:

  • Nextcloud version: 33.0.3
  • PHP Version: 8.3
  • Database: MariaDB 11.4.10

Client details:
Tested on several OSs and browsers

Nextcloud log (data/nextcloud.log)

No errors logged.

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

Start by comparing how internal links are resolved from the Rich Workspace README.md preview with the existing behavior in the Text editor and file list, following the click path described in the reproduction steps. Reproduce the rename from target.md to target-new.md and verify that the preview link continues to open the renamed file by fileId, including after reloading the folder view.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.