nextcloud / nextcloud/files_lock
Wrong message on public share
Open
Nobody has claimed this yet.
bug
good first issue
help wanted
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 48
Description
When sharing a folder throw a public link, if a visitor tries to upload a file with a name that already exists, and the existing file is locked the notification error message is: Could not rename part file to final file
Should be more descriptive of the fact that the file is locked
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the public-share upload path that produces the “Could not rename part file to final file” notification when an existing file is locked. Confirm where that message is selected and check nearby coverage, if present. Done means the notification clearly explains that the existing file is locked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100