mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Item moves between collections requiring manual sync #1594
Reference in New Issue
Block a user
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 @AlmightyJojo on GitHub (May 19, 2023).
Subject of the issue
Item moves between collections requiring manual sync
Deployment environment
Server Installed = 1.28.1
Web Installed = 2023.3.0b
Database = SQLite: 3.39.2
OS/Arch = linux / x86_64
Running within Docker = Yes (Base: Debian)
Environment settings overridden = Yes
Uses a reverse proxy = Yes
IP header Match = Config/Server: X-Real-IP
Websockets enabled and functional.
Single Org deployment. Org's users personal Vaults disabled.
Collections with group permissions.
Local deployment. No Inet.
Install method: Docker Compose - Debian 11
Clients used: Web, Firefox Extension, Windows Desktop app
Reverse proxy and version: Nginx Proxy Manager 2.10.1
Steps to reproduce
Windows desktop client: Existing item in collection A. Move item from collection A to collection B
Firefox extension: Unlock vault and view collection B. Item not present. Settings - sync vault now. Review Collection B. Item now present.
docker-compose up -d
Expected behavior
Items to automatically sync between collection moves. Not requiring manual sync.
Item adds / deletes, edits of item sync / updating immediately. Would like collection moves to do same.
Example:
Windows desktop client: Existing item in collection A. Move item from collection A to collection B
Firefox extension: Unlock vault and view collection B. Item moved is immediately present.
Actual behavior
Windows desktop client: Existing item in collection A. Move item from collection A to collection B
Firefox extension: Unlock vault and view collection B. Item not present. Settings - sync vault now. Review Collection B. Item now present.
@BlackDex commented on GitHub (May 25, 2023):
I have solved the issue via #3546