New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write to own-/nextcloud on save and/or interval of X seconds/minutes #116
Comments
+1 |
+1 as well This would completely change how onlyoffice operates, but I think it would be better. |
We also have this problem in our organization, since everyone expects "saving" to be a save of the file to the owncloud server, so that you get the "current" version of the file when downloading. |
+1 |
+1 |
Would appreciate this as well. Depending on the usage, a file could remain opened on a editor for hours or even days. This could lead to versioning missing several iterations of a document which is not ideal. Although saving a new version every time a change is made would lead to hundreds of versions on nextcloud which would be counterproductive. An ideal approach would be to autosave the file every x seconds/minutes (could be an admin setting) even if the file is still opened somewhere. |
I also vote for auto saving every x seconds or minutes! |
Until forcesave is solved properly I think I might have found a feasible workaround, namely the sessionidle option in the documentserver default.json. Setting this to e.g. 60m disconnects idle sessions afer an hour, with the users getting a message: When there's no more sessions, the document will be saved back to ownCloud. Assuming our users aren't working around the clock, that should make sure that documents are saved back after a finite amount of time, probably at least during the night. As a bonus, this also saves some licenses. @LinneyS What do you think, is that a viable option or could it cause problems in other places? |
+1 |
1 similar comment
👍 |
@fmkaiser Thanks for this workaround. A real auto-save would still be ideal though. |
+1 for automatically writing the document server's cached changes to the backend file at regular intervals |
Hi all! |
Currently onlyoffice writes a changed file to owncoud10-30 seconds after ALL editors closed the file.
Is there a possibility that onlyoffice triggers this write every X seconds (if a change occurred)? This would avoid sync problems if someone forgets to close the file, which is a problem if another client is changing the file with the owncloud desktop/mobile client.
The text was updated successfully, but these errors were encountered: