The changelog of 6.3.7 mentions that the force-save feature in OnlyOffice has been removed again.
I truly hope this feature will return (but fixed I guess?) since it’s an important function to be user-friendly towards casual users of the software.
The bug is caused by the OnlyOffice side.
If you enable force-save and the user save a file manually, then another user open the file, the two users will work on different versions of the file. The one saved will overwrite the other.
Until the bug is fixed in OnlyOffice, the current best practice is let the user close the file to force the file be saved.
I see, the only problem with that is that the file is not saved until ALL users close the file and that can be very confusing behavior. I hope this will become a “normal” situation one day where a user can save the file or discard all changes. Just like on the desktop, although that will probably never happen
Thanks for information, can you please share link to OnlyOffice issue about this problem?
The problem had been fixed by changing the way to call OnlyOffice in Seafile and config OnlyOffice properly. 7.0.5 version contains the fix.
You can find more information here: https://download.seafile.com/published/seafile-manual/deploy/only_office.md
Thanks, this works well! Before I configure Onlyoffice via this manual https://seafile.readthedocs.io/en/latest/installation/office/onlyoffice/ but it miss this feature!
Is there any way to force enable Onlyoffice CoAuthoring “autoAssembly” option by default, without manually change it after each restart?
Maybe you can ask in OnlyOffice’s forum.
Thanks, I got answer from OnlyOffice developers here ONLYOFFICE - ONLYOFFICE community :
You can create a new config file with this parameter inside the container /etc/onlyoffice/documentserver/ local-production-linux.json and mount it on host
Will be good to describe this in Seafile manual.