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

rnwgnr commented 4 years ago

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 commented 4 years ago

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

pkmkrishnakumar-zz commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Can confirm it too, Ubuntu 18.04 different instances.

dheule commented 4 years ago

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

nursoda commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

apg1980 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

dasunsrule32 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Related issues: #55, #53

rnwgnr commented 4 years ago

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 commented 4 years ago

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 https://github.com/nextcloud/documentserver_community/issues/12#issuecomment-584148660

HugoPrinz commented 4 years ago

@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 commented 4 years ago

@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 commented 4 years ago

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

tjareson commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@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 commented 4 years ago

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

tjareson commented 4 years ago

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 commented 4 years ago

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

q-wertz commented 4 years ago

found this in the original DocumentServer Issues: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/55 and https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/54#issuecomment-304230708

rnwgnr commented 4 years ago

Looks like there are a bunch of issues regarding this topic, some more the 2 years old: https://github.com/ONLYOFFICE/onlyoffice-owncloud/issues/27 https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/122 https://github.com/nextcloud/activity/issues/391 https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/241

Eisteed commented 4 years ago

Got some similar errors with latest version of nextcloud & document server community (on centos 7) Tried to execute the cron job command proposed by @googol42

In ConverterBinary.php line 64:
namespace error : Namespace prefix wp14 on sizeRelH is not defined
  /drawingml/2006/main"/></wp:cNvGraphicFramePr><wp14:sizeRelH relativeFrom="page"
                                                                                 ^
  namespace error : Namespace prefix wp14 on pctWidth is not defined
  /main"/></wp:cNvGraphicFramePr><wp14:sizeRelH relativeFrom="page"><wp14:pctWidth
                                                                                 ^
  namespace error : Namespace prefix wp14 on sizeRelV is not defined
  p14:pctWidth>0</wp14:pctWidth></wp14:sizeRelH><wp14:sizeRelV relativeFrom="page"
                                                                                 ^
  namespace error : Namespace prefix wp14 on pctHeight is not defined
  wp14:pctWidth></wp14:sizeRelH><wp14:sizeRelV relativeFrom="page"><wp14:pctHeight

                                                                          ^

OnlyOffice seems to be working as expected anyway now, but it's strange and I still had some similar problem (if not the same as op). Some days ago one document was never opening (loading forever) and some data were lost (document was empty when downloaded) then the data of the document came back insides a few hours/days later, I can't find any logs related to this error... (and no error message when loading forever) :/ and cannot reproduce it now x)..

Luxamman commented 4 years ago

Yes same as #77 I think

Repeat:

ONLYOFFICE in Nextcloud works fine, saves the changes to the (in the browser) opened file, I can reopen it in the browser with the changes made before by ONLYOFFICE in Nextcloud. No problem online/in the browser.

But when I open the same file (synced by the latest client) on the PC with LibreOffice, the file has no changes. So when I save the file in LibreOffice, it's synced back to Nextcloud and overwrites the changes made in ONLYOFFICE.

So the sync is only working from the PC to the cloud, but not from the cloud to the PC.

Hope this will be gone soon to work with that great feature :)

Nextcloud 18.0.1 with Community Document Server 0.1.5 and ONLYOFFICE 4.1.4. Nextcloud Desktop Client Version 2.6.2stable-Win64 (build 20191224)

tjareson commented 4 years ago

The sync from cloud to PC works as well, the problem is between Onlyoffice and nextcloud. Onlyoffice gets the file handed over for edit. All changes are kept by onlyoffice in a temp file called editor.bin The issue is now: when onlyoffice is closed these changes don't get copied back to the file which is shown in nextcloud. That also gets visible in the last modified date in nextcloud. It never changes even if just edited in onlyoffice. Somehow the recognition if every editing session is done, is not working properly. The issue is there for sometime, but looks like no solution available yet.

I solved it by not using the onlyoffice community server anymore, but installing the docker container with collabora (which is a web version of libreoffice). It gets integrated the same way in nextcloud via it's own nextcloud app. It works and all sync problems are gone. Even simultaneous working on the same document always produces a in sync file in nextcloud at any time.

brievenbusalex commented 4 years ago

I have the same problems with syncing the changes from onlyoffice to nextcloud. This happened when I upgraded from Nextcloud 17.0.4 (with my own Onlyoffice docker container)

And changed to:

Nextcloud Hub 18.0.2
Onlyoffice App 4.1.4
Community Document Server 0.1.5

For now I keep running Nextcloud 18.0.2 and re-installed the onlyoffice docker container/image (https://www.onlyoffice.com/nl/download.aspx - onlyoffice 5.4.2.46) and am using that document server URL in the nextcloud Onlyoffice app server settings.

No syncing problems now and No errors in the logfile like:

no namespace error : Namespace prefix wp14 on sizeRelV is not defined

Hope this helps in finding a solution for fixing this.

open7c commented 4 years ago

Is this project dead or what? So many Issues here about this problem, some with an age of 2 month or more - and no solution or feedback from the devs?

Digiseb commented 4 years ago

This is really really depressing .. It was announced and now we are left completely alone after the roll-out, especially now that everyone is looking for a "Not google or MIcrosoft Docs" solution .. no matter where you look, nowhere any reaction to it extreme bug reports. Thats a Gamekiller for Nextcloud ..

tjareson commented 4 years ago

I was wondering about the same and my recommendation is: just use collabora instead of onlyoffice integration. It's also availble as a docker container. The setup took me like 20 minutes.

There is a collabora app in nextcloud which needs the url to the collabora container, so pretty much the same concept, only that it works. The onlyoffice app and community server app I've deactivated and deleted. Here is the how-to I've used (at the end of the page, before is more marketing) https://nextcloud.com/collaboraonline/

PeterBenzin commented 4 years ago

I was wondering about the same and my recommendation is: just use collabora instead of onlyoffice integration. It's also availble as a docker container. The setup took me like 20 minutes.

There is a collabora app in nextcloud which needs the url to the collabora container, so pretty much the same concept, only that it works. The onlyoffice app and community server app I've deactivated and deleted. Here is the how-to I've used (at the end of the page, before is more marketing) https://nextcloud.com/collaboraonline/

Is that an option on shared hosting then?

brievenbusalex commented 4 years ago

See my earlier comment. I re-tested after upgrading to Nextcloud 18.0.3. I can now easily switch between my own installed document server (docker container) and the Nextcloud Community Document Server 0.1.5.

Situation Onlyoffice with the Nextcloud Community Document Server 0.1.5: If I edit a document in Onlyoffice with the Nextcloud Community Document Server 0.1.5. and exit Onlyoffice the change (a new version of the document) is not really saved to Nextcloud. I you open the document again the changes are visible (read again from cache in the document server I think). It's easy to check if you have a Nextcloud client active on a Windows 10 environment for example, the changed document is not synchronized -> so no new version in Nextcloud server.

Situation Onlyoffice with own installed (docker container) Document Server If I edit a document in Onlyoffice with my own Document Server (onlyoffice 5.4.2.46). and exit Onlyoffice the change (a new version of the document) is immediately saved to Nextcloud. I checked in my Nextcloud client active on a Windows 10 environment -> the changed document is synchronized 'near realtime' -> so there is a new version in Nextcloud server.

So the question is, what makes the difference between those two installations of an Onlyoffice Document Server?

tjareson commented 4 years ago

Is that an option on shared hosting then?

Not sure what you mean by shared hosting?

KopfKrieg commented 4 years ago

Is that an option on shared hosting then?

To answer your question: Yes it is. I have a single Collabora container running for three Nextcloud instances (2x v17, 1x v18), and it's running fine. There is a limitation, though. 10 concurrent users is the current limit if I'm not mistaken. It's possible to change the limit, or just deploy more containers, whatever you prefer.

rnwgnr commented 4 years ago

Please stick the conversation to the topic of this issue. This is not the right place to discuss alternative deployments, i guess https://help.nextcloud.com would be the place to go.

I anyone has digged deeper into this can provice additional information i'd be gracefully add that to the opening post.

Despite that i'm somewhat disappointed about the lack of attention after the "big reveal" a few weeks ago. I'm afraid about this project becoming a similar failure as the much proposed "Social" app which had a big announcement back then and is still far away from being usable and development stopped completely.

fantast7 commented 4 years ago

I guess it could have to do with the callback url api: https://api.onlyoffice.com/editors/callback

Any ideas, how to check it?

mmr-code commented 4 years ago

Got the same behaviour with the latest docker-compose deployment. Cronjob also does not save the changes from OnlyOffice to Nextcloud.

bunjes commented 4 years ago

Same problem here. We were happy to use the built-in OnlyOffice after upgrading nextcloud to v18 but now it seems, we have to switch back to our separate OnlyOffice container vm. That's disappointing. (Note: after pulling the latest onlyoffice docker image, the not-flushing document changes to nextcloud issue has re-appeared)

open7c commented 4 years ago

2,5 months later and there is still not a fix or something.

In the meantime people are complaining that problem in comments at many Heise articles regarding online collaboration tools.

PeterBenzin commented 4 years ago

2,5 months later and there is still not a fix or something.

In the meantime people are complaining that problem in comments at many Heise articles regarding online collaboration tools.

That's sad. How can this issue be assigned to a product owner?

hendrikreimers commented 4 years ago

I have send Nextcloud a message directly over the contact form on their website. And i've send them the link to this issue too. Hope they will show a reaction and a solution soon.

b3nis commented 4 years ago

I have the same issue. Lost data already. I really hope they can prioritize this issue.

biva commented 4 years ago

Hello all, I guess the main place to discuss this issue with the dev is https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/21 with a specific explanation here: https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/21#issuecomment-568745636

[edit] I was wrong, it's apparently a NC issue, not an ONLYOFFICE issue (https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/21#issuecomment-607822941)

nextcloud / documentserver_community

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

How to use GitHub

Steps to reproduce