I have a mail reply from an official Nextcloud representative that the sync client does sync MS Office lock files (~$*) . I checked in my NC folder (in a shared subfolder successfully made availabe via groupfolders) and there is a lock file for a document I am working on, which wasn’t synced on macOS (can’t check other OSes).
I deleted the respective entry in the global ignore list in the sync client (so it seemingly was ignored out-of-the-box) which made the lock file available online and in the synced folder.
Unfortunately, despite the lock file being there now, MS Office didn’t open the document read-only from another test computer. This works without problems in our local network with our NAS, I have no idea why this is so difficult.
I don’t want to have my people explicitly lock a file or have them call up eachother informing them not to edit file XYZ.
Are there any new findings at the moment? We are currently having a law firm review our move into the M365 world. Oh wonder! This is not possible in a legally compliant way if you want to get any benefit from the functions in the end. In our area (consulting), we are not allowed to store almost anything in the cloud, so there is no real benefit. We are still on NC27 because of the lack of OCR support in the newer versions. Has anything changed in terms of filelocking?
I was struggling to get locking files from LibreOffice or Microsoft Office to work as well. What fixed it on multiple Windows and Linux devices was to reinstall the nextcloud client. Now we get the lock from local office software and collabora.
Has anyone managed to get it working? I am evaluating Nextcloud for potential move from ownCloud and neither of them have working locking.
My Nextcloud is freshly installed by AIO, version 31.0.0, Temporary files lock is installed. I tried opening a shared MS Word document on two Windows 11 24H2 computers with client version 3.16.0, virtual files disabled, and it did not work. Office on the other computer did not open the file in read-only mode and was able to make changes to the document. Which then caused a conflict on the first computer while the document was still open by both.
Sorry I can’t add something meaningful, but I want to clarify:
I wrote about Transactional File Locking in my initial post. It was not my intention for this thread. Intention of this thread is that office files should be locked (read only) for other users once someone starts editing (web or desktop).
@aprochazka was also asking about this, not about transactional file locking.
From
“What Transactional File locking is not for: it will not prevent multiple users from editing the same document, or give notice that other users are working on the same document. Multiple users can open and edit a file at the same time and Transactional File locking does not prevent this. Rather, it prevents simultaneous file saving.”
