mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #6648] Bug: Web UI crashes when creating organization passwordManagerPlans is undefined #2497
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2497
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @junet-1 on GitHub (Jan 1, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6648
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ORG_CREATION_USERS
Config:
Vaultwarden Build Version
1.35.1
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
traefik 3.6
Host/Server Operating System
Linux
Operating System Version
Docker Image
Clients
Web Vault
Client Version
No response
Steps To Reproduce
To Reproduce
Expected Result
The organization should be created successfully, or the UI should show a proper validation/permission error.
Actual Result
The Web UI crashes during submit with a JavaScript runtime error:
TypeError: can't access property "find",
this.passwordManagerPlans is undefined
Org not being created
Logs
Screenshots or Videos
Additional Context
No response
@BlackDex commented on GitHub (Jan 1, 2026):
You didn't searched closed issues
#6638
#6644
#6645
@pictosun commented on GitHub (Jan 2, 2026):
But why closing the issues, when the bug is still within actual version? Isn't it confusing for people searching for that bug?
@stefan0xC commented on GitHub (Jan 2, 2026):
Because it's an already addressed issue in the code base. So there's nothing to track anymore. The issue tracker is not a support forum. You can use discussions for that.
Also I'm not sure what's confusing about searching both open and closed issues. When I search for the error message GitHub also tells me that there are closed issues: