mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Deleting folder in Vault doesn't update the cached client-side status of affected ciphers #4
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 @mprasil on GitHub (May 16, 2018).
The updates on the server side are actually done correctly, when I reload the Valut page, ciphers are in
No_folderas they should be, it's only the client-side cache that's wrong. I assume, we should be returning some data from/api/folder/<id>/deleteto let Vault know which ciphers were updated?BTW this has nothing to do with #20 - the client side behavior didn't change before or after implementing those changes. It's just something I noticed while working on the PR.
@dani-garcia commented on GitHub (May 19, 2018):
I just tried this in the official server at vault.bitwarden.com and it seems to do the same, the method doesn't return anything and the ciphers in the deleted folder are visible from "All items" but not from "No folder". Once the page is reloaded, it's fine again.
It seems like a bug in the web vault to me.
@mprasil commented on GitHub (May 19, 2018):
Might be worth reporting upstream so @kspearrin is aware. I don't have Bitwarden account to test unfortunately.
@mprasil commented on GitHub (May 24, 2018):
I've reported the issue upstream - #204. Closing this one.