i have faced an issue with Seafile webdav (Seafdav) when i use Seafile Version 11 after upgrade.
The issue is the follow:
In Windows file explorer i have successful a Webdav drive over https to the Seafile server. So seafdav is enabled, we can see all folders. When i upload some files like pdf or simple text files i get a error “…file is to big…” and i have 0 Bytes files in the folder.
When i downgrade to Seafile Version 10 again no problems at all. Everything works fine then.
We use Sefafile docker community.
It seems that wsgidav added some checks in version 4.3, which caused your issue.
We have also conducted tests, and it seems that this issue only occurs when connecting to seafdav using Windows File Explorer. Other WebDAV clients do not encounter this problem.
We will conduct further debugging and submit an issue to wsgidav project to see if they can resolve this problem.
thats very bad news because we cannot use Seafile with Windows file explorer anymore. Using a connector is not a solution because when someone has open an excel sheet then this excel sheet is not locked for other users that open that excel sheet at the same time! Finally they get an iconsistent excel…
So that means we cannot use Seafile anymore
The Webdav functionality is the most important feature over years in Seafile! Many user of us use Seafile Webdav with native Windows file explorer.
So can you tell me how long it takes to fix that issue?