File locking in/for desktop client - what is the current status?

spikusmax · October 18, 2024, 7:06am

Hello,

I’m implementing NextCloud for a small organisation as the migrate away from Office365. Currently a mixed environment but eventually will be Mac only.

For a range of reasons they prefer to use the desktop file sync rather than the web interface.

I’ve come across an issue where people are able to open documents that another user has open. The result is a whoever saves last wins.

So far my Googling tells me that the issue of file locking is a long one with several variations (depending on if a file is opened from the web-ui/locally, and edited locally or in the web UI)

I’m just wondering if anyone can tell me if, in theory, for NextCloud (28.0.11) and the Desktop Client (Mac 3.14.1): should the client be locking files on NextCloud when opened locally, and respecting file locks (i.e. opening in read only mode) set by the Desktop Client?

Many thanks,

Spike

tflidd · October 22, 2024, 8:06am

It seems that they have implemented something recently:

github.com/nextcloud/desktop

Please implement locking on macOS-vfs builds

opened 10:34AM - 30 Apr 24 UTC

closed 07:51AM - 12 Sep 24 UTC

marcotrevisan

enhancement os:

macOS feature:

virtual filesystem feature: locking

Please implement locking on macOS-vfs builds. Client version 3.13.0-macOS-vfs… is missing the lock and unlock behaviour. In my humble opinion this feature should be a top level item in the list of the next things to implement for Mac OS VFS. My idea of the functionality, for it to be useful, would be: 1. "lock on Office file open" and "unlock on Office file close". Feel free to remove the "Office" word from the previous sentences. 2. Have a context menu item in Finder to manually lock and unlock. 3. Show a lock icon on a locked file, along with the lock owner username (or maybe the first X characters of it...) decorating the file name in Finder, highlighted with some color if possible. If the username is not easy to show, a tooltip may do! Please don't underestimate this point: a clearly visible and highlighted lock information will be spotted by the user **before** opening the file, and there will be less need for a custom popup on file open, like other popular vendors do. 4. Also show the locker username in the context menu as a first level citizen. 5. (Perhaps unnecessary if point 3 is implemented) For Office files: have a custom popup on file open warning the user that the file is locked. A subsequent popup should then arise when the file is unlocked... this also implies making the file writable again and reopening it. @claucambra it may seem much stuff but points 1..4 are very important in my humble opinion, and points 1-2 are essential. Thanks!

However, you have to lock and unlock files manually.

But that is just reading through the bug tracker, I have no hands on experience with the mac clients.