Documentserver: Unexpected behaviour causing data loss

[putt1ck]

A user opens a file from Nextcloud; edits the file; sees the file is saved and tells a colleague the file is updated so they can send the file to the customer. But the file is not updated (not saved in user speak) because they understand the file's location as being in the project folder on the company Nextcloud.

The expected behaviour when the file is "saved" is that it is saved in the location from which they opened it. Telling users that what they understood as "save" no longer means what they think it means, and the only way to save in their terms is to make all users with the document open close it, and then wait 10 seconds.

A prima facie simple fix for this would be that the current "saved" messaging is changed to "updated" (works for both users only working in OnlyOffice and those using separate file stores) and a save button added that writes the file back to the location it was opened from (or saves the file as most users understand the concept). The existing write back 10 seconds after all editor windows are closed can be retained for continuity and as a failsafe.

This bug is present in all versions of DocumentServer when used with Nextcloud (and presumably is the same issue for any use with a remote file store).

[putt1ck]

Relates to https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/257

[mvvvmd]

We have found this to be a problem for our users also. They expect auto saving to mean the file in the Nextcloud folder is updated with the latest changes. Even when the document is still open. Some kind of change as described above could work to resolve this for sure.