This is done without any notice/message/warning to User2 or User1.
The changes that User2 made overwrites the changes that User1 made. User2 shouldn't be able to open and/or save their changes because User1 already had FileA open Actual behaviour User 2 edits FileA and saves (which updates through WebDav).User 1 edits FileA and saves (which updates through WebDav).This issue has been brought up (independently) time and time again by our customers, so it's a much sought after feature from our client base. Our main use would be through webdav however, it would probably be necessary to honor the lock in the web interface and possibly also the sync client. I'm aware this has been discussed pretty heavily in the OC github, but I was hoping the opinion may be different in NC. It would be really nice to have true file locking in NC, such that opening a file prevents editing/opening by a second user until closed.
0 kommentar(er)
