nextcloud / nextcloud/end_to_end_encryption
browser: fix e2ee folder renaming experience
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- PHP
- Stars
- 320
- Forks
- 36
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 81
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
e2ee folders cannot be renamed. Trying to rename will give an error "cannot rename"
option 1: make renaming possible
option 2: hide the rename button
versions
Nextcloud: 33.0.5
e2ee app: 2.1.1
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
Reproduce the failed rename in a browser using Nextcloud 33.0.5 with e2ee app 2.1.1, then trace the end-to-end-encrypted folder rename flow in this repository. Done means either encrypted folders can be renamed successfully or the rename control is hidden, matching the selected option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100