starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Renaming folder will not rename subfolders #1349

New Issue
Closed
opened 2026-02-05 00:41:06 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 00:41:06 +03:00
Owner
Copy Link

Originally created by @maxhq on GitHub (Aug 22, 2022).

Subject of the issue

When renaming a folder, all subfolders will then appear on the top level prefixed with the old parent folder and a slash.

Deployment environment

  • vaultwarden version: 1.25.2

  • Install method: Docker image (vaultwarden/server:latest)

  • Clients used: web vault and Bitwarden Linux Client

  • Reverse proxy and version: none

  • MySQL/MariaDB or PostgreSQL version: none

Steps to reproduce

Example folder structure:

  • parent
    • daughter
    • son

Rename parent to authority.

Expected behaviour

  • authority
    • daughter
    • son

Actual behaviour

  • authority
  • parent/daughter
  • parent/son

When renaming authority back to parent the previous structure is restored.

Originally created by @maxhq on GitHub (Aug 22, 2022). ### Subject of the issue When renaming a folder, all subfolders will then appear on the top level prefixed with the old parent folder and a slash. ### Deployment environment * vaultwarden version: 1.25.2 * Install method: Docker image (vaultwarden/server:latest) * Clients used: web vault and Bitwarden Linux Client * Reverse proxy and version: none * MySQL/MariaDB or PostgreSQL version: none ### Steps to reproduce Example folder structure: - parent - daughter - son Rename `parent` to `authority`. ### Expected behaviour - authority - daughter - son ### Actual behaviour - authority - parent/daughter - parent/son When renaming `authority` back to `parent` the previous structure is restored.
OVERLORD added the wontfix label 2026-02-05 00:41:06 +03:00
OVERLORD commented 2026-02-05 00:41:10 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Aug 23, 2022):

Unfortunately that is not something we can change on the server side.
The server never receives the actual folder name, and thus there is no way for the server side to try and match this.

This should either be reported as a bug/feature request at Bitwarden it self.
Either here https://community.bitwarden.com/c/feature-requests/5 or here https://github.com/bitwarden/clients/issues

@BlackDex commented on GitHub (Aug 23, 2022): Unfortunately that is not something we can change on the server side. The server never receives the actual folder name, and thus there is no way for the server side to try and match this. This should either be reported as a bug/feature request at Bitwarden it self. Either here https://community.bitwarden.com/c/feature-requests/5 or here https://github.com/bitwarden/clients/issues
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label wontfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1349
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?