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

File changes are shown in OnlyOffice but don't appear in Files app #12

Open
rnwgnr opened this issue Jan 18, 2020 · 256 comments
Open

File changes are shown in OnlyOffice but don't appear in Files app #12

rnwgnr opened this issue Jan 18, 2020 · 256 comments
Labels
bug Something isn't working

Comments

@rnwgnr
Copy link

rnwgnr commented Jan 18, 2020

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

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:

  • The timestamp of the file does not change.
  • When downloading the file, the changes are lost.

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.

@KopfKrieg
Copy link

I just want to add it also happens with PostgreSQL as database (and redis as cache).

@pkmkrishnakumar-zz
Copy link

pkmkrishnakumar-zz commented Jan 21, 2020

This happens in Document Server_Community version: 0.1.2
Similar to others, I too have same issue of not saving the document, but changes reflects in onlyoffice alone. But its been saved few minutes after inactive session .

And if the document is being collaborated, sessions of the users are not terminated even if the user closes the window or onlyoffice.
I hope the problem is hiding in termination of session. If the session is closed, document will be saved automatically. So we need to have an icon or some thing like that to close the session when closing the window or closing onlyoffice. And we need force save option as in onlyoffice

And the requirement is file has to be saved if the current user / last collaborated user closes their window.

@apg1980
Copy link

apg1980 commented Jan 22, 2020

