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

Closed
opened 2026-04-06 01:34:18 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jb2barrels on 6/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.
image

*Originally created by @jb2barrels on 6/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. ![image](https://github.com/dani-garcia/vaultwarden/assets/129100561/8b8bcaa5-628d-49fc-99e7-2d17abb1bb26)
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1079