mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
[BUG] Users unable to create nested collections #2059
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 @snaketech-tu on GitHub (Oct 10, 2024).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD, SMTP_AUTH_MECHANISM
Vaultwarden Build Version
v1.32.1
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx 1.25.5
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Web Vault, Browser Extension
Client Version
No response
Steps To Reproduce
Newbutton in the upper right corner.Collection.Nest collection under.Expected Result
All collections that the user has
editrights to should be selectable. This was working in v1.31.x.Actual Result
No items are shown in the dropdown box.
Logs
No response
Screenshots or Videos
No response
Additional Context
No response
@CedricBojoly commented on GitHub (Oct 10, 2024):
I have the same bug on two different systems
@Misterbabou commented on GitHub (Oct 11, 2024):
Same issue here as a workaround it is working in the Admin Console
@CedricBojoly commented on GitHub (Oct 11, 2024):
it does not work in the admin console either
@BlackDex commented on GitHub (Oct 11, 2024):
To be clear, This does NOT work via the Password Manager View, but only via the Admin Console view.
That is not something Vaultwarden can change, it is a bug in the web-vault which was still there in 2024.8.x last time i checked. I have not checked 2024.9.x and newer.
So @Misterbabou your issue regarding that this is also for admins and owners is not correct.
As far as i can tell there seems to be a strange thing for users who are a manager and allowed to create collections, but then are not able to select an already existing collection which they have access to.
@BlackDex commented on GitHub (Oct 11, 2024):
I was able to figure it out, a PR for this is in the make.