mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #1920] No attachment Upload from within Organization possible #1106
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#1106
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 @derdrave on GitHub (Aug 18, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1920
Hi,
first of all: Great product and I love using it. Many thanks for all the work you put into this project.
Recently (since Version 1.22) I have a specific problem with attachment-uploads from within organization from browser:
Browser: recent / up to current date Chrome or Firefox (even Nightly)
OS: Windows / Linux / OS X (I think it doesn't matter)
Working Case
debug-log for the working case :
The problematic case
a) in Chrome: cannot read property 'id' of null
b) in Firefox: s is null
debug-log for the problematic case:
The Vaultwarden LOG_LEVEL debug does not show anything useful, but maybe the popup-hints are already leading into a good direction?
I would be grateful for help/a fix if possible.
@BlackDex commented on GitHub (Aug 18, 2021):
I can confirm, via the Org tab it fails, via the My Vault tab it works.
@wcdgit commented on GitHub (Aug 18, 2021):
I can confirm the described behaviour. Even with a fresh docker install of version 1.22.2. The bug is db independent - I tested postgres, mariadb and sqlite.
Version 1.21.0 does not have this problem.
@BlackDex commented on GitHub (Aug 18, 2021):
Looks like there is a change in the API.