Skip to content
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

Closed
christoph-bessei opened this issue Nov 12, 2017 · 13 comments
Closed

Comments

@christoph-bessei
Copy link

christoph-bessei commented Nov 12, 2017

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.

@informatico-madrid
Copy link

+1

@tavinus
Copy link
Contributor

tavinus commented Dec 23, 2017

+1 as well

This would completely change how onlyoffice operates, but I think it would be better.
Versioning would also benefit a lot from this, since we would have more versions saved (right?).

@KuenzelIT
Copy link

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.

@e-tagirov
Copy link

+1

@y0va
Copy link

y0va commented Jun 15, 2018

+1

@IwishIcanFLighT
Copy link

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.

@KuenzelIT
Copy link

I also vote for auto saving every x seconds or minutes!

@fmkaiser
Copy link

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:

capture_001_22082018_180846

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?

@AFrancani
Copy link

+1

1 similar comment
@hostingnuggets
Copy link

👍

@IwishIcanFLighT
Copy link

@fmkaiser Thanks for this workaround. A real auto-save would still be ideal though.

@J4RF
Copy link

J4RF commented Aug 10, 2020

+1 for automatically writing the document server's cached changes to the backend file at regular intervals

@LinneyS
Copy link
Member

LinneyS commented Sep 29, 2020

Hi all!
Try Keep intermediate versions when editing in settings in v6.0.1

@LinneyS LinneyS closed this as completed Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.