Re: [tor-bugs] #30869 [Internal Services/Service - nextcloud]: [Nextcloud] Feedback re: collaborative document editing

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#30869: [Nextcloud] Feedback re: collaborative document editing
-------------------------------------------------+-------------------------
 Reporter:  alsmith                              |          Owner:
                                                 |  nextcloud-admin@…
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Service -          |        Version:
  nextcloud                                      |
 Severity:  Normal                               |     Resolution:
 Keywords:  nextcloud, migration                 |  Actual Points:
Parent ID:  #29415                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by micah):

 Replying to [comment:2 arma]:
 > Replying to [comment:1 alsmith]:
 > > Another issue I'm noticing: When I download a document (.xlxs and
 .docx so far) from NextCloud, I get a many-days-old version of the
 document instead of what is in the collaborative editing version of the
 document.
 >
 > Oh hey, I saw an issue with nc.riseup.net that matches this behavior:
 Gaba pointed me to an xlsx hosted there, and the online version worked
 (after spending a few minutes loading), but the downloaded version was
 just a blank xlsx file. I was confused, but maybe it was giving me the
 many-days-old version, i.e. back when it first started.

 The way this works, as is detailed in the wiki page, is as follows:

 The Onlyoffice document server copies the document from nextcloud, so
 while the document is "open" it will differ from the version stored in
 nextcloud (that is, is if someone tries to download from nextcloud she
 will see a different version).

 The document is only stored back in nextcloud after all editing sessions
 have finished. That means that while there's a session open (either active
 or idle) the versions will differ, and if either the document server or
 the connection between nextcloud and document server break for some reason
 it is possible that there will be data loss.

 There is a setting for expiring idle sessions after a certain amount of
 time. This helps making sure the document will not hang indefinitely in
 the document server if someone leaves a tab open. We are using 15 minutes.

 Many days old is much older than it should be, and I have not been able to
 reproduce this. Can you provide me with an example when you see it so I
 can investigate?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30869#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs