nextcloud / nextcloud/richdocuments

Renamed document doesn't change name for other users

Open
#3,471 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: share link
Dominant language
JavaScript
Stars
453
Forks
147
Avg merge
14h 54m
Merged PRs (30d)
83

Description

Describe the bug
When we share a file to other users and then inside Collabora Online we rename it using "file name input" on the top - file becomes renamed in the storage only for one user (I was renaming using file owner and only file owner saw the new name).

To Reproduce
Steps to reproduce the behavior:

  1. Open Nextcloud, share some document with other user
  2. Open shared document with owner of a file and user who get the share
  3. Rename file using owner view (on the top bar in Collabora Online)
    Result: file gets renamed only in one session. Close file, refresh file list, notice that file is not renamed in the list for both of them. Open again in Collabora Online - you will get 2 different names for the same file.

Expected behavior
File should be renamed in all the sessions and both users see the same name in Collabora Online and on the file list.

Screenshots
rename3-2024-02-15_07.54.35.webm

Client details:
Desktop

Server details

Nextcloud version: Nextcloud Hub 7 29.0.0 dev

Version of the richdocuments app 8.4.0-dev

Version of Collabora Online 23.05

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

No file or test entry point is named in the report. Start by reproducing the rename with a shared document using Nextcloud Hub 7, richdocuments 8.4.0-dev, and Collabora Online 23.05; done means both sessions and the file list show the same name after renaming and refreshing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.