mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-17 01:12:27 -05:00
No collections displayed when adding an item #1881
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 @AznoYT on GitHub (Mar 18, 2024).
Subject of the issue
When we want to add a new item to a particular collection, it displays “No collection to display.” although there are multiple collections,
we need to change the organization and then come back to it so that it displays the list of available collections
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
We use the VaultWarden Docker container with 3 organizations to configure on it, 4 users with the 3 organizations to configure.
No specific parameters other than domains
Expected behaviour
Normally when adding, if you have selected a collection in the left column, the identifier you want to add is automatically put in the collection.
Actual behaviour
We have updated the VaultWarden server since the problem appeared, we tried to lower the version of the Windows applications in order to verify that the problem does not come from the applications but nothing has changed
Troubleshooting data
@AleksejEgorov commented on GitHub (Mar 18, 2024):
We faced same issue too.
@n1am commented on GitHub (Mar 18, 2024):
I noted this too.
A simple workaround to solve the issue is to set the ownership (Who owns this item?) to the private vault and then change it back to the organization.
@BlackDex commented on GitHub (Mar 18, 2024):
Which client version are you using
You mentioned lowering it, but never mentioned which versions you tested.
@BlackDex commented on GitHub (Mar 18, 2024):
Also, try a manual sync and see what happens.
@AleksejEgorov commented on GitHub (Mar 18, 2024):
Bitwarden Version 2024.3.0
Shell 28.2.4
Renderer 120.0.6099.291
Node 18.18.2
Architecture x64
Vaultwarden 1.30.5
Manual sync has no effect,
@BlackDex commented on GitHub (Mar 18, 2024):
I get the exact same behavior with
vault.bitwarden.com.This is a client issue, which we can not fix.
I suggest to report this upstream at Bitwarden and also try it your self on there Cloud service.