I can confirm this issue as well.
I can edit and watch the changes in the web interface.
But no file sync is initated and no files version is created as well the timestamp did not change.
Nextcloud running on ubuntu 18.04, php7.3fpm, latest postgresql.
This error comes up several times in an hour:
{"reqId":"J8CAcxdnyyTHiHMCF2qE","level":3,"time":"2020-01-22T08:20:43+01:00","remoteAddr":"","user":"--","app":"documentserver_community","method":"","url":"--","message":{"Exception":"OCA\\DocumentServer\\Document\\DocumentConversionException","Message":"save_code: d.rb.ua,La,d.Me,e.Document)})}null!=d.fa&&(this.memory.va(Ai.fa),this.ra.Dk(function(){e.Epb(d,a,!0,c)}))};this.Epb=function(d,a,c,z){var h=0,Ga=d.fa.length-1;if(1==a&&(h=d.Selection.xa,Ga=d.Selection.ya,h>Ga)){var f=Ga;Ga=h;h=f}0>Ga&&(Ga=0);0>h&&(h=0);f=d.fa;for(var La=this;h<=Ga&&h<f.length;++h){var n=f[h];switch(n.ka){case $f:var r=n.Ym();ff!==r?it(r,n.Qv(),function(d,a,c,e){oh===d?a.ewa()?d=Ai.Qca:(d=Ai.Pya,c=!0):d=a.zpa()?Ai.Mfa:Ai.mza;La.ra.ta(d,function(){gB(La.ra,La.bq.Qja++,a,{UE:function(){e(c)}})})},\nsave: Uncaught TypeError: Cannot read property 'ua' of null\nDoctRenderer:<result><error code=\"save\" /></result>\n","Code":0,"Trace":[{"file":"/var/www/nextcloud/apps/documentserver_community/lib/DocumentConverter.php","line":123,"function":"run","class":"OCA\\DocumentServer\\Document\\ConverterBinary","type":"->","args":["/NEXTCLOUD-DATA/nextcloud-tmp/oc_tmp_q6UGwN-.xml"]},{"file":"/var/www/nextcloud/apps/documentserver_community/lib/DocumentConverter.php","line":78,"function":"runCommand","class":"OCA\\DocumentServer\\DocumentConverter","type":"->","args":[{"__class__":"OCA\\DocumentServer\\Document\\ConvertCommand"}]},{"file":"/var/www/nextcloud/apps/documentserver_community/lib/Document/DocumentStore.php","line":168,"function":"saveChanges","class":"OCA\\DocumentServer\\DocumentConverter","type":"->","args":["/NEXTCLOUD-DATA/data/appdata_ocl353ioyjno/documentserver_community/doc_4198266707",["38;CgAAADEAXwA1ADcANAABABwAAQAAAAUAAAACAAAAAAAAAAMAAAA=","26;CgAAADEAXwA1ADcANAACABwAAAAAAAAAAAA=","78;AgAAADEA//8BAF/X5hsU5QEAOQEAAAIAAAAGAAAABgAAAAYAAAAdAAAAHQAAABwAAAA1AC4ANAAuADIALgA0ADYALgBAAEAAUgBlAHYA"],"/NEXTCLOUD-DATA/data/appdata_ocl353ioyjno/documentserver_community/doc_4198266707/saved.docx","docx"]},{"file":"/var/www/nextcloud/apps/documentserver_community/lib/Document/SaveHandler.php","line":56,"function":"saveChanges","class":"OCA\\DocumentServer\\Document\\DocumentStore","type":"->","args":[4198266707,[{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"},{"__class__":"OCA\\DocumentServer\\Document\\Change"}]]},{"file":"/var/www/nextcloud/apps/documentserver_community/lib/BackgroundJob/Cleanup.php","line":69,"function":"flushChanges","class":"OCA\\DocumentServer\\Document\\SaveHandler","type":"->","args":[4198266707]},{"file":"/var/www/nextcloud/lib/public/BackgroundJob/Job.php","line":79,"function":"run","class":"OCA\\DocumentServer\\BackgroundJob\\Cleanup","type":"->","args":[null]},{"file":"/var/www/nextcloud/cron.php","line":125,"function":"execute","class":"OCP\\BackgroundJob\\Job","type":"->","args":[{"__class__":"OC\\BackgroundJob\\JobList"},{"__class__":"OC\\Log"}]}],"File":"/var/www/nextcloud/apps/documentserver_community/lib/Document/ConverterBinary.php","Line":56,"CustomMessage":"Error while applying changes for document 4198266707"},"userAgent":"--","version":"18.0.0.10","id":"5e27f8380f4c6"}

@Digiseb
Copy link

Digiseb commented Jan 23, 2020

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?

@hendrikreimers
Copy link

Can confirm it too, Ubuntu 18.04 different instances.

@dheule
Copy link

dheule commented Jan 24, 2020

same here, Gentoo x86_64, MariaDB, updated instance ...

@nursoda
Copy link

nursoda commented Jan 25, 2020

same here, NC18release on current Arch, NGINX, mariadb, documentserver 0.1.3, onlyoffice 4.1.2:

  • click on .odt (file opens in onlyoffice/communityeditionserver), edit it, press "x" to close app, all fine
  • reload files page, timestamp of just edited file is old
  • reopen file in onlyoffice: recent modifications are there
  • download file and open in libreoffice: recent modifications are NOT there

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.

@nonplusnl
Copy link

Same bug -- Upgraded Nextcloud18 on Ubuntu 18.04
However, I notice that when I leave the browser tab with Onlyoffice in it sitting there, it appears to autosave every half hour or so. File gets written to disk with updated timestamp at :00 and :30 when changes are made in the meantime.
So it appears, for me at least, that I cannot save manually ('Save' icon greyed out), and closing OnlyOffice loses changes. But waiting until scheduled :00/:30 autosave works?!

@ostasevych
Copy link

Same bug -- Upgraded Nextcloud18 on Ubuntu 18.04
However, I notice that when I leave the browser tab with Onlyoffice in it sitting there, it appears to autosave every half hour or so. File gets written to disk with updated timestamp at :00 and :30 when changes are made in the meantime.
So it appears, for me at least, that I cannot save manually ('Save' icon greyed out), and closing OnlyOffice loses changes. But waiting until scheduled :00/:30 autosave works?!

As a temporary solution you may uncheck Autosave. However, it should be fixed somewhere... Maybe this 30 minutes delay is hard coded somehwhere?...

image

@apg1980
Copy link

apg1980 commented Jan 29, 2020

i can confirm that the saving behaviour in 0.1.4 is working quite better.
file is saved after view seconds automatically.
if you have disabled autosave in 0.1.3, the feature is set enabled after updating to 0.1.4.

@nursoda
Copy link

nursoda commented Jan 29, 2020

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?
Edit: No change in respect to the "not saved timely" after update to 0.1.5 for me.

@dasunsrule32
Copy link

I'm on 0.1.5 with the same issue, can't use it since I don't know it will save or not.

@apg1980
Copy link

apg1980 commented Jan 31, 2020

Ok, i think i figured it out. Changes will be written to nextcloud after the next nextcloud cronjob was compleately run.

@dasunsrule32
Copy link

dasunsrule32 commented Jan 31, 2020

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.

@nursoda
Copy link

nursoda commented Jan 31, 2020

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).

@dasunsrule32
Copy link

dasunsrule32 commented Jan 31, 2020

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.

@chrstn-hntschl
Copy link

chrstn-hntschl commented Feb 4, 2020

Related issues: #55, #53

@rnwgnr
Copy link
Author

rnwgnr commented Feb 4, 2020

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.

@googol42
Copy link

googol42 commented Feb 6, 2020

What works for my nextcloud instance is a cron job with

 *        *    *    *     *     php -f /var/www/yourdomain/occ documentserver:flush

But I would consider this just as a workaround...

EDIT: see #12 (comment)

@HugoPrinz
Copy link

@googol42: Good idea/workaround. Could you share an example how this would look like in my cron.php? I hope I'm making sense.

@googol42
Copy link

googol42 commented Feb 10, 2020

@HugoPrinz this has nothing to do with the cron.php. I added an additional cronjob to execute the php file occ. See https://docs.nextcloud.com/server/18/admin_manual/configuration_server/occ_command.html

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.

@HugoPrinz
Copy link

@googol42 Thanks for sharing. I'll look into this.

@tjareson
Copy link

tjareson commented Feb 18, 2020

Same problem here, using the nextcloud 18.0.1 docker image with integrated community server. 0.1.5 on ubuntu 16.04 server.
The issue renders the onlyoffice integration kind of useless, as people getting totally confused that they edit the document, but then download an empty file, as it never gets build and replicated back into the file space of nextcloud. Still if they open in nextcloud, onlyoffice is showing them all changes...
If I look into the container I can see all the temp directories in the appdata with all the Editor.bin files relating to the files which are edited.
Does anyone know how I can force to process them?
I also see the topic that if I open and leave a document several times in the same session, it counts up and show that several users are working on the document, but it is always my account.

@tjareson
Copy link

I've used the cron job from @googol42 as well, and looks like working quite reliable so far.
But in my case I had to implement it on the docker host, as somehow I couldn't get cron to work properly in the nextcloud container.

          • root /* * * * * root /usr/bin/docker exec -t containername sudo -u www-data php occ documentserver:flush

@tjareson
Copy link

@HugoPrinz this has nothing to do with the cron.php. I added an additional cronjob to execute the php file occ. See https://docs.nextcloud.com/server/18/admin_manual/configuration_server/occ_command.html

However, I had this cronjob active for some time, but it only helped somewhat... to put it in a nutshell: I still have data losses.
@googol42 Are you aware of specific situations where you see changes not saved even with the cron job? (Just to be warned what better not to do...)

@googol42
Copy link

@tjareson no, I don't have any further information :(

@tjareson
Copy link

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.
So the workaround is a bit limited...

@Digiseb
Copy link

Digiseb commented Feb 24, 2020

Start begining Problems with the Cronjob Workarround. Cronjob ist blocket by this one of Errorcode..

In ConverterBinary.php line 64:
namespace error : Namespace prefix wp14 on sizeRelH is not defined
now, compleat Workarround is broken maybe about one corrupt file in the Line..?

@francks-git
Copy link

Here is the version installed :
snap_2022-04-30_05-36-59
What's yours ?

@bastiencyr
Copy link

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.

@francks-git
Copy link

Thank's for the infos.
No cool* file in the whole nexcloud sub-directories :-/
Yes, collabora installation through Applications is really straight forward.
Default xlsx and docx features seem useful enough.
But, I think I am going away from the subject of this thread ;)

@kawasumi2019
Copy link

My NC + OO server had the same problem as this issue, but I was able to solve it.
In my case, the situation was very similar to this issue (ONLYOFFICE/DocumentServer#1521).
The cause of this issue was the name of the user agent used by NextCloud.

"NextCloud Server Crawler"

My Apache server prohibits access using UAs with keywords such as "Crawler" or "Bot".
As a result, internal access was always 404 error when trying to save as a file.
Therefore, I solved it by adding the condition "%{REMOTE_ADDR} is not local IP address".
I hope this information helps someone.

@saumsaum
Copy link

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.
Nextcloud 23
Community Document Server 0.1.12
ONLYOFFICE 7.4.4

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:
<m_bFromChanges xsi:nil="true"/>

However, when I click "Save" or use autosave, the XML file contains this line:
<m_bFromChanges>true</m_bFromChanges>

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.
Before:
"m_bFromChanges" => "fromChanges",
After:
/* "m_bFromChanges" => "fromChanges", */

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.

@Svampebob1
Copy link

Therefore, as workaround, in file apps/documentserver_community/lib/Document/ConvertCommand.php, I commented line 101.
Before:
"m_bFromChanges" => "fromChanges",
After:
/* "m_bFromChanges" => "fromChanges", */

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

@mrbaseman
Copy link

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.

@cpot
Copy link

cpot commented Dec 8, 2022

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

@kintaro1981
Copy link

Same problem here. 👎
I'm on Storage Share from Hetzner

I really want to runaway from Google Drive but with this issue I can't trust Nextcloud. 😞

@arnowelzel
Copy link

Same problem here. 👎 I'm on Storage Share from Hetzner

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.

@kintaro1981
Copy link

Why a dockerized Onlyoffice works and not the integrated one?

I can see that there are bugs reported in onlyoffice repository too, example:
ONLYOFFICE/onlyoffice-nextcloud#660

@arnowelzel
Copy link

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.).

@kintaro1981
Copy link

@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?

@arnowelzel
Copy link

@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":

  1. Install the OnlyOffice document server as docker container as described in https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx
  2. Install and configure the integration app in Nextcloud: https://apps.nextcloud.com/apps/onlyoffice

@kintaro1981
Copy link

Understood thank you for the clarification.

I have another question:
What stops Community Document Server to get fixed about this issue?
It only needs more "love" from NC developers?
I think this is a huge issue for "Family NC users" that search for an all in one alternative to finally leave "BigCorp" suites.

@arnowelzel
Copy link

arnowelzel commented May 13, 2023

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.

@kintaro1981
Copy link

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.

@arnowelzel
Copy link

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

@ferdiga
Copy link

ferdiga commented May 13, 2023

I had a discussion with Hetzner if they would offer a "click and run" collabora server together with nextcloud. apparently there is no demand.
It's easy to set up a collabora docker but the configuration is/was a bit of a hassle especially after or if the collabora config requirements were changed.
IMO the typical hardware requirements for a docker collabora server for family and SME use are low and could be provided.
I assume most people would prefer to spend a few € on a SAAS solution.

@arnowelzel
Copy link

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.

@ogmkp
Copy link

ogmkp commented Nov 1, 2023

Is this issue still occurs ?

@ferdiga
Copy link

ferdiga commented Nov 3, 2023

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.

@pallebone
Copy link

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.

@ferdiga
Copy link

ferdiga commented Nov 4, 2023

that's the main (and crucial) reason why I am not using this app

@kintaro1981
Copy link

kintaro1981 commented Apr 7, 2024

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:
#318 (comment)

the only problem is that modified date/time of files in the client filesystem is not the same as in nextcloud server

@ostasevych
Copy link

ostasevych commented Apr 7, 2024

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.

This is done through cron service. So, potentially you may try to decrease it to 1 mins.
Of course, in case of realtime collaboration the changes in UI are observed immediately.

the only problem is that modified date/time of files in the client filesystem is not the same as in nextcloud server

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 ?

@dodancs
Copy link

dodancs commented Sep 25, 2024

I have recently came across this exact issue.
Nextcloud: 29.0.7 (docker / production-apache)
Onlyoffice: 7.5 up to 8.1
Onlyoffice app: 9.4.0

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:

==> /var/log/onlyoffice/documentserver/converter/out.log <==
[2024-09-25T19:52:58.018] [INFO] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - Start Task

==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2024-09-25T19:52:58.032] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - AddTask saveFromChanges

==> /var/log/onlyoffice/documentserver/converter/out.log <==
[2024-09-25T19:52:58.038] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - downloadFileFromStorage list 1954134065/Editor.bin,1954134065/output.txt
[2024-09-25T19:52:58.040] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - downloadFileFromStorage complete
[2024-09-25T19:52:58.040] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - downloadFileFromStorage list
[2024-09-25T19:52:58.056] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - processChanges end
[2024-09-25T19:52:58.818] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - stdout:
[2024-09-25T19:52:58.818] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - stderr:
[2024-09-25T19:52:58.818] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - ExitCode (code=0;signal=null;error:0)
[2024-09-25T19:52:58.822] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - processUploadToStorageChunk path=1954134065_6709/changes.zip; sha256=37060b9d2567667e2a856e50c3a260b8ea6e2087151deca5ad103db44c7ca7f4
[2024-09-25T19:52:58.822] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - processUploadToStorageChunk path=1954134065_6709/changesHistory.json; sha256=855ccb1d7d4c29e32130482dc9d70a67cf6ee7e5b1dcde89ce96ef8355bc49c1
[2024-09-25T19:52:58.822] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - processUploadToStorageChunk path=1954134065_6709/output.xlsx; sha256=566fbd7f36901525789d9936e62c5b09e3f06b6ed3202bcd53a40beb95dc273d
[2024-09-25T19:52:58.825] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - processUploadToStorage complete
[2024-09-25T19:52:58.825] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - output (data={"ctx":{"tenant":"localhost","docId":"1954134065","userId":"oc7f8of1z1om_example1","shardKey":"1954134065"},"cmd":{"wopiParams":null,"c":"sfc","id":"1954134065","userid":"oc7f8of1z1om_example","userindex":1,"data":null,"title":"output.xlsx","outputformat":257,"outputpath":"output.xlsx","status_info":0,"savekey":"1954134065_6709","jsonparams":{"documentLayout":{"openedAt":1727301144223}},"lcid":9,"useractionid":"oc7f8of1z1om_example","useractionindex":1,"nobase64":true,"status_info_in":3172963,"originformat":257}})
[2024-09-25T19:52:58.825] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - postProcess
[2024-09-25T19:52:58.826] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - deleteFolderRecursive
[2024-09-25T19:52:58.827] [INFO] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - End Task

==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2024-09-25T19:52:58.829] [INFO] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - receiveTask start: {"ctx":{"tenant":"localhost","docId":"1954134065","userId":"oc7f8of1z1om_example1","shardKey":"1954134065"},"cmd":{"wopiParams":null,"c":"sfc","id":"1954134065","userid":"oc7f8of1z1om_example","userindex":1,"data":null,"title":"output.xlsx","outputformat":257,"outputpath":"output.xlsx","status_info":0,"savekey":"1954134065_6709","jsonparams":{"documentLayout":{"openedAt":1727301144223}},"lcid":9,"useractionid":"oc7f8of1z1om_example","useractionindex":1,"nobase64":true,"status_info_in":3172963,"originformat":257}}
[2024-09-25T19:52:58.841] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - Start commandSfcCallback
[2024-09-25T19:52:58.842] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - getCallbackByUserIndex: userIndex = 1 callbacks = {"userIndex":1,"callback":"http://nextcloud/apps/onlyoffice/track?doc=XYZ"}
[2024-09-25T19:52:58.842] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - Callback commandSfcCallback: callback = http://nextcloud/apps/onlyoffice/track?doc=XYZ
[2024-09-25T19:52:58.844] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - commandSfcCallback forgotten no empty: isSendHistory = false
[2024-09-25T19:52:58.844] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - commandSfcCallback presence: count = 0
[2024-09-25T19:52:58.861] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - postData request: url = http://nextcloud/apps/onlyoffice/track?doc=XYZ;data = {"key":"1954134065","status":2,"url":"http://oon.example.com/cache/files/data/1954134065_6709/output.xlsx/output.xlsx?md5=XYZ&expires=1727294879&shardkey=1954134065&filename=output.xlsx","history":{},"users":["oc7f8of1z1om_example"],"actions":[{"type":0,"userid":"oc7f8of1z1om_example"}],"lastsave":"2024-09-25T19:52:43.000Z","notmodified":false,"filetype":"xlsx"}

==> /var/log/onlyoffice/documentserver/converter/out.log <==
[2024-09-25T19:52:58.870] [INFO] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - ackTask addResponse
[2024-09-25T19:52:58.870] [INFO] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - ackTask ack

==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2024-09-25T19:52:59.008] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - postData response: data = {"error":1}
[2024-09-25T19:52:59.008] [WARN] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - sendServerRequest returned an error: data = {"error":1}
[2024-09-25T19:52:59.008] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - commandSfcCallback restore 7 status
[2024-09-25T19:52:59.064] [WARN] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - storeForgotten
[2024-09-25T19:52:59.071] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - getCallbackByUserIndex: userIndex = 1 callbacks = {"userIndex":1,"callback":"http://nextcloud/apps/onlyoffice/track?doc=XYZ"}
[2024-09-25T19:52:59.110] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - cleanupCacheIf db.affectedRows=1
[2024-09-25T19:52:59.110] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - storeForgotten cleanupRes=true
[2024-09-25T19:52:59.110] [DEBUG] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - End commandSfcCallback
[2024-09-25T19:52:59.111] [INFO] [localhost] [1954134065] [oc7f8of1z1om_example1] nodeJS - receiveTask end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests