[GH-ISSUE #1103] [probably an upstream bug] Nested folder renaming #779

New issue

Closed

opened 2026-03-03 02:03:07 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 02:03:07 +03:00

Owner

Originally created by @nicolaspernoud on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1103

Subject of the issue

When renaming a nested folder from the web interface, the subfolders go "out" of the renamed folder.

Your environment

Web Vault Version 2.15.1

Steps to reproduce

If I have a folder Racine/Professionnel with subfolders, and I rename it to Racine/Professionnel_Test, all the sub folders keep the name Racine/Professionnel/Subfolder and go "out" of the Racine/Professionnel_Test directory.

Expected behaviour

All the sub folders should be renamed accordingly.

Originally created by @nicolaspernoud on GitHub (Aug 17, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1103 ### Subject of the issue When renaming a nested folder from the web interface, the subfolders go "out" of the renamed folder. ### Your environment Web Vault Version 2.15.1 ### Steps to reproduce If I have a folder Racine/Professionnel with subfolders, and I rename it to Racine/Professionnel_Test, all the sub folders keep the name Racine/Professionnel/Subfolder and go "out" of the Racine/Professionnel_Test directory. ### Expected behaviour All the sub folders should be renamed accordingly.

kerem closed this issue

2026-03-03 02:03:07 +03:00

kerem commented

2026-03-03 02:03:08 +03:00

Author

Owner

@jjlin commented on GitHub (Aug 17, 2020):

As you said, this is an issue on the client side, as the server doesn't have visibility into the (encrypted) folder names. Bitwarden doesn't have a true concept of nested folders; it's just a naming convention that is special-cased on the display side (https://bitwarden.com/help/article/folders/). The clients could conceivably generate multiple requests to rename all subfolders when you change the name on a parent folder, but you'd have to make a feature request for that (https://community.bitwarden.com/c/feature-requests/5/).

@jjlin commented on GitHub (Aug 17, 2020): As you said, this is an issue on the client side, as the server doesn't have visibility into the (encrypted) folder names. Bitwarden doesn't have a true concept of nested folders; it's just a naming convention that is special-cased on the display side (https://bitwarden.com/help/article/folders/). The clients could conceivably generate multiple requests to rename all subfolders when you change the name on a parent folder, but you'd have to make a feature request for that (https://community.bitwarden.com/c/feature-requests/5/).

kerem commented

2026-03-03 02:03:08 +03:00

Author

Owner

@nicolaspernoud commented on GitHub (Aug 18, 2020):

Ok, thanks for the details. I will do the feature request.

@nicolaspernoud commented on GitHub (Aug 18, 2020): Ok, thanks for the details. I will do the feature request.

kerem referenced this issue

2026-03-03 08:53:08 +03:00

[PR #779] [MERGED] Add Github build Action #2800

kerem referenced this issue

2026-03-03 08:53:09 +03:00