[Bug] Latest testing, collections do not load (Related to PascalCase changes?) #5593

New Issue

Closed

opened 2026-03-07 20:30:58 -06:00 by GiteaMirror · 8 comments

GiteaMirror commented 2026-03-07 20:30:58 -06:00

Owner

Copy Link

Originally created by @jb2barrels on GitHub (Jun 27, 2024).

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

• vaultwarden version: testing (Latest) - As of June 27 2024

• 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.

Originally created by @jb2barrels on GitHub (Jun 27, 2024). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> 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 <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: testing (Latest) - As of June 27 2024 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker Compose * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Web vault * Reverse proxy and version: <!-- if applicable --> Nginx Proxy Manager with SSL ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> 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. 

GiteaMirror closed this issue 2026-03-07 20:30:58 -06:00

GiteaMirror commented 2026-03-07 20:30:59 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Jun 27, 2024):

Probably related to #4681, but could be something different.

@BlackDex commented on GitHub (Jun 27, 2024): Probably related to #4681, but could be something different.

GiteaMirror commented 2026-03-07 20:30:59 -06:00

Author

Owner

Copy Link

@stefan0xC commented on GitHub (Jun 27, 2024):

It also happens on vault.bitwarden.com so this probably unrelated to vaultwarden (might even be intentional).
cf. https://github.com/bitwarden/clients/issues/9823

@stefan0xC commented on GitHub (Jun 27, 2024): It also happens on vault.bitwarden.com so this probably unrelated to vaultwarden (might even be intentional). cf. https://github.com/bitwarden/clients/issues/9823

GiteaMirror commented 2026-03-07 20:30:59 -06:00

Author

Owner

Copy Link

@jb2barrels commented on GitHub (Jun 27, 2024):

It also happens on vault.bitwarden.com so this probably unrelated to vaultwarden (might even be intentional). cf. bitwarden/clients#9823

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):
8f05a90b96

So it seems the admin collections issue crept in on vaultwarden between June 23rd - June 24th.
I don't see a web vault update between those dates, so I do wonder if the above is a coincidence or some recent change that was somewhat copied over from Bitwarden into Vaultwarden.

@jb2barrels commented on GitHub (Jun 27, 2024): > It also happens on vault.bitwarden.com so this probably unrelated to vaultwarden (might even be intentional). cf. [bitwarden/clients#9823](https://github.com/bitwarden/clients/issues/9823) 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): https://github.com/dani-garcia/vaultwarden/commit/8f05a90b96adfe06722d01510923759fe61a8bd6 So it seems the admin collections issue crept in on vaultwarden between June 23rd - June 24th. I don't see a web vault update between those dates, so I do wonder if the above is a coincidence or some recent change that was somewhat copied over from Bitwarden into Vaultwarden.

GiteaMirror commented 2026-03-07 20:31:00 -06:00

Author

Owner

Copy Link

@stefan0xC commented on GitHub (Jun 28, 2024):

seems like this setting is responsible for the behavior: a4c7fadbf4/src/db/models/organization.rs (L409)

@stefan0xC commented on GitHub (Jun 28, 2024): seems like this setting is responsible for the behavior: https://github.com/dani-garcia/vaultwarden/blob/a4c7fadbf4ffa242fb78ebd152080028e7f2993c/src/db/models/organization.rs#L409

GiteaMirror commented 2026-03-07 20:31:00 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Jun 28, 2024):

Ah, we can set that back to false for now. And add flex/v2 later.

@BlackDex commented on GitHub (Jun 28, 2024): Ah, we can set that back to false for now. And add flex/v2 later.

GiteaMirror commented 2026-03-07 20:31:00 -06:00

Author

Owner

Copy Link

@stefan0xC commented on GitHub (Jun 28, 2024):

Ah, we can set that back to false for now. And add flex/v2 later.

I don't think those two are that related (like I said https://github.com/dani-garcia/bw_web_builds/pull/169#issuecomment-2185324417 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)

• Implement Custom User Permissions
• Deprecate Manager role and write migration to set new "can manage" permission over assigned collections.
• Deprecate "Access All" Flag and write migration to apply "can manage" permission to all collections.
• Add new /api/organizations/<org_uuid>/collections/bulk-access endpoint for new bulk collection assignment
• Support option to limit creation/deletion of collections to owners/admins.
• Adapt the collections_v2 endpoint to return "unvailable": true if the cipher becomes unavailable due to changed permissions. (edit: Or rather this might be missing from my PR. I have not really looked at it that deeply.)

@stefan0xC commented on GitHub (Jun 28, 2024): > Ah, we can set that back to false for now. And add flex/v2 later. I don't think those two are that related (like I said https://github.com/dani-garcia/bw_web_builds/pull/169#issuecomment-2185324417 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) - [ ] Implement Custom User Permissions - [ ] Deprecate Manager role and write migration to set new "can manage" permission over assigned collections. - [ ] Deprecate "Access All" Flag and write migration to apply "can manage" permission to all collections. - [ ] Add new `/api/organizations/<org_uuid>/collections/bulk-access` endpoint for new bulk collection assignment - [ ] Support option to limit creation/deletion of collections to owners/admins. - [ ] Adapt the `collections_v2` endpoint to return `"unvailable": true` if the cipher becomes unavailable due to changed permissions. (edit: Or rather this might be missing from my PR. I have not really looked at it that deeply.)

GiteaMirror commented 2026-03-07 20:31:00 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Jun 28, 2024):

Oef. That sounds to me like a Backup your database first before update situation.

@BlackDex commented on GitHub (Jun 28, 2024): Oef. That sounds to me like a **Backup your database first before update** situation.

GiteaMirror commented 2026-03-07 20:31:01 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Jun 28, 2024):

I created a PR to fix this specific issue, and a small issue i found with the new native app. #4685

@BlackDex commented on GitHub (Jun 28, 2024): I created a PR to fix this specific issue, and a small issue i found with the new native app. #4685

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#5593