-
Notifications
You must be signed in to change notification settings - Fork 29
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
File changes are shown in OnlyOffice but don't appear in Files app #12
Comments
I just want to add it also happens with PostgreSQL as database (and redis as cache). |
This happens in Document Server_Community version: 0.1.2 And if the document is being collaborated, sessions of the users are not terminated even if the user closes the window or onlyoffice. And the requirement is file has to be saved if the current user / last collaborated user closes their window. |
I can confirm this issue as well. |
I also have this bug on three different Nextcloud instances, a completely fresh new installation, two upgrade versions. All on Ubuntu server 18.04. Program cannot be used. Are there already solutions here? |
Can confirm it too, Ubuntu 18.04 different instances. |
same here, Gentoo x86_64, MariaDB, updated instance ... |
same here, NC18release on current Arch, NGINX, mariadb, documentserver 0.1.3, onlyoffice 4.1.2:
Edit: Next day (!) the file timestamp has been updated and changes are visible to synced files also. New changes are not saved to the file to file but cached in OO again. Sidenote: "Convert using Onlyoffice" (from 3dot-menu) gives me "Bad response: Start tag expected, '<' not found" Edit: → This has been fixed in 0.1.4, at least for me it's working now: e.g. applying "Convert using Onlyoffice' on a .otd creates a .docx. |
Same bug -- Upgraded Nextcloud18 on Ubuntu 18.04 |
As a temporary solution you may uncheck Autosave. However, it should be fixed somewhere... Maybe this 30 minutes delay is hard coded somehwhere?... |
i can confirm that the saving behaviour in 0.1.4 is working quite better. |
Can't confirm that saving is any better. Still takes minutes at least until changes are visible via files app / webdav. But according to my (non-systematic) observations, it's not necessary to keep the Onlyoffice app open for the file to be saved. It just takes (way too much) time. Is that a conceptual issue? |
I'm on 0.1.5 with the same issue, can't use it since I don't know it will save or not. |
Ok, i think i figured it out. Changes will be written to nextcloud after the next nextcloud cronjob was compleately run. |
This is where a hybrid background job mode between Cron and Ajax would be nice I suppose and then giving things like the document server the highest priority when it comes to Ajax. That way your files would always be up to date. 5+ minutes isn't good enough for saving of docs from the document server to nextcloud. |
Triggering a mini-'save-this-document'-Ajax-Job would be sufficient. It doesn't have to be a full cron job after closing a document. But I definitely consider it a bug that changes are not saved upon Document/OnlyOffice-app-close if "real cron" is configured (which is recommended). |
Right, that's what I was leaning towards. I haven't looked at the nextcloud source, so I don't know exactly what would need to be done without looking into things. I would prefer that job to run after every change in a document like Google Docs. Just having that revision history would be great. |
This issue has been confirmed multiple times by now, there are 3 different issues reporting this behaviour. Any kind of feedback from the devs would be nice, the DocumentServer community is unusable due to unintended data loss. |
What
EDIT: see #12 (comment) |
@googol42: Good idea/workaround. Could you share an example how this would look like in my cron.php? I hope I'm making sense. |
@HugoPrinz this has nothing to do with the However, I had this cronjob active for some time, but it only helped somewhat... I deactivated it again, because suddenly saw errors I did not see before. Furthermore I did not find any documentation what this is supposed to do. I just tried it. I still have data losses btw. |
@googol42 Thanks for sharing. I'll look into this. |
Same problem here, using the nextcloud 18.0.1 docker image with integrated community server. 0.1.5 on ubuntu 16.04 server. |
I've used the cron job from @googol42 as well, and looks like working quite reliable so far.
|
|
@tjareson no, I don't have any further information :( |
We have just noticed issues with the cron job workaround, if more than one user/session is editing the document. It can happen then that only the things which were edited/inserted by the second user/session remains in the document and everything previous is gone. |
Start begining Problems with the Cronjob Workarround. Cronjob ist blocket by this one of Errorcode.. In ConverterBinary.php line 64: |
I have the version 21.11.4.1.1 of COOLWSD . But I don't have the built in version of collabora, I set up the server with docker. I had to configure the server in the settings file coolwsd.xml : https://sdk.collaboraonline.com/docs/installation/Configuration.html#user-interface-settings . The new UI is not set by default. Maybe there is a PR somewhere in NC github to include the new UI in the built in app. The settings file is in /etc/coolwsd in a classical installation but for the built in server I don't know if it is even possible. The built in version of office app in NC are limited, they have been designed to be easy to set up. |
Thank's for the infos. |
My NC + OO server had the same problem as this issue, but I was able to solve it. "NextCloud Server Crawler" My Apache server prohibits access using UAs with keywords such as "Crawler" or "Bot". |
I'm not sure if this is the right place to post - if not, please ignore... On my installation, I tracked down the issue and was able to fix it. When I open a document, I can do "Save copy" or "Download as" - this actually works. But autosave on exit didn't work; even manual save didn't work when autosave was turned off. I figured out that in the latter case "x2t" binary segfaulted. x2t is a binary which obviously converts a document to .docx, .odt and so on. To run x2t, a temporary XML file is created that specifies source and destination files and some parameters. When I use "Save copy" or "Download as", the XML file contains this line: However, when I click "Save" or use autosave, the XML file contains this line: The former works, the latter makes x2t segfault. So it seems that x2t has some problems when this "m_bFromChanges" tag is set. However, for my use case it doesn't seem to be important, so I modified the way the XML file is written. Therefore, as workaround, in file apps/documentserver_community/lib/Document/ConvertCommand.php, I commented line 101. Then it works - at least for me. Actually it would be better to fix the bug in x2t, but I can't spend more time on that and I can live with the workaround. I hope that this will help someone else. |
This didn't work for me. I restarted the docker image, just to be sure. This worked for me: docker exec -u www-data php occ documentserver:flush |
In my installation (NC 25.0.1) this change causes that the time stamp of the documents is up to date in the file system, but the changes made in onlyoffice are lost. |
We have also some occurrence (rare but should be none) of document losses with alfresco plugin, obviously bad to keep trust among onlyoffice users see ONLYOFFICE/DocumentServer#1814 |
Same problem here. 👎 I really want to runaway from Google Drive but with this issue I can't trust Nextcloud. 😞 |
This has nothihng to do with Nextcloud - it's just this app which does not work reliable. Switch to a Docker based OnlyOffice server and the integration app or use Nextcloud Office in a Docker container and you are good to go. |
Why a dockerized Onlyoffice works and not the integrated one? I can see that there are bugs reported in onlyoffice repository too, example: |
The issue mentioned at ONLYOFFICE/onlyoffice-nextcloud#660 was fixed and the issue is closed. So feel free to try the Docker version as described at https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx along with the integration app at https://apps.nextcloud.com/apps/onlyoffice. And if you don't trust OnlyOffice at all, you may give Nextcloud Office a try as well - it works also very good and got many improvements over the last 1-2 years (correct display of all apps with HighDPI modes, faster display etc.). |
@arnowelzel sorry I'm a little bit confused. So the issue was fixed on onlyoffice-nextcloud but not in the documentserver_community 0.1.13 that includes an older (7.2.1) version of onlyoffice? am I right? |
@kintaro1981 No - the issue was fixed for the OnlyOffice server by Ascensio. The "Community Document Server" for Nextcloud in this repository is a fork which is not by Ascensio and does not work in the same way as the official version. The repository at https://github.com/ONLYOFFICE/onlyoffice-nextcloud is the "real" OnlyOffice document server created and maintained Ascensio. And this server is usually used either as a Docker container or as a standalone server and with the OnlyOffice integration app which is also by Ascensio. So the "official" and recommended way which works much better then that "Community Document Server":
|
Understood thank you for the clarification. I have another question: |
The situation is a bit complicated. Originally Ascensio and Nextcloud cooperated to improve the OnlyOffice integration app so OnlyOffice could become the preferred default office application for the then new "Nextcloud Hub". The Nextcloud team also wanted to provide a version of OnlyOffice which is easier to install and runs without docker and hoped they will get support by Ascensio for this. Then Ascensio decided to make editing on mobile devices a paid feature and the community version only allows displaying files on mobile devices (also see ONLYOFFICE/DocumentServer#805). This caused a lot of confusion in the community and eventually someone created a fork of the document server which still allows mobile editing - however Ascensio was not very happy about this either. Then we have the situation with the Ukraine and some companies stopped working with Ascensio alltogether, for example: https://dms-solutions.co/blog/dms-solutions-stops-doing-business-with-onlyoffice-due-to-onlyoffice-close-ties-with-russia/ I know that also people from the Nextcloud team don't believe that OnlyOffice will be used a lot in the future and they concentrate their work on Nextcloud Office which is based on Collabora and which is the default office package in the Nextcloud Hub setup since end of 2011. Nextcloud Office also works quite well as an integrated setup similar to the Community Document Server and is actively supported. So the "Community Document Server" ended up as a project which has no priority at all. I also don't think this will ever change. My own pull request to add at least a note in the app description was totally ignored (not even a comment about that why it was not merged): #219 As I see it, this project is dead and just nobody wants to remove the app from the Nextcloud app store. |
Wow now now is more clear. The problem I see here for Nextcloud is that without an integrated all in one document server can’t compete with bigcorp in easy family size installations. And I think that this installations are very important to them make use of NC for work to make NC more profitable. Not all families know how to run a docker (and not all families that know how to run a docker want have more instances to maintain). I know how to run it but I choose Storage Share from Hetzner to not have to invest time in maintaining a little NC instance. NC for this subject needs to understand that people need a “just works” experience without friction or their are going to give up and go back to bigcorp suite. |
As I said: Nextcloud Office is a good alternative to OnlyOffice - that also provides a document server based on Collabora and can be installed as an app without the need for a Docker installation. However for bigger installations a Docker image is also available. Also see my article about this (including some hints for the installation) here: https://arnowelzel.de/en/nextcloud-office |
I had a discussion with Hetzner if they would offer a "click and run" collabora server together with nextcloud. apparently there is no demand. |
There are Nextcloud hosters who also offer Collabora out of the box and I also maintain a number of Nextcloud setups with Collabora myself. When the intial setup is done, the regular maintenance is not that time consuming. |
Is this issue still occurs ? |
I think Only Office saves changes not instantly (neither with and without manual saving) as one would expect, but only after some time. |
Problem is that if someone saves then someone else comes to edit it then potentially changes get lost. |
that's the main (and crucial) reason why I am not using this app |
I tried document server 0.1.16 and it "fixed" for me (NC managed by hetzner - storage share). In my case modifications made in onlyoffice are synced back to nextcloud (windows) clients every 5 minutes, not perfect but better than nothing. take a look here and try: the only problem is that modified date/time of files in the client filesystem is not the same as in nextcloud server |
This is done through cron service. So, potentially you may try to decrease it to 1 mins.
Check your NC locale settings, and the settings at the hoster. PS Meanwhile, have you tried this OO in docker https://hub.docker.com/r/thomisus/onlyoffice-documentserver-unlimited ? |
I have recently came across this exact issue. Whenever I make changes to a document. the changes are present when opened through onlyoffice but when I download the file from Nextcloud or sync it to my PC, it is always the old version of the file without the latest changes. Here are my logs when that happens:
|
How to use GitHub
Steps to reproduce
Nextcloud: 18.0.0 (happens with SQLite and MariaDB Backend) , internal store only.
DocumentServer_Communtiy version: 0.1.1
Still happens 18.0.3 and Document Server 0.1.5
Whenever editing a file in OnlyOffice, the changes are not reflected in the "Files" app:
Nevertheless when opening the file again in OnlyOffice, the changes are there.
I guess OnlyOffice caches the document internally and the changes are not copied back to the users storage folder.
The text was updated successfully, but these errors were encountered: