mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-16 08:54:01 -05:00
[GH-ISSUE #4700] Import doubles an import folder #10772
Reference in New Issue
Block a user
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?
Originally created by @BlackDex on GitHub (Jul 3, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4700
Discussed in https://github.com/dani-garcia/vaultwarden/discussions/4692
Originally posted by epiniguin July 2, 2024
Subject of the issue
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Install method: Docker
Clients used:
web vault, firefox extension
Reverse proxy and version:
nginx/1.26.1 installed on the router
MySQL/MariaDB or PostgreSQL version:
PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
Other relevant details:
Steps to reproduce
Use web vault or firefox extension. I did not try other clients.
Expected behaviour
Vaultwarden should import a data without creating(doubling) a folder.
Actual behaviour
Vaultwarden doubles the folder and imports the data there.
Troubleshooting data
@BlackDex commented on GitHub (Jul 3, 2024):
First, @epiniguin sorry for closing this too fast.
Second, I'm working on resolving this issue. It also does this with Bitwarden imports for example.
It actually doesn't matter, we always create new folders, no matter what.
@epiniguin commented on GitHub (Jul 3, 2024):
In this case I propose to change the "Folder" input type at the Import page from select to text.
It will be more clear and more useful. Because now we should create new folder before import, but after import we should delete an empty folder.
@BlackDex commented on GitHub (Jul 3, 2024):
We do not modify the clients, and thus also not the web-vault.
We need to adjust the code on the server side to support this, and we should check if the uuid already exists, if not create a new folder, though that might be tricky, as a uuid collision might be possible in theory.
@BlackDex commented on GitHub (Jul 4, 2024):
Fixed it via a new PR #4702