[Bug] Latest testing, collections do not load (Related to PascalCase changes?) #4682
Comments
|
Probably related to #4681, but could be something different. |
|
It also happens on vault.bitwarden.com so this probably unrelated to vaultwarden (might even be intentional). |
I was able to rollback to the June 20th build of vaultwarden (via doing a docker build) - which has the Web vault 2024.5.1 (collections issue is not present in that vaultwarden build): So it seems the admin collections issue crept in on vaultwarden between June 23rd - June 24th. |
|
seems like this setting is responsible for the behavior: vaultwarden/src/db/models/organization.rs Line 409 in a4c7fad |
|
Ah, we can set that back to false for now. And add flex/v2 later. |
- More info here: dani-garcia#4682
I don't think those two are that related (like I said dani-garcia/bw_web_builds#169 (comment) the new endpoint is already used instead). To actually implement flexible collections we will have to change more stuff (not sure if this is everything but that's what I've noted down so far)
|
|
Oef. That sounds to me like a Backup your database first before update situation. |
Collections were not visible in the organization view.
This was because the `flexibleCollections` was set to `true`
Found an issue with loading some old created Secure Notes which had `{}`
as there `data` value. This isn't allowed. When detected, replace it
with `{"type":0}`
Fixes dani-garcia#4682
Collections were not visible in the organization view.
This was because the `flexibleCollections` was set to `true`
Found an issue with loading some old created Secure Notes which had `{}`
as there `data` value. This isn't allowed. When detected, replace it
with `{"type":0}`
Fixes dani-garcia#4682
|
I created a PR to fix this specific issue, and a small issue i found with the new native app. #4685 |
Collections were not visible in the organization view.
This was because the `flexibleCollections` was set to `true`
Found an issue with loading some old created Secure Notes which had `{}`
as there `data` value. This isn't allowed. When detected, replace it
with `{"type":0}`
Fixes dani-garcia#4682
Collections were not visible in the organization view.
This was because the `flexibleCollections` was set to `true`
Found an issue with loading some old created Secure Notes which had `{}` or `{"type":null}` as there `data` value.
This isn't allowed. When detected, replace it with `{"type":0}`
Fixes dani-garcia#4682
Fixes dani-garcia#4590
Collections were not visible in the organization view.
This was because the `flexibleCollections` was set to `true`
Found an issue with loading some old created Secure Notes which had `{}` or `{"type":null}` as there `data` value.
This isn't allowed. When detected, replace it with `{"type":0}`
Fixes #4682
Fixes #4590
Collections were not visible in the organization view.
This was because the `flexibleCollections` was set to `true`
Found an issue with loading some old created Secure Notes which had `{}` or `{"type":null}` as there `data` value.
This isn't allowed. When detected, replace it with `{"type":0}`
Fixes dani-garcia#4682
Fixes dani-garcia#4590
Subject of the issue
Collections tree in the filters box does not show all collections after upgrading to latest testing. (Maybe related to the latest PascalCase changes?)
Deployment environment
Install method: Docker Compose
Clients used:
Web vault
Reverse proxy and version:
Nginx Proxy Manager with SSL
Steps to reproduce
Expected behaviour
Collections tree should load under the filters section.
Example screenshot, where it shows collections do exists but do not show up in the collections tree on the left.
The text was updated successfully, but these errors were encountered